i810 not loaded: i915GMS not detected on Dell X1

This problem is still present on Dapper Flight 5 (freshly installed from Install CD).

I also tried glxgears, it is dead slow (2 fps?).

Here is the graphics related output of lspci:

0000:00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 03)
        Subsystem: Dell: Unknown device 01a3
        Flags: bus master, fast devsel, latency 0
        Capabilities: <available only to root>

0000:00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03) (prog-if 00 [VGA])
        Subsystem: Dell: Unknown device 01a3
        Flags: bus master, fast devsel, latency 0, IRQ 11
        Memory at dff00000 (32-bit, non-prefetchable) [size=512K]
        I/O ports at ec38 [size=8]
        Memory at c0000000 (32-bit, prefetchable) [size=256M]
        Memory at dfec0000 (32-bit, non-prefetchable) [size=256K]
        Capabilities: <available only to root>

0000:00:02.1 Display controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)
        Subsystem: Dell: Unknown device 01a3
        Flags: bus master, fast devsel, latency 0
        Memory at dff80000 (32-bit, non-prefetchable) [size=512K]
        Capabilities: <available only to root>

This is the logfile of X.org.

Please past:

  lspci -n

I just realized that this is a followup on bug 30803. When using the i810 driver, direct rendering works again and OpenGL is fast again.

Whilst this is a bug, the output from the logfiles is still import for your particular version of laptop.

If you have 8086:2592 in your 'lspci -n', this is a duplicate of bug #30803 now marked as a duplicate of bug #35473.

Yes, this is the case:

$ lspci -n
0000:00:00.0 0600: 8086:2590 (rev 03)
0000:00:02.0 0300: 8086:2592 (rev 03)
0000:00:02.1 0380: 8086:2792 (rev 03)
0000:00:1c.0 0604: 8086:2660 (rev 03)
0000:00:1d.0 0c03: 8086:2658 (rev 03)
0000:00:1d.1 0c03: 8086:2659 (rev 03)
0000:00:1d.2 0c03: 8086:265a (rev 03)
0000:00:1d.3 0c03: 8086:265b (rev 03)
0000:00:1d.7 0c03: 8086:265c (rev 03)
0000:00:1e.0 0604: 8086:2448 (rev d3)
0000:00:1e.2 0401: 8086:266e (rev 03)
0000:00:1e.3 0703: 8086:266d (rev 03)
0000:00:1f.0 0601: 8086:2641 (rev 03)
0000:00:1f.1 0101: 8086:266f (rev 03)
0000:00:1f.3 0c05: 8086:266a (rev 03)
0000:01:00.0 0200: 14e4:1677 (rev 01)
0000:02:01.0 0607: 1180:0476 (rev b3)
0000:02:01.1 0c00: 1180:0552 (rev 08)
0000:02:01.2 0805: 1180:0822 (rev 17)
0000:02:03.0 0280: 8086:4220 (rev 05)

the bug has been corrected in bug #35473

What you mean is "a possible patch has been tested in..." :)

You are right ;) Any comment about the patch ?