Difference between revisions of "Talk:Laptop-mode-tools"
(SATA drive state sensing problem.) |
(IDE drivers make no difference reading SATA drive state.) |
||
Line 7: | Line 7: | ||
{{cmdroot|hdparm -y /dev/sda}} | {{cmdroot|hdparm -y /dev/sda}} | ||
− | works perfectly -> drive will spindown properly. I obtained the much simpler spindown shell script, and looking into this issue noticed that: | + | works perfectly -> drive will spindown properly. I obtained the much simpler spindown shell script, and looking into this issue noticed that the command: |
{{cmdroot|hdparm -C /dev/sda}} | {{cmdroot|hdparm -C /dev/sda}} | ||
− | + | always returns: | |
/dev/sda: | /dev/sda: | ||
drive state is: standby | drive state is: standby | ||
+ | regardless of the current state of the drive, and the script never goes further (thinks the drive is in standby, when it is clearly spinning...) | ||
− | + | Of note, I do not have the IDE driver in my kernel, only using the SATA - ATA_PIIX compiled in. Perhaps I need to include the IDE module to sense the drive state correctly? This seems a bit bizarre, as everything else works well. | |
− | + | Update - compiling IDE drivers into the kernel does nothing to change the output - drive is always listed as "standby" no matter what state it actually is in.. | |
[[User:gsmenden|gsmenden]] 2:55 12 Feb 2006 (EST) | [[User:gsmenden|gsmenden]] 2:55 12 Feb 2006 (EST) |
Revision as of 10:00, 12 February 2006
Problems with spindown
On my T43p (2.6.15.3), these tools plain don't work for me -- the daemon refuses to spin down my hdd despite the most aggressive values put in the laptop-mode.conf file.
So far trying to debug the problem:
# hdparm -y /dev/sda
works perfectly -> drive will spindown properly. I obtained the much simpler spindown shell script, and looking into this issue noticed that the command:
# hdparm -C /dev/sda
always returns:
/dev/sda: drive state is: standby
regardless of the current state of the drive, and the script never goes further (thinks the drive is in standby, when it is clearly spinning...)
Of note, I do not have the IDE driver in my kernel, only using the SATA - ATA_PIIX compiled in. Perhaps I need to include the IDE module to sense the drive state correctly? This seems a bit bizarre, as everything else works well.
Update - compiling IDE drivers into the kernel does nothing to change the output - drive is always listed as "standby" no matter what state it actually is in..
gsmenden 2:55 12 Feb 2006 (EST)