Andrew Joakimsen wrote:

I find that my system can not suspend to disk or suspend to ram correctly. After I suspend the system boots back up with a black screen and I need to press ctrl+alt+bkspc twice for anything to show up on the screen... which totally negates any benefit suspend-to-disk can offer.

You keep repeating variations on this question. Each time you get various suggestions. I think you will have more luck if you try out each suggestion and report the results. Then people can help you more. When you post your results, keep in mind the needs of the people who are helping you: -1- Post a concise but hopefully complete summary of your system hardware and current software configuration, so people don't have to go back and reread all the different threads you've started. (BTW, 'latest' isn't a good version number) -2- Answer each suggestion. Post a concise description of what you tried and what effect it had, starting with a quote of the original suggestion. Include log extracts where possible/relevant. Answer even if you didn't try it, explaining why not. Looking at the archives, you have answered a few suggestions. But more often, you haven't answered but have simply started another thread with the same old question. That doesn't encourage people to provide help. Neither does making sarcastic comments in OT threads. HTH, Dave PS I'd suggest trying Manne's suggestion as a start. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Andrew Joakimsen wrote:

The system is using a Gigabyte GA-MA78GM-S2H mainboard (AMD 780G chipset), onboard HD 3200 graphics with the fglrx driver ("ATI Radeon HD 3200 Graphics (RS780 9610)") ver. 8.493_2.6.25.5_1.1-2.1 (Sun 08 Jun 2008 08:30:57 AM EDT)

Have you tried suspend and the other suspend tests with the _radeon_ driver instead of the fglrx driver? Remember the fglrx driver is binary black box. While it does give very good graphics performance, it is like an eight-headed hydra when it comes to playing nice with the rest of the system. For a quick check (as root): cp /etc/X11/xorg.conf /etc/X11/xorg.conf.fglrx edit /etc/X11/xorg.conf Change fglrx to radeon in Section Device and delete all fglrx options, comment out AIGLX IN ServerLayout and comment DAMAGE and Composite in Extensions section similar to the following: Section "Device" ... Driver "radeon" ... <DELETE ALL FGLRX OPTIONS> ... VendorName "ATI" EndSection Section "ServerLayout" ... # Option "AIGLX" "True" .... EndSection Section "Extensions" # Option "DAMAGE" "true" # Option "Composite" "true" EndSection Drop to runlevel 3 with "telinit 3" and remove the fglrx driver and install the radeon driver: rmmod fglrx && modprobe radeon Go back to runlevel 5 with "telinit 5" and test without the fglrx driver. When you are done, to get your fglrx config back, simply "cp /etc/X11/xorg.conf.fglrx /etc/X11/xorg.conf" and reboot (yes reboot, the radeon driver doesn't completely unload from memory with rmmod for some chipsets - save yourself the misery) -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org