[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: NVIDIA and Etch : WAS Re: Problems with GRUB and SATA



> 
> <snip xorg nvidia log>
> > (II) Initializing extension GLX
> > 
> > Backtrace:
> > 0: /usr/bin/X(xf86SigHandler+0x6d) [0x4802ed]
> > 1: /lib/libc.so.6 [0x2ac51f460110]
> > 2: /lib/libc.so.6(__ctype_tolower_loc+0x25) [0x2ac51f45a2c5]
> > 3: /usr/bin/X(xf86nameCompare+0xfe) [0x4a4cde]
> > 4: /usr/bin/X(InitInput+0x103) [0x45ea23]
> > 5: /usr/bin/X(main+0x337) [0x430e57]
> > 6: /lib/libc.so.6(__libc_start_main+0xda) [0x2ac51f44d4ca]
> > 7: /usr/bin/X(FontFileCompleteXLFD+0x9a) [0x43026a]
> > 
> > Fatal server error:
> > Caught signal 11.  Server aborting
> > 
> 
> Ah!  Seems to be a problem with the GLX extension,  are you sure the 
> nvidia-glx package matches the source from which you compiled the module?
> 
> I have googled this error (last line of backtrace) and it appears others 
> are having problems and it does seem to be the nvidia-glx package 
> causing the problem.  Bug#415878 (1) seems similar to your problem and 
> suggests commenting the Load glx from xorg.  Might want to try this and 
> see if it loads (albeit without glx acceleration) and add to the bug 
> report if necessary.
> 
> HTH
> 
> Wackojacko
> 


My thanks to Anthony, Joe, Magnus.... and especially to Jacko (can't
bring myself to write 'Wackojacko')   You were spot on...  remove the
"Load GLX" from xorg.conf and set the driver back to 'nvidia' and it
started up perfectly .......well .....'almost'. As you may recall from
earlier posts I had a heavy pink cast over the KDE desktop.... it's
still there, but now at least it goes away as soon as I start the
nvidia-settings programme .... unfortunately, it returns when I switch
to Gnome.... but as don't usually switch between display-managers it
shouldn't be a major problem.

Can I ask (and learn) then about the backtrace reporting.   I presume
than the backtrace always then applies to the last element on the log
prior to it?   I didn't know that (if correct).. so although I read the
backtrace I thought it was telling me that step seven in the trace was
the root problem (something to do with the fonts)... rather than the
actual bugbear being the last thing in the log above the point where the
backtrace begins.   Is my assumption correct?  Is it always so?  If
yes... then todays been helpful on two counts.

So ... final question (if you don't mind) how do I add this to the bug
report as you suggested?  Sorry, bug reporting is also new to me.


Thanks again folks... it really is <very> much appreciated....


Ian





Reply to: