On Wed, 05 Apr 2006 07:53:28 +0100 Margot got an infinite number of monkeys to type out:
> > Like I say, whether I choose 'linux' or '2614-2' I still get: > > > > [EMAIL PROTECTED] joehill]# uname -r > > 2.6.14-2mdk > > > > This is starting to look real bad :-\ > > > > Thanks for any help. > > > > Unfortunately, urpmi kernel-source just installs the *latest* > kernel-source - it doesn't pick one to match the kernel(s) you've got > installed. > > You might be better off using rpmdrake - uninstall all kernels you've > got (except the one you're using at the time!) That's the problem, I can't get out of this new kernel I installed from Hawkwind's repos :-\ And I can't install the matching source, either from urpmi or rpmdrake, because for some reason the system thinks they're already installed: [EMAIL PROTECTED] joehill]# urpmi kernel-source The package(s) are already installed The following package names were assumed: kernel-source-2.6.14.2mdk If I could install the kernel source and build the nvidia drivers against *that*, it may solve my original problem...I hope. I still can't believe xorg from updates would break 3d accel. > and then install a matching pair of suitable kernel & kernel-source. > > Also, run lilo -v to see what kernel 'linux' is linked to. Aye, there's the problem, all lilo entries are pointing at the new kernel: [EMAIL PROTECTED] joehill]# lilo -v LILO version 22.6.1, Copyright (C) 1992-1998 Werner Almesberger Development beyond version 21 Copyright (C) 1999-2004 John Coffman Released 17-Nov-2004, and compiled at 14:16:24 on Sep 12 2005 Reading boot sector from /dev/hda Using GRAPHIC secondary loader Calling map_insert_data Mapping message file /boot/message -> message-graphic Calling map_insert_file Boot image: /boot/vmlinuz -> vmlinuz-2.6.14-2mdk Mapping RAM disk /boot/initrd.img -> initrd-2.6.14-2mdk.img Added linux * Boot image: /boot/vmlinuz -> [EMAIL PROTECTED] joehill]# lilo -v LILO version 22.6.1, Copyright (C) 1992-1998 Werner Almesberger Development beyond version 21 Copyright (C) 1999-2004 John Coffman Released 17-Nov-2004, and compiled at 14:16:24 on Sep 12 2005 Reading boot sector from /dev/hda Using GRAPHIC secondary loader Calling map_insert_data Mapping message file /boot/message -> message-graphic Calling map_insert_file Boot image: /boot/vmlinuz -> vmlinuz-2.6.14-2mdk Mapping RAM disk /boot/initrd.img -> initrd-2.6.14-2mdk.img Added linux * Boot image: /boot/vmlinuz -> vmlinuz-2.6.14-2mdk Mapping RAM disk /boot/initrd.img -> initrd-2.6.14-2mdk.img Added linux-nonfb Boot image: /boot/vmlinuz -> vmlinuz-2.6.14-2mdk Mapping RAM disk /boot/initrd.img -> initrd-2.6.14-2mdk.img Added failsafe Boot image: /boot/vmlinuz-2.6.14-2mdk Mapping RAM disk /boot/initrd-2.6.14-2mdk.img Added 2614-2 vmlinuz-2.6.14-2mdk Mapping RAM disk /boot/initrd.img -> initrd-2.6.14-2mdk.img Added linux-nonfb Boot image: /boot/vmlinuz -> vmlinuz-2.6.14-2mdk Mapping RAM disk /boot/initrd.img -> initrd-2.6.14-2mdk.img Added failsafe Boot image: /boot/vmlinuz-2.6.14-2mdk Mapping RAM disk /boot/initrd-2.6.14-2mdk.img Added 2614-2 Is there a way out of this? -- JoeHill / RLU #282046 / www.freeyourmachine.org +++++++++++++++++++++++++++ "There is no fire like passion, there is no shark like hatred, there is no snare like folly, there is no torrent like greed." -- Buddha ____________________________________________________ Want to buy your Pack or Services from Mandriva? Go to http://store.mandriva.com Join the Club : http://www.mandrivaclub.com ____________________________________________________
