Ubuntu
xorg package

ATI Radeon 7200 not detected by x in livecd.

Bug #108327 reported by Evan Huus on 2007-04-20

This bug report is a duplicate of: Bug #103223: X incorrectly defaults to using disabled Intel onboard graphics card instead of nVidia FX5500 PCI card. Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	xorg (Ubuntu)	Confirmed	Low	Unassigned

Bug Description

My PC has an ATI Radeon 7200 graphics card (PCI connections), and a built-in Intel chipset. When using the standard i386 feisty livecd, x fails to configure itself properly.

If I use the normal boot option, it goes to a black screen after the boot splash, and nothing further happens. If I switch my monitor to the Intel port, it displays garbage.

If I boot in safe graphics mode, I get an x server error after the boot splash. The gist of the error message is that no device was found at PCI location 1:8:0. When I view the xorg.conf file from nano, there is only one device listed, which appears to be the correctly configured Intel chip. The screen section uses this device.

I managed to get it to work by adding a device to xorg.conf with the PCIBus location as "1:8:0", and the driver as "radeon". I then changed the screen section to use the new device rather than the Intel. After saving that modification and starting x, I have working, 3d accelerated graphics.

It seems to me that this isn't a driver issue, it is simply an issue of x not detecting the graphics card properly. I also have this issue with the edgy livecd, although the safe graphics mode in edgy gives a blank screen rather than an error.

Tags:

Revision history for this message

Dan O'Huiginn (daniel-ohuiginn) wrote on 2007-04-21:

Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description didn't include enough information.

Please include the information requested from [WWW] https://help.ubuntu.com/community/DebuggingXAutoconfiguration as separate attachments.

Changed in xorg:
assignee:	nobody → daniel-ohuiginn
status:	Unconfirmed → Needs Info

Revision history for this message

Evan Huus (eapache) wrote on 2007-04-21:

Output of "lspci -n" Edit (433 bytes, text/plain)

Attached is the output of "lspci -n".

Revision history for this message

Evan Huus (eapache) wrote on 2007-04-21:

Output of "sudo discover --disable..." Edit (112 bytes, text/plain)

Attached is the output of "sudo discover --disable=parallel,serial,usb,ide,scsi,pcmcia --format="%M\t%S\t%D\t%i\n" video"

Revision history for this message

Evan Huus (eapache) wrote on 2007-04-21:

Output of "sudo xresprobe " Edit (25 bytes, text/plain)

The output of "sudo xresprobe <driver>" was always exactly the same (I tried it with radeon, ati, and i810).

Revision history for this message

Evan Huus (eapache) wrote on 2007-04-21:

xorg.conf unedited - Valid Edit (3.3 KiB, text/plain)

Attached is the xorg.conf file that was configured automatically when booting in safe graphics mode.

Revision history for this message

Evan Huus (eapache) wrote on 2007-04-21:

xorg.conf edited - Valid Edit (3.4 KiB, text/plain)

Attached is the xorg.conf file with the modifications I made to it in order to get functional graphics.

Revision history for this message

Dan O'Huiginn (daniel-ohuiginn) wrote on 2007-04-21:

Thanks for providing that information.

Changed in xorg:
assignee:	daniel-ohuiginn → nobody
status:	Needs Info → Confirmed

Revision history for this message

Evan Huus (eapache) wrote on 2007-04-26:

I don't know if this is important or not, but (with the modified xorg.conf) there is a second of screen garbage after the boot splash. The login screen then appears, and it works fine. It looks like it's not loading properly the first time and is refreshing or something, but I don't really know.

Revision history for this message

Bryce Harrington (bryce) wrote on 2007-05-24:

Thanks for reporting this bug.

It sounds like there are at least two issues here. First, that in safe graphics mode it is not detecting your radeon card; safe graphics mode ought to *always* work. Second, that it is not detecting your monitor.

The second issue is already known (bug 3731), so I'm going to focus this bug report on the first issue.

However, it sounds like you've worked around the first issue. For the second issue, the workaround is to add the HorizSync and VertRefresh rates for your monitor. Currently it is using generic values which probably aren't appropriate for your monitor. Usually you can find this info from your monitor's manual, or by looking on the monitor manufacturer's website in their support channels. If you do find this info, can you please report it back here so we can add it to our database so it works in future versions of ubuntu?

Changed in xorg:
importance:	Undecided → Medium
status:	Confirmed → Needs Info

Revision history for this message

Evan Huus (eapache) wrote on 2007-05-24:

#10

My monitor is an ancient 15" Proview pv-564d. I do not have the manual anymore, and it is no longer on Proview's website. I have googled extensively and cannot find the appropriate refresh rates. This is the pertinent part of my xorg.conf, unedited:

Section "Monitor"
Identifier "Generic Monitor"
Option "DPMS"
HorizSync 28-51
VertRefresh 43-60
EndSection

Bryce Harrington (bryce) on 2007-06-02

Changed in xorg:
status:	Needs Info → Unconfirmed

Revision history for this message

Evan Huus (eapache) wrote on 2007-06-02:

#11

Unfortunately, my Proview monitor died yesterday, so I can no longer test the HorizSync and VertRefresh rates. However, I have determined that the garbage screen only appears on the Radeon: changing the screen part of my xorg.conf to use my onboard Intel i810 instead of the Radeon leaves me with no garbage screen, independent of the monitor. It seems then that it is still a driver problem, not a monitor detection problem.

Revision history for this message

Bryce Harrington (bryce) wrote on 2007-06-15:

#12

Too bad about the Proview, but let me see if I understand the remaining issues properly:

a. When booting the LiveCD, it detects your onboard video card and configures xorg.conf to use it instead of the added radeon card. (This sounds sort of like Bug #75316, except the opposite, or like bug 103223)
b. It is picking "vesa" for your onboard intel video card instead of "i810" or "intel" as it should
c. After manually fixing it to use the Radeon with the open source 'radeon' driver, it works correctly, except that there is a garbage screen that appears after the boot screen but before the login screen.

Bug c. may actually be in the splash screen rather than in xorg. Can you verify this by modifying your /boot/grub/menu.lst and removing the 'splash' option? If this makes the problem go away, then that bug is in usplash.

Changed in xorg:
importance:	Medium → Low
status:	Unconfirmed → Needs Info

Revision history for this message

Evan Huus (eapache) wrote on 2007-06-15:

#13

a. Yes, but when I plug the monitor into the onboard slot, I get garbage, despite apparently correct configuration.
b. No, that's just because I didn't know about ttys when I fixed it, so I had to boot in safe graphics mode to get to a terminal.
c. Yes.

Just a note, that if I use a bios option to force onboard, it works perfectly with the intel.

I'll try removing splash and post back.

Revision history for this message

Evan Huus (eapache) wrote on 2007-06-15:

#14

It isn't a bug in usplash. After removing the splash option, it still gives a brief screen of garbage before the login screen and after "Starting Gnome Display Manager".

Bryce Harrington (bryce) on 2007-06-15

Changed in xorg:
status:	Needs Info → Confirmed

Revision history for this message

Evan Huus (eapache) wrote on 2007-06-16:

#15

When logging out or switching users, there is also a garbage screen before the login window appears. Does this mean that it's a bug in the login window, not x, or does x restart in those cases?