Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi, I'm using Debian etch, with a 2.6.18-6-686 smp kernel
my video adapter is a GeForce 8800.
I used the card with my old system, but now i have an intel core2-quad processor, the nvidia driver doesn't work, neither the package driver (i guess this one doesn't support up to 8800), nor the one from the nvidia site.
i also found this howto: http://www.informatix.or.id/willy/in...smp-kernel.php
except its not for debian, its for slackware.
here's the tail of Xorg.0.log (package-driver-output):
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(0): Enabling RENDER acceleration
(EE) NVIDIA(0): Failed to initialize the GLX module; please check in your X
(EE) NVIDIA(0): log file that the GLX module has been loaded in your X
(EE) NVIDIA(0): server, and that the module is the NVIDIA GLX module. If
(EE) NVIDIA(0): you continue to encounter problems, Please try
(EE) NVIDIA(0): reinstalling the NVIDIA driver.
(EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module! Please ensure
(EE) NVIDIA(0): that there is a supported NVIDIA GPU in this system, and
(EE) NVIDIA(0): that the NVIDIA device files have been created properly.
(EE) NVIDIA(0): Please consult the NVIDIA README for details.
(EE) NVIDIA(0): *** Aborting ***
(II) UnloadModule: "nvidia"
(II) UnloadModule: "ramdac"
(II) UnloadModule: "wfb"
(II) UnloadModule: "fb"
(EE) Screen(s) found, but none have a usable configuration.
My xorg.conf is just out of the box, except that i changed vesa to nvidia and enabled glx
I already googled for hours but wasn't able to find any usefull support for smp+nvidia, tell me if i should use anothe kernel (but i don't want to moss smp), or whatever else, i'll be very gladfull for any usefull help
PS: not sure if this thread belongs to hardware or to distros
This is easier than you think. The installation process for nVidia graphics on a multiple processor (SMP) system is the same as a single processor. If you have re-configure your kernel and re-compile it, you will have to re-compile the nVidia module because the symbols and pointers will be wrong. I strongly recommend do not use the pre-compile module. I recommend to always compile the nVidia module or else you will have problems. About the GLX problem, you either have a library problem or a problem in your /etc/X11/xorg.conf. From what I see, it hard to say what is causing it. I suggest post /etc/X11/xorg and the output of lsmod.
Do not use a framebuffer of nVidia (rivafb or nvidiafb) with the nVidia module or else they will conflict with each other.
tnx for the reply,
i uninstalled the package drivers and made sure nvidiafb wasn't loaded, then i re-ran the nvidia-installer, and it worked! i was also able to run glxgears, _but_ since i rebooted the machine its behaving like before,
so here's the tail of Xorg.0.log (nvidia-installer-driver)
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
(II) Initializing extension GLX
<eof>
it displays a black screen and as soon as i hit any key i'm back at the text-console, so it kind of gets stuck with the GLX extension
xorg.conf:
# vidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 1.0 (buildmeister@builder3) Fri Jan 11 15:05:59 PST 2008
# /etc/X11/xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the /etc/X11/xorg.conf manual page.
# (Type "man /etc/X11/xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg
xauth: creating new authority file /root/.serverauth.3615
X: warning; process set to priority -1 instead of requested priority 0
X Window System Version 7.1.1
Release Date: 12 May 2006
X Protocol Version 11, Revision 0, Release 7.1.1
Build Operating System: UNKNOWN
Current Operating System: Linux 4sukker 2.6.18-6-686 #1 SMP Sun Feb 10 22:11:31 UTC 2008 i686
Build Date: 18 January 2008
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 Feb 16 16:52:21 2008
(==) Using config file: "/etc/X11/xorg.conf"
XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0"
after 0 requests (0 known processed) with 0 events remaining.
This is strange - I got a 7600 and no problem.
How did you install the nvidia driver? Had trouble with some kernel version a while back.
Why is the agpgart module loaded? Ain't this a pci-e card?
The nvidia driver should work with a default debian kernel - it's not the debian way to install the driver but I couldn't care less.
Any way you screwed up something when you followed this tutorial and recompiled the kernel?
Last edited by crashmeister; 02-16-2008 at 11:19 AM.
i just used the installer from the nvidia website (http://us.download.nvidia.com/XFree8...69.09-pkg1.run)
which used to work perfectly nice in the past (on non smp-kernels)
of course i also installed all the necessary packages like gcc, kernel headers, libc-dev etc.
the installer complains that no matching kernel interface was found, and that it needs to compile one, which succeeds (at least the installer thinks so ), then it works until the box is rebooted.
yes, its an pci-e card, maybe the agpgart is also responsible for pci-e? at least "rmmod agpgart" complains that the module is in use by the nvidia module.
i already recompiled it several times, i found out, that if i simply disable the glx module i'm at least able to run the card in twinview mode. But of course without the glx module the driver is quite senceless
when i say compile, i'm talking about letting the installer compile the driver, are you using a different method to compile the driver (is there a "make-it-work"-Makefile ) ? are you using some command line options which i didn't?
yeah, i checked the logs, its just as i posted above, dmesg itself it not very helpfull as it only says nvidia module loaded, no complains about glx.
Just get a plain vanilla debian-smp-kernel in there - forget about compiling your own except your machine has 64 mb ram - and d/l the driver from nvidia and install it.
Plus compiling your own kernels with most (about 95% distros is a major pain to keep it up todate and everything else in sync)is just a m/s thing except you don't have any ram at all.The days when it was necessary to do that are over.
Compiling my own kernels was something I did a couple of years ago but it just doesn't make sense anymore with the machines today - except you run slack it seems like.
Here's what you do:
1. install debian kernel
2. get nvidia driver from website and install it
3. get back here and tell us what went wrong
Last edited by crashmeister; 02-17-2008 at 11:57 AM.
When loading up X Window Server with nVidia module and the screen goes to blank, it means the nVidia module is working. To fix the blanking, use the utility gtf to create modelines for your monitor. Then place the modelines in the monitor section. It does help to set the min and max of both the vertical and horizontal specs of your computer monitor. If your monitor is an LCD monitor, you may have to force EPID to off.
I forgot to say that nVidia will over write X11 libraries, so X Window Server might get confused with mixed libraries. I have not had trouble in the past when I install nVidia's modules. They over write the X11 libraries and worked fine. Many people said this method is wrong and they want to use other video cards in the future, so they created a method to copy X11 libraries and nVidia libraries to make it easy to switch between the two. Gentoo does this easily. Other distributions does the same.
I suggest use Gentoo because just like Debian, it works with CLI and has additional easy utilities to help you change settings.
I have no problems compiling the kernel and making the nVidia module to work. Installing nVidia is easy compared to other modules such as VMware modules. I am using kernel version 2.6.22 and nVidia version 100.14.19.
Quote:
Plus compiling your own kernels with most (about 95% distros is a major pain to keep it up todate and everything else in sync)is just a m/s thing except you don't have any ram at all.The days when it was necessary to do that are over.
Compiling my own kernels was something I did a couple of years ago but it just doesn't make sense anymore with the machines today - except you run slack it seems like.
There are no problems compiling the kernel. It is good experience and knowledge to have. Also compiling the kernel can decrease the amount of memory and some vulnerabilities that a full blown kernel has before. Third by compiling the kernel, you can add additional security.
There are no problems compiling the kernel. It is good experience and knowledge to have. Also compiling the kernel can decrease the amount of memory and some vulnerabilities that a full blown kernel has before. Third by compiling the kernel, you can add additional security.
Good one
Can you elaborate on that please so we learn this things,too?
Back to topic:
Does the xserver work with the nv driver?
Pls PM me the nvidia install log (it's in /var/log).
@Elektro
I have a lcd monitor, which displays "out of range"-warnings, so i could eliminate that problem
I don't want to change to gentoo since i use debian on over 14 boxes, but i guess maybe my kernel is simply to old since your's 2.6.22 and mine only 2.6.18?
@chrashmeister
no it doesn't work with the nv-driver since the card is not yet supported by nv
nvidia-installer --update says i already have the newest version (169.09).
I can't PM you, maybe because my forum status is n00by? so i'll just post it here:
Code:
nvidia-installer log file '/var/log/nvidia-installer.log'
creation time: Mon Feb 18 14:26:35 2008
option status:
license pre-accepted : false
update : true
force update : false
expert : false
uninstall : false
driver info : false
precompiled interfaces : true
no ncurses color : false
query latest version : false
OpenGL header files : true
no questions : false
silent : false
no recursion : false
no backup : false
kernel module only : false
sanity : false
add this kernel : false
no runlevel check : false
no network : false
no ABI note : false
no RPMs : false
no kernel module : false
force SELinux : default
no X server check : false
force tls : (not specified)
X install prefix : (not specified)
X library install path : (not specified)
X module install path : (not specified)
OpenGL install prefix : (not specified)
OpenGL install libdir : (not specified)
utility install prefix : (not specified)
utility install libdir : (not specified)
doc install prefix : (not specified)
kernel name : (not specified)
kernel include path : (not specified)
kernel source path : (not specified)
kernel output path : (not specified)
kernel install path : (not specified)
proc mount point : /proc
ui : (not specified)
tmpdir : /tmp
ftp mirror : ftp://download.nvidia.com
RPM file list : (not specified)
Using: nvidia-installer ncurses user interface
-> The latest NVIDIA Accelerated Graphics Driver for Linux-x86 (version 169.09)
is already installed.
Strange again - figured it would pull 171-something because thats what it did with my machine.On the other hand that was 32 bit.
Try nvidia-installer --sanity - maybe something pops up there.
Check with lspci if your card is recognized properly since you xconfig says 'unknown device'.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.