![](https://seccdn.libravatar.org/avatar/4937736922892cdb4e6e48aacb15b2ee.jpg?s=120&d=mm&r=g)
Aniruddha wrote:
On Mon, 2007-10-29 at 16:27 -0700, Sloan wrote:
I tried that by removing and reinstalling the nvidia driver with zypper. unfortunately this didn't work. What else can I try?
It should also be possible to do this before rebooting if you change the symlink to the kernel source. Is there a openSUSE tool for this?
AFAIK the suse tools will manage the suse nvidia packages, which are built for the suse kernels - but if you're using the -rt kernel, you're going to be downloading the driver from nvidia.com and doing a manual install.
Also, IIRC there are ways to build for a kernel you're not running, you'd have to run the nvidia installer with the help option to get the exact syntax needed, as I've never done that, but only remember seeing something about it in the nvidia installer options.
Joe
Thank you for answer. By looking around in yast2 package manager I determined that kernel-rt is at version 2.6.22.5-31. My current kernel is version 2.6.22.9-0.4.
The current symlink points to 2.6.22.9-0.4. Changing this to linux-2.6.22.5-31-obj (with ln -sfn linux-2.6.22.5-31-obj) should solve the Nvidia driver issue.
The drivers built for the suse kernel won't work with the -rt kernel. I'd expect at the very least, no hardware-accelerated 3D, and perhaps a crash upon attempting to load the drivers.
Is there an easy way to manage kernel symlinks in openSUSE?
The ln command seems easy to me - but then again, I guess I'm not familiar with whatever "symlink management" software you've used before. In any case, I've not had to do any sort of manual kernel symlink management on suse. The kernel versions I've built all coexist happily in /usr/src/ along with the suse supplied kernels and the init scripts are smart enough to load the correct modules on boot. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org