Comment 463 for bug 59695

> Nothing seems to be working in hardy where it worked in gutsy.
> so i am still entering hdparm -B 254 /dev/sda manually after each resume
> from suspend or hibernate.

There are limitations to the /etc/pm/xx/disk solution. If I have time,
I'll spend some of it to improve it.

..erh, that is, since it's trivial to improve it, I just improved it.

Previously, the 'disk' files only applied to one disk (because only one
disk is listed in one 'disk' file, *and* because there is a quoting
error in the other 'disk' file. I've edited them, and they now include
disks /dev/sd[a-z], and all disks /dev/hd[a-z]. (originally they only
included /dev/sda).

Either way, you should check that your root disk is in the list. option
is that you can look and find out what disk it is that your system root
is, and make sure that's the disk in the config.d 'disk' file.

> Is this a separate bug or part of the same bug and bug fix? Would any
> more information be helpful?

If you are having the problem, and you are able to disable your disk's
pm with the hdparm command, than it is *not* a separate bug.

If you are having the problem, and you are *unable* to change your
disk's pm with the hdparm command, then that *is* a separate bug --
namely, a bug to be filed with hdparm.

Also, make sure that the resulting 'disk' files in the /etc/pm/config.d
and /etc/pm/power.d are executable.
[CODE]
chmod a+x /etc/pm/config.d/disk /etc/pm/power.d/disk
[/CODE]

> But in the mean time, the hardware defaults can be changed via software,
> which leaves the burden of closing the "insanity gap" solely on Linux
> software developers [snip]

*nod* it's not an issue of fault, it's an issue of who can do something
about it. :-)