I've installed AMD Catalyst 13.8 BETA2 by following these directions.It works fine on the administrative user it was setup with, but a non-admin user gets the black screen on login.Non-admin user works in software rendering mode but not hardware. cat /var/log/Xorg.0.log[ 42815.421] (EE) AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory][ 42815.421] (EE) AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory][ 42815.421] (EE) AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory]From the installation, there was this command:sudo ln -s lib /usr/lib64ls -l /lib shows that root user and root group own the directory and subdirectories.How can non-admin users safely get the necessary access to these files?Note: the symlink command has been corrected in the linked instructions.
How to safely give non-root access to lib so that Catalyst hardware acceleration can function?
ubuntu;drivers;ati
I think I'm starting to get what happened. One of the answers on the page you linked to tells you to run this:cd /usr ; sudo ln -svT lib /usr/lib64That will i) move you into the /usr directory and ii) create a link called lib64 (which will be /usr/lib64 if you run the ln command in /usr) pointing to /usr/lib. The command should not be run as your admin user (that's why it has sudo) and it should certainly not be run from your admin user's $HOME directory.Please re-read the instructions and follow them exactly. Also read this note (included just under the ln command):(Note: The second command shouldn't be necessary if there is already such a symbolic link named lib64 pointing to folder lib there. And if there is already a real folder by that name (determined with ls -l /usr/lib64), you should ensure that its contents are safely moved into folder /usr/lib and then delete --the now empty-- folder /usr/lib64 before executing this command).So, make sure there is no /usr/lib64 directory, if there is, move its contents to /lib before running the ln command. NOTE: The actual ln command in my answer is ln -svT lib /usr/lib64, if that is really what you ran, the link will be created at /usr/lib64 irrespective of where you run it from.