A question about suspend feature

cwwilson721 · 06-26-2006, 12:56 PM

For ever, I have not been able to suspend/resume my laptop.

While just doing normal messing around with my box, I did:

Code:

hdparm -d1 /dev/hda

And had the following results:

Code:

Commands/features:
        Enabled Supported:
           *    NOP cmd
           *    READ BUFFER cmd
           *    WRITE BUFFER cmd
           *    Host Protected Area feature set
           *    Look-ahead
           *    Write cache
           *    Power Management feature set
                Security Mode feature set
           *    SMART feature set
           *    Device Configuration Overlay feature set
                SET MAX security extension
                Address Offset Reserved Area Boot
                Power-Up In Standby feature set
           *    Advanced Power Management feature set
           *    SMART self-test
           *    SMART error logging

If the above (in red) is not set, would that be why I can't resume from suspend?

If so, how do I set this?

This may explain alot of issues with people not being able to resume also....

Caeda · 06-26-2006, 09:45 PM

Actually, i would read that red statement much more literally.
Power Up In Standby Feature Set...
So when the drive powers up, it does so into standby mode.

cwwilson721 · 06-26-2006, 09:58 PM

Found this in here:

Quote:

6.x Power-up in Standby feature set
The optional Power-up in Standby feature set allows devices to be powered-up into the Standby
power management state to minimize inrush current at power-up and to allow the host to
sequence the spin-up of devices. The feature set may be enabled or disabled via the SET
FEATURES command. The feature set may be enabled by use of a jumper or similar means.
When enabled by a jumper, the feature set may not be disabled via the SET FEATURES
command. If this feature set is implemented, the fact that it is implemented and enabled is
reported in the IDENTIFY DEVICE or IDENTIFY PACKET DEVICE response.
The enabling of this feature set shall be persistent across power-down. When this feature set is
enabled, the device shall power-up into Standby.

So what does this mean?

EyesOnly · 06-27-2006, 10:39 AM

When the machine is turned on, the harddisks will start in standby-mode. This way they can be started sequential, thus lowering the power-peaks: starting 15 disks or so at once causes quite a peak; this is really a feature used in servers, whit a lot of disks

On a side-note, problems whit resuming from standby are usually caused by incomplete linux-support. I could not use resume until kernel 2.6.15 or so. Before that some drivers for my hardware just didn't support resume. linux standby support is known to be flaky at best...

cwwilson721 · 06-27-2006, 10:49 AM

Thanks. That helped clear the cobwebs.

Flaky doesn't come close tho...lol

Never have been able to suspend/resume successfully, but can hibernate/resume fine....Was just thinking that MAY have been one reason why, but I guess they just word it badly.

Again, thanks, all, for the replies.

Old_Fogie · 06-27-2006, 10:50 AM

cw..

I suspect that this is not related to a hard drive, but let's say a computer with multiple hard drives is the way that I read that.

For example, when I boot up my pc... I have a bunch of physical different hard drives. So in my /etc/rc.d/rc.local I put in for example:

My primary slack install is on /dev/hda...which is not put to sleep ever. I tried it but linux is really goofy for the operating systems hard drive to go to sleep and then wake up, I get cable bit errors on resume.

echo "Setting hard drives sleep time"
/usr/sbin/hdparm -S 180 /dev/hdb
/usr/sbin/hdparm -S 180 /dev/hdc

the 180 is increments of 12 seconds...so that's 15 minutes. What this means is the pc turns on, then the hdb and hdc go to sleep in 15 minutes.

I read what you listed as the option to start my pc with hdb and hdc in sleep mode already...and then I just use the main drive of /dev/hda.

I can get full hibernate/sleep mode on my laptop with the built-in mobo sleep/hibernate; and even the mobo's standby mode..which is counternamed to linux way.

I think to put the hard drive to sleep you have to patch the kernel in accordence with this link here:
http://www.suspend2.net/

that's included in SuSE linux and I can tell you it really worked in SuSE and I'm utterly jealous that slackware doesnt include it

cwwilson721 · 06-27-2006, 10:59 AM

Getting suspend to work is on my 'todo' list, somewhere after buying a new car but before my kids all go to college....(In other words, eventually...lol)

EyesOnly · 06-27-2006, 10:59 AM

Quote:

Originally Posted by Old_Fogie

cw..
I think to put the hard drive to sleep you have to patch the kernel in accordence with this link here:
http://www.suspend2.net/

that's included in SuSE linux and I can tell you it really worked in SuSE and I'm utterly jealous that slackware doesn't include it

Meh.. I am able to put my system disk to sleep just fine, on slackware whit both kernel 2.4 and 2.6.. But I found it to be not really usefull, since the system disk is accessed so often i needed a very short time-to-sleep interval, and it would wakeup very soon after going to sleep..

Putting a data-disk to sleep is indeed usefull, and has always worked out of the box for me after setting the intervals whit hdparm.

Old_Fogie · 06-27-2006, 07:02 PM

the quick power off suspend n linux is called standby on my compaq.

my compaq calls linux suspend hibernate, e.g a deep sleep.

the suse using that suspend w/patch kernel rox. you could have every app open, and boom low power off, or deep sleep. even worked for a desktop. it was nice to have the desktop up and in KDE in 5 seconds flat from drawing no electric. i'm overclocked, so i draw a lot of power. my neighborhood probably dim's when i power on lol.

like you cw i'm gonna get it working in slack...one of these days

ps..i put in the new kde on slack 10.2 and my city don't work in kweather

i'm so mad (jk)

by for now.

cwwilson721 · 06-27-2006, 07:05 PM

Never could get KWeather in 10.2. It works fine in -current