Created attachment 35392 [details] my xorg.cong, which I have used in all older OS versions Hi, I haven't never problems with suspend2ram on my mythbuntu computer, i'm using mythbuntu from version 8.04 LTS and before I have used this comp for my own purposes with Ubuntu and it was from version dapper drake 6.06 without any problems with suspend2ram. Now I have upgraded from 9.10 Karmic Koala with Xorg 7.4 to the 10.04 Lucid Lynx with Xorg 7.5 ( where is KMS enabled ) and when I do suspend2ram and then wake up (it's connected only TV-Output SVideo) the TV looks like this: http://img203.imageshack.us/i/foto01113927428.jpg/ http://img535.imageshack.us/i/foto01103934043.jpg/ EVERYTHING is without problem, Xorg detects my graph. card without xorg.conf without any problems ( that it's great !!! ) and it's only connected TV-Output SVideo ! I have tried start with my xorg.conf, which I have used in all older versions of the mythbuntu it's in attachment. I'm attaching Xorg log files without xorg.conf and Xorg log file with my xorg.conf. Some info from glxheads: GL_VERSION: 1.5 Mesa 7.7.1 GL_VENDOR: DRI R300 Project GL_RENDERER: Mesa DRI R300 (RV350 4153) 20090101 x86/MMX+/3DNow!+/SSE TCL DRI2
Created attachment 35393 [details] Enabled KMS and used xorg.conf attached above
Created attachment 35394 [details] Enabled KMS without any xorg.conf - completely autodetection
When I disable KMS as is described here: http://www.ubuntu.com/getubuntu/releasenotes/1004#Working%20around%20bugs%20in%20the%20new%20kernel%20video%20architecture everything works fine
Alex Deucher wrote: >What exact problem are you seeing? Is it just S-video that's not >coming back up properly after resume? If so, I would consider that a >different issue than the others above. I would suggest filing a new >bug and we'll determine if it's a duplicate or not. I have tried connect monitor ( because before was connected only Svideo ), have enabled KMS and have tried wake up from suspend2ram and the screen on monitor was refreshed, but some pixels was bad ( some pixels was green, .. ), but what it's horrible my keyboard doesn't respond, so I can't switch to the console by ctrl+alt+1 and whole X was freezed. The Svideo output was the same as is described in first comment, like this: http://img203.imageshack.us/i/foto01113927428.jpg/ http://img535.imageshack.us/i/foto01103934043.jpg/
Can you attach your dmesg from before and after s2ram? Also, does s2ram work with a monitor attached rather than s-video (i.e., use a monitor only before and after s2ram)?
(In reply to comment #5) > Can you attach your dmesg from before and after s2ram? Also, does s2ram work > with a monitor attached rather than s-video (i.e., use a monitor only before > and after s2ram)? I don't know how to use dmesg, exactly how to use dmesg, in order to receive what you need. Pls, give me some info how ( i'm linux friendly, so suffice simply example )
(In reply to comment #6) > I don't know how to use dmesg, exactly how to use dmesg, in order to receive > what you need. > > Pls, give me some info how ( i'm linux friendly, so suffice simply example ) run the command 'dmesg' to see it. redirect it to a file before and after suspend and attach those files. before suspend: dmesg > before_suspend.dmesg after resume: dmesg > after_resume.dmesg
Created attachment 35415 [details] without xorg.conf - dmesg output before suspend2ram
Created attachment 35416 [details] without xorg.conf - dmesg output after resume from suspend2ram
Created attachment 35417 [details] without xorg.conf - after resume from suspend2ram screen look like this But when I press enter in console, screen is refreshed and the big white lines with many color pixels disappears.
Hi dev, how it looks with this issues?
sNop, Ubuntu 10.04 Desktop reached EOL on May 9, 2013. For more on this, please see https://wiki.ubuntu.com/Releases . If this is reproducible in a supported release, it will help immensely if you filed a new report with Ubuntu by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information running the following from a terminal: ubuntu-bug xorg Also, please feel free to subscribe me to it. For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.