Re: KDE and hdparm (was: Re: [gentoo-user] Disable fcron logging)

2010-08-30 Thread Mick
On 24 August 2010 14:31, Alex Schuster wo...@wonkology.org wrote:
 Mick writes:

 On Sunday 22 August 2010 22:39:47 Alex Schuster wrote:

  BTW, my two additional drives spin up when I log into KDE. Weird,
  they are not even mounted.

 From KDE-4.4.4 the start up interferes with the hard drives:

 http://thread.gmane.org/gmane.linux.gentoo.user/232044

 I don't why but it does, messes up any settings that hdparm may have
 set up and p*sses me off.  o_O

 As soon as KDE starts up (even when waking up from suspend to ram) it
 resets the drives.  I haven't found a way of telling it how to behave
 (i.e. by respecting existing settings in hdparm).

 Argh, that's annoying. Thanks for the information. O well, first I
 setuid'ed hdparm to make it work as a user, then I reverted that back as I
 started it in /etc/init.d/local, and now I'm again setuid'ing it so I can
 set the settings from /etc/conf.d/hdparm in ~/.kde4/Autostart/.

 I filed a bug: https://bugs.kde.org/show_bug.cgi?id=248905
 You might want to vote for it so it gets some attention and will hopefully
 be fixed soon.

Thanks Wonko,

As reported on https://bugs.gentoo.org/show_bug.cgi?id=334393 the workaround of:

touch /etc/pm/power.d/harddrive

stops KDE4.4.4/5 from messing up the existing hdparm settings (at
least as far as acoustic management is concerned).  At least now I
don't have to listen this Seagate sata rattling all day!  :-)
-- 
Regards,
Mick



KDE and hdparm (was: Re: [gentoo-user] Disable fcron logging)

2010-08-24 Thread Alex Schuster
Mick writes:

 On Sunday 22 August 2010 22:39:47 Alex Schuster wrote:

  BTW, my two additional drives spin up when I log into KDE. Weird,
  they are not even mounted.
 
 From KDE-4.4.4 the start up interferes with the hard drives:
 
 http://thread.gmane.org/gmane.linux.gentoo.user/232044
 
 I don't why but it does, messes up any settings that hdparm may have
 set up and p*sses me off.  o_O
 
 As soon as KDE starts up (even when waking up from suspend to ram) it
 resets the drives.  I haven't found a way of telling it how to behave
 (i.e. by respecting existing settings in hdparm).

Argh, that's annoying. Thanks for the information. O well, first I 
setuid'ed hdparm to make it work as a user, then I reverted that back as I 
started it in /etc/init.d/local, and now I'm again setuid'ing it so I can 
set the settings from /etc/conf.d/hdparm in ~/.kde4/Autostart/.

I filed a bug: https://bugs.kde.org/show_bug.cgi?id=248905
You might want to vote for it so it gets some attention and will hopefully 
be fixed soon.

Wonko