Red Hat Bugzilla – Bug 162874
Radeon9200Pro freezes system under FC4
Last modified: 2007-11-30 17:11:09 EST
Description of problem:
Video Card ATI Radeon 9200PRO
Daytek Monitor 719BF
System freezes when X windows is started uisng startx.
Tried using VESA but fails to start X window without freezing.
Version-Release number of selected component (if applicable):
Everytime. Haven't been able to use the system in grphical mode!
Steps to Reproduce:
1. boot in grphical mode
2. boot in runlebvel 3 and use startx
Blank screen; no other terminals accessible!
X window starts in all its glory
Your problem may be fixed in the latest rawhide version.
Can you test xorg-x11-6.8.2-44 ?
Similar problem using LCD1515 with Radeon9200PRO. Motherboard is A8VDeluxe
with AMD A64 3000+. FC4 cannot probe this monitor during installation.
Tried backing off to FC3, 64-bit and 32-bit versions and have the same sort of
problems. Looks like Fedora is wait and see for me!
David, have you tried the latest rawhide version?
Oliver. No I have not. I am a newbie to Fedora and cannot find a set of iso
images that will allow me to install a working system.
I have an athlon64 + radeon 9200pro and had no problems installing or using it.
I'm still using an old CRT though. My motherboard is a Abit KV8 Pro.
Please see bug #161242, and test the workarounds indicated in that report
to see if the same problem affects you.
Also, try the latest rawhide xorg-x11 to see if that solves the problem or
Do either of these solutions solve the problem? Please indicate that, and
attach your X server log file, config file, and other related details if
the problem persists after testing these two items.
Setting status to "NEEDINFO_REPORTER", and awaiting requested information.
Closing bug, as the original reporter hasn't replied to the bug since
it was filed with any additional information, and there is no response
to our requests to test the latest update.
Assuming the problem was either transient, or a local issue, or has
been fixed in a Fedora update. If the problem does still exist in
the latest Fedora update, provide a status update in the bug report,
attach your X server log file and config file as individual uncompressed
file attachments, and provide any details that might be helpful in
further diagnosing the problem, then set the bug report to REOPENED
Setting state to "CURRENTRELEASE" under the above assumption.