https://bugzilla.novell.com/show_bug.cgi?id=734226 https://bugzilla.novell.com/show_bug.cgi?id=734226#c0 Summary: Suspend/resume to RAM not working properly in openSuSE 12.1 Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: pavel.hlousek@gmail.com QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.8 (KHTML, like Gecko) Chrome/17.0.922.0 Safari/535.8 SUSE/17.0.922.0 I have a K52F laptop with i915 graphics. When I try to suspend it to RAM the screen goes black but the backlight stays on. No matter how I try I cannot get it to resume (Fn+running man, power button). The only thing that works is to hold power button for 5s and then turn the power on again which is not a resume but a usual boot. I've read the SDB: Suspend to RAM article and I've tried all the hints: boot with "vga=0 init=/bin/bash", calling s2ram with all the variants of options first with the -v option then with the -v option. Everytime it went exactly as described above: black screen with backlight on and no way to resume. Sometimes I could see a message for a very short moment before the screen went black. I wasn't able to read it all as it appears only for a very short time, but it said something like "...graphics drive in use...". When suspending from KDE, the /var/log/pm-suspend.log contains only success messages. Please, can you help me? Reproducible: Always Steps to Reproduce: 1. Suspend 2. Try to resume Actual Results: Does not suspend properly (backlight stays on). Does not resume. Expected Results: Suspends and then resumes :) $ s2ram -n Machine unknown This machine can be identified by: sys_vendor = "ASUSTeK Computer Inc. " sys_product = "K52F" sys_version = "1.0 " bios_version = "K52F.205" -- 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.