Suspend on System76 in Lucid
For some reason I note with horror that my computer will no longer suspend since upgrading to lucid. This is a bit of a problem since my machine isn’t doing so well with batteries these days, but I’m surprised because this is a system 76 laptop and I’d have expected their hardware to basically work.
At least the boot is pretty fast, so shutting it down isn’t killing me.
Thoughts?
Some difficult bugs seem to have struck suspend / resume, and random freezes that appear from the symptoms to be related. The one consistent symptom is fsck on bootup with “INFO: recovery required on readonly filesystem” in dmesg – obviously nothing else got written to the (readonly) logs.
I put some links to several Launchpad bugs that might (or might not) all be the same thing at http://www.iol.ie/~stuartneilson/Bootup_fsck.html , and there are some links to Ubuntu Forum rant threads.
What does exactly happen? Does it hang while suspending, fail to suspend or something else?
Try the procedure in Documentation/power/basic-pm-debugging.txt in the kernel tree to see which part is broken. You may also try mainline kernels (google “Mainline kernel ppa”) which are newer versions of kernel built with Ubuntu’s config. In my experience ACPI bugs introduced in one version are usually fixed in the next one.
And most importantly, did you file a bug?
Lucid suspend appears broken for quite a lot of hardware. My IBM ThinkPad T42p won’t suspend any more either.
I have had the same issue, but downgrading my nvidia drivers to pre-195 worked it out for me.
Is the hardware in question Canonical certified or tested to be compatible with Lucid via Canonical’s hardware partner program?
-jef
You said you upgraded. Did suspend work before the upgrade? If so, are you sure it’s the hardware that’s not working? It sounds like it was the software that changed.
Edd
If this were the case with my laptop, I’d file a bug and describe all the symptoms precisely.
I was researching some suspend issues of my own with Lucid on unrelated hardware and thought I saw something about this. If I’m remembering right (which is questionable–I tend to futz around in Lunux after cracking a beer) the webcam was sending a wakeup request right after it received a sleep request. It had always been doing this but the newer kernel actually understands the request whereas it was previously ignored by accident. They recommended changing a driver option (with hal or /sys) so it couldn’t send wake requests.
I could be totally off-base though. A copy of your /var/log/syslog and /var/log/pm-suspend.log (or something of that name) for the times around the suspend attempt should shed light on what’s going wrong after pm-suspend gets called.
Maybe the upgrade borked something? A clean install may work better…
Thinkpad X60S same problem after upgrade – no time to investigate so far.
Since commenting above, I found a setting that appears to have fixed suspend and resume (and freezing) on my laptop:
Add “radeon.modeset=0″ (or “nomodeset”) to GRUB_CMDLINE_LINUX_DEFAULT
See http://www.iol.ie/~stuartneilson/Bootup_fsck.html for more details and a list of related Launchpad bug reports.
My ASUS K72JR is broken too. So is my girlfriend’s IBM Thinkpad x32. I’ve never had anything other than Lucid on both however, so I’m not sure if it’s a regression or just not supported.
What might be more helpful is if someone can post what we’re supposed to do when suspend/hibernate breaks on our machines so we can report it to Canonical/Launchpad or whoever upstream…
Make sure the latest System76 Driver is installed. If it isn’t fixed by now it will be soon. Plus you can email them and/or post in their section of the Ubuntu forum.