[Bug 1771] Intel 865G on P4P800-VM I830WaitLpRing() lockup

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Dec 28 10:05:13 PST 2004


Please do not reply to this email: if you want to comment on the bug, go to          
the URL shown below and enter yourcomments there.   
 
https://bugs.freedesktop.org/show_bug.cgi?id=1771        
   




------- Additional Comments From andrej.prsa at guest.arnes.si  2004-12-28 10:05 -------
Hi, I tried a couple of things to do with the graphic card after Jason and 
Matthias were kind enough to supply feedback, here are the results:

                            --- 1ST TEST ---

I tried playing with VideoRam option and this time the X didn't initialize DRI 
at all. I'm posting an excerpt of the logfile here, only the relevant part, for 
brevity. I'll enumerate the parts here for commenting purposes:

1) The version is 6.8.1 built from CVS:

X Window System Version 6.8.1
Release Date: 17 September 2004
Build Date: 04 November 2004

2) The part that is changed: I set VideoRam to 32636 after dmesg'ing to see
   what's the stolen memory size. If relevant, AGP aperture size is set to
   128MB. The output below strikes me as unusual - how does I830 function
   see 418812kB available memory???

(II) I810(0): detected 32636 kB stolen memory.
(II) I810(0): I830CheckAvailableMemory: 418812 kB available
(--) I810(0): Pre-allocated VideoRAM: 32636 kByte
(**) I810(0): VideoRAM: 32636 kByte

3) Finally, the DRI initialization failure:

(II) I810(0): 4 kBytes additional video memory is required to
	enable tiling mode for DRI.
(II) I810(0): 4 kBytes additional video memory is required to enable DRI.
(II) I810(0): Disabling DRI.

                               --- 2ND TEST ---

I tried commenting out VideoRam option completely - to remind you, originally
I had it set to 32768. This time startx didn't work at all - all I got was a
silly picture and a frozen graphic card that could not be accessed again,
although the system was fully responsive. Since I didn't think of any better
way to capture it, I took my digital camera and took two screenshots, literally! 
;) Please find them at:

     http://www.fiz.uni-lj.si/~prsa/screenshot1.jpg
     http://www.fiz.uni-lj.si/~prsa/screenshot2.jpg

(I didn't attach them to the bug report because of their size). Seemingly it has 
something to do with i830 module, because if I modprobe it and startx, the same 
thing happens regardless of VideoRam setting. If on the other hand i830 isn't 
modprobe'd, i915 gets loaded automatically.

                               --- 3RD TEST ---

The test a.k.a. "The Weird One!" ;) I set VideoRam to 32768 and I startx'd. The 
logfile shows that everything is perfectly ok, DRI enabled, everything else as 
well, but glxinfo then reports that there is NO direct rendering available!? 
This was sooo weird I had to come to the bottom of this and the result is 
absolutely unbelievable: I set .xinitrc to start gnome; if gnome is used as the 
window manager, then DRI won't work, but if it's TWM or similar, DRI works! How 
weird is that? Anyway, even with TWM and DRI enabled, the original I830 ring 
problem pops up and crashes the card in about 10 seconds of tuxracer 
(unmistakenly, it never lasts longer than 10 seconds!).

Finally, if of any help, the 865patch program doesn't affect the results I put 
out here in any way.
        
   
   
--         
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email       
   
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


More information about the xorg-bugzilla-noise mailing list