New ATI chipset not recognized (PCI 1002:71c4) [also radeonfb]

Bug #36316 reported by Michael Milligan
28
Affects Status Importance Assigned to Milestone
discover-data (Ubuntu)
Fix Released
Medium
Unassigned
xserver-xorg-video-ati (Ubuntu)
Invalid
Medium
Ubuntu-X

Bug Description

Testing Dapper Flight 5. Just received a brand new Thinkpad T60p (model 2007-86U). Booted up Flight 5 install CD, base system and everything installed just fine. On reboot, Xorg failed to start.

First, lspci -vv:
...
0000:01:00.0 VGA compatible controller: ATI Technologies Inc: Unknown device 71c4 (prog-if 00 [VGA])
        Subsystem: Lenovo: Unknown device 2007
        Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Interrupt: pin A routed to IRQ 11
        Region 0: Memory at d0000000 (32-bit, prefetchable) [size=256M]
        Region 1: I/O ports at 2000 [size=256]
        Region 2: Memory at ee100000 (32-bit, non-prefetchable) [size=64K]
        Expansion ROM at ee120000 [disabled] [size=128K]
        Capabilities: [50] Power Management version 2
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [58] #10 [0011]
        Capabilities: [80] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
                Address: 0000000000000000 Data: 0000

Revision history for this message
Michael Milligan (milli) wrote : /var/log/Xorg.0.log

Next, the Xorg log.

Revision history for this message
Susan Cragin (susancragin) wrote :

This may be a similar problem to
bug 32368

Revision history for this message
Michael Milligan (milli) wrote :

Similar, yes. The X300 in the Dell is a relatively recent chipset too.

I have since learned that the chipset in my T60p is the M56, based on the RV530 core, so it will be similar if not identical to the X1600 PCI express cards.

I am experimenting with just adding the PCI identifier to the radeonfb driver in the kernel and the radeon/ati driver in Xorg...

Revision history for this message
Stefan van der Walt (stefanv) wrote : ATI Mobility Radeon X1400 not recognised

This driver also fails to recognise my X1400.

$ lspci | grep ATI
0000:01:00.0 VGA compatible controller: ATI Technologies Inc: Unknown device 7145

$ startx
...
X Window System Version 7.0.0
...
(EE) No devices detected.

The only driver that worked thus far was "vesa" (at 1024x768 only) and the unsupported fglrx binary driver from ATI.

Paul Sladen (sladen)
Changed in xserver-xorg-driver-ati:
status: Unconfirmed → Confirmed
Revision history for this message
Michael Milligan (milli) wrote :

Forgot to post back results... I added the PCI ID to the radeon driver and rebuilt the kernel. No worky. It just pukes it's guts out. Nothing on screen. I've since learned that the output engine is very different, and the 2D core isn't even Radeon-based in this chipset.

If I use the 'fglrx' driver from linux-restricted-modules (>=2.6.15.9.1), and cheat by telling the binary fglrx driver (which is >= 8.24.8) that the Chip ID is 0x71c5 in the xorg.conf file, then it works flawlessly.

Changed in xserver-xorg-driver-ati:
assignee: nobody → ubuntu-x-swat
status: Unconfirmed → Confirmed
Revision history for this message
Michael Milligan (milli) wrote :

With the upgrade of linux-restricted-modules (>= 2.6.15.11-1) and xorg-driver-fglrx to include version 8.25.18 of the fglrx proprietary ATI driver, PCI id 1002:71c4 is now recognized by the driver and works just peachy.

I've seen/heard/found no news about updated ati/radeon open source drivers to support this chipset.

Revision history for this message
DaveAbrahams (boostpro) wrote : A problem remains in 6.06 release ISO

Currently the release version of the live CD will not start kdm on a Thinkpad T60p. The report is that "no devices are found." It may now be detecting the driver, since it comes up as ATI, but I don't think there's an appropriate module installed. I'd be happy to provide more detail if anyone asks.

FWIW, the regular ubuntu live CD boots up flawlessly on this machine.

Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

Please check if the Xorg.0.log gives, in addition to ati blurb, finally something like "No Mach64 device detected" (a bit longer line, though). If there is such, just mark this as duplicate of bug #28925.

Revision history for this message
DaveAbrahams (boostpro) wrote :

I'm travelling right now and not in a position to test it; If you remind me in two weeks I might be able to do that. Sorry

Revision history for this message
Michael Milligan (milli) wrote :

I think this particular bug can be closed. We're just stuck with using ATI's proprietary fglrx driver on laptops with recent ATI chipsets, as supplied in Dapper by an appropriate linux-restricted-modules-* package, along with xorg-driver-fglrx and fgrlx-control.

Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

After googling I found out that it has a X1xxx/FireGLV5200-series (ie. R500-class) card. Yes, no need to try, it just doesn't work.

There is actually a working 2D driver for these cards already written, unfortunately ATI/AMD has not given the coder a permission to release it (the coder is under NDA). They have not denied it, but because permission is needed nothing has been going forward. Not too nice.

I'd suggest changing the importance to "Wishlist", since there's nothing Ubuntu can do about this. It's up to AMD.

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

Well hang on, if you have proprietary modules (i.e. restricted) enabled, it doesn't (T60p - marked as a dupe of this bug) detect the chipset and install that driver, which it ought to (does with other chipset IDs). That is a bug Ubuntu can fix. Getting ATI to release proprietary drivers is (sadly) not something we can fix. Given the existing proprietary driver works, all I'm hoping is it will work no less badly than other chipsets using that driver.

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

oops - "no less badly" should read "no less well" :-)

Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

Closed source fglrx is not installed automatically for any card currently. The restricted modules are there, yes, but not the xorg-driver-fglrx, and even installing xorg-driver-fglrx does not change Xorg.conf to use "fglrx" instead of "ati". The open source drivers work for most cards, including X300 - X850 series.

Anyway, this has nothing to do with the open source ati driver except for the fact that it would be nice if ATI would allow supporting these X1000-series cards. So putting "rejected" on the xserver-xorg-video-ati part.

I think the plans for feisty included allowing automatic use of a proprietary driver for the X1300 - X1950 series that have not even 2D support in the open source driver, so leaving discover1-data - ie. your wish might come true and the proprietary driver would be installed for your device without manual installation / Xorg.conf modifying.

Changed in xserver-xorg-video-ati:
status: Confirmed → Rejected
Revision history for this message
gagarine (gagarine) wrote :

same problem with ati chip 71d4 on my t60p

I put 71d4 on the pci database ( http://pciids.sourceforge.net/ ).

Juste update the pci database -> sudo update-pciids

before:
01:00.0 VGA compatible controller: ATI Technologies Inc Unknown device 71d4

after:
01:00.0 VGA compatible controller: ATI Technologies Inc M56GL [Mobility FireGL V5250]
----

WARNING:
Why the 7.04 Feisty Fawn pci database is not up to date??

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

New discover-data recognizes M56GL [ATI Mobility FireGL V5200] correctly, but as you know the free driver does not support it, so it still uses vesa by default.

Changed in discover1-data:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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