Since I installed X.org 6.8.0 I am unable to start X and it freezes the graphics card, keyboard and (after a few seconds) the mouse. The error I am receiving is below. I have tried it with 2 different kernels (2.6.7-gentoo-r7 which was working before and 2.6.8-gentoo-r4 which is the latest gentoo development kernel). Error in I810WaitLpRing(), now is 8364, start is 6357 pgetbl_ctl: 0x1fd30001 pgetbl_err: 0x0 ipeir: 0 iphdr: e0905000 LP ring tail: 40 head: 0 len: f001 start 24e0000 eir: 0 esr: 1 emr: 3d instdone: ff7a instpm: 0 memmode: 4 instps: 10 hwstam: 9ac7 ier: 0 imr: 9ac7 iir: 0 space: 65464 wanted 65528 Fatal server error: lockup Please consult the The X.Org Foundation support at http://wiki.X.Org for help. Please also check the log file at "/var/log/Xorg.0.log" for additional informati on. *** If unresolved symbols were reported above, they might not *** be the reason for the server aborting. FatalError re-entered, aborting Caught signal 11. Server aborting
I had same problem. If I use Option "NoAccel" It allows X to start. But "cat something" in xterm is real slow.
I am now using Gentoo's x.org 6.8.0-r1, which has some additional patches in it. I have also recently upgraded to gcc-3.4... Somewhere in these two the problem was fixed. The changelog for x.org 6.8.0-r1 is at http://packages.gentoo.org/ebuilds/?xorg-x11-6.8.0-r1 but I can't see anything specifically relating to our problem. Performance is fine under this version.
I have: x11-base/xorg-x11-6.8.0-r1 * sys-devel/gcc-3.3.4-r1 * I will give 3.4 a spin.
I have a similar problem: i815 chipset with integrated graphics, running perfectly on the same machine with kernel 2.4.25. Also ran ok with kernel 2.6.5 but I didn't test it much because of other problems with that kernel. Now, trying kernel 2.6.9 produces this: X is unable to start, I see a black screen and the X cursor, then it freezes and the screen is filled with vertical coloured lines. The computer is alive though, I can ssh to it and everything is alright, only the graphics part is gone. After halt and power-up, booting into 2.4.25, everything is fine. So I guess it has something to do with the kernel version and modifications made to the i810/agpgart/whatever modules. Here is the relevent part from Xorg.0.log: ========== Error in I810WaitLpRing(), now is 6684, start is 4683 pgetbl_ctl: 0xf3d0001 pgetbl_err: 0x8b0000 ipeir: 0 iphdr: 385f6c65 LP ring tail: 258 head: 0 len: f001 start 13c0000 eir: 0 esr: 1 emr: 3d instdone: ff7a instpm: 0 memmode: 4 instps: 810 hwstam: bac7 ier: 0 imr: bac7 iir: 0 space: 64928 wanted 65528 Fatal server error: lockup Please consult the The X.Org Foundation support ========== Relevant portions of xorg.conf: ========== Section "Module" Load "type1" Load "freetype" Load "extmod" Load "dbe" Load "v4l" Load "synaptics" EndSection Section "Device" Identifier "i810" Driver "i810" Option "XvMCSurfaces" "6" Option "BackingStore" "on" VideoRam 8192 EndSection ========== Distribution is Slackware-current, Xorg version is 6.8.1, glibc 2.3.3, gcc 3.3.4 Thanks, Mihnea
Duplicate of #1353 and #1771.
Did you try 6.8.1? It has several i810 related bugfixes.
Sorry, should read all comments to the end of the page... :-]
I now have a 2.6.9 installed on a test machine, but it runs flawlessly. Please post your xorg.conf and Xorg.0.log
Same error using X.org 6.8.1 X Window System Version 6.8.1 Release Date: 17 September 2004 X Protocol Version 11, Revision 0, Release 6.8.1 Build Operating System: Linux 2.4.21-14.ELsmp i686 [ELF] Current Operating System: Linux 2.6.9-1.667 #1 Tue Nov 2 14:41:25 EST 2004 i686 Build Date: 20 October 2004 Build Host: tweety.build.redhat.com AUDIT: Sat Jan 8 01:50:25 2005: 3312 X: client 5 rejected from local host Error in I810WaitLpRing(), now is 13376, start is 11375 pgetbl_ctl: 0xfd30001 pgetbl_err: 0x0 ipeir: 0 iphdr: feecd568 LP ring tail: 678 head: 548 len: 10f001 start 12ac000 eir: 0 esr: 1 emr: 3d instdone: ff7a instpm: 0 memmode: 5 instps: 810 hwstam: 9ac7 ier: 0 imr: 9ac7 iir: 0 space: 65224 wanted 65528 Fatal server error: lockup
i810 and i815 use the same driver code. It is likely that this problem has been fixed in 6.8.2. *** This bug has been marked as a duplicate of 1343 ***
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.