Bug 448798 - On startx: monitor shuts off, system locks up
Summary: On startx: monitor shuts off, system locks up
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: 9
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Dave Airlie
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2008-05-28 20:33 UTC by John Ellson
Modified: 2018-04-11 13:39 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-12-09 22:46:57 UTC

Attachments (Terms of Use)
Logfile from failed start attempt (39.08 KB, text/plain)
2008-05-28 20:33 UTC, John Ellson
no flags Details

Description John Ellson 2008-05-28 20:33:35 UTC
Description of problem:
Attempt to use  "ATI Technologies Inc RS480 [Radeon Xpress 200G Series]"
with monitor connected to VGA port (and none to DVI port) results in the
monitor being turned off and the system locking up.

I suspect that its testing for a monitor on the DVI port?   I don't have a DVI
monitor I can try, and the DVI socket on this HP box is incompatible with a VGA
adaptor for trying a VGA monitor on the DVI port.

This is without any /etc/X11/xorg.conf

I notice that lspci seems to find two graphics cards????

    01:05.0 VGA compatible controller: ATI Technologies Inc RS480 [Radeon Xpress
200G Series]
    01:05.1 Display controller: ATI Technologies Inc Unknown device 5854

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. reboot into runlevel 3
2. login
3. startx
Actual results:
Monitor switches off.  System hangs.  No response to ctrl-alt-f1, ctrl-alt-del,
or remote login attempts.  Have to powercycle.

Expected results:
Working graphics, like with fedora-8

Additional info:
Last working driver was:
but this can't be used now that the ABI has changed.

Comment 1 John Ellson 2008-05-28 20:33:35 UTC
Created attachment 306984 [details]
Logfile from failed start attempt

Comment 2 John Ellson 2008-06-16 15:39:15 UTC
Any progress on this?  Need any info from me?  I note that the "bad" driver has
been pushed to fc8,  so perhaps you'll get a few more reports now.

Comment 3 John Ellson 2008-12-08 15:57:18 UTC
This problem appears cured after upgrading to FC10.

Comment 4 Matěj Cepl 2008-12-09 22:46:57 UTC
Thanks for letting us know.

Note You need to log in before you can comment on or make changes to this bug.