aselvan: I don't have direct rendering on, but I did have Load "glx" in the module section i xorg.conf. I found this: http://ubuntuforums.org/showthread.php?t=610924dd - and after doing: export DISPLAY=:0 it did say direct rendering on. Not really sure why - or what it going on.. I think I need to make sure what all those damn parts in xorg.conf mean ;)
I also tried the disable-reboot-enable-reboot of the restricted driver, and now my second problem (not being able to restart my x-server or use suspend mode) is fixed. ! :) Notice: I was not able to start my x-server after i disabled the restricted driver - so I had to do this: sudo apt-get install xserver-xgl (at least I think that was it... found it somewhere), and after that I had to edit my xorg.conf screen section to fix the resolution....(screen/display/virtual) Although thinks are working fine, the original problem doesn't seem fixed. When running Firefox in full-screen mode and trying to edit the address, Xgl uses up all cpu again. But if the direct rendering stuff is wrong .. I guess that is the reason? I'm posting more questions then answers .. sorry :) -- firefox and xgl cause 100% CPU https://bugs.launchpad.net/bugs/145696 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
