Hi,
I have trouble with the ATI driver permissions. flg_glxgears give me:

FGLTexMgr: open of shared memory object failed (Permission denied)
__FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
FGLTexMgr: open of shared memory object failed (Permission denied)
__FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
FGLTexMgr: open of shared memory object failed (Permission denied)
__FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
FGLTexMgr: open of shared memory object failed (Permission denied)
...

As root there are no problems.
i followed ATIs instructions on:
http://www2.ati.com/drivers/linux/li...20.html#176878

And I have the tempfs properly mounted (it actually took care of the problem initially, but after a kmod upgrade the problem is re-occuring).


Follow up:
It seems the problem is from permissions on the tempfs:
[smgan@PC2-BIL ~]$ ls /dev/shm/ -al
total 16
drwxrwxrwt 2 root users 60 Sep 7 14:52 .
drwxr-xr-x 13 root root 3840 Sep 7 14:52 ..
-rw------- 1 minc minc 1048576 Sep 7 14:52 ATISHM00

Only the user that first mounts the tempfs can use the driver
i tried to fix this in fstab:
tmpfs /dev/shm tmpfs auto,users,gid=users 0 0

But to no avail.

Could someone advice me on what to put in the fstab to make the permissions right? (I tried umask=0007 but it did not work)


Thanks
Soren

I don't think that multiple users should, in fact, be able to use the same shared memory. I believe that Radeon uses the shared memory to communicate between processes running in the kernel and in user space, and, if multiple users were permitted to use the same shared memory, the user-space processes could get very confused.

What needs to be done is for Radeon to create an entry in /dev/shm for each user. But, of course, Radeon doesn't see much need to support multiple, simultaneous, system users. And their driver code is not open source, so you can't make any changes.

Consider switching drivers. nVidia, for example, doesn't use shared memory, and Intel's driver code is open-sourced.

Thanks for the explanantion, sounds like a likely cause.
I'll get an NVidia card next time!

Thanks
Soren