xorg fails with module i810 error (module does not exist

Bug #431955 reported by RagnarokAngel
62
This bug affects 12 people
Affects Status Importance Assigned to Milestone
xserver-xorg-video-intel (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: xorg

Updated Karmic yesterday and I can not get x running running startx begins to boot up x, then fails with (EE) Failed to load module "i810" (module
does not exist, 0) then I get dropped back to the shell

Problem persists after running an update right before reporting this bug.

ProblemType: Bug
Architecture: i386
Date: Thu Sep 17 11:49:59 2009
DistroRelease: Ubuntu 9.10
MachineType: TOSHIBA Satellite A135
Package: xorg 1:7.4+3ubuntu5
ProcCmdLine: root=UUID=05f2458d-2464-4319-b704-1b0103314754 ro single
ProcEnviron:
 PATH=(custom, no user)
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.34-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu5
 libgl1-mesa-glx 7.6.0~git20090817.7c422387-0ubuntu4
 libdrm2 2.4.13-1ubuntu1
 xserver-xorg-video-intel 2:2.8.1-1ubuntu1
 xserver-xorg-video-ati 1:6.12.99+git20090825.fc74e119-0ubuntu1
SourcePackage: xorg
Uname: Linux 2.6.31-10-generic i686
XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/xorg.conf'
Xrandr: Error: command ['xrandr', '--verbose'] failed with exit code 1: Can't open display
dmi.bios.date: 05/21/2007
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V1.50
dmi.board.name: IAKAA
dmi.board.vendor: TOSHIBA
dmi.board.version: 1.00
dmi.chassis.asset.tag: *
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnTOSHIBA:bvrV1.50:bd05/21/2007:svnTOSHIBA:pnSatelliteA135:pvrPSAD0U-05400P:rvnTOSHIBA:rnIAKAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
dmi.product.name: Satellite A135
dmi.product.version: PSAD0U-05400P
dmi.sys.vendor: TOSHIBA
fglrx: Not loaded
glxinfo: Error: command ['glxinfo'] failed with exit code 255: Error: unable to open display
setxkbmap: Error: command ['setxkbmap', '-print'] failed with exit code 255: Cannot open display "default display"
system:
 distro: Ubuntu
 architecture: i686kernel: 2.6.31-10-generic
xdpyinfo: Error: command ['xdpyinfo'] failed with exit code 1: xdpyinfo: unable to open display "".
xkbcomp:
 Error: command ['xkbcomp', ':0', '-w0', '-'] failed with exit code 1: Error: Cannot open display ":0"
                   Exiting

[lspci]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03)
     Subsystem: Toshiba America Info Systems Device [1179:ff02]

Revision history for this message
RagnarokAngel (ragnarokangel-s) wrote :
Bryce Harrington (bryce)
Changed in xorg (Ubuntu):
status: New → Confirmed
Revision history for this message
Manuel Siggen (manuel-siggen) wrote :

Same problem here since today (26th of september). I'm using an Thinkpad X40 with an Intel 82852/855GM (rev 02) graphic controller.

The strange thing is : Xorg fails to load the i810 module, but I think it was using the i815 module before...

Revision history for this message
Manuel Siggen (manuel-siggen) wrote :

Yesterday update brought new version of kdm, kubuntu-minimal and kubuntu-desktop. After that I did a

    sudo dpkg-reconfigure xorg

... and now X is starting again.

Revision history for this message
Toni Ruottu (toni-ruottu) wrote :

I'm on a Lenovo Thinkpad T500. My Xorg falls back to a generic vga driver with the same error...

cyberix@eval:~$ cat /var/log/Xorg.0.log|grep "(EE)"
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(EE) Failed to load module "i810" (module does not exist, 0)
(EE) GLX error: Can not get required symbols.

So I do get a desktop, but acceleration doesn't work.

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

That error message is irrelevant. The correct one in this case is in the end

(II) intel(0): EDID for output TV1
 ddxSigGiveUp: Closing log

affects: xorg (Ubuntu) → xserver-xorg-video-intel (Ubuntu)
Revision history for this message
Ilmari Vacklin (wolverian) wrote :

Timo: Are you working on this?

Revision history for this message
RagnarokAngel (ragnarokangel-s) wrote :

I personally don't have this issue anymore, so I don't know what was fixed/changed.

Revision history for this message
indrek (indrek-seppo) wrote :

I had problem with same kind of symptoms (upgraded to karmic today, failed to load i810). Both with my old xorg.conf and without any.

What helped was a new xorg.conf file with

Section "Device"
        Identifier "Configured Video Device"
        driver "intel"
EndSection

Section "Monitor"
        Identifier "Configured Monitor"
EndSection

Section "Screen"
        Identifier "Default Screen"
        Monitor "Configured Monitor"
        Device "Configured Video Device"
EndSection

The important part being driver "intel" in "Device" section.

I actually upgraded to x-swat repository also (and I run upgraded drivers at the moment), but this might be irrelevant, as without xorg.conf file mentioned it didnt work.

Hope this might help people with similar problem..

Revision history for this message
Motin (motin) wrote :

Using intel driver did remove the message but not solve the issue at least for me. It worked great before the latest updates... which makes me ask if anyone know how to restore the packages to the working versions?? What packages etc?

Please don't say that we have to wait for a fix to be released which could take weeks, under which time the computer is basically useless with a ultraslooooooooooooooooooow interface... A restore routine would make it possible to use the computer and testing other stuff while waiting for a fix at least...

(Hopefully someday we can have a feature like this: http://brainstorm.ubuntu.com/idea/628/ making this kind of restore easy)

Revision history for this message
Motin (motin) wrote :

FYI, Whatever problem I had is now gone after latest updates. Can use the computer again.

Bryce Harrington (bryce)
tags: added: karmic
Bryce Harrington (bryce)
description: updated
Revision history for this message
Toni Ruottu (toni-ruottu) wrote :

Errors with my Intel card might have been different from this bug. However, I got rid of them by removing restricted ATI driver packages. So, in case some of you have restricted driver packages installed for other video cards, I'd try removing them for a while, and reporting back, if this fixed the issue or not.

Revision history for this message
Tormod Volden (tormodvolden) wrote :

I will close this bug since it seems to have been fixed in updates.

Changed in xserver-xorg-video-intel (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Zenigata17 (bedouin-drebon) wrote :

Well actually it seems tat the driver i810 is gone and that only intel driver might be used...

In Hardy, or Jaunty, use of intel driver instead of i810 could cause freezes wile closing lid on i855GM cards.

This bug is back in Karmic, and the ansence of i810 driver prevents to get around it.

Changed in xserver-xorg-video-intel (Ubuntu):
status: Fix Released → Confirmed
Revision history for this message
Tormod Volden (tormodvolden) wrote :

Zenigata, please file your own bug report, using "ubuntu-bug xserver-xorg-video-intel". This issue was resolved for the original reporter here.

Note that the "module i810" error message is not important and can be ignored.

Changed in xserver-xorg-video-intel (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Oleksiy Lukin (alukin) wrote :

This issue is not resolved at all. After reboot the same problem occurs and creating xorg.conf with "intel" driver puts my monitor Flatron W2343S out of sync.

mzaki77 (mzaki77)
Changed in xserver-xorg-video-intel (Ubuntu):
status: Fix Released → Fix Committed
status: Fix Committed → Incomplete
Revision history for this message
Tormod Volden (tormodvolden) wrote :

See comment #14.

Changed in xserver-xorg-video-intel (Ubuntu):
status: Incomplete → Fix Released
Revision history for this message
protoman (protomank) wrote :

Well, I did NOT had theis problem, until I just made and upgrade... Now I'm getting it and worse, I can't run X at all, the " Ubuntu is running in low graphics" tool is simply useless to me... :-(
Not can't go to console because my monitor says it does not support the video mode.

The weird thing: If I do boot with the install CD, rename /etc/X to X.bak and do a boot, then renaming the file back to X and run startx... it works!

Man this bug is URGENT, seems like a broken update to me!

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.