Ubuntu
discover1-data package

Dapper: IBM T60p, ATI Mobility FireGL V5200 not detected

Bug #46527 reported by Alex Bligh
8
Affects Status Importance Assigned to Milestone
discover1-data (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

On installing Dapper (Daily ISO as of 24 May 06), the wrong screen driver is detected. It should install fglrx, but instead installs VESA.

This is corrected by
1. Installing the fglrx X driver, kernel modules etc.
2. Performing the following modification to /etc/X11/xorg.conf

Section "Device"
 Identifier "ATI Technologies, Inc. ATI Default Card"
 Driver "fglrx" <----- ADD THIS LINE
 #Driver "vesa" <---- COMMENT OUT THIS LINE
 BusID "PCI:1:0:0"
 ChipID 0x71c5 <----- ADD THIS LINE
EndSection

Clearly the problem here is that the fglrx detection routines are missing the above ChipID as one that works with fglrx. I believe the display driver is a ATI Mobility FireGL V5200.

After this mod has been made, accelerated screen drawing works perfectly.

Revision history for this message
Simon Law (sfllaw) wrote :

Hi Alex,

Please run the following commands:
$ lspci -vn | tee /tmp/lspci-vn.log
$ sudo discover --enable=isa,pci --format="%S\t%D\n" video | tee /tmp/discover.log
$ sudo xresprobe ati | tee /tmp/xresprobe.log
$ sudo xresprobe fglrx | tee -a /tmp/xresprobe.log

Then, please attach /tmp/lspci-vn.log, /tmp/discover.log, and
/tmp/xresprobe.log to this bug report using the following link:
https://launchpad.net/distros/ubuntu/+bug/46527/+addattachment

Thanks.

Revision history for this message
Alex Bligh (ubuntu-alex-org) wrote : discover.log

discover.log as requested

Revision history for this message
Alex Bligh (ubuntu-alex-org) wrote : lspci-vn.log as requested

lspci-vn.log.as requested

Revision history for this message
Alex Bligh (ubuntu-alex-org) wrote : xresprobe.log as requested

xresprobe.log as requested

Revision history for this message
Paul Sladen (sladen) wrote :

discover1-data 1002:71c4 -> Radeon Mobility

Changed in xserver-xorg:
status: Needs Info → Confirmed
Revision history for this message
Paul Sladen (sladen) wrote :

Alex: before I upload this change can you make sure that your card works with the 'ati' open-source driver. Because 'fglrx' is the binary driver we can't make it by default, but can at least add the missing ID to the database so that it doesn't default to 'vesa'.

Revision history for this message
Alex Bligh (ubuntu-alex-org) wrote :

Paul,

OK, I did this:

Replace 'Driver "fglrx"' by 'Driver "ati"' leaving ChipID line: X does not start as the driver complains that the ChipID line is not valid.

Replace 'Driver "fglrx"' by 'Driver "ati"' commenting out ChipID line: X does not start as the driver complains that it cannot detect an ATI chipset at the bus ID specified.

The same occurs (in both cases) if I use "radeon" not "ati".

It seems to me that the underlying problem here is that the open-source ATI driver does not detect the chipset concerned. A quick google suggests it has the same programming interface as some of the other Radeon Mobility chips so perhaps the non-proprietary driver just needs to be tweaked to detect it.

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

Other bug subscribers

Remote bug watches

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