Hprofile

Deprecated article

This article is deprecated (obsolete). Contents are no longer relevant, and are intended for historical reference only!

TLDR: Do not use this article!

Resources

Home

hprofile is an application that can be used to manage multiple profiles be it hardware or software. The following subsection are just examples on what could be done with hprofile.

Warning
The following subsections were written by the author of this article for hprofile-2.0. hprofile-3.0 has already those profiles in the tarball, so they are installed by default. An ebuild is available here and bug #523448 was made for 3.0 addition in the official tree.

Installation

Emerge

root #emerge --ask sys-apps/hprofile

Hardware profiles

Prelude

Important
The following sections assume that you have a patched hprofile init service. So grab the following init service because the default is too old... and I finished by completely re-writing it.)

FILE hprofile.initd

#!/sbin/openrc-run
# Copyright 1999-2014 Gentoo Foundation
# Distributed under the terms of the 2-clause BSD or GPL-2 license
# $Header: hprofile.initd,v 1.2 2014年08月01日 13:05:23 -tclover Exp $
config_file="/etc/conf.d/${SVCNAME}"
description="initialize hprofile boot profiles"
depend(){
aftermodules
}
start(){
localprofilevalue
forprofilein$HPROFILE;do
value=$(hpdet$profile)
ebegin"Selecting $profile profile $value"
hprofile$profile.$value
eend"$?""Failed to start $profile.$value profile"
done
return0
}
stop(){
localprofile
forprofilein$HPROFILE;do
ebegin"Stoping $profile profile"
hprofile-s$profile
eend"$?""Failed to stop $profile profile"
done
return0
}
# vim:fenc=utf-8:ft=gentoo-init-d:ci:pi:sts=0:sw=4:ts=4:

FILE hprofile.confd

# $Header: hprofile.confd,v 1.2 2014年08月01日 13:05:23 -tclover Exp $
# This variable is a list of profiles to start when starting the service
HPROFILE="vga power"
# vim:fenc=utf-8:ft=gentoo-conf-d:ci:pi:sts=0:sw=4:ts=4:

