From: Sheer El-S. <sh...@gm...> - 2007-11-04 22:19:14
|
Well I was running Gutsy, 2.6.22 and radeonhd and suspend to ram seemed to work reliably for 3-4 times I used it. Then I tried switching kernels to an older kernel (with SLAB?) listed off the ubuntu MBP howto that supposedly helped with suspend and also installed fglrx. Things worked pretty nicely and I don't even think power usage went up much (though its hard to tell because the battery info in proc keeps vanishing and trackerd is running up the CPU) but suspend broke consistently. I switched back to the original kernel and radeonhd and suspend seemed to work again but then when I tried to resume it this morning the screen stayed depressingly blank. Could this be because I left a monitor section in my xorg.conf (from when I had installed fglrx)? I'm going to try to revert to my pure radeonhd xorg and see how things go. I've already removed the fglrx module and am running the original kernel and I had hoped this would get me back to a stable setup. Does anyone have an MBP 2,2 with stable suspend/resume using radeonhd? I can wait for a month or two for ATI to sort out its issues but I really need stable suspend/resume. Sheer ps I'm using ubuntu's suspend/resume which does not use s2ram I believe. On 10/26/07, Soeren Sonnenburg <mac...@nn...> wrote: > On Fri, 2007-10-26 at 13:07 -0500, Scott L Price wrote: > > If I remove the 'monitor' section in my xorg.conf file the radeon mostly > > works fine. > > > > Suspend to RAM does not work. It resumes to just a blank screen. I > > have not played with it a long time, so there may be a configuration to > > make it work. > > I just suspended + resumed 10 times in a row... it works and even within > 1-2 seconds. I guess you don't have 'posting' enabled, I suspend via > s2ram -f -p ... > > Soeren > |