RenderAccel in the nvidia-legacy drivers was always experimental which is why it defaulted to off. From ftp://download.nvidia.com/XFree86/Linux-x86/1.0-7174/README.txt : "Enable or disable hardware acceleration of the RENDER extension. THIS OPTION IS EXPERIMENTAL. ENABLE IT AT YOUR OWN RISK. There is no correctness test suite for the RENDER extension so NVIDIA can not verify that RENDER acceleration works correctly. Default: hardware acceleration of the RENDER extension is disabled." So if you are getting crashes enabling it the legacy drivers I'm afraid that's to be expected. NVIDIA fixed RenderAccel in later releases of their drivers.
If NVRM: Xid is being printed to the console or is turning up in /var/log/messges you definitely have an issue with the binary drivers. NVRM: Xid messages are output by the binary driver basically saying "something unexpected happened" but only NVIDIA can really make sense of them (they can indicate genuine driver problems as well as troublesome hardware). This bug has become confused. It is not clear whether everyone is really seeing the same issue. I would say that if you are not using a legacy card then you are probably better off not posting to this bug but instead opening an issue of your own. Mikkel: Is the issue still happening under Feisty? Are any NVRM: Xid message being printed in dmesg/ /var/log/messges ? -- [Dapper] Firefox hard locks when RenderAccel is enabled https://bugs.launchpad.net/bugs/6279 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