Note
Every script file `/etc/hprofile/profiles/$profile/{scripts/*,ptest,stop,post-start}' should have the executable bit set. Or else, a peculiar error will rise up.

Power

When thinking about a better way to have dynamic power profiles that could be dynamically switched depending on hardware or software state is not straightforward especially for power management which could depend on many software e.g. sys-power/powertop , sys-apps/hdparm to name a few. So, how could you get hardware profiles and switch between them dynamically? And how to get everything together? How many daemons to start depending on what hardware or software state?

That sum up quite a few considerations to what a user can face when trying to build a nice setup with power management in mind. [S]he can remember of Windows(tm) power management profiles if [s]he ever used it. Or else, [s]he did not thought about it because [s]he used to run a GNU Linux or BSD based distribution with everything putted together and does not know how to begin with if [s]he is not satisfied with what [s]he gets.

Now sys-power/powertop -2 grew up to be quite a good piece of software. If you're running an Intel based platform, you can get access to pretty much everything one would expect if trying to build power profiles. But the package does not ship with a daemon-ish like software nor with a configuration or profile file which PowerTOP could pick up when launched in the next restart. One has to launch it again and again in a terminal and enable power management for every power manageable hardware... quite the redundant an manual way every time the system boot up.

Note
Now PowerTOP shows up the command line executed for each option, it became easy to pick them up and make power management profiles. Although the following is based on Intel hardware, the idea is there to be picked up for AMD hardware power profiles.

This basic profile will try to implement Disk, CPU (see External resources), network interfaces and ALSA drivers power saving capabilities.

One would need the following files to set up basic power management profiles.

FILE /etc/hprofile/profiles/power/profiles

adp
bat
dyn
med
quiet

Note
adp stand for AC adapter, bat for battery, dyn for dynamic (performance profile), med for medium and quiet for quiet of courses.

FILE /etc/hprofile/profiles/power/default

adp

FILE /etc/hprofile/profiles/power/ptest

#!/bin/sh
if[-e"/sys/class/power_supply/A*/online"];then
status=$(cat/sys/class/power_supply/A*/online)
case${status}in
1)profile="adp";;
0)profile="bat";;
esac
fi
echo"${profile:-adp}"
# vim:fenc=utf-8:ci:pi:sts=0:sw=4:ts=4:

Note
This start script is added to ease starting profiles and remove code duplication. So this script should have the executable bit set.

FILE /etc/hprofile/profiles/power/start

#!/bin/sh
# $Id: /etc/hprofile/profiles/power/base-start, 2014年07月31日 -tclover $
CPU=${1:-powersave}
PCI=${2:-auto}
USB=${3:-auto}
HDA=${5:-1}
NMI=${6:-0}
VMW=${7:-1000}
ASPM=${8:-default}
SCSI=${4:-min_power}
forcpuin$(ls-d/sys/devices/system/cpu/cpu[0-9]*);do
echo$CPU>$cpu/cpufreq/scaling_governor
done
[-e/sys/module/pcie_aspm/parameters/policy]&&
echo$ASPM>/sys/module/pcie_aspm/parameters/policy
forscsiin$(ls-d/sys/class/scsi_host/host[0-9]*);do
[-e$scsi/link_power_management_policy]||continue
case$(cat$scsi/proc_name)in
ahci|usb-storage)echo$SCSI>$scsi/link_power_management_policy;;
esac
done
# set usb host to auto powersave
forusbin$(ls-d/sys/bus/usb/devices/{usb[0-9],[0-9]-[0-9]});do
echo$USB>$usb/power/control
done
# pci power control
forpciin$(ls-d/sys/bus/pci/devices/0000:0*);do
echo$PCI>$pci/power/control
done
# snd-hda-intel powersave
[-e/sys/module/snd_hda_intel/parameters/power_save]&&
echo$HDA>/sys/module/snd_hda_intel/parameters/power_save
# turn off NMI watchdog
[-e/proc/sys/kernel/nmi_watchdog]&&
echo$NMI>/proc/sys/kernel/nmi_watchdog
# VM write back timeout
[-e/proc/sys/vm/dirty_writeback_centisecs]&&
echo$VMW>/proc/sys/vm/dirty_writeback_centisecs
# vim:fenc=utf-8:ci:pi:sts=0:sw=4:ts=4:

FILE /etc/hprofile/profiles/power/scripts/adp.start

#!/bin/sh
script=/etc/hprofile/profiles/power/start
$script"powersave""auto""auto""min_power""1""0""default"
hprofiledisk.adp
if[-n"$DISPLAY"];then
xbacklight-set25
xsetdpms300600800
fi
# vim:fenc=utf-8:ci:pi:sts=0:sw=4:ts=4:

FILE /etc/hprofile/profiles/power/scripts/bat.start

#!/bin/sh
script=/etc/hprofile/profiles/power/start
$script"powersave""auto""auto""min_power""1""0""1500""powersave"
hprofiledisk.bat
if[-n"$DISPLAY"];then
p
xbacklight-set20
xsetdpms300400600
fi
# vim:fenc=utf-8:ci:pi:sts=0:sw=4:ts=4:

FILE /etc/hprofile/profiles/power/scripts/dyn.start

#!/bin/sh
script=/etc/hprofile/profiles/power/start
$script"performance""on""on""max_power""0""1""500""performane"
hprofiledisk.dyn
if[-n"$DISPLAY"];then
xbacklight-set35
xsetdpms6008001200
fi
# vim:fenc=utf-8:ci:pi:sts=0:sw=4:ts=4:

FILE /etc/hprofile/profiles/power/scripts/med.start

#!/bin/sh
script=/etc/hprofile/profiles/power/start
$script"performance""on""on""min_power""0""1""500""performance"
hprofiledisk.adp
if[-n"$DISPLAY"];then
xbacklight-set30
xsetdpms450600900
fi
# vim:fenc=utf-8:ci:pi:sts=0:sw=4:ts=4:

FILE /etc/hprofile/profiles/power/scripts/quiet.start

#!/bin/sh
script=/etc/hprofile/profiles/power/start
$script"powersave""auto""auto""min_power""1""0""2500""powersave"
hprofiledisk.quiet
if[-n"$DISPLAY"];then
xbacklight-set20
xsetdpms200400600
fi
# vim:fenc=utf-8:ci:pi:sts=0:sw=4:ts=4:

Note
xset dpms argument unit is second, first for standby, second for suspend and third for off mode. Second, the new version of those scripts toggle almost every scsi host, pci and usb controler to auto power management control. Maybe this behavior is not wanted for some use cases, so edit the scripts for your needs!

I have a /etc/acpi/defaults.sh script that make use of those scripts, at least battery and AC Adapter. Those two power profiles are dynamically switched if AC power is un/plugged. See ACPI article for more info about the acpid default.sh script. It's not enough? Do you want more tunings? Expand the article then!

RFKill

This hardware profile subsection could be beneficial to the previous section, however software RF killing/switching can be quite troublesome which require cold reboot and removing battery/AC power for a few seconds to be able to get back usable wireless (WiFi/Bluetooth) interfaces again. This happen on my Intel GM45 based laptop. Luckily there is a physical switch to kill Bluetooth and WiFi radio.

There's no much consideration for this section, if your hardware support RFKill, add it to your hardware profile!

Note
b prefix stand for Bluetooth, k for kill, w for wan and sw for switch.

FILE /etc/hprofile/profiles/rfkill/ptest

FILE /etc/hprofile/profiles/rfkill/default

Note
The two previous files are intentionally left empty!

FILE /etc/hprofile/profiles/rfkill/profiles

bsw
ksw
wsw

FILE /etc/hprofile/profiles/rfkill/scripts/bsw.start

#!/bin/sh
echo1>/sys/class/rfkill/rfkill1/state
# vim:fenc=utf-8:ft=sh:ci:pi:sts=0:sw=4:ts=4:

FILE /etc/hprofile/profiles/rfkill/scripts/bsw.stop

#!/bin/sh
echo0>/sys/class/rfkill/rfkill1/state
# vim:fenc=utf-8:ft=sh:ci:pi:sts=0:sw=4:ts=4:

FILE /etc/hprofile/profiles/rfkill/scripts/wsw.start

#!/bin/sh
echo1>/sys/class/rfkill/rfkill0/state
echo1>/sys/class/rfkill/rfkill2/state
# vim:fenc=utf-8:ft=sh:ci:pi:sts=0:sw=4:ts=4:

FILE /etc/hprofile/profiles/rfkill/scripts/wsw.stop

#!/bin/sh
echo0>/sys/class/rfkill/rfkill0/state
echo0>/sys/class/rfkill/rfkill2/state
# vim:fenc=utf-8:ft=sh:ci:pi:sts=0:sw=4:ts=4:

FILE /etc/hprofile/profiles/rfkill/scripts/ksw.start

#!/bin/sh
hprofilerfkill.bsw
hprofilerfkill.wsw
# vim:fenc=utf-8:ft=sh:ci:pi:sts=0:sw=4:ts=4:

FILE /etc/hprofile/profiles/rfkill/scripts/ksw.stop

#!/bin/sh
hprofilerfkill.bsw
hprofilerfkill.wsw
# vim:fenc=utf-8:ft=sh:ci:pi:sts=0:sw=4:ts=4:

Note
To determine what RFKill switch is for what, you will have to `cat /sys/class/rfkill/rfkill*/type' to know that. Of course, there are several manner to make this profile as each $profile.st* is just ran to apply a state so each $profile.start and $profile.stop is a profile in its own. So, feel free to expand those to your needs.

