I think the original bug report here (NoDCC causes hang) has been fixed.
I am currently testing the trident driver on an ancient laptop here, and
it has many bugs, but this isn't one of them. The "vesa" mode doesn't
work, and most importantly auto-detection doesn't work. Manually writing
your own X
I'm running Maverick, I'll have to try it on Natty whenever it gets out or I
feel like trying a nightly.
Still affected with latest updates...
Failed to allocate :
size : 32768 bytes
alignment : 32 bytes
domains : 2
#
# A fatal error has been detected by the Java Runtime Environme
No longer an issue in Ubuntu 10.4, the card is detected out of the box
with open source drivers. It is also detected at Hardware Drivers and
works fine for normal use and OpenGL apps.
However, once the propitiatory software drivers are enabled, the system
fails to launch compiz and catches a segm
** Attachment added: "BootDmesg.gz"
http://launchpadlibrarian.net/38948012/BootDmesg.gz
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/38948013/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/38948014/Dependencies.txt
** Att
Public bug reported:
Binary package hint: xorg
My ATI Radeon HD 4870 simply shows up as "undetected fglrx" when I run
the "System Test" app on Ubuntu 9.10 x64. It also fails to enable fglrx
from Hardware Drivers. I have been able to get the 9.12 drivers from
ATI's site properly configured on the
5 matches
Mail list logo
