10.2 suspend to disk does not show up anymore on HP laptop

in place upgrade from 10.1 to 10.2....

Went very smoothly save for a manual JRE download from Sun. The only other
issue is that the suspend to disk option no longer is offered neither in the
"Logout" nor the Menu bar applet. No signs of it anywhere. I checked the
Yast repository for 'suspend' and 'laptop'...all packages seem to be
installed.

Laptop is an HP Pavilion zv6000, AMD 3500+, ATI 200Express video.


TIA,
Mike

Mike,

KDE? If so, does it work from the KPowersave applet?

Uwe

--
Novell Support Connection Volunteer SysOp
Please don't send me support related e-mail unless I ask you to do so.

No. I've been using Gnome exclusively.

I'll switch to KDE to give your suggestion a try.


Thanks,
Mike


"Uwe Buckesfeld" <u.buckesfeld@web.de> wrote in message
news:48Olh.22183$jS4.15761@prv-forum2.provo.novell.com...
> Mike,
>
> KDE? If so, does it work from the KPowersave applet?
>
> Uwe
>
> --
> Novell Support Connection Volunteer SysOp
> Please don't send me support related e-mail unless I ask you to do so.

Changed the session to KDE. KPowersave is running, seemingly A-OK.
Choosing to suspend to RAM errors and spits me back out to the desktop.
Still no suspend to disk option.

Running Kpowersave under Gnome produces as an error (error 11 IIRC) and
isn't even functional.

Interesting to note, Kpowersave is version 071-6. Sourceforge shows the
latest unstable release of 071-5. Perhaps an even newer version of
Kpowersave will fix things? Dunno.

<scratching head>



"Mike M" <nospam@nospam.net> wrote in message
news:C59mh.22303$jS4.3972@prv-forum2.provo.novell.com...
> No. I've been using Gnome exclusively.
>
> I'll switch to KDE to give your suggestion a try.
>
>
> Thanks,
> Mike
>
>
> "Uwe Buckesfeld" <u.buckesfeld@web.de> wrote in message
> news:48Olh.22183$jS4.15761@prv-forum2.provo.novell.com...
>> Mike,
>>
>> KDE? If so, does it work from the KPowersave applet?
>>
>> Uwe
>>
>> --
>> Novell Support Connection Volunteer SysOp
>> Please don't send me support related e-mail unless I ask you to do so.
>
>

Mike,

Yast, System, Power Management,
Click "Suspend Permissions": Is "Supsend to disk" checked?

Uwe

--
Novell Support Connection Volunteer SysOp
Please don't send me support related e-mail unless I ask you to do so.

Mike M wrote:

> No. I've been using Gnome exclusively.
>
> I'll switch to KDE to give your suggestion a try.


--
ispyhumanfly :: telnet://euphoriabbs.net <> http://spydev.ath.cx
irc_ #perl @ freenode.net <> email_ ispyhumanfly@gmail.com

Mike M wrote:

> Interesting to note, Kpowersave is version 071-6. Sourceforge shows the
> latest unstable release of 071-5. Perhaps an even newer version of
> Kpowersave will fix things? Dunno.

interesting. it's funny how i too had similar issues with older
installations of opensuse ( 10.0 ) until i stopped using KDE all
together and started using smaller window managers ie fluxbox.

havn't had any issues since. and point of fact my skill in linux
increased 10 fold when i wasn't able to rely on the bells and whistles
of gnome and kde.

also have you tried running these utilities via command line? i would
check and see what the actual full length command lines are for these
applications to. you would be surprised how easy it is to get things to
work in linux if you just get down in there and do it yourself.

--
dan stephenson :: linux/perl/xml <> http://spydev.ath.cx
irc_ #perl @ freenode.net <> email_ ispyhumanfly@gmail.com

Yes, Suspend to disk is checked...

After playing around with this for a while, I've found that using s2ram is
the key. IIRC, "s2ram -f" places the laptop into a RAM-suspended state.
Works well!

Looks like this funcationality isn't built into the GUI, but it does work
well.

I have to restart the wireless interface after coming out of s2ram, but it's
a small price to pay. In fact, when booting a SuSE 10.1 installation on the
same laptop, the wlan0 interface must be manually invoked to make it
available after boot-up. It looks like it's trying to intialize during
startup, but never does. Is there a way to force this interface to start at
boottime?


Thanks,
Mike


"Uwe Buckesfeld" <u.buckesfeld@web.de> wrote in message
news:LLlmh.22381$jS4.7658@prv-forum2.provo.novell.com...
> Mike,
>
> Yast, System, Power Management,
> Click "Suspend Permissions": Is "Supsend to disk" checked?
>
> Uwe
>
> --
> Novell Support Connection Volunteer SysOp
> Please don't send me support related e-mail unless I ask you to do so.

Mike,

great news!
Put the -f option in the config file
http://en.opensuse.org/Pm-utils

As for the NIC: Are you using the Network Manager? Because this is enabled as a hook by default and should therefore restart automatically. IF, I guess, the NIC is set to be started at boot time in Yast.

Uwe



--
Novell Support Connection Volunteer SysOp
Please don't send me support related e-mail unless I ask you to do so.