On 12/12/05, Alex Deucher <[EMAIL PROTECTED]> wrote: > On 12/10/05, Erik <[EMAIL PROTECTED]> wrote: > > khaqq wrote: > > > > >On Sat, 10 Dec 2005 22:22:43 +0100 > > >Erik <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > >>Alex Deucher wrote: > > >> > > >> > > > > > >(...) > > > > > > > > > > > >>>your system probably uses udev to change permissions on devices on the > > >>>fly. make sure your user is in the video group (or whatever group > > >>>your distro uses for it). > > >>> > > >>> > > >>> > > >>Yes, that was the workaround! I added my normal username to the video > > >>group and changed the part of xorg.conf to: > > >>Section "dri" # from http://dri.freedesktop.org/wiki/Building > > >> Group "video" # from http://dri.freedesktop.org/wiki/Building > > >> Mode 0660 # from http://dri.freedesktop.org/wiki/Building > > >>EndSection # from http://dri.freedesktop.org/wiki/Building > > >> > > >>But I still consider it a bug that I cannot use any groupname. At least > > >>it must be a bug in the documentation at > > >>http://dri.freedesktop.org/wiki/Building to not say that I have to use > > >>one particular groupname ("video"). > > >> > > >> > > > > > >This should be in your system's documentation. The "video" group is > > >distribution-dependent and does not come from DRI/Mesa. > > >Check the file /etc/group > > > > > Yes, it should be in the system's documentation. But it should also be > > on the http://dri.freedesktop.org/wiki/Building page. It currently says > > "To restrict DRI access to a certain group, do (after creating the > > driusers group and adding users to it):" but should really say something > > like: > > To restrict DRI access to a certain group, find the name of the group > > that is for video hardware access on your system. Have a look in > > /etc/group. It might be called for example "video". Add the users you > > want to access the video hardware to that group. Then add this to xorg.conf: > > Section "DRI" > > Group "video" > > Mode 0660 > > EndSection > > > > It's a wiki ;) feel free to add it. The thing is though, the udev > group and dev permissions really has nothing to do with the DRI. Not > all distros do it the same way. It makes sense to make note of that > as well. > > Alex > I do not think udev is the bad guy in this. Udev will set the initial permission (look in /etc/udev/permissions.d) but pam will override this. Look in /etc/security/console.perms if any special permissions are set for char/dri devices.
Sander ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