VGA

I use sys-apps/hprofile to manage VGA profile to my laptop and my desktop. On my desktop, I use hprofile to switch between nvidia-drivers, nouveau and nv (x11-drivers/xf86-video-nv ) when the previous profiles do no work; and to switch radeon and intel on my laptop which has switchable graphics via VGASwitcheroo. Now I have a new laptop with NVIDIA Optimus, VGASwitcheroo/PRIME does work quite bit avoiding to get a hot potato because that thing has a GT750M GPU! although I have to wait linux-3.16 and Mesa-10.3 to make any use of a GT750M and go through the black screen of death (right, BSOD(tm)).

Just be sure to built kernel modules about everything — at least i915, nouveau, radeon, ttm, drm, and optionally (?) ac, button, video, i2c-algo-bit — to avoid useless hassles and be able to boot with a single kernel be it with vesa/nvidia-drivers, or i915, or nouveau.

Create the necessaries folder /etc/hprofile/profiles/vga/{scripts,files/etc/X11/xorg.conf.d} and add the following files.

Note
Of course, the necessary files should be added for the following profiles, you do not need to copy every single profile related file if you do not have any use of it. Just do not switch to that particular profile with missing files later when using vga profile. Or even better, do not add, or rather remove, those particular profiles from the profile list file.

