vesa driver used instead of radeon for R300

Bug #90175 reported by David Balažic
2
Affects Status Importance Assigned to Milestone
discover1 (Debian)
Fix Released
Unknown
discover1 (Ubuntu)
Fix Released
Medium
Timo Aaltonen

Bug Description

Herd 5 desktop CD, live boot

vesa is used instead of radeon driver.

If I delete the xorg.conf, X automatically uses the radeon driver and the GUI is suddenly not like a ZX Spectrum any more !
details follow

Revision history for this message
David Balažic (xerces8) wrote :
Revision history for this message
David Balažic (xerces8) wrote :
Revision history for this message
David Balažic (xerces8) wrote :

The log file when run without a xorg.conf file :

Revision history for this message
David Balažic (xerces8) wrote :

Another thing, I tried to change screen from 1280x1024 to 1024x768 (with VESA driver) and got an X crash, see the log

And it always uses the stupid 60 Hz refresh rate !

Revision history for this message
Kyle McMartin (kyle) wrote :

Please include the output of "lspci -vvnn" in your report so we can fix the driver detection. Additionally, it would help if you'd file another bug for the seperate issue of the crash.

Thanks!
  Kyle

Revision history for this message
Kyle McMartin (kyle) wrote :

Needs info, but I'm guessing this will end up being a bug on discover-data.

Changed in xorg:
status: Unconfirmed → Needs Info
assignee: nobody → kyle
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

could you run in a terminal:

discover --disable=serial,parallel,usb,ide,scsi --format="%V %M\t%S\t%D\n" video

and attach that and /var/log/casper.log so we could see why it chose vesa.

Revision history for this message
Kyle McMartin (kyle) wrote :

That's pretty messed up, I just verified that the two ATI pci ids in your Xorg.log are indeed properly configured in discover-data...

(II) PCI: 01:00:0: chip 1002,4144 card 1458,4016 rev 00 class 03,00,00 hdr 80
(II) PCI: 01:00:1: chip 1002,4164 card 1458,4017 rev 00 class 03,80,00 hdr 00

Revision history for this message
David Balažic (xerces8) wrote :

$ discover --disable=serial,parallel,usb,ide,scsi --format="%V %M\t%S\t%D\n" video
parse error reading X server string `snd-bt87x'
parse error reading X server string `snd-bt87x'
Brooktree Corporation Bt878 Audio Capture unknown unknown
ATI Technologies Inc R300 AD [Radeon 9500 Pro] XFree86 ati
ATI Technologies Inc R300 AD [Radeon 9500 Pro] (Secondary) XFree86 ati

Revision history for this message
David Balažic (xerces8) wrote :
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

There is a bug in xserver-xorg.postinst.in, which assumes that the first line is the actual one we should use. Unfortunately, it seems that this cannot be fixed reliably. If discover doesn't recognize the device (=it isn't mapped to a X driver), output is like this:

nexus6 X11 # discover --disable=serial,parallel,usb,ide,scsi --format="%V %M\t%S\t%D\n" video
parse error reading X server string `unknown'
parse error reading X server string `unknown'
Intel Corporation 82Q963/Q965 Integrated Graphics Controller unknown unknown

(yes, I edited discover-data to not know that card)

so, since you have a video capture device it has a similar output to a "unknown" one, and the script thinks you have an unsupported card and uses vesa. I don't know a way to fix this so that it won't be a) ugly b) reliable.

Revision history for this message
David Balažic (xerces8) wrote :

Is it that hard to tell video capture an gfx cards apart ?

Yesterday I experienced a small wonder. I booted a live Cd (not Ubuntu) on the same PC and :
 - it used the correct driver
 - it didn't try to make me blind with screen flickering (it used a 70 Hz vrefresh)

I guess Ubuntu's goals don't match mine.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

no need to be sarcastic, I know this sucks ;)

What I don't know is why discover lists your tv-tuner as a video card. Maybe we could just add 'tvcard' to the --disable list? Could you try running

discover --disable=serial,parallel,usb,ide,scsi,tvcard --format="%V %M\t%S\t%D\n" video

and tell us what it gives.

Revision history for this message
David Balažic (xerces8) wrote :

It returns :
Unknown or unsupported bus `tvcard'

Why is still discover 1.x used ? Debian uses v2 since 2005 (sarge aka v3.1)

Revision history for this message
David Balažic (xerces8) wrote :

I see discover2 differences between viedo outpu devices (gfx cards), that is calls "display" and video in devices, called "video".
discover1 mixes them all into "video".

Even then, xserver-xorg.postinst.in should be fixed. Why assume the first entry in the list is correct ? The list has no rule for ordering item, has it ? So it it is practically random.
Choosing a random entry from a list can't be a good plan.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

actually, could you run

discover --disable=serial,parallel,usb,ide,scsi --format="%V %M\t%S\t%D\n" video 2>/dev/null

I missed the '2>/dev/null' -part which means that error messages are directed to /dev/null, and they are not seen by the postinst. We should be able to filter out the other bogus entries somehow.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

I can handle this :)

Changed in xorg:
assignee: kyle → tepsipakki
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

reassigning, there is a patch to fix discover.

Changed in xorg:
status: Needs Info → Confirmed
Changed in discover1:
importance: Undecided → Medium
Changed in discover1:
status: Unknown → Fix Committed
Changed in discover1:
status: Fix Committed → Fix Released
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Freeze exception filed.

Changed in discover1:
status: Confirmed → In Progress
Revision history for this message
David Balažic (xerces8) wrote :

FYI: The patch did not make it into the beta.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

there is now a new version in Feisty.

Changed in discover1:
status: In Progress → Fix Released
Revision history for this message
David Balažic (xerces8) wrote :

Are there ISOs to try out ?
Or can I build them myself ?

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Try a current daily livecd, that should work.

http://cdimage.ubuntu.com/daily-live/

now the i386 version is oversized, so you have to wait until it is fixed.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

rumour has it that tomorrow the image should be usable :)

Revision history for this message
David Balažic (xerces8) wrote :

I tried http://cdimage.ubuntu.com/daily-live/20070405/feisty-desktop-i386.iso
and it uses the radeon driver.
Yoo-hoo ! ;-)

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.