ignoring s3-bios and s3-mode suspend quirks with nvidia cards does not work
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
hal (Ubuntu) |
Fix Released
|
High
|
Martin Pitt | ||
Hardy |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: hal-info
Hi,
the Fujitsu Lifebook E8410 comes in two flavours: Intel graphics or NVIDIA graphics. Running Hardy currently suspend to RAM ist not possible on E8410 with NVIDIA graphics (The Lifebook seems to suspend fine, but freezes immediately after switching on power).
With the current 20-video-
pm-suspend --quirk-s3-bios --quirk-s3-mode
This fails. If called without arguments, the Lifebook is resuming fine.
As a dirty hack I did:
root@lulu:
--- 20-video-
+++ /root/20-
@@ -44,13 +44,9 @@
<merge key="power_
</match>
<match key="system.
-
- <match key="system.
<merge key="power_
<merge key="power_
</match>
-
- </match>
<match key="system.
<merge key="power_
<merge key="power_
After that, pm-suspend is called without any arguments and my Lifebook with NVIDIA resumed fine.
Kind regards
Gerd
Hm, actually that's exactly the case that
hal (0.5.11~ rc2-1ubuntu3) hardy; urgency=low
* 01_default_ suspend_ quirks. patch: Disable video quirks when running on a
known-good video driver (proprietary nvidia and fglrx, and Intel >=
915GM). Doing this here is better than the previously applied pm-utils
patch, since it avoids ignoring explicit pm-utils command line arguments,
consistently uses the same behaviour for suspend and resume, and keeps the
logic where it actually belongs.
-- Martin Pitt <email address hidden> Mon, 24 Mar 2008 17:35:38 +0100
was supposed to take care of. Seems that doesn't really work then?
Does /sys/module/nvidia exist for you? or do you use the free nv driver? Can you please edit /usr/lib/ hal/scripts/ linux/hal- system- power-suspend- linux and add the following two lines right after the first line:
set -x
exec 2>/suspend.log
and then try to suspend, and resume (or reboot, if it failed). Can you please attach /suspend.log here?