David,
I went through this "fun" about 2 weeks ago (you can search the
archives for the problems I went through--I got some helpful replies,
but some questions were never answered...).
One fundamental problem is that the ram disk wasn't updated on your
system (this happened to me too). Sounds like you're lucky though--you
must not be using all Reiserfs partitions. I was, and the kernel
upgrade rendered my system unbootable. After a lot of tries, I finally
got my system sort-of booting again, at which time I immediately built a
kernel from source. I'll never use RPMs to update the kernel again. I
had been routinely building 2.2 kernels from source on my MDK7.2 system,
but hadn't gotten around to familiarizing myself with the 2.4 kernel
options yet. No time like the present to learn. :-)
I'm still having the problem with being unable to generate a ramdisk
using my 2.4.9 kernel (sounds like it's the same problem you have). If
you find a resolution to that, I'd be very interested in hearing about
it. I haven't had time to try to track it down.
Dan
On Sun, 2001-09-09 at 00: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
>
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
