I just tried to fire up Quake III on a laptop with an Intel 830 chipset
and the i830 DRI snapshot from a couple of days ago. The game started,
but only displayed one frame (I think). I switched consoles, killed Q3,
and then got this message on the console:
[drm:i830_wait_ring] *ERROR* space: 131048 wanted 131064
[drm:i830_wait_ring] *ERROR* lockup
I've seen similar errors before, but I don't know if they were exactly
I can get NWN to play on here at about 13 fps with those drivers, but
there are some other problems there. (It has stuttering audio, at roughly
the frequency corresponding to the games frame rate. It also crashes
eventually. I was trying out Q3 for the first time on this laptop to see
if it experiences the same problems. I haven't been able to see if the
same error appears on the console in NWN, though.)
Glxgears runs fine on here, with 148 fps. (Slow, but is this normal for this
chipset?) Glxinfo reports that direct rendering _is_ working. The X server,
by the way, is the XFree86 4.3.0 shipped w/ Red Hat 9, and the kernel is the
Red Hat 9 kernel w/ the Dec. 12 ACPI patches applied. As far as I can tell,
the kernel drm module and server module for the Intel 830 driver I downloaded
are installed correctly.
I was getting DRM errors with Red Hat 8.0, too, but I don't know whether
they were the same ones or not. They occured using Galeon, rather than a
3D client. I didn't write down the errors there, because I thought that
upgrading to Red Hat 9 and the latest drivers would probably make them go
away. But, they sure looked similar to what I'm seeing now.
Does anyone have an idea of where the problem might be? (I've done a little
bit of work on the R100 driver myself, and wanted to look through the i830
source myself, but the anonymous CVS servers have been a wreck for the last
Thanks for the help!
Get latest updates about Open Source Projects, Conferences and News.