[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: More Nvidia Problems



ABrady,
  Actually, I installed my kernel with up2date.  It left the old one
intact (along with all of its modules), and put it as "linux-bak" in lilo.
So when I REALLY need my accerated nvidia drivers, I just reboot with the
old kernel.  The NVIDIA_kernel module which was built for that version
correctly loads.  But now with 2.4.3-12, when rebuilding the NVIDIA_kernel
with the newest driver, I used "--force" because it claimed to be already
installed.
  Just for you, uninstalled the NVIDIA_GLX package, as well as
NVIDIA_kernel.  I tried a rpm -ihv on the NVIDIA_kernel, and got exactly
the same output.

--Walker

On Sat, 7 Jul 2001, ABrady wrote:

> On Sat, 7 Jul 2001 13:45:47 -0400 (EDT) Walker Traylor
> <wtraylor professionalsites com> spake unto us:
>
> > Guys,
> >   I saw the previous thread about the Nvidia problems, but I'm still
> > getting errors.  I downloaded the lastet
> > NVIDIA_kernel-1.0-1251.src.rpm, I
> > did a --rebuild, then a -Uhv to install it.  I get lots of unresolved
> > symbols with the depmod part of the script.  Here's my output:
> >
> > [root muthaship wtraylor]# rpm -Uhv
> > /usr/src/redhat/RPMS/i386/NVIDIA_kernel-1.0-1251.i386.rpm --force
> > Preparing...
> > ###########################################
> > [100%]
> >    1:NVIDIA_kernel
> > ###########################################
> > [100%]
> > depmod: *** Unresolved symbols in
> > /lib/modules/2.4.3-12/kernel/drivers/video/NVdriver
> > /lib/modules/2.4.3-12/kernel/drivers/video/NVdriver: unresolved symbol
> > __global_cli
> > /lib/modules/2.4.3-12/kernel/drivers/video/NVdriver: unresolved symbol
> > tqueue_lock
> > /lib/modules/2.4.3-12/kernel/drivers/video/NVdriver: unresolved symbol
> > __global_save_flags
> > /lib/modules/2.4.3-12/kernel/drivers/video/NVdriver: unresolved symbol
> > __global_restore_flags
> > /lib/modules/2.4.3-12/kernel/drivers/video/NVdriver: insmod
> > /lib/modules/2.4.3-12/kernel/drivers/video/NVdriver failed
> > /lib/modules/2.4.3-12/kernel/drivers/video/NVdriver: insmod NVdriver
> > failed
> >
> > NVdriver installed successfully
> >
> > [root muthaship wtraylor]#
> >
> > Any ideas?
>
> Here's a lesson for you: NEVER, EVER, EVER, EVER use the -U flag on a
> kernel!! For that matter, it isn't usually wise to use the -F flag
> either. And definitely NEVER use --force to get it to overwrite
> important stuff!!!
>
> Some have gotten away with it, I know. But, just like driving drunk,
> sooner or later you won't get away with it any more. This is usually the
> sort of thing that happens when one does such things.
>
> You can recover, maybe, by going back to the old kernel (using the -i
> flag to install it) and making a new stanza in lilo.conf, running lilo
> and rebooting into that kernel. Then rpm -e the one you used the -U flag
> on and start over. Be sure to wipe out the old modules from the bad
> kernel, too.
>
> If it fails a second time, at least you can recover. Then you can rpm -i
> the source, manually configure it and play around until you get one that
> works. Kinda like when one downloads a kernel tarball, except I presume
> it has some patches in it that the stock kernel doesn't have.
>
> --
> The dark ages were caused by the Y1K problem.
>
>
>
> _______________________________________________
> Seawolf-list mailing list
> Seawolf-list redhat com
> https://listman.redhat.com/mailman/listinfo/seawolf-list
>





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]