Hi,

I installed XFree86 4.5.0 in my LFS system, and all went fine, no compilation problems, just the BLFS book steps and I were able to get a decent graphics server running

the problem I'm having is a bit annoying... when my system boots up and I enter into my GNOME desktop, I cannot run any program that makes use of hardware acceleration because the /dev/dri/card0 device is owned by user root and group root

A partial solution for me was to change the ownership from root:root to root:video and adhering my user to the video group, therefore making my user being able to access the DRI device and, consequently, being able to play Wolfenstein: Enemy Territory, or just firing up any screensaver that makes use of OpenGL hardware accelerated graphics

but every time the system boots up, the ownership is changed automagically, so every time I log into GNOME I have to get a terminal and change the ownership again as root, but this is not an elegant solution...

I have modified my /etc/udev/rules.d/udev.rules and /etc/udev/rules.d/50-lfs.rules (don't know why on earth has to be 2 udev rules files) and in the 2 files the line refering to the DRI device is modified to have the GROUP="video", but the result is the same, I have to manually re-change the ownership...

how can I solve this?

Thanks in advance,

Julio

Any particular graphics driver you're using?

Hi kjordan,

the graphics driver I'm using is the Intel i810 driver, and the DRI device configured is the Intel i915 (it's the latest graphics chip series from intel, in this case Intel GMA900)

Julio

Hi,

the problem persists... is there any way to make the ownership of the /dev/dri/card0 device remain as root:video instead of root:root? it's very annoying to have to change ownership by hand everytime I want acceleration support for my regular user

Julio

Append chgrp video /dev/dri/card* to make_extra_nodes() in /etc/rc.d/init.d/udev script

Do you have a section like this in your X config file ?

Section "DRI"
Mode 0666
EndSection

Hi,

thanks freegianghu and madluther,

I've solved the problem, I wrote the Mode 0666 line in the DRI section and it worked

Thanks a lot ,

Julio