On Fri, Jul 09, 2004 at 09:42:28AM -0500, Marc Williams wrote:
> On Thu, 08 Jul 2004 16:15:04 -0700, Nifty Hat Mitch wrote:
>
> > On Fri, Jul 02, 2004 at 09:52:09PM -0500, Marc Williams wrote:
> >> On Fri, 02 Jul 2004 17:59:08 -0700, Ioan Podoleanu wrote:
> >> > You're right, the combination nvidia-1.0-6106 with xawtv is a killer.
> >> > For xawtv, if you use "-remote" which disables overlay mode, it should
> >> > work. I also use -noxv which reduces the procesor use even further.
> >> > It's not perfect, but it works for me. My line now is: xawtv -c
> >> > /dev/video0 -remote -noxv .
> >>
> >> Thanks for the tip. Adding -remote -noxv does indeed provide an
> >> acceptable workaround. I hope I can eventually get overlay mode back
> >> though.
> >
> > I wonder if xawtv is making a gfx call that causes rivafb.ko to load. What
> > if rivafb.ko was moved ...?
>
> Since that would be an easy test and since I am in no position to argue
> otherwise, I tried it. It didn't work. Had the exact same freeze up as
> previously. But thanks for the resolution attempt.
>
> I think I'll leave my rivafb.ko permanently renamed since it doesn't seem
> to hurt anything...
Just in case the kernel loads objects in ways that ignore the file
name move it out of the normal dir. I have left mine in place and do
not see lockups. I think that rivafb.ko is a distraction at this point.
For gfx libraries there is a library file collision with the two
Mesa packages and the nVidia package. We should look there next.
At one time nVidia suggested that the Mesa libraries be removed. If
you get a message from the nVidia installer that things had been
'tinkered with' the Mesa rpms may be overwriting the nVidia GL
libraries (see Note 1 below).
We can track interesting changes as various gl drivers and libraries
are installed and uninstalled with "glxinfo":
glxinfo > /var/tmp/glxinfo-before-a-change
glxinfo > /var/tmp/glxinfo-after-a-change
Look for these Mesa packages and their contents.
Follow symbolic links with care:
xorg-x11-Mesa-libGL-6.7.0-5
xorg-x11-Mesa-libGLU-6.7.0-5
$ rpm -q --list xorg-x11-Mesa-libGL
/usr/X11R6/lib/libGL.so.1
/usr/X11R6/lib/libGL.so.1.2
/usr/lib/libGL.so.1
$ rpm -q --list xorg-x11-Mesa-libGLU
/usr/X11R6/lib/libGLU.so.1
/usr/X11R6/lib/libGLU.so.1.3
/usr/lib/libGLU.so.1
===
$ locate libGL.so
/usr/lib/libGL.so
/usr/lib/libGL.so.1.0.6106
/usr/lib/libGL.so.1
/usr/X11R6/lib/libGL.so.1
/usr/X11R6/lib/libGL.so.1.2
/usr/X11R6/lib/libGL.so
Do the same locate thing for libGLU.so
Compare and contrast the output of this "ls" listing
before and after running the nVidia installer in initstate 3.
Do the same diff/compare/contrast for libGLU and glxinfo.
# ls -l /usr/lib/libGL.so /usr/lib/libGL.so.1.0.6106 /usr/lib/libGL.so.1 /usr/X11R6/lib/libGL.so.1 /usr/X11R6/lib/libGL.so.1.2 /usr/X11R6/lib/libGL.so > ls-{before,after}
Same ls thing for libGLU.so (see /etc/cron.daily/slocate.cron
to refresh the data locate looks at after running install tool
as needed (nVidia's installer, rpm, up2date, yum).
# rpm -q --whatprovides /usr/X11R6/lib/libGL.so.1
xorg-x11-Mesa-libGL-6.7.0-5
# diff ls-before ls-after
Fill in here......
You might also, run a couple GL and X applications under strace to
track which libraries are being loaded and track each to it's rpm
or install package. This is always fun and informative, it might
tell you if an X library is somehow left over from the X86Free to
X-org switch.
Speaking of fun, give this file a look: /usr/lib/libGL.la
Here are some notes that pass by as the nVidia installer runs.
Note:(1)
WARNING: Your driver installation has been altered since it was initially
installed; this may happen, for example, if you have since
installed the NVIDIA driver through a mechanism other than the
nvidia-installer (such as rpm or with the NVIDIA tarballs). The
nvidia-installer will attempt to uninstall as best it can. Please
see the file '/var/log/nvidia-installer.log' for details.
So what is the log telling us?
Note:(2)
WARNING:
Your kernel was configured to include rivafb support as
a loadable kernel module.
The rivafb driver conflicts with the NVIDIA driver; the
NVIDIA kernel module will still be built and installed,
but be aware that the NVIDIA driver will not be able to
function properly if the rivafb module is loaded!
This note(3) was key for me. Make sure you have the right
/etc/X11/*conf* file. move all except xorg.conf into an OLD directory
so one of the many alternate names does not get
loaded. /var/log/Xorg.0.log should be checked both for the date/time
stamp but also for contents. Example
# ls -ltr /var/log/*X*
# less /var/log/Xorg.0.log
Note:(3)
Installation of the NVIDIA Accelerated Graphics Driver for Linux-x86
(version: 1.0-6106) is now complete. Please update your XF86Config or
xorg.conf file as appropriate; see the file
/usr/share/doc/NVIDIA_GLX-1.0/README for details.
xawtv also can depend on a kernel video drivers. The hardware and
driver under /dev/videoN could be important. We should drill down
there as well. List the kernel module for video. The nVidia driver
and GL may have nothing to do with this!
When I run xawtv I see some info.
# xawtv -noscale -noxv -c "/dev/video0"
...
/dev/video0 [v4l]: no overlay support
...
FWIW: xawtv also runs for me via ssh with a remote display.
glxinfo returns a very different list of functions
for a remote display.
For a program to learn what feature is supported the libraries
must be correct which is why I am trying to cover so many things
here.
And lastly a kernel version check since things are stable here,
mine is:
# uname -r
2.6.6-1.435.2.3
--
T o m M i t c h e l l