FILE /etc/hprofile/profiles/vga/profiles

intel
radeon
nvidia
nv
nouveau
fglrx

Note
This is necessary because the console font will be messed whenever a new profile is switched.

FILE /etc/hprofile/profiles/vga/post-start

#!/bin/sh
echo"Finished starting profile ${1}"
/etc/init.d/consolefontrestart
# vim:fenc=utf-8:ft=sh:ci:pi:sts=0:sw=4:ts=4:

FILE /etc/hprofile/profiles/vga/stop

#!/bin/sh
if[-e/sys/kernel/debug/vgaswitcheroo/switch];then
case${1}in
intel|radeon|nouveau)echoON>/sys/kernel/debug/vgaswitcheroo/switch;;
esac
fi
echo"Finished Stopping profile ${1} and moving back xorg.conf"
# vim:fenc=utf-8:ft=sh:ci:pi:sts=0:sw=4:ts=4:

Note
If a specific kernel module is loaded with an initramfs or modules init services, the appropriate profile will be selected with the following script.

FILE /etc/hprofile/profiles/vga/ptest

#!/bin/sh
n=/dev/null
s=/sys/kernel/debug/vgaswitcheroo/switch
if[!-e$s];then
grep-qi915/proc/modules||modprobei915>$n2>&1
grep-qradeon/proc/modules||modproberadeon>$n2>&1
grep-qnouveau/proc/modules||modprobenouveau>$n2>&1
fi
if[-e$s];then
vga=$(grep+$s)
pci=$(sed-nre's/^[0-9].*\+.*[a-zA-Z]:([0-9].*$)/1円/p'$s)
if[-d/sys/bus/pci/drivers/nouveau/$pci];then
drv=nouveau
elif[-d/sys/bus/pci/drivers/radeon/$pci];then
drv=radeon
fi
case$vgain
*:IGD:+*)echo"intel";exit;;
*:DIS:+*)echo"$drv";exit;;
esac
fi
unsetnpcisvga
drv="$(lspci-k|sed-nre's/Kernel driver in use: ((i915|fglrx|radeon|nouveau|nvidia))/1円/p')"
echo"${drv:-invalid}"
# vim:fenc=utf-8:ft=sh:ci:pi:sts=0:sw=4:ts=4:

FILE /etc/hprofile/profiles/vga/scripts/fglrx.start

#!/bin/sh
echo"Starting vga profile to fglrx"
if!modprobefglrx;then
echo"failed to load fglrx module"
exit
fi
["$(eselectopenglshow)"!="ati"]&&eselectopenglsetati
["$(eselectxvmcshow)"!="ati"]&&eselectxvmcsetati
# vim:fenc=utf-8:ft=sh:ci:pi:sts=0:sw=4:ts=4:

