[Ubuntu-x-swat] [Bug 577340] Re: [RC410] Xpress 200M hangs when resuming from suspend with DRI, with or without KMS

2010-07-15 Thread acimmarusti
My bad!, don't use the if at all. The addition to the code should be: /* quirk for rs4xx laptop to make it resume * - it hangs on resume inside the dynclk 1 table. */ return; -- [RC410] Xpress 200M hangs when resuming from suspend with DRI, with or without KMS https://bugs.launchpad.net/bugs/57

[Ubuntu-x-swat] [Bug 577340] Re: [RC410] Xpress 200M hangs when resuming from suspend with DRI, with or without KMS

2010-07-15 Thread acimmarusti
I may have the answer. It worked for my laptop with a video card: 01:05.0 VGA compatible controller: ATI Technologies Inc Radeon XPRESS 200M 5955 (PCIE) So, recently there was a commit to the 2.6.35rc5 kernel by David Airlie (he pointed this out to me): http://git.kernel.org/?p=linux/kernel/git/

[Ubuntu-x-swat] [Bug 305301] Re: [RC410] Xpress 200M hangs when resuming from suspend with DRI (needs KMS)

2010-04-02 Thread acimmarusti
Mark, I was having this problem before, you don't need to reinstall. Just remove this file: sudo rm /var/lib/NetworkManager/NetworkManager.state This is known problem with Network-Manager: http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=571331 Now restart and upon login everything should wor

[Ubuntu-x-swat] [Bug 305301] Re: [RC410] Xpress 200M hangs when resuming from suspend with DRI (needs KMS)

2010-04-01 Thread acimmarusti
Gene, It's highly likely our chips are different, but they all seem related to RC410 -> http://www.x.org/wiki/Radeon%20ASICs Nevertheless, try this: in a terminal run gconf-editor Now there browse to: apps/gnome-power-manager/general/ On the righthand side you should see network_sleep (hopeful

[Ubuntu-x-swat] [Bug 305301] Re: [RC410] Xpress 200M hangs when resuming from suspend with DRI (needs KMS)

2010-04-01 Thread acimmarusti
Though I haven't been running Ubuntu in a long time, I've experienced this issue with Debian Squeeze. I've been constantly tracking this ubuntu bug for a workaround. Fortunately I've found a fix that is working pretty well for me. Go to System Tools > Configuration Editor Now browse to: apps/gno