Re: [gentoo-user] nvidia drivers and glx
This occured to me when I upgraded to the 2.6.11 nitro sources... after moving back to gentoo-dev-sources (or gentoo-sources now) the problem went away. On 4/26/05, Bruno Lustosa <[EMAIL PROTECTED]> wrote: > On 4/25/05, Robert Morris <[EMAIL PROTECTED]> wrote: > > I had this too. I believe its the permissions being changed by/for PAM. > > Check to make sure you are in the video group. Add your user to it if > > you're not. That fixed it for me. > > Well, it seems to be fixed by downgrading glibc back to 2.3.4-20041102. > I'm not sure if it's that glibc must be the same version of > emul-linux-x86-glibc. > Anyway, with old glibc, it's working. > > Symbol __glXgetActiveScreen from module > > /usr/lib/modules/extensions/libdri.a is unresolved! > > Symbol __glXgetActiveScreen from module > > /usr/lib/modules/extensions/libdri.a is unresolved! > > XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0" > > Yes, I also saw these in xdm.log, but only once. > It seems that glibc is at fault, as a simple downgrade solved the problem. > > -- > Bruno Lustosa, aka Lofofora | Email: [EMAIL PROTECTED] > Network Administrator/Web Programmer | ICQ: 1406477 > Rio de Janeiro - Brazil | > > -- > gentoo-user@gentoo.org mailing list > > -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] nvidia drivers and glx
On 4/25/05, Robert Morris <[EMAIL PROTECTED]> wrote: > I had this too. I believe its the permissions being changed by/for PAM. > Check to make sure you are in the video group. Add your user to it if > you're not. That fixed it for me. Well, it seems to be fixed by downgrading glibc back to 2.3.4-20041102. I'm not sure if it's that glibc must be the same version of emul-linux-x86-glibc. Anyway, with old glibc, it's working. > Symbol __glXgetActiveScreen from module /usr/lib/modules/extensions/libdri.a > is unresolved! > Symbol __glXgetActiveScreen from module /usr/lib/modules/extensions/libdri.a > is unresolved! > XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0" Yes, I also saw these in xdm.log, but only once. It seems that glibc is at fault, as a simple downgrade solved the problem. -- Bruno Lustosa, aka Lofofora | Email: [EMAIL PROTECTED] Network Administrator/Web Programmer | ICQ: 1406477 Rio de Janeiro - Brazil | -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] nvidia drivers and glx
On Mon, 2005-04-25 at 15:00 -0400, Mike Markowski wrote: > Bruno Lustosa wrote on 04/25/05 12:40 ET: > > Hello. > > After some update, the GLX extensions stopped working. > > I noticed it because opengl xscreensavers would just segfault. After I > > quit X and tried to restart it, I would get a segfault when trying to > > load the glx extension. [...] > > I noticed this Saturday morning after doing a Friday night update > (Athlon 2600+, nvidia video). FWIW, the errors I see on my ~x86 set up > are below. I haven't had a chance to start tracking it down yet... > > Mike I had this too. I believe its the permissions being changed by/for PAM. Check to make sure you are in the video group. Add your user to it if you're not. That fixed it for me. Robert -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] nvidia drivers and glx
Bruno Lustosa wrote on 04/25/05 12:40 ET: > Hello. > After some update, the GLX extensions stopped working. > I noticed it because opengl xscreensavers would just segfault. After I > quit X and tried to restart it, I would get a segfault when trying to > load the glx extension. [...] I noticed this Saturday morning after doing a Friday night update (Athlon 2600+, nvidia video). FWIW, the errors I see on my ~x86 set up are below. I haven't had a chance to start tracking it down yet... Mike X Window System Version 6.8.2 Release Date: 9 February 2005 X Protocol Version 11, Revision 0, Release 6.8.2 Build Operating System: Linux 2.6.11-gentoo-r2 i686 [ELF] Current Operating System: Linux home 2.6.11-gentoo-r6 #1 Sat Apr 23 11:02:21 EDT 2005 i686 Build Date: 06 March 2005 Before reporting problems, check http://wiki.X.Org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Sat Apr 23 15:13:39 2005 (==) Using config file: "/etc/X11/xorg.conf" Using vt 7 Symbol __glXgetActiveScreen from module /usr/lib/modules/extensions/libdri.a is unresolved! Symbol __glXgetActiveScreen from module /usr/lib/modules/extensions/libdri.a is unresolved! XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0" after 0 requests (0 known processed) with 0 events remaining. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] nvidia drivers and glx
A really silly thought: did you try opengl-update nvidia ? W On Mon, Apr 25, 2005 at 02:17:32PM -0300, Bruno Lustosa wrote: > On 4/25/05, Jason Cooper <[EMAIL PROTECTED]> wrote: > > Some packages use static library paths to libGL, libXm, etc. Try > > re-merging your screensaver app to pick up the new path. X.org recently > > shuffled around the locations of some libraries. > > Yes, I tried doing this as soon as I saw it was not working, however > it still doesn't work. > Anyway, I file a bug on bugzilla. I'm not sure if this is an nvidia > issue or not, as it was working and stopped after an "unrelated" > update. > I tried reemerging xscreensaver, nvidia-kernel/glx. > I'll see what else I can do. > Btw, do you know of a package to make /var/log/emerge.log more readable? > Thank you! > > -- > Bruno Lustosa, aka Lofofora | Email: [EMAIL PROTECTED] > Network Administrator/Web Programmer | ICQ: 1406477 > Rio de Janeiro - Brazil | > > -- > gentoo-user@gentoo.org mailing list -- * Address: 45 Spelman Hall, Princeton University 08544 * * Phone: x68958 AIM: AngularJerk* *E-mail: [EMAIL PROTECTED]From: sep.dynalias.net * omega says hi i think he might be sulking because he has fur ~S Sortir en Pantoufles: up 14 days, 4:33 -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] nvidia drivers and glx
On 4/25/05, Jason Cooper <[EMAIL PROTECTED]> wrote: > Some packages use static library paths to libGL, libXm, etc. Try > re-merging your screensaver app to pick up the new path. X.org recently > shuffled around the locations of some libraries. Yes, I tried doing this as soon as I saw it was not working, however it still doesn't work. Anyway, I file a bug on bugzilla. I'm not sure if this is an nvidia issue or not, as it was working and stopped after an "unrelated" update. I tried reemerging xscreensaver, nvidia-kernel/glx. I'll see what else I can do. Btw, do you know of a package to make /var/log/emerge.log more readable? Thank you! -- Bruno Lustosa, aka Lofofora | Email: [EMAIL PROTECTED] Network Administrator/Web Programmer | ICQ: 1406477 Rio de Janeiro - Brazil | -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] nvidia drivers and glx
Bruno Lustosa ([EMAIL PROTECTED]) scribbled:
> Hello.
> After some update, the GLX extensions stopped working.
> I noticed it because opengl xscreensavers would just segfault. After I
> quit X and tried to restart it, I would get a segfault when trying to
> load the glx extension.
> The xorg.conf hasn't been changed.
> Finally, I had to remove the glx module from xorg.conf to have it
> working again (no 3d though).
> I tried re-emerging nvidia-{kernel,glx}, and also opengl-update
> nvidia, to no avail.
> Also, after this, I updated the drivers to the latest version (I was
> locked in 7167-r1, now I'm at 7174).
> I'm running gentoo on an athlon64.
> Anyone knows what make it fail? I looked into emerge.log, and only
> packages I saw that could generate weird things was baselayout and
> glibc.
Some packages use static library paths to libGL, libXm, etc. Try
re-merging your screensaver app to pick up the new path. X.org recently
shuffled around the locations of some libraries.
hth,
Cooper.
--
gentoo-user@gentoo.org mailing list
[gentoo-user] nvidia drivers and glx
Hello.
After some update, the GLX extensions stopped working.
I noticed it because opengl xscreensavers would just segfault. After I
quit X and tried to restart it, I would get a segfault when trying to
load the glx extension.
The xorg.conf hasn't been changed.
Finally, I had to remove the glx module from xorg.conf to have it
working again (no 3d though).
I tried re-emerging nvidia-{kernel,glx}, and also opengl-update
nvidia, to no avail.
Also, after this, I updated the drivers to the latest version (I was
locked in 7167-r1, now I'm at 7174).
I'm running gentoo on an athlon64.
Anyone knows what make it fail? I looked into emerge.log, and only
packages I saw that could generate weird things was baselayout and
glibc.
--
Bruno Lustosa, aka Lofofora | Email: [EMAIL PROTECTED]
Network Administrator/Web Programmer | ICQ: 1406477
Rio de Janeiro - Brazil |
--
gentoo-user@gentoo.org mailing list
