DebianThis forum is for the discussion of Debian 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.
am having a problem getting the offical nvidia drivers for debian working i know i must use a patched version of the nvidia installer due to the kenerl
Linux littleb 2.6.21-2-686 #1 SMP Wed Jul 11 03:53:02 UTC 2007 i686 GNU/Linux
Code:
nvidia-installer log file '/var/log/nvidia-installer.log'
creation time: Sun Sep 30 09:42:17 2007
option status:
license pre-accepted : false
update : false
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
-> 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: No)
-> No precompiled kernel interface was found to match your kernel; this means
that the installer will need to compile a new kernel interface.
-> Performing CC sanity check with CC="gcc-4.1".
-> Performing CC version check with CC="gcc-4.1".
-> Kernel source path: '/lib/modules/2.6.21-2-686/build'
-> Kernel output path: '/lib/modules/2.6.21-2-686/build'
-> Performing rivafb check.
-> Performing nvidiafb check.
-> Performing Xen 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-i2c.o nvacpi.
o nv.o nv-vm.o os-agp.o os-interface.o os-registry.o nv-i2c.o nvacpi.o nvidi
a.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 -f stprof stprof.o symtab.h Modules.symvers
rm -f -rf .tmp_versions
rm -f Makefile
-> Building kernel module:
executing: 'cd ./usr/src/nv; make module SYSSRC=/lib/modules/2.6.21-2-686/bu
ild SYSOUT=/lib/modules/2.6.21-2-686/build'...
sh ./conftest.sh "gcc-4.1" "gcc-4.1" /lib/modules/2.6.21-2-686/build /lib/mo
dules/2.6.21-2-686/build cc_sanity_check full_output
sh ./conftest.sh "gcc-4.1" "gcc-4.1" /lib/modules/2.6.21-2-686/build /lib/mo
dules/2.6.21-2-686/build select_makefile full_output
make --no-print-directory -f Makefile module
NVIDIA: calling KBUILD...
make CC=gcc-4.1 KBUILD_VERBOSE=1 -C /lib/modules/2.6.21-2-686/build SUBDIRS
=/tmp/selfgz74469473/usr/src/nv modules
test -e include/linux/autoconf.h -a -e include/config/auto.conf || ( \
echo; \
echo " ERROR: Kernel configuration is invalid."; \
echo " include/linux/autoconf.h or include/config/auto.conf are mis
sing."; \
echo " Run 'make oldconfig && make prepare' on kernel src to fix it
."; \
echo; \
/bin/false)
mkdir -p /tmp/selfgz74469473/usr/src/nv/.tmp_versions
rm -f /tmp/selfgz74469473/usr/src/nv/.tmp_versions/*
make -f scripts/Makefile.build obj=/tmp/selfgz74469473/usr/src/nv
cp /tmp/selfgz74469473/usr/src/nv/nv-kernel.o /tmp/selfgz74469473/usr/src/nv
/nv-kernel.o
cp: cannot stat `/tmp/selfgz74469473/usr/src/nv/nv-kernel.o': No such file o
r directory
make[3]: *** [/tmp/selfgz74469473/usr/src/nv/nv-kernel.o] Error 1
make[2]: *** [_module_/tmp/selfgz74469473/usr/src/nv] Error 2
NVIDIA: left KBUILD.
nvidia.ko failed to build!
make[1]: *** [module] Error 1
make: *** [module] Error 2
-> Error.
ERROR: Unable to build the NVIDIA kernel module.
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.
linux-headers-2.6.21-2-686 is already the newest version.
linux-image-2.6.21-2-686 is already the newest version
are you using the debian nvidia driver? I couldn't get that one to work, but the one off from the nvidia website works just fine. There are a couple threads on it from this summer. Hope that helps...
In the past I've used both the official Nvidia source and the official Debian way. I'd like my box (fresh Debian/Lenny install) to stay as pure Debian as possible.
From what I gather, there is no Debian nVidia drivers at this time in Lenny. Does anybody have any idea with they will be released?
No more para-virtualization patched driver is necessary since Lenny now uses linux-image-2.6.22 kernels rather than that 2.6.21 that had that problem.
The NVidia driver from NVidia works fine, but since Lenny now uses gcc version 4.2 and puts that into its environment you need to do:
export CC=gcc-4.1
Then run the installer normally and do dpkg-reconfigure xserver-xorg afterwards to load the nvidia driver just installed.
You could also pull the driver using the Debian way from Sid. However you must then use apt pinning so you don't start pulling in software from Sid and no longer be running Lenny. I believe there is a dependency for the xorg-xserver from Sid if installing the NVidia driver from Sid. If you just use the NVidia driver downloaded from NVidia, that isn't necessary. But folks have installed the Debian way and pulled in the xorg upgrade without complaints that I've seen. Just watch out for a keyboard driver bug that is the main thing holding back the newer xorg from being released into Lenny I think.
Plenty of how-to's at the Debian forum for this stuff, and articles in the Debian wiki. You'll get it done with a small bit of investigating.
No more para-virtualization patched driver is necessary since Lenny now uses linux-image-2.6.22 kernels rather than that 2.6.21 that had that problem.
When I went from the 2.6.18 kernel to the 2.6.20, I had to use the patched driver from Nvidia. When I went to the 2.6.21 kernel I tried the un-patched Nvidia driver and still got the same error and had to use the patched Nvidia driver optimized for the 2.6.21. When I went to 2.6.22, I'm pretty sure I tried the NVIDIA-Linux-x86-100.14.11-pkg1.run which still gave me the paravirtualization error and used the same version "patched" driver from Nvidia.
I've been kind of preoccupied lately and have not done updates too often. But when I did update three weeks ago, when I would enable beryl the OS would go into an endless cycle of re-boots as there were display problems. I had to boot into single user mode to un-install Beryl and Beryl-manager to be able to boot into graphic mode. Then re-install the patched driver and beryl.
According to the Nvidia installer, libglx.so was not sym-linked or something similar.
I used to had the same problem with kernel 2.6.21. on my 32 bit box but i ran the patched drivers and work fine, then i move 2.6.22 and no need for patched drivers, now i'm running 64 bits and no problem found.
But try this new drivers you still are using NVIDIA-Linux-x86-100.14.11-pkg1.run
Thanks, fellas. I'm trying as hard as I can to stay pure Debian. So that is why I've yet to use the Nvidia method. But it looks like I just might have to.
The idea of using Sid repos, even if I do pin it, doesn't thrill me much. So it looks like it's Nvidia for me.
By the way what about when I distro-upgrade to the next testing version (in a year or two)? I know I'll have to do some jumping through hoops to get my drivers up and running again. Can anyone point me to a good site on how to proceed?
It's always better to stay with the official Debian packages. Running Lenny, you should now have kernel 2.6.22. Check that first. If necessary install that kernel, reboot, then... this is the right way to do it.
Hey alioop, i really don't know about performance with Nvidia or debian drivers because i haven't test it yet. I'm running cedega and wine to play some games with my box, i have a 8800gtx and its a shame not give it some use jejeje. If you found which driver give better performance let me know.
rickh
Quote:
in order to understand what's going on here, study this.
thanks for that link. i read it and now using both repos jejeje, i downloaded open office 2.3 cd jeje, now i just can installed it, and get new stuff like icedove 2.0 without risking my system. Thanks very much
Well doing that kind of thing wasn't exactly what rickh was recommending. He simply was suggesting the opinion of many Debian users that building the NVidia driver and module will be more customized for the Debian system when done using packages built with that in mind rather than the one size fits all NVidia script.
Each package you pull from Sid with the -t unstable switch brings in that package plus any additional dependencies and recommends that can't be satisfied with available Lenny packages.
So, the more you install from Sid, the more you are running a mixed Lenny/Sid system. The packages not released into testing are delayed for a variety of reasons, but unless the only reason you see on the developer page for "Why is this package not in testing yet" is that is can't be built on other architectures but on yours (normally i386) it's okay, then it really isn't ready, as judged by bugs, time tested, installable without breaking some other Lenny package, etc.
For example, if you look at Icedove you'll see things like new bugs introduced by the upgrade, upgrading some things needed as dependencies makes a bunch of other Lenny packages uninstallable, etc. Until these issues are sorted and fixed, the newer Icedove is not ready for Lenny.
I'm not saying it will positively break things that you use or will notice if they are broken. Many times pulling in specific packages works out okay. But it is counter to the Debian way of ensuring stability by way of sticking with one distribution and using Debian packages whenever possible, which was the whole point of Rickh's advice regarding doing the NVidia installation the Debian way.
Most often, if what's in testing doesn't satisfy then the best approach would be an upgrade to unstable. A full unstable system with a more careful approach regarding software upgrades is likely more stable than a Lenny system mixed together with a bunch of Sid packages. That is the approach taken by the Sidux distribution. The same approach is used by many users of Sid proper (not going with the Sidux fork).
I any case, this stuff makes for an interesting discussion! I just wanted to stop you in your tracks with the reminder, if you didn't realize it, that you are NOT safe from changing your system to Sid just by making the default release testing, if you personally -t unstable a bunch of Sid packages. You can be bitten by some of the dependencies pulling in packages that are not yet in Lenny for good reasons.
No problem with a single proprietary driver binary install, perhaps, but it is not a good idea to go forward pulling software in as you suggest. But since it is your system, enjoy.
Personally, I've always used the NVidia downloaded script on any distro and enjoy the latest releases, betas with their fixes, and support from NVidia tech's when doing that. I only added Sid at one time to get that 2.6.22 Kernel in the days when we needed it for NVidia. I still used the script. But, to each his own.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
I just wanted to stop you in your tracks with the reminder, if you didn't realize it, that you are NOT safe from changing your system to Sid just by making the default release testing, if you personally -t unstable a bunch of Sid packages. You can be bitten by some of the dependencies pulling in packages that are not yet in Lenny for good reasons.
