Re: [2/6] 2.6.21-rc2: known regressions

Stefan Seyfried
2007-03-10T11:44:29Z

On Sat, Mar 10, 2007 at 10:01:21AM +0100, Ingo Molnar wrote:
>
> * Pavel Machek <pavel@suse.cz> wrote:
> > s2ram should be able to work around this, it has parts from
> > radeontool. (suspend.sf.net).
>
> i'm wondering, do you have any idea how Windows handles the
> suspend/resume quirks problem area? Do they "curse BIOS vendors and
> maintain a large DB of DMI-driven exceptions", or do they perhaps have
> some fundamentally better approach than us? If it's the former, then we
> might as well try to bring more automatism (and more of your database)
> into the kernel itself.

I think that in windows, you simply install the "HP nx$FOOBAR intel graphics
driver" on a nx$FOOBAR machine, and the "ASUS $FOOBAR ATI graphics driver"
on an ASUS $FOOBAR machine etc. Those drivers are mostly stock intel/ATI/
whoever drivers, but with the little bit of extra knowledge on how to wake
up the graphics chip.

And there is no console mode in Windows. If you restrict yourself to
"it works from X", many machines do not need workarounds.

> btw., the s2ram database seems quite a bit spotty:
>
> $ ./s2ram -n
> Machine is unknown.
> This machine can be identified by:
> sys_vendor = "System manufacturer"
> sys_product = "System Product Name"
> sys_version = "System Version"
> bios_version = "ASUS A8N-E ACPI BIOS Revision 1008"
>
> $ ./s2ram -n
> Machine is unknown.
> This machine can be identified by:
> sys_vendor = "Hewlett-Packard "
> sys_product = "compaq nx9030 (PG630ET#ABD) "
> sys_version = "Rev 1 "
> bios_version = "F.15 "
> See http://en.opensuse.org/S2ram for details.
>
> even at the link above i didnt find any clear algorithm about how to
> extend the quirks-list and the white-list - while i expect that most
> people experience what i did: that s2ram doesnt know their boxes.
> (otherwise they would not visit that URL at all i suspect)

Ok. To be honest, you are the first reporter that seems to have read the
documentation above, but not understood what to do.

So i'll put it into even simpler steps:

- get the current version of s2ram
- boot your system with init=/bin/bash, mount /proc and /sys
- try the s2ram options in the combinations listed on the above page
- as soon as you find an option that works, please retry it from a
full booted system (including X)
- if it still works, please report the options used and the output of
"s2ram -n" to the suspend-devel mailinglist.

i might consider reworking the documentation if there are more reports
about problems with the procedure.
--
Stefan Seyfried

"Any ideas, John?"
"Well, surrounding them's out."