ATI Radeon X800XL - wrong driver selected, and fails unless both monitor ports connected

Bug #38649 reported by Richard Downer
14
Affects Status Importance Assigned to Milestone
xserver-xorg-video-ati (Ubuntu)
Incomplete
Medium
Ubuntu-X

Bug Description

Testing Kubuntu Dapper Flight 6 on AMD64. On the clean out-of-the-box installation, the X server fails to start. On logging in at the console, Xorg.0.log finishes with:

(WW) ATI: PCI Mach64 in slot 1:0:0 could not be detected!
(WW) ATI: PCI Mach64 in slot 1:0:1 could not be detected!
(EE) No devices detected.

After some research, it seems that the Xserver is selecting the wrong display driver. xorg.conf contains 'Driver "ati"' when apparently it should be 'Driver "radeon"'.

After making this change, the X server will run, but only at a low resolution. Examining Xorg.0.log, it seems that all the higher resolutions are being filtered out because X believes that the monitor's specifications are not compatible with the modes. However this is incorrect; my TFT monitor is being correctly detected - the monitor model name and H sync/V sync values do appear in the log.

However I also noticed in the log references to the secondary monitor port, which I have not connected. It seemed to suggest that the hsync/vsync specifications were being reset to conservative defaults because no DDC monitor was detected.

When I plugged in the secondary monitor connection (actually to the second input on the same TFT monitor as the primary connection) X worked properly and showed full resolution.

Xorg.0.log and xorg.conf files to follow shortly.

Revision history for this message
Richard Downer (rd-launchpad) wrote : xorg.conf on first boot after installation

xorg.conf on first boot after installation

Revision history for this message
Richard Downer (rd-launchpad) wrote : Xorg.0.log after first boot which failed to start X at all

Xorg.0.log after first boot which failed to start X at all

Revision history for this message
Richard Downer (rd-launchpad) wrote : xorg.conf after correcting the Driver

xorg.conf after correcting the Driver

Revision history for this message
Richard Downer (rd-launchpad) wrote : Xorg.0.log with corrected driver and only one monitor attached

Xorg.0.log with corrected driver and only one monitor attached. In this configuration, X starts at a low resolution only

Revision history for this message
Richard Downer (rd-launchpad) wrote : Xorg.0.log after Driver config corrected and with both monitor ports connected

Xorg.0.log after Driver config corrected and with both monitor ports connected. In this configuration the server worked as expected.

Revision history for this message
Tormod Volden (tormodvolden) wrote :

The wrong driver issue is probably a duplicate of bug #23356.

Revision history for this message
Barry deFreese (bddebian) wrote :

Richard. A fix was released for 23356, does this resolve your problem? Thank you.

Changed in xorg:
status: Unconfirmed → Needs Info
Revision history for this message
Richard Downer (rd-launchpad) wrote :

Tormod, Barry,

I have re-tested this using the Kubuntu LTS Beta 2 live CD but unfortunately the problem is still there and the symptoms are the same:

  * Once the OS has finished loading I am left with the bootsplash Kubuntu screen and nothing else
  * xorg.conf has driver set to "ati" - I manually changed this to "radeon"
  * Restartd kdm, but it came up in a low resolution
  * Plugged in the second monitor port on the graphics card and restarted kdm; this time it came up in the correct resolution

I have also just retested the both-monitor-ports problem on my existing Dapper installation after an aptitude update and dist-upgrade - again, no improvement, if both monitor ports are not connected X picks a low display resolution.

Changed in xorg:
assignee: nobody → ubuntu-x-swat
Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

Marking this as duplicate of bug #28925, which is generally about the unfortunate need to specify "radeon" manually, generally making Ubuntu experience 0 if one doesn't know how to edit xorg.conf manually.
The monitor issue (640x480 because primary monitor resolutions not detected correctly) is a separate bug, and also known.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.