FILE /etc/hprofile/profiles/vga/scripts/fglrx.stop

#!/bin/sh
echo"Stopping nvidia profile."
rmmodfglrx||echo"failed to remove fglrx module."&&exit1
# vim:fenc=utf-8:ft=sh:ci:pi:sts=0:sw=4:ts=4:

FILE /etc/hprofile/profiles/vga/scripts/intel.start

#!/bin/sh
echo"Starting intel vga profile"
modprobei915||exit$?
if[-e/sys/kernel/debug/vgaswitcheroo/switch];then
echoIGD>/sys/kernel/debug/vgaswitcheroo/switch&&
echoOFF>/sys/kernel/debug/vgaswitcheroo/switch
fi
["$(eselectopenglshow)"!="xorg-x11"]&&eselectopenglsetxorg-x11
["$(eselectxvmcshow)"!="intel-i915/i965"]&&eselectxvmcset'intel-i915/i965'
# vim:fenc=utf-8:ft=sh:ci:pi:sts=0:sw=4:ts=4:

FILE /etc/hprofile/profiles/vga/scripts/nouveau.start

#!/bin/sh
echo"Starting nouveau vga profile"
modprobenouveau||exit$?
if[-e/sys/kernel/debug/vgaswitcheroo/switch];then
echoDIS>/sys/kernel/debug/vgaswitcheroo/switch
#	echo OFF >/sys/kernel/debug/vgaswitcheroo/switch
fi
["$(eselectopenglshow)"!="xorg-x11"]&&eselectopenglsetxorg-x11
["$(eselectxvmcshow)"!="xorg-x11"]&&eselectopenglsetxorg-x11
# vim:fenc=utf-8:ft=sh:ci:pi:sts=0:sw=4:ts=4:

FILE /etc/hprofile/profiles/vga/scripts/nouveau.stop

#!/bin/sh
echo"Stopping nouveau vga profile"
# uncomment the following line and last one if one need
# to force remove nouveau/kms driver for e.g. nvidia
if[!-esys/kernel/debug/vgaswitcheroo/switch];then
echo0>/sys/class/vtconsole/vtcon1/bind
if!rmmodnouveau;then
echo"failed to remove nouveau module"
else
/etc/init.d/consolefontrestart
rmmodttm
rmmoddrm_kms_helper
rmmoddri
fi
fi
# vim:fenc=utf-8:ft=sh:ci:pi:sts=0:sw=4:ts=4:

FILE /etc/hprofile/profiles/vga/scripts/radeon.start

#!/bin/sh
echo"Starting radeon vga profile"
modproberadeon||exit$?
if[-e/sys/kernel/debug/vgaswitcheroo/switch];then
echoDIS>/sys/kernel/debug/vgaswitcheroo/switch
#	echo OFF >/sys/kernel/debug/vgaswitcheroo/switch
fi
echolow>/sys/class/drm/card0/device/power_profile
["$(eselectopenglshow)"!="xorg-x11"]&&eselectopenglsetxorg-x11
["$(eselectxvmcshow)"!="xorg-x11"]&&eselectxvmcsetxorg-x11
echoprofile>/sys/class/drm/card0/device/power_method# or 'dynpm'
echoauto>/sys/class/drm/card0/device/power_profile# or 'low|mid'
# vim:fenc=utf-8:ft=sh:ci:pi:sts=0:sw=4:ts=4:

FILE /etc/hprofile/profiles/vga/scripts/radeon.stop

#!/bin/sh
echo"Stopping fglrx vga profile."
# uncomment the following line and last one if one need
# to force remove nouveau/kms driver for e.g. fglrx
if[!-esys/kernel/debug/vgaswitcheroo/switch];then
#	echo 0 >/sys/class/vtconsole/vtcon1/bind
if!rmmodnouveau;then
echo"failed to remove fglrx module"
else
/etc/init.d/consolefontrestart
#		rmmod ttm
#		rmmod drm_kms_helper
#		rmmod dri
fi
fi
# vim:fenc=utf-8:ft=sh:ci:pi:sts=0:sw=4:ts=4:

