On 21 April 2010 09:21, Michael wrote:
> Got it!
>
> When I ran
> sudo update-alternatives --config gl_conf
>
> I was presented with fglrx auto or fglrx manual (or without fglrx at
> all). Choosing auto did not work. Manual worked fine
>
> Thanks for the support
>
> --
> LIBGL_DRIVERS_PATH wrong a
Got it!
When I ran
sudo update-alternatives --config gl_conf
I was presented with fglrx auto or fglrx manual (or without fglrx at
all). Choosing auto did not work. Manual worked fine
Thanks for the support
--
LIBGL_DRIVERS_PATH wrong after deactivating and restarting computer
https://bugs.la
glxinfo | grep rendering
Error: couldn't find RGB GLX visual or fbconfig
--
LIBGL_DRIVERS_PATH wrong after deactivating and restarting computer
https://bugs.launchpad.net/bugs/552903
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
Output of ldconfig -p | grep GL
libQtOpenGL.so.4 (libc6) => /usr/lib/libQtOpenGL.so.4
libGLU.so.1 (libc6) => /usr/lib/libGLU.so.1
libGLEW.so.1.5 (libc6) => /usr/lib/libGLEW.so.1.5
libGL.so.1 (libc6, OS ABI: Linux 2.4.20) => /usr/lib/libGL.so.1
libGL.so.1 (li
On 20 April 2010 11:18, Michael wrote:
> @Alberto Milone
> Well it sounds to me like there is a problem with the upgrade path. Mine is
> not a clean install, I updated from Karmic, where I was using drivers from
> the ATI website. I completely uninstalled them and installed the drivers
> throug
@Alberto Milone
Well it sounds to me like there is a problem with the upgrade path. Mine is not
a clean install, I updated from Karmic, where I was using drivers from the ATI
website. I completely uninstalled them and installed the drivers through jockey
and this was the result I got.
If I remo
@Michael
/usr/lib/libGL.so.1 is not supposed to exist in Ubuntu Lucid (as the new
alternatives system works in a different way). Having one will definitely cause
problems.
Note: you should not create a new link as, if you installed the fglrx
driver with Jockey, ldconfig will know where to find f
Solved number 16 by doing this
sudo rm /usr/lib/libGL.so.1
sudo ln -s /usr/lib/fglrx/libGL.so.1.2 /usr/lib/libGL.so.1
http://ubuntu-virginia.ubuntuforums.org/showpost.php?p=9015235&postcount=103
--
LIBGL_DRIVERS_PATH wrong after deactivating and restarting computer
https://bugs.launchpad.net/bugs
I have tried both changing the path in 10fglrx and removing that file
but both results in the following output from glxinfo | grep rendering
Error: couldn't find RGB GLX visual or fbconfig
Any suggestions? I am on fglrx 2:8.723.1-0ubuntu2 and xorg-xserver-core
2:1.7.6-2ubuntu5
--
LIBGL_DRIVERS_
This bug was fixed in the package fglrx-installer - 2:8.721-0ubuntu8
---
fglrx-installer (2:8.721-0ubuntu8) lucid; urgency=low
* debian/rules, fglrx.dirs, fglrx.postinst:
- Install the blacklist file in /lib/fglrx instead of
/usr/lib/fglrx so that the file is available ear
** Package changed: jockey (Ubuntu) => fglrx-installer (Ubuntu)
** Changed in: fglrx-installer (Ubuntu)
Importance: Undecided => High
** Changed in: fglrx-installer (Ubuntu)
Status: New => Triaged
** Changed in: fglrx-installer (Ubuntu)
Assignee: (unassigned) => Alberto Milone (al
This is an issue in the packaging of the fglrx driver. It's not Jockey
that causes this (at least directly).
--
LIBGL_DRIVERS_PATH wrong after deactivating and restarting computer
https://bugs.launchpad.net/bugs/552903
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Depends if you're using 32 bits programs (requiring a package of 32libs) or
not.
For me it is (for you it might not be if you don't have that directory):
pa...@aivas:~$ echo $LIBGL_DRIVERS_PATH
/usr/lib/dri:/usr/lib32/dri
--
LIBGL_DRIVERS_PATH wrong after deactivating and restarting computer
htt
Opss that was a response to a private email.
--
LIBGL_DRIVERS_PATH wrong after deactivating and restarting computer
https://bugs.launchpad.net/bugs/552903
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
Depends if you're using 32 bits programs (requiring a package of 32libs)
or not.
For me it is (for you it might not have the lib32 directory):
pa...@aivas:~$ echo $LIBGL_DRIVERS_PATH
/usr/lib/dri:/usr/lib32/dri
I have no idea about the other problems or how you can have rendering
without this va
I removed (moved to somewhere else) the file and now I do have direct
rendering.
However:
$ export LIBGL_DEBUG=verbose
$ glxinfo | grep -i direct
libGL: OpenDriver: trying /usr/lib/dri/tls/r600_dri.so
libGL: OpenDriver: trying /usr/lib/dri/r600_dri.so
libGL: Can't open configuration file /etc/dri
What are the correct values?
I also have this problem.
--
LIBGL_DRIVERS_PATH wrong after deactivating and restarting computer
https://bugs.launchpad.net/bugs/552903
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Removing the file disables the acceleration again, since
LIBGL_DRIVERS_PATH is now empty. I'm going to set in my environment
instead.
--
LIBGL_DRIVERS_PATH wrong after deactivating and restarting computer
https://bugs.launchpad.net/bugs/552903
You received this bug notification because you are a
Confirmed. Removing the fglrx dir from those paths sets the correct variable ,
and glxinfo reports that
"direct rendering: Yes".
--
LIBGL_DRIVERS_PATH wrong after deactivating and restarting computer
https://bugs.launchpad.net/bugs/552903
You received this bug notification because you are a mem
Ok found the problem.
Removing fglrx or deactivating it doesn't remove the file
/etc/X11/Xsession.d/10fglrx
That is run sometime after the /etc/environment (since i tried to put the
correct values there, but was replaced by this)
That contains this code:
LIBGL_DRIVERS_PATH=/usr/lib/fglrx/dri
if [
Started happening again after a update when i tried (stupidly) to enable
and disable the fglrx drivers (but it didn't crash jockey now).
Regardless, the value of
pa...@aivas:~$ echo $LIBGL_DRIVERS_PATH
/usr/lib/fglrx/dri
Is persistent even if the fglrx and fglrx-modaliases are uninstalled, or
eve
I reinstalled and it didn't crash now. However i have no xorg.conf. It seems
to be auto generated. I've now disabled the firegl drivers, updated and it
seems that the opensource drivers enabled the R700 path? Regardless i have
3d acceleration without the ati driver.
--
LIBGL_DRIVERS_PATH wrong af
"jockey crashed" doesn't really help me understand what went wrong.
My guess is that your xorg.conf wasn't set to "fglrx", therefore you
kept using the open driver with the GL libraries from the proprietary
driver.
In order to reproduce the problem in Jockey, please remove the "fglrx"
package and
"Solved" by sudo find . -name *fglrx*
and removing every single file given.
Gah. Binary drivers suck.
--
LIBGL_DRIVERS_PATH wrong after deactivating and restarting computer
https://bugs.launchpad.net/bugs/552903
You received this bug notification because you are a member of Ubuntu
Bugs, which i
glxinfo reported problems
libGL: OpenDriver: trying /usr/lib/fglrx/dri/tls/r600_dri.so
libGL: OpenDriver: trying /usr/lib/fglrx/dri/r600_dri.so
libGL error: dlopen /usr/lib/fglrx/dri/r600_dri.so failed
(/usr/lib/fglrx/dri/r600_dri.so: cannot open shared object file: No such file
or directory)
li
25 matches
Mail list logo