Mailinglist Archive: opensuse-bugs (13490 mails)

[bugzilla_noreply@xxxxxxxxxx]

https://bugzilla.novell.com/show_bug.cgi?id=281798#c12





--- Comment #12 from Felix Möller <felix@xxxxxxxxxxxx>  2007-10-23 02:03:46 MST 
---
(In reply to comment #10 from Stefan Seyfried)
> This is still not totally clear. We have an A100 here that suspends fine with
> "S3_BIOS|S3_MODE".

There are alot of differnt A100s. The number after the 100 is important too in
my case 773.

Mine is:
Fixes: 0x3  S3_BIOS S3_MODE
This machine can be identified by:
    sys_vendor   = "TOSHIBA"
    sys_product  = "Satellite A100"
    sys_version  = "PSAA9E-099039GR"
    bios_version = "5.90   "

> Our s2ram binary now has the framebuffer suspend sysfs hack from comment #5
> built in, so you don't need the script in pm-utils anymore.
>
> I still need to find out what is different on your machine versus the one we
> have here. Until i can test this (and it will be next week earliest, since i
> will be traveling), please just use a config file in /etc/pm/config.d that
> just contains "S2RAM_OPTIONS='-f -v'".
I am using the radeonhd driver by now and to suspend the machine I have to use:
# cat /etc/pm/config.d/config
S2RAM_OPTS="--force --vbe_post --vbe_mode --vbe_save"

Without the --vbe_post the machine dies hard on resume so that nothing is
written in the logs. When just using one of [--vbe_mode, --vbe_save] the
consoles do not work after suspend.


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.