| View previous topic :: View next topic |
| Author |
Message |
flysideways
Guru
Joined: 29 Jan 2005
Posts: 438
|
 Posted: Sat Nov 05, 2005 8:19 pm Post subject: nvidia Rant [mostly Solved] |
 |
|
[RANT]
I have spent way too much of the last 2 days trying to get the nvidia driver working on two of my three Gentoo installs. The first one is a 32 bit athlon the other is an amd64. I've tried NVmkdevices.sh, I've tried the udev hack, I've tried various kenels and versions of the nvidia driver, I've even tried building the nvidia sourced driver against a couple of different kernels. The one thing that remains consistant is that modprobe nvidia fails. It doesn't matter if I have /dev/nvidia* or not, or used the various chmod suggestions.
Now I understand the anality of not wanting nonGPLed stuff calling the kernel. I thought that was why I had to suffer through the growing pains of ipw2100 from some of its earliest versions on my then new Centrino laptop. If I get it right there is the kernel driver which is GPLed and there is an Intel provided proprietary firmware. Maybe someday the video card manufacturers will go that way, but I don't want this pain until then.
Did I mention my third Gentoo box is also an amd64, same motherboard as the other amd64, matter of fact pretty much same everything except processor? I've had nvidia-kernel on it for a while now and it gets -uD world pretty regularly but it is still on a 2.6.11 kernel, one that's no longer in portage.
All I wanted to do was use the nvidia driver to hook a box up to mv tv and view my videos.
[/RANT]
The 32 bit athlon box works fine with FC4, 2.6.13 and nvidia 7676. Go figure. Fedora for multimedia is a pain with the various needed repositories. Just throwing Win Media Center at it would solve the problem, but........
I'm sure that if I were a better hack this'd be no problem, but I'm not.
Last edited by flysideways on Sun Nov 06, 2005 1:25 am; edited 1 time in total |
|
| Back to top |
|
 |
