2006-02-03 Steven Haigh <netwiz@xxxxxxxxx> wrote > Hi all, > > Has anyone managed to get the ATI driver working under X.Org 7.0.0 > from rawhide? I downloaded 8.21.7 from ATI however it only supports > up to X.Org 6.9.x. > > Has anyone got this working with X.Org 7.0.0? On a related note, have anyone got either "radeon" or "ati" to work on an x86_64 lately? When I try to start X with either of these drivers the machine just freezes. The screen turns black, and no keys are working (no ctrl-alt-del, no ctrl-alt-backspace, no capslock, no numlock...) After a hard reboot I can't seem to find anything in the Xorg-logs or dmesg og /var/log/messages to shed any light on what happens. I currently use the "vesa" driver, but it refuses to give me more than 1024x768 and that looks quite ugly on an 1280x1024 LCD. The problem seems to be identical to https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=162874 but that bug was closed, and as nobody else has complained my guess is that it might only affect x86_64 (or some other subset of the Radeon 9200 SE users out there) lspci -v: 01:00.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200 SE] (rev 01) (prog-if 00 [VGA]) Subsystem: Unknown device 4953:4947 Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 11 Memory at e0000000 (32-bit, prefetchable) [size=128M] I/O ports at a800 [size=256] Memory at ff4f0000 (32-bit, non-prefetchable) [size=64K] Expansion ROM at ff4c0000 [disabled] [size=128K] Capabilities: [58] AGP version 3.0 Capabilities: [50] Power Management version 2 01:00.1 Display controller: ATI Technologies Inc RV280 [Radeon 9200 SE] (Secondary) (rev 01) Subsystem: Unknown device 4953:4946 Flags: bus master, 66MHz, medium devsel, latency 64 Memory at d8000000 (32-bit, prefetchable) [size=128M] Memory at ff4e0000 (32-bit, non-prefetchable) [size=64K] Capabilities: [50] Power Management version 2 uname -rv 2.6.15-1.1895_FC5 #1 SMP Wed Feb 1 22:57:53 EST 2006 rpm -q xorg-x11-drv-ati xorg-x11-drv-ati-6.5.7.2-1 rpm -q xorg-x11-drv-vesa xorg-x11-drv-vesa-1.0.1.2-1 Anything else I can do to debug this? Should I reopen the bug mentioned, or add a new one? Rgds. Ola Thoresen -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list