12.1: Lockup i810

Chemtux · 05-04-2008, 01:20 AM

Hi,

Does anyone else experience a X-lockup with i810-driver?
"Error in I810WaitLpRing()"

mRgOBLIN · 05-04-2008, 01:34 AM

Use the intel driver

gegechris99 · 05-04-2008, 01:37 AM

Hello,

I've one machine for which I use the i810 driver, I haven't got any error since I upgraded to 12.1 yesterday morning. When does the error occur? During start-up of X or after some time after using X?

Smedley · 05-04-2008, 01:38 AM

Quote:

Originally Posted by Chemtux

Hi,

Does anyone else experience a X-lockup with i810-driver?
"Error in I810WaitLpRing()"

Edit your /etc/X11/xorg.conf and add the following:

Code:

Section "Module"
        Load  "synaptics"
        Load  "xtrap"
        Load  "extmod"
#       Load  "dri"
        Load  "glx"
        Load  "record"
        Load  "dbe"
        Load  "GLcore"
        Load  "type1"
        Load  "freetype"
EndSection

Comment out Load "dri"

If that does not work, post your xorg.conf

aopq · 05-04-2008, 01:47 AM

Section "ServerFlags"
Option "AIGLX" "false"
EndSection

Chemtux · 05-04-2008, 03:10 AM

Thanks people,

The solution is: Option "AIGLX" "false"

I don't know why and i don't know why this has changed from 12.0...maybe aopq can explain?

Smedley...Dri was already #-ed

aopq · 05-04-2008, 03:34 AM

I do not know it either.
I found it somewhere recently.

#Load "dri" seems not to actually disable it.
Disable "dri" was necessary to disable it.

However, when Option "AIGLX" "false" is written,
it seems to be unnecessary.

bgeddy · 05-04-2008, 09:59 AM

I was wondering when this would pop up when current was released as stable.

I've been trying to get DRI working with current (now 12.1) and the i810 drivers for quite a long time. See my previous posts:

http://www.linuxquestions.org/questi...t=current+i810

http://www.linuxquestions.org/questi...t=current+i810

With my onboard Intel video, setting colour depth to 24 disables dri and lets X run OK. However I can't get dri working across two boxes and with various distros using this version of X.

Note that this is not a Slackware problem but a problem with the X drivers.