You are not logged in.
Right after boot:
sudo hdparm -B /dev/sdb
/dev/sdb:
APM_level = 254I didn't change anything with this setting but after waking up from suspend it is:
sudo hdparm -B /dev/sdb
/dev/sdb:
APM_level = 96Not a big problem but kind of annoying. I would expect it to stay the way it was before suspend. I don't have lmt or pm-utils installed. I have tlp installed though, but its systemd services are disabled.
Do you have any tips on where to look for the one who changes values?
I put at button on it. Yes. I wish to press it, but I'm not sure what will happen if I do. (Gune | Titan A.E.)
Offline
For whatever it is worth, I'm used to setting it again after resuming on my netbook (in which a drive otherwise goes to sleep after 5 seconds of inactivity). I guess laptop-mode-tools and tlp do this for you, you could also make systemd-sleep run it.
Last edited by lucke (2015-01-07 21:52:33)
Offline
I have tlp installed though, but its systemd services are disabled.
Then enable the services, they are necessary.
Offline
They are necessary to use TLP. But if I disable them TLP should not have any effect on the apm_level of the disk.
I am not trying to find out how to use tlp. I am wondering why the disk's apm_level is changed when suspending to ram.
I put at button on it. Yes. I wish to press it, but I'm not sure what will happen if I do. (Gune | Titan A.E.)
Offline
Hypothesis 1: HDD power supply is cut upon suspend --> the hardware forgets the APM settings; what you see is the hw default
Hypothesis 2: BIOS applies the shown setting on resume
Anyway: why not let TLP do the correct setting upon resume?
Offline