Hello, On Sat, 14 Jun 2008, Michael Biebl wrote: >> Note that the order in which the enclosed script calls vbetool matches >> that used in the files from the package acpi-support. > > This is getting pretty weird. > > I thought, the only quirks you were using are --quirk-dpms-on? > Why should the order of the vbetools calls matter in such a case?
I think I created some confusion (See below) for which I apologise.
> Could you please repeat, which quirks exactly you are using?
The quirks being used currently are:
--quirk-dpms-on --quirk-vbe-post --quirk-vga-mode3
--quirk-vbestate-restore
The ".fdi" file I attached to the bug report does not use "dpms-on" but
mentions all the others above.
> Could you also please let us know, which graphics hardware and driver
> you are using (free vs. closed source)
I'm using the driver "i810_drv" from "xserver-xorg-video-intel"
debian package version 2:2.3.1-1. The graphics device appears to be 855GM.
The hardware details should be in the "lshal" output which I sent to
this bug report. However, if you need anything more please let me
know.
The confusion, I created was as follows.
If I use "pm-suspend" with no arguments then for some reason the
quirks from the "fdi" file are _not_ applied. This is documented on
the web page:
http://people.freedesktop.org/~hughsient/quirk/quirk-suspend-try.html
At this point I _erroneously_ said that "pm-suspend --quirk-dpms-on"
works. What I meant is that
pm-suspend --quirk-dpms-on --quirk-vbe-post --quirk-vga-mode3
--quirk-vbestate-restore
works for me. However, I also need to have these quirks applied
in a particular order.
The (for me) correct order is the same as the order in which these
quirks are applied by the current "acpi-support" scripts. The order
in which the quirks are applied by the 99video file in "pm-utils" is
different.
I hope this clarifies matters.
Regards,
Kapil.
--
signature.asc
Description: Digital signature
