Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
I have managed to make dri/drm work with my X600SE PCIE card.
The machine is a Toshiba M70 laptop.
I've built drm and r300_dri.so from CVS.
I'm using X11R7 from ubuntu dapper.
Unfortunately that didn't worked 'out of the box'
as the pciid of my card seems to be rather unknown
here is the output of lspci:
0000:01:00.0 VGA compatible controller: ATI Technologies Inc: Unknown
device 5462 (prog-if 00 [VGA])
Subsystem: Toshiba America Info Systems: Unknown device ff06
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-
Latency: 0, Cache Line Size: 0x08 (32 bytes)
Interrupt: pin A routed to IRQ 169
Region 0: Memory at c8000000 (32-bit, prefetchable) [size=128M]
Region 1: I/O ports at 3000 [size=256]
Region 2: Memory at b8100000 (32-bit, non-prefetchable) [size=64K]
Expansion ROM at b8120000 [disabled] [size=128K]
Capabilities:  Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities:  #10 
Capabilities:  Message Signalled Interrupts: 64bit+
Address: 0000000000000000 Data: 0000
so basically what I've done is adding:
0x1002 0x5462 CHIP_RV350|CHIP_IS_MOBILITY "ATI Radeon X600 SE"
#define PCI_CHIP_RV370_5462 0x5462
Here is a part of my xorg.conf: (I've forced the pciid for the ati driver)
Identifier "ATI Technologies, Inc. Radeon X600 (RV380)"
Option "AccelMethod" "exa"
Option "DynamicClocks" "true"
Option "BIOSHotkeys" "true"
and ... that failed, with an "irq 16: nobody cared (try booting with the
error upon Xorg startup... why ? Because I'm also using the vesa
My diagnosis was that when the drm module loads it detects the presence
framebuffer and fallback to 'stealth mode' probe. In this mode
NOT called. The problem is that vesafb doesn't call pci_register_driver
either. I think
that's the reason for the misdetection of the irq number.
I've found two workarounds for this bug:
- Boot with vga=normal (no framebuffer)
- Boot with pci=routeirq (which is my preferred solution)
With that the irq is correctly routed to irq 169;
Everything now seems to be working (glxinfo, glxgears, gl-based
screensaver, ppracer, ...).
So basically I'm wondering:
-If the 0x5462 id could be added ?
-Is there a more robust solution for the irq bug ?
By the way, Xorg doesn't work (lots of display weirdness and random
crash) with the
radeonfb driver, I was wondering if it's a specific bug or if radeon drm
is known to be an impossible combination.
(please CC me, I'm not subscribed)