PovMan
Guru
Joined: 30 Sep 2002
Posts: 375
Location: Australia
|
| Posted: Sat Nov 05, 2005 9:22 pm Post subject: |
|
|
How does the modprobe fail? Like, what kind of error?
_________________
I am SPAM, hear me roar.
Before posting your own topic, try to answer at least one unanswered one. |
|
| Back to top |
|
|
flysideways
Guru
Joined: 29 Jan 2005
Posts: 438
|
| Posted: Sun Nov 06, 2005 12:23 am Post subject: |
|
|
This is from a K7S5A with an XP2000. /dev/nvidia* exist from NVmakedevices.sh .
| Code: | K7S5A ~ # modprobe nvidia
FATAL: Error inserting nvidia (/lib/modules/2.6.13-gentoo-r5/video/nvidia.ko): No such device
|
From/var/log/messages, there is no riva in the kernel
| Code: | Nov 5 17:22:47 K7S5A nvidia: module license 'NVIDIA' taints kernel.
Nov 5 17:22:47 K7S5A NVRM: The NVIDIA probe routine was not called for 1 device(s).
Nov 5 17:22:47 K7S5A NVRM: This can occur when a driver such as rivafb or rivatv was
Nov 5 17:22:47 K7S5A NVRM: loaded and obtained ownership of the NVIDIA device(s).
Nov 5 17:22:47 K7S5A NVRM: Try unloading the rivafb (and/or the rivatv) kernel module
Nov 5 17:22:47 K7S5A NVRM: (or reconfigure your kernel without rivafb support), then
Nov 5 17:22:47 K7S5A NVRM: try loading the NVIDIA kernel module again.
Nov 5 17:22:47 K7S5A NVRM: No NVIDIA graphics adapter probed!
Nov 5 17:22:47 K7S5A NVRM: The NVIDIA probe routine was not called for 1 device(s).
Nov 5 17:22:47 K7S5A NVRM: This can occur when a driver such as rivafb or rivatv was
Nov 5 17:22:47 K7S5A NVRM: loaded and obtained ownership of the NVIDIA device(s).
Nov 5 17:22:47 K7S5A NVRM: Try unloading the rivafb (and/or the rivatv) kernel module
Nov 5 17:22:47 K7S5A NVRM: (or reconfigure your kernel without rivafb support), then
Nov 5 17:22:47 K7S5A NVRM: try loading the NVIDIA kernel module again.
Nov 5 17:22:47 K7S5A NVRM: No NVIDIA graphics adapter probed!
. |
From nvidia-installer.log, thought it should be nvidia.o not nvidia.ko | Code: | Using: nvidia-installer ncurses user interface
-> License accepted.
-> No precompiled kernel interface was found to match your kernel; would you li
ke the installer to attempt to download a kernel interface for your kernel f
rom the NVIDIA ftp site (ftp://download.nvidia.com)? (Answer: Yes)
-> No matching precompiled kernel interface was found on the NVIDIA ftp site;
this means that the installer will need to compile a kernel interface for
your kernel.
-> Kernel source path: '/lib/modules/2.6.13-gentoo-r5/source'
-> Performing CC test with CC="cc".
-> Performing rivafb check.
-> Cleaning kernel module build directory.
executing: 'cd ./usr/src/nv; make clean'...
rm -f -f nv.o nv-vm.o os-agp.o os-interface.o os-registry.o nv.o nv-vm.o os-
agp.o os-interface.o os-registry.o nvidia.mod.o
rm -f -f build-in.o nv-linux.o *.d .*.{cmd,flags}
rm -f -f nvidia.{o,ko,mod.{o,c}} nv_compiler.h *~
rm -f -rf .tmp_versions
-> Building kernel module:
executing: 'cd ./usr/src/nv; make module SYSSRC=/lib/modules/2.6.13-gentoo-r
5/source SYSOUT=/lib/modules/2.6.13-gentoo-r5/build'...
.
.
.
.
.
Kernel module compilation complete.
ERROR: Unable to load the kernel module 'nvidia.ko'. This is most likely
because the kernel module was built using the wrong kernel source files.
Please make sure you have installed the kernel source files for your
kernel; on Red Hat Linux systems, for example, be sure you have the
'kernel-source' rpm installed. If you know the correct kernel source
files are installed, you may specify the kernel source path with the
'--kernel-source-path' commandline option.
-> Kernel module load error: insmod: error inserting './usr/src/nv/nvidia.ko':
-1 No such device
-> Kernel messages:
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as rivafb or rivatv was
NVRM: loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the rivafb (and/or the rivatv) kernel module
NVRM: (or reconfigure your kernel without rivafb support), then
NVRM: try loading the NVIDIA kernel module again.
NVRM: No NVIDIA graphics adapter probed!
eth0: Media Link On 100mbps full-duplex
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as rivafb or rivatv was
NVRM: loaded and obtained ownership of the NVIDIA device(s).
NVRM: Try unloading the rivafb (and/or the rivatv) kernel module
NVRM: (or reconfigure your kernel without rivafb support), then
NVRM: try loading the NVIDIA kernel module again.
NVRM: No NVIDIA graphics adapter probed!
ERROR: Installation has failed. Please see the file
'/var/log/nvidia-installer.log' for details. You may find suggestions
on fixing installation problems in the README available on the Linux
driver download page at www.nvidia.com.
|
/var/log/gdm after build of current kernel. | Code: |
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.12-gentoo-r6 i686 [ELF]
Current Operating System: Linux K7S5A 2.6.13-gentoo-r5 #3 Fri Nov 4 20:25:30 CST 2005 i686
Build Date: 07 October 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: Fri Nov 4 20:59:24 2005
(==) Using config file: "/etc/X11/xorg.conf"
Symbol __glXgetActiveScreen from module /usr/lib/modules/extensions/libdri.a is unresolved!
Symbol __glXgetActiveScreen from module /usr/lib/modules/extensions/libdri.a is unresolved!
(EE) Failed to initialize GLX extension (NVIDIA X driver not found)
|
My K8 install will stay Gentoo but I may try KnoppMyth on the K7S5A.
Thanks for taking the time to look at this.
Edit:I frequently actually write notes as I'm playing with the computers but not very often when I think it's a routine operation. I somehow didn't expect this to become so involved. |
|
| Back to top |
|
|
flysideways
Guru
Joined: 29 Jan 2005
Posts: 438
|
| Posted: Sun Nov 06, 2005 1:24 am Post subject: |
|
|
| Quote: | | I'm sure that if I were a better hack this'd be no problem, but I'm not. |
OK, I had nvidiafb in the kernel as a module on the K7S5A and built in on the K8. After removing that nvidia loads. I lose my nice small text console though and also have some other problems because Gnome is now some very funny colors. I'll look through xorg.conf and the Nvidia guide and see what I've missed.
Edit: Neither xorg.conf had a DefaultDepth specified, added at 24 and all is good. Frame rates at 1600x1200 full screen in glxgears; K8 with FX5200 52fps, K7 with FX5500 78fps. Is the Fx5500 really supposed to be that much faster than the FX5200 or is it some setting or the amd64 stuff? Now it's time to get the K7 up as a media center. |
|
| Back to top |
|
|
jonnevers
Veteran
Joined: 02 Jan 2003
Posts: 1594
Location: Gentoo64 land
|
| Posted: Sun Nov 06, 2005 2:24 am Post subject: |
|
|
| flysideways wrote: | | Quote: | | I'm sure that if I were a better hack this'd be no problem, but I'm not. |
OK, I had nvidiafb in the kernel as a module on the K7S5A and built in on the K8. After removing that nvidia loads. I lose my nice small text console though and also have some other problems because Gnome is now some very funny colors. I'll look through xorg.conf and the Nvidia guide and see what I've missed.
|
if you want framebuffer support, try vesa-tng. it should be in the kernel you already have and it does not interfere with the nvidia kernel module. I use vesa-tng with a default setting of 1280x1024-32@85 |
|
| Back to top |
|
|
ecatmur
Advocate
Joined: 20 Oct 2003
Posts: 3595
Location: Edinburgh
|
| Posted: Sun Nov 06, 2005 2:54 am Post subject: |
|
|
Yeah, the Linux vt model is broken: when you switch in/out of X you're basically rebooting the video card so another driver can take over. Maybe someday we'll be able to use the same driver for all consoles, and fall back to (S)VGA only when things go very wrong... vesa-tng works ok for me though.
_________________
No more cruft
dep: Revdeps that work
Using command-line ACCEPT_KEYWORDS? |
|
| Back to top |
|
|
dmpogo
Advocate
Joined: 02 Sep 2004
Posts: 3267
Location: Canada
|
| Posted: Tue Nov 08, 2005 4:22 am Post subject: |
|
|
| flysideways wrote: | | Quote: | | I'm sure that if I were a better hack this'd be no problem, but I'm not. |
OK, I had nvidiafb in the kernel as a module on the K7S5A and built in on the K8. After removing that nvidia loads. I lose my nice small text console though and also have some other problems because Gnome is now some very funny colors. I'll look through xorg.conf and the Nvidia guide and see what I've missed.
Edit: Neither xorg.conf had a DefaultDepth specified, added at 24 and all is good. Frame rates at 1600x1200 full screen in glxgears; K8 with FX5200 52fps, K7 with FX5500 78fps. Is the Fx5500 really supposed to be that much faster than the FX5200 or is it some setting or the amd64 stuff? Now it's time to get the K7 up as a media center. |
100fps for glxgear is too small, on good cards it is in thousands.
I think you don't have something enabled, agp or opengl.
What does
cat /proc/driver/nvidia/agp/status
say ? |
|
| Back to top |
|
|
Headrush
Watchman
Joined: 06 Nov 2003
Posts: 5597
Location: Bizarro World
|
| Posted: Tue Nov 08, 2005 5:07 am Post subject: |
|
|
| jonnevers wrote: | | if you want framebuffer support, try vesa-tng. it should be in the kernel you already have and it does not interfere with the nvidia kernel module. I use vesa-tng with a default setting of 1280x1024-32@85 |
Or just vesa support. I thought vesa-tng didn't work on amd64 yet? |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
