[gm45] i810 kernel module doesn't load since version 2.6.31-17-generic-pae or greater

[randomas]

Binary package hint: xserver-xorg-video-intel

Since the sistem was updated to kernel 2.6.31-17-generic-pae or greater (currently 2.6.31-18, and it is what was used to generate bug report), the system (ubuntu karmic gnome) switched to using the vesa driver to to the i810 driver not loading.
As well as what the apport-bug generated, I've attached the relevant dmesg section (gives errors about i915).

This is from the xorg.log

 (II) LoadModule: "intel"
(II) Loading /usr/lib/xorg/modules/drivers//intel_drv.so
(II) Module intel: vendor="X.Org Foundation"
        compiled for 1.6.4, module version = 2.9.0
        Module class: X.Org Video Driver
        ABI class: X.Org Video Driver, version 5.0
(II) LoadModule: "i810"
(WW) Warning, couldn't open module i810
(II) UnloadModule: "i810"
(EE) Failed to load module "i810" (module does not exist, 0)
(II) LoadModule: "vesa"

this is what I get if I try and modprobe i810 manually:

FATAL: Error inserting i810 (/lib/modules/2.6.31-18-generic-pae/kernel/drivers/gpu/drm/i810/i810.ko): Unknown symbol in module, or unknown parameter (see dmesg)

and relevant dmesg
[ 4447.404830] i810: disagrees about version of symbol drm_core_get_reg_ofs
[ 4447.404838] i810: Unknown symbol drm_core_get_reg_ofs
[ 4447.405039] i810: disagrees about version of symbol drm_irq_uninstall
[ 4447.405043] i810: Unknown symbol drm_irq_uninstall
[ 4447.405452] i810: disagrees about version of symbol drm_exit
[ 4447.405456] i810: Unknown symbol drm_exit
[ 4447.405652] i810: disagrees about version of symbol drm_core_ioremapfree
[ 4447.405656] i810: Unknown symbol drm_core_ioremapfree
[ 4447.406014] i810: disagrees about version of symbol drm_init
[ 4447.406018] i810: Unknown symbol drm_init
[ 4447.406241] i810: disagrees about version of symbol drm_core_ioremap
[ 4447.406245] i810: Unknown symbol drm_core_ioremap

At the moment the work around for this is to boot into the 2.6.31-16 kernel and everything works fine, but it does seem there's been a regression in an update. I don't have an xorg.conf file, the system should be able (or used to be able to) select the right settings automagically.

Hope this is fixed soon.

TIA

ProblemType: Bug
Architecture: i386
Date: Mon Feb 1 13:16:29 2010
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
MachineType: ASUSTeK Computer Inc. UL30VT
Package: xserver-xorg-video-intel 2:2.9.0-1ubuntu2.1
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-18-generic-pae root=UUID=bd47e08a-3ce3-4103-8bae-9a3e938e5886 ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-18.55-generic-pae
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu10
 libgl1-mesa-glx 7.6.0-1ubuntu4
 libdrm2 2.4.14-1ubuntu1
 xserver-xorg-video-intel 2:2.9.0-1ubuntu2.1
 xserver-xorg-video-ati 1:6.12.99+git20090929.7968e1fb-0ubuntu1
SourcePackage: xserver-xorg-video-intel
Uname: Linux 2.6.31-18-generic-pae i686
XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/xorg.conf'
dmi.bios.date: 11/04/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 203
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UL30VT
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr203:bd11/04/2009:svnASUSTeKComputerInc.:pnUL30VT:pvr1.0:rvnASUSTeKComputerInc.:rnUL30VT:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: UL30VT
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
fglrx: Not loaded
system:
 distro: Ubuntu
 architecture: i686kernel: 2.6.31-18-generic-pae

[lspci]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07)
     Subsystem: ASUSTeK Computer Inc. Device [1043:1af2]
01:00.0 VGA compatible controller [0300]: nVidia Corporation Device [10de:0a74] (rev ff) (prog-if ff)

[Moritz Naumann (mnaumann)]

I think I am running into the same issue.

(II) LoadModule: "i810"
(WW) Warning, couldn't open module i810
(II) UnloadModule: "i810"
(EE) Failed to load module "i810" (module does not exist, 0)
(II) LoadModule: "vesa"
(II) Loading /usr/lib/xorg/modules/drivers//vesa_drv.so

I also run Karmic and similar hardware (Asus UL30A). I assume the driver which X is trying to load there is /usr/lib/xorg/modules/drivers/intel_drv.so whch does exist (and has the same permissions as other drivers):
-rw-r--r-- 1 root root 664K 2010-01-10 11:49 /usr/lib/xorg/modules/drivers/intel_drv.so

However, I realize the i915 module is loaded....
~$ lsmod|grep -E '[[:blank:]]i[0-9]+'
drm 193856 2 i915
i2c_algo_bit 7076 1 i915
video 23612 1 i915
intel_agp 32816 2 i915

[randomas (randomas)]

Moritz you're probably right, most of the errors i get in dmesg are for the i915, but I still can't quite point the finger on where the issue is, furthermore I found that the i810 is just a warning that occurs anyway (even when the intel card starts properly). So the problemis with i915. Using the 16 point release of the kernel solves the problem for me.

I'm still stumped as to what causes it though.

[randomas (randomas)]

I rebooted into the non working kernel and using: lsmod|grep -E '[[:blank:]]i[0-9]+'
I got nothing, so that confirms it.
When I use that command and the x-server is working properly I get the same out put as Moritz.
The results of dmesg|grep i915 are attached.

[randomas (randomas)]

kernel 2.6.31-19-generic-pae has fixed the issue for me.

Thank you!

[William Bustos Rodriguez (willbrod)]

@randomas, the upgrade to kernel 2.6.31.19 brough the issue to me. Kernel 2.6.31.17 was working propertly and after upgrade nothing.

(EE) Failed to Load module "i810", module does not exist
(EE) Open /dev/fb0: no such file or directory
(EE) Intel (0): no modes
(EE) Screen(s) found, but none have usable configuration.

So, nothing so far.

[randomas (randomas)]

@William, that seems to be a different error, but I'm not competent enough to say for sure.
In my case the issue was actually with i915 not loading properly.
It turns out that i810 is actually deprecated, with a working system I still get the i810 warning but everything is working fine.
What hardware are you running? It would be helpful if you could add bug report documentation using apport, that way the knowledgeable people can really help you.

[Vikram Dhillon (dhillon-v10)]

This issue was reported against karmic, so can you confirm if this issue exists with the most recent Lucid Lynx 10.04 Alpha release? ISO CD images are available at http://cdimage.ubuntu.com/releases/lucid/ . Thanks in advance.

[Jeffrey Walton (noloader)]

Same issue. Dell GX 270, Intel P4, 82865G Intel Graphics Controller. Available modes are 800x600 and 640x480.

$ cat Xorg.0.log
...
(II) LoadModule: "i810"
(WW) Warning, couldn't open module i810
(II) UnloadModule: "i810"
(EE) Failed to load module "i810" (module does not exist, 0)

$ sudo apt-get install xserver-xorg-video-intel
Reading package lists... Done
Building dependency tree
Reading state information... Done
xserver-xorg-video-intel is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

$ uname -a
Linux descartes 2.6.31-19-generic #56-Ubuntu SMP Thu Jan 28 01:26:53 UTC 2010 i686 GNU/Linux

[Bryce Harrington (bryce)]

[Resetting to incomplete since we need a response from the original reporter on this].

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]