FILE /etc/hprofile/profiles/vga/scripts/nvidia.start

#!/bin/sh
echo"Starting nvidia vga profile"
if!modprobenvidia;then
echo"failed to load nvidia module"
exit$?
fi
["$(eselectopenglshow)"!="nvidia"]&&eselectopenglsetnvidia
# vim:fenc=utf-8:ft=sh:ci:pi:sts=0:sw=4:ts=4:

FILE /etc/hprofile/profiles/vga/scripts/nvidia.stop

#!/bin/sh
echo"Stopping nvidia vga profile"
if!rmmodnvidia;then
ret=$?
echo"failed to remove nvidia module"
exit$?
fi
# vim:fenc=utf-8:ft=sh:ci:pi:sts=0:sw=4:ts=4:

FILE /etc/hprofile/profiles/vga/files/etc/X11/xorg.conf.d/40-monitor.conf.fglrx

Section "Monitor"
	Identifier "Default"
EndSection
Section "Device"
	Identifier "ATI"
	Driver "fglrx"
EndSection
Section "Screen"
	Identifier "FGLRX"
	Device "ATI"
	Monitor "Default"
EndSection

FILE /etc/hprofile/profiles/vga/files/etc/X11/xorg.conf.d/40-monitor.conf.intel

Section "Monitor"
	Identifier "Default"
EndSection
Section "Device"
	Option "DRI" "True"
	Option "XvMCSurfaces" "6"
	Identifier "GMAX"
	Driver "intel"
EndSection
Section "Screen"
	Identifier "INTEL"
	Device "GMAX"
	Monitor "Default"
EndSection

FILE /etc/hprofile/profiles/vga/files/etc/X11/xorg.conf.d/40-monitor.conf.nouveau

Section "Monitor"
 Identifier "Default"
EndSection
Section "Device"
 Option "EXAVsync" "True"
 Option "GLXVBlank" "True"
 Identifier "nVidia"
 Driver "nouveau"
EndSection
Section "Screen"
 Identifier "NOUVEAU"
 Device "nVidia"
 Monitor "Default"
EndSection

FILE /etc/hprofile/profiles/vga/files/etc/X11/xorg.conf.d/40-monitor.conf.nvidia

Section "Monitor"
 Identifier "Default"
EndSection
Section "Device"
 Option "AddARGBGLXVisuals" "on"
 Option "NoLogo"
 Identifier "nVidia"
 Driver "nvidia"
EndSection
Section "Screen"
 Identifier "NVIDIA"
 Device "nVidia"
 Monitor "Default"
EndSection

FILE /etc/hprofile/profiles/vga/files/etc/X11/xorg.conf.d/40-monitor.conf.radeon

Section "Monitor"
	Identifier "Default"
EndSection
Section "Device"
	Option "AccelMethod" "EXA"
	Option "ClockGating" "On"
	Option "ForceLowPowerMode" "On"
	Option "VGAAccess" "On"
	Identifier "RadeonHD"
	Driver "radeon"
	Option	 "MonitorLayout" "LVDS, AUTO"
EndSection
Section "Screen"
	Identifier "RADEON"
	Device "RadeonHD"
	Monitor "Default"
EndSection

And with that, you should be able to switch vga profile as you like without needing an extra kernel and setup. Just close your X session and type hprofile vga.$profile ENTER.

The ptest script will just look if VGASwitcheroo (Intel HD Graphics/AMD ATI Radeon hybrid graphics) or PRIME (Intel HD Graphicss/NVIDIA Optimus) is available and which driver is loaded and then start the appropriate profile. One can black list modules and leave the other un-black listed to be able to chose ...a default VGA profile. Or else, use of /etc/hprofile/profiles/vga/default file.

FILE /etc/hprofile/profiles/vga/default

intel

Warning
This hardware profile shall be used out of X server by killing, if necessary, X server or display manager or desktop environment or windows manager session or even all of them.

Note
Notice that two lines should be commented out in nouveau.stop and/or radeon.stop to force remove radeon/nouveau and ttm,kms... drivers to be able to load nvidia or fglrx driver.

Hard disk

A disk profile is even straightforward because there fewer issue to keep in mind. So this section will be short and straightforward. Additionally, one need sys-apps/hdparm .

Note
/etc/hprofile/profiles/disk/{ata,usb} should have the executable bit set, this is just a little helper to make the profiles less blind at applying disk power management.

FILE /etc/hprofile/profiles/disk/default

adp

FILE /etc/hprofile/profiles/disk/ata

#!/bin/sh
echo"$(ls-d/sys/devices/pci*/*/ata*/host*/target*/*/block/sd[a-z]2>/dev/null)"
# vim:fenc=utf-8:ft=sh:ci:pi:sts=0:sw=4:ts=4:

FILE /etc/hprofile/profiles/disk/usb

#!/bin/sh
fordevin$(ls-d/sys/devices/pci*/*/usb*/*/*/host*/target*/*/block/sd[a-z]2>/dev/null)
do
echonoop>$dev/queue/scheduler
done
# vim:fenc=utf-8:ft=sh:ci:pi:sts=0:sw=4:ts=4:

FILE /etc/hprofile/profiles/disk/post-start

#!/bin/sh
fordevin$(/etc/hprofile/profiles/disk/ata);do
echocfq>$dev/queue/scheduler
echo0>$dev/queue/iosched/slice_idle
echo64>$dev/queue/iosched/quantum
# more opitmizations with ncq
echo1024>$dev/queue/nr_requests
echo2>$dev/device/queue_depth
done
# vim:fenc=utf-8:ft=sh:ci:pi:sts=0:sw=4:ts=4:

FILE /etc/hprofile/profiles/disk/ptest

#!/bin/sh
echo"adp"
# vim:fenc=utf-8:ft=sh:ci:pi:sts=0:sw=4:ts=4:

FILE /etc/hprofil/profiles/disk/profiles

bat
adp
dyn
quiet

FILE /etc/hprofile/profiles/disk/stop

#!/bin/sh
ata="$(/etc/hprofile/profiles/disk/ata)"
[-n"$ata"]&&hdparm-q-S120-B254-M254$ata
# vim:fenc=utf-8:ft=sh:ci:pi:sts=0:sw=4:ts=4:

FILE /etc/hprofile/profiles/disk/scripts/adp.start

#!/bin/sh
/etc/hprofile/profiles/disk/usb
ata="$(/etc/hprofile/profiles/disk/ata)"
[-n"$ata"]&&hdparm-q-S120-B230-M254$ata

FILE /etc/hprofile/profiles/disk/scripts/bat.start

#!/bin/sh
/etc/hprofile/profiles/disk/usb
ata="$(/etc/hprofile/profiles/disk/ata)"
[-n"$ata"]&&hdparm-q-S120-B210-M230$ata

FILE /etc/hprofile/profiles/disk/scripts/dyn.start

#!/bin/sh
/etc/hprofile/profiles/disk/usb
ata="$(/etc/hprofile/profiles/disk/ata)"
[-n"$ata"]&&hdparm-q-S180-B254-M254$ata

FILE /etc/hprofile/profiles/disk/scripts/quiet.start

#!/bin/sh
/etc/hprofile/profiles/disk/usb
ata="$(/etc/hprofile/profiles/disk/ata)"
[-n"$ata"]&&hdparm-q-S120-B200-M200$ata

Important
When using this hardware profile, you do not obviously need any extra hdparm init service, setting up dynamically hard disk profiles is more than sufficient. Or else, edit it to your needs. So remove hdparm service with rc-update if need be.

External resources

New profiles with hprofile v3.0+ can be found in this repository.

Aknowledgments

tokiclover