https://bugzilla.novell.com/show_bug.cgi?id=631759
https://bugzilla.novell.com/show_bug.cgi?id=631759#c8
--- Comment #8 from Elmar Stellnberger 2010-10-02 10:18:33 UTC ---
Strange; now that I retest with the latest and current openSUSE kernel s2ram
starts to work; perhaps because the kernel has been updated two times in the
meanwhile (now it is 2.6.34.7-0.3-desktop):
s2ram -f: external monitor comes up, integrated monitor stays garbeled blue
s2ram -a 1: flirring screen; nothing gets displayed
s2ram -a 2: like s2ram -f
s2ram -a 3: like s2ram -a 1
works well:
s2ram -f -p -m
s2ram -f -p
s2ram -f -m
However when booting into runlevel 5 (X runs) I get the following results:
* no agp (as shown by /proc/driver/nvidia/agp/status)
after resume the following happens:
at first: freq out of range
then: video mode is restored correctly
later: video mode is destroyed again: ext.mon.:
very low resolution about 640x480 or sth. like that, flurring screen
(no agp: achieve this by modprobe intel_agp and NvAGP-option in xorg.conf.)
*agpgart
monitor out of freq 74kHz/164Hz instead of 60Hz (lcd error msg + black scr)
+crash (Alt-PrnScr S-U-B does not qork: Magic SysRq Keys)
* nvagp:
crash: black screen; no out of sync error message
Interestingly the nvagp-option is still required to restore the graphics mode
on resume from s2disk (tested: still working for s2disk).
Likely we should work on the resume-behaviour of the intel_agp-module as
nvagp does not seem to be a way out in this case (and for it is the standard
agp module). This seems eminently doable since graphics mode resume works at
least at the first glance for no agp usage.
--
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.