| View previous topic :: View next topic |
| Author |
Message |
<3
Veteran
Joined: 21 Oct 2004
Posts: 1081
|
 Posted: Sun Jan 02, 2005 8:28 am Post subject: WTF is up with these permissions |
 |
|
when I try to play ut2004
| Quote: | #ut2004
open /dev/[sound/]dsp: No such file or directory
Error: Could not open /dev/nvidiactl because the permissions
are too resticitive. Please see the FREQUENTLY ASKED QUESTIONS
section of /usr/share/doc/NVIDIA_GLX-1.0/README for steps
to correct.
Signal: SIGSEGV [segmentation fault]
Aborting. |
when I try to play doom3
| Quote: | #doom3
DOOM 1.1.1286 linux-x86 Nov 24 2004 17:56:04
GetLocalAddress failed: gethostbyname failed: localhost host not found
------ Initializing File System ------
Loaded pk4 /opt/doom3/base/game00.pk4 with checksum 0x7dafc4d4
Loaded pk4 /opt/doom3/base/game01.pk4 with checksum 0x16cf3b8a
Loaded pk4 /opt/doom3/base/pak000.pk4 with checksum 0x28d208f1
Loaded pk4 /opt/doom3/base/pak001.pk4 with checksum 0x40244be0
Loaded pk4 /opt/doom3/base/pak002.pk4 with checksum 0xc51ecdcd
Loaded pk4 /opt/doom3/base/pak003.pk4 with checksum 0xcd79d028
Loaded pk4 /opt/doom3/base/pak004.pk4 with checksum 0x765e4f8b
Loaded pk4 /opt/doom3/base/pak005.pk4 with checksum 0x8ffc3621
Current search path:
/home/cashe/.doom3/base
/opt/doom3/base
/opt/doom3/base/pak005.pk4 (63 files)
/opt/doom3/base/pak004.pk4 (5137 files)
/opt/doom3/base/pak003.pk4 (4676 files)
/opt/doom3/base/pak002.pk4 (6120 files)
/opt/doom3/base/pak001.pk4 (8972 files)
/opt/doom3/base/pak000.pk4 (2698 files)
/opt/doom3/base/game01.pk4 (2 files)
/opt/doom3/base/game00.pk4 (2 files)
game DLL: 0x0 in pak: 0x0
file system initialized.
--------------------------------------
----- Initializing Decls -----
------------------------------
------- Initializing renderSystem --------
using ARB renderSystem
renderSystem initialized.
--------------------------------------
5151 strings read from strings/english.lang
Couldn't open journal files
execing editor.cfg
execing default.cfg
couldn't exec DoomConfig.cfg
couldn't exec autoexec.cfg
5151 strings read from strings/english.lang
----- Initializing Sound System ------
sound system initialized.
--------------------------------------
----- R_InitOpenGL -----
Setup X display connection
dlopen(libGL.so.1)
Initializing OpenGL display
Using XFree86-VidModeExtension Version 2.2
DGA DirectVideo Mouse (Version 2.0) initialized
Free86-VidModeExtension Activated at 640x480
Using 8/8/8 Color bits, 8 Alpha bits, 24 depth, 8 stencil display.
Error: Could not open /dev/nvidiactl because the permissions
are too resticitive. Please see the FREQUENTLY ASKED QUESTIONS
section of /usr/share/doc/NVIDIA_GLX-1.0/README for steps
to correct.
signal caught: Segmentation fault
si_code 1
Trying to exit gracefully..
pure virtual method called
double fault Aborted, bailing out |
I also had a problem with my sound which I posted here. (this problem is fixed btw) where the permissions for my audio was borked.
It seems something is screwing with my file permissions. I don't ever remeber messing with permissions, I don't even know how to change permissions so I have no idea WTF is going on. If anyone knows how to fix the ut2004, doom3 or these permissions problems in general plaease reply.
THX |
|
| Back to top |
|
 |
abcdefg
Apprentice
Joined: 29 Feb 2004
Posts: 216
Location: The Netherlands
|
| Posted: Sun Jan 02, 2005 9:28 am Post subject: |
|
|
| Code: | | chmod 777 /dev/nvidia* |
This fixed it for me, it's probably an insecure way of doing that but it's the only way I know how to solve it... Because the permission are set wrong verry often I have the line in my startup file:
| Code: | | echo "chmod 777 /dev/nvidia*" >> /etc/conf.d/local.start |
edit: typo |
|
| Back to top |
|
|
inzano
n00b
Joined: 01 Jan 2005
Posts: 3
Location: Lund, Sweden
|
| Posted: Sun Jan 02, 2005 12:40 pm Post subject: |
|
|
If you are the only user on your system, 777 might be a choice. But in general, you should never have those permissions on files. If it is a non-executable file, 644 will do most of the time.
In this particular case, it is probably the PAM system which changes your permissions through /etc/security/console.perms. Try to comment out the line <dri>=.....
That should do the trick. |
|
| Back to top |
|
|
<3
Veteran
Joined: 21 Oct 2004
Posts: 1081
|
| Posted: Sun Jan 02, 2005 8:57 pm Post subject: |
|
|
| commenting out the <dri> line did the trick. Lastly I would like to ask, why is pam screwing up the permissions? Is there a way to stop it from doing that agian? |
|
| Back to top |
|
|
FreeFly42
l33t
Joined: 03 Nov 2003
Posts: 848
Location: Houston, TX
|
| Posted: Sat Jan 08, 2005 7:20 pm Post subject: |
|
|
Commenting out the dri line in /etc/security/console.perms defeats one of the cool features of PAM and possibly makes your system less secure.
Seems to me like it would be better to work with the system. First, either create a new group or use an existing group for dri (glx direct rendering) access (I use the group games since that's pretty much the only place glx is really used). Then rather than commenting out the line:
| Code: | | <dri>=/dev/nvidia* /dev/3dfx* |
in /etc/security/consone.perms, find and edit the following line:
| Code: | | <xconsole> 0600 <dri> 0600 root |
So that it becomes:
| Code: | | <xconsole> 0600 <dri> 0600 root.games |
or whatever other group you chose.
Then when a user who is a member of the games group logs in to an xconsole, the ownership of /dev/nvidia* will change to be owned by that user with permissions 600. This prevents two users from trying to access the device simultaneously ensuring that only the user actually logged on to the xconsole has access.
_________________
Kent
Planes are dangerous, get out of 'em quick |
|
| Back to top |
|
|
|
Other Things Gentoo
