Flight 2 installation selected vesa instead of i810

Created an attachment (id=5349)
my xorg.conf file

Created an attachment (id=5350)
my Xorg.0.log file

transient fl2 issue

The problem is still present with a fresh install of the latest Dapper Daily
(20060107 version)

I still have the same problem with a fresh install of Flight 3. The installer gives me the vesa driver by default. To get i810, I must go and manually select it with a dpkg-reconfigure xserver-xorg

Confirmed at: https://launchpad.net/distros/ubuntu/dapper/+bug/6619

I also appear to have this same bug on a Sony Vaio TX650P.

The video chip is an i915, but the driver installed by flight 3 is VESA.

Please let me know if there is any more information you would like me to provide.

-Matt

Bug still present with fresh install of Dapper Flight 4

I've got the same problem on a Dell Latitude X1 (i915GMS). Here is the relevant output of lspci -v:

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: [d0] Power Management version 2

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: [d0] Power Management version 2

For me manual selection does not provide any help, since with i810 no image is displayed. So detection is not the only problem.

0000:00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express P rocessor to DRAM Controller (rev 04)
        Subsystem: Uniwill Computer Corp: Unknown device 9050
        Flags: bus master, fast devsel, latency 0
        Capabilities: [e0] #09 [2109]

0000:00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GM L Express Graphics Controller (rev 04) (prog-if 00 [VGA])
        Subsystem: Uniwill Computer Corp: Unknown device 9800
        Flags: bus master, fast devsel, latency 0, IRQ 10
        Memory at ffe80000 (32-bit, non-prefetchable) [size=512K]
        I/O ports at ec00 [size=8]
        Memory at d0000000 (32-bit, prefetchable) [size=256M]
        Memory at ffe40000 (32-bit, non-prefetchable) [size=256K]
        Capabilities: [d0] Power Management version 2

0000:00:02.1 Display controller: Intel Corporation Mobile 915GM/GMS/910GML Expre ss Graphics Controller (rev 04)
        Subsystem: Uniwill Computer Corp: Unknown device 9800
        Flags: fast devsel
        Memory at 40000000 (32-bit, non-prefetchable) [disabled] [size=512K]
        Capabilities: [d0] Power Management version 2

This bug is still present on Dapper Flight 5.

The recent update of discover1-data should solve this problem:

discover1-data (1.2005.11.25ubuntu2) dapper; urgency=low

  * 8086:2592 Intel 915GM/GMS/910GML Express Graphics Controller [Malone: #35473]
  * 8086:2782 82915G Express Chipset Family Graphics Controller [Malone: #28262]
 * 8086:2792 Mobile 915GM/GMS/910GML Express Graphics Controller [Malone: #28262]

 -- Paul Sladen <email address hidden> Wed, 22 Mar 2006 03:08:18 +0000

I have tested it by running discover1; before this update, the video driver to use was identified as "unknown". Now it is identified as "i810".