As I already mentioned you can prevent the fglrx kernel module from being loaded.
Then you get some message like: (EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized. (WW) fglrx(0): *********************************************** (WW) fglrx(0): * DRI initialization failed! * (WW) fglrx(0): * (maybe driver kernel module missing or bad) * (WW) fglrx(0): * 2D acceleraton available (MMIO) * (WW) fglrx(0): * no 3D acceleration available * (WW) fglrx(0): ********************************************* * in /var/log/Xorg.0.log as 3D acceleration will not work without the module. Suspend however will work (at least on my machine). 2007/10/2, Charl P. Botha <[EMAIL PROTECTED]>: > I understand that one is dependent on ATI for a fix. However, isn't it > wise to include at least SOME kind of workaround or documentation in > Gutsy concerning this problem? Will anyone even get around to that > seeing that this bug has been classified "wishlist" ? > > It really makes a fantastic impression when a computer locks up hard the > first time the user tries to suspend or hibernate it. ;) > > -- > [gutsy] Suspend to Ram does not work on Z61m > https://bugs.launchpad.net/bugs/121653 > You received this bug notification because you are a direct subscriber > of the bug. > -- [gutsy] Suspend to Ram does not work on Z61m https://bugs.launchpad.net/bugs/121653 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
