On Sunday 09 September 2001 02:48, David Guntner wrote: > I'm hoping that someone can help me here.... > > I'm running Mandrake 8.0, and when I ran MandrakeUpdate this morning, I > noticed that there was a new kernel upgrade from my existing 2.4.3-20mdk to > 2.4.7-12.3mdk. I selected the kernel, header, source, and doc .rpm files > and let it do its thing. > > I now have a semi-crippled system. :-/ Modules don't seem to work anymore, > so it can't find things like my sound card and ethernet card. When running > depmod, I get an error message saying that > /lib/modules/2.4.3-20mdk/modules.dep can't be opened for writing - which > makes sense considering it isn't there anymore.... :-) What I want to know > is WHY does it want the old directory instead of the new one? For that > matter, a "uname -r" command returns the old version number instead of the > new one. Does anyone know what I'm missing, to get this thing back on its > feet again? > > I did fix the broken symlinks in the /boot directory (which broke after > running the upgrade), except for the initrd.img link, which is still > pointing to a non-existant file. I can't run a mkinitrd command, because > doing so gets me a message saying that the kernel doesn't know about the > loop device (presumably since I can't load any modules until depmod knows > where to look). > > Any assistance would be *greatly* appreciated. :-) > > --Dave use rpm to install kernel 2.4.3 from your install CDs Go pay the village scourger for five lashes for not reading the advisory which says that you should not use MandrakeUpdate on a kernel, never ever Download the kernel and install it with rpm -ivh This will leave LILO with a dual-boot--for old kernel and new kernel. Civileme
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
