Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#1556 - DRI support on Intel chipsets broken

Attached to Project: Arch Linux
Opened by LB06 (LB06) - Thursday, 30 September 2004, 19:09 GMT
Last edited by Judd Vinet (judd) - Monday, 04 October 2004, 18:32 GMT
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To Judd Vinet (judd)
Architecture not specified
Severity Medium
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

xorg log:

drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (Unknown error 999)
drmOpenDevice: open result is -1, (Unknown error 999)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (Unknown error 999)
drmOpenDevice: open result is -1, (Unknown error 999)
drmOpenDevice: Open failed
[drm] failed to load kernel module "i915"
(II) I810(0): [drm] drmOpen failed
(EE) I810(0): [dri] DRIScreenInit failed. Disabling DRI.

It seems the i915 module is required for direct rendering on Intel chipsets. Please add it to the next stock kernel.
This task depends upon

Closed by  Judd Vinet (judd)
Monday, 22 November 2004, 00:37 GMT
Reason for closing:  Fixed
Comment by LB06 (LB06) - Thursday, 30 September 2004, 19:19 GMT
Also, I cannot modprobe agpgart or intel-agp(cannot find module), which were loaded properly in slack, where dri was loaded sucessfully on my notebook.
Comment by LB06 (LB06) - Thursday, 30 September 2004, 19:40 GMT
I found out agpgart and intel-agp are compiled into the kernel instead as modules (sorry, been away for a while). But my problem still remains
Comment by Judd Vinet (judd) - Monday, 04 October 2004, 18:33 GMT
Does /dev/dri/card0 exist?

And if so, does your user have RW access to it?

Comment by LB06 (LB06) - Tuesday, 05 October 2004, 10:11 GMT
/dev/dri exists, but I cannot find a single device node in it.
Comment by LB06 (LB06) - Tuesday, 05 October 2004, 10:14 GMT
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=130862

RH also suffered from the same bug.
Comment by LB06 (LB06) - Monday, 11 October 2004, 17:34 GMT
After doing some research myself, I did some observations.

First, I have an Intel 855GM chipset. As stated on various websites it is only supported by the i830 or the new i915 driver (Slack also loaded the i830 driver according to lsmod, dri worked). I also found out you need 3 drivers/modules to get x with dri: A kernel driver, a userspace driver(Xorg?), a userspace dri/drm driver(X/mesa?). So I have various options.

(1) Try to continue with i810
(2) Try i830
(3) Try i915

(1)
The i810 seems to work fine for non accelerated stuff, but the i810_dri driver/module obviously doesn't work for a non i810 chipset. Xorg seems to know about this and wants to load the i915 dri drivers. There is no matching kernel module, however(why doesn't it try to load i830, this one is present in the kernel?)

(2)
This one is present in kernel, but not in userland(x.org/mesa?). There is no matching module in /usr/X11R6/lib/modules/drivers, however. There also is no dri module in /usr/X11R6/lib/modules/dri.

(3)
This one is meant to replace i830 (and possibly i810). Not present in kernel, not present in userland, but there is a dri driver.

So only the i810 has all the required stuff, but the problem is that my GPU is incompatible with it. i830 lacks an x.org and dri module. i915 lacks a x.org and kernel module.

I hope this helps.
Comment by LB06 (LB06) - Monday, 11 October 2004, 17:56 GMT
Correction, the i810 x.org module will always work on any i8xx and i915(since xorg 6.8) chipset. (Why the hell do they still call it i810 then?). But since the only compatible dri module available in /usr/X.../dri is i915, so it wants to load this one. It only hasn't been implemented in the kernel however. Very strange.
Comment by Judd Vinet (judd) - Monday, 18 October 2004, 23:50 GMT
The new drivers are present in 2.6.9

Loading...