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.
I have had a similar problem that some of you are reporting, however for me it occurred at the 2.6.20 kernel upgrade, so I'm now back at 2.6.18-4.
And yes i like to try and keep things "the Debian way" as much as possible except for when it comes to the nvidia drivers.
The one thing i found out about this para_virt_ops option is that it is a kernel module compiled for the purposes of helping out programs like vmware and suck. I haven't yet found it in modconf and as happytux reported, the only way that i have seen for removing this option is to build your own kernel with the para_virt_ops module turned off.
The para_virt_ops module, from what i have seen reported, requires that the kernel be "taint free" from any third party modules. Also from what i have seen, it has been logged as a bug and hopefully someone, somewhere is looking into a way to fix it.
Many people have also spoken about asking nvidia the same old question of allowing the source code to be opened. I honestly cant see this happening in a hurry. So for now, until a release for a new kernel without this problem or nvidia go opensource, i am sticking with a 2.6.18-4 kernel.
Just thought i would throw my 2 cents worth in as i spent a weekend trying to solve it and didn't want others to do the same without knowing what they are up for.
DJ
Good to know info - sorry I draggged your orignal post off on a tangent...guess it pays to pay attention to the original post, eh ?!
You're right, sorry about that; I was in a hurry and wanted to help. I looked at the link you provided, and is very similar to the way I did it. I already had custom kernel, so I didn't update the kernel, but the remainder of the process did work when the other ways wouldn't. I am going to try to get the nvidia drivers installed this weekend on my etch machine.
No problem at all - it took me forever to find a site that had a comprehensive set of instructions that actually worked. The Debian Wiki has some too, but I've never compared them to the link I posted. Glad you got it working.
I compiled my own 2.6.21.1 kernel which had paravirtulisation enabled and meant I also got the error
Code:
GPL-incompatible module nvidia.ko uses GPL-only symbol 'paravirt_ops'
I fixed it using this method which didn't require a recompile of the kernel or a reboot to be able to run nVidia's 1.0.9755 installer.
I reproduce the steps below
Code:
1. Get kernel - linux-<version>.tar.bz2
2. Uncompress to /usr/src/linux-<version>
3. rm /lib/modules/<version>/build
4. ln -s /usr/src/linux-<version> /lib/modules/<version>/build
4. cp /usr/src/linux-headers-<version>/.config /usr/src/linux-<version>
5. cd /usr/src/linux-<version>
6. make xconfig (to be able to run x as root, I have installed sux) <-This line is my change
7. Disable paravirtualization in 'processor features'. Save and exit.
8. make prepare
9. make scripts
10. now i could compile and install nvidia kernel drive
But when I reboot here is what I have to do every time (I use KDE)
Code:
1.Boot into kernel
2.Kernel tries to load x-server and screen goes blank
3.I press Ctrl-Alt-F1
4.Log in as normal user
5. su -
6../etc/init.d/kdm stop
7.Install nVidia driver using .run script
8../etc/init.d/kdm start
9.Above boots me into KDE as normal user
1. Ctrl-Alt-F1
2. Login as root
3. sh nvidia-installer.run --uninstall
4. aptitude purge nvidia-kernel-source
5. aptitude purge nvidia-glx
6. Reboot
Not entirely sure that a reboot was needed but figured what the heck. I suspect it was unnecessary. When you reboot, it will not load x. Login as normal user.
Code:
1. su -
2. Enable unstable from the main source or mirror (main, contrib and non-free) in /etc/apt/sources.list
3. apt-get update && apt-get install nvidia-kernel-source module-assistant nvidia-settings
4. m-a prepare && m-a a-i nvidia
5. grep -q ^nvidia /etc/modules || echo nvidia >> /etc/modules
6. apt-get install nvidia-glx
7. Disable unstable from the main source or mirror (main, contrib and non-free) in /etc/apt/sources.list
8. /etc/init.d/kdm stop
9. modprobe nvidia
10. Check /etc/X11/xorg.conf that the driver is nvidia
11. /etc/init.d/kdm start
Now my 2.6.21.1 kernel loads up into X without issue. The above I got from here
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.