Dan Hensley grabbed a keyboard and wrote:
>
> 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.
Well, in the process of trying to back out the new kernel and replacing the
old kernel, I managed to have that end up happening to me. The system
said, after I had reinstalled the kernel from the CD-ROM, that it couldn't
mount / at boot time (kernel panic). Oops. My / system *is* Reiser FS. I
think, based on what you're saying, that the stock kernel .rpm file off of
the CD-ROM may not know what to do with it. I had set up a /boot partition
which was ext2, which had previously let me boot up the system.
So, despite my best efforts to reverse my mistake (and thanks again to
those who replied with helpful suggestions - I did learn a bunch of things
from them), it looks like I get to reinstall from scratch again after all.
Dammit. What's annoying about it is that it's sooo bloody time consuming,
and with the 8.1 final release coming up, I hate to have to go through this
so close to the next install. :-)
> 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 *definitely* thinking along these lines, too. I think from now on I'll
just grab the source, doc, and header .rpm files and install them, and then
compile the kernel. I've been browsing verious sources to get myself back
up to speed (used to do this back in the Red Hat 2.x days; then I got
lazy... :) on kernel compiling, so I think I'll be able to handle it from
there. Maybe. :-)
One thing, though, which hasn't been adequately explained to me: By what
magic does depmod know *which* of the directories under /lib/modules to
pull from? How does it know which version of the kernel that you're
running? Does anyone know the answer to this mystery? :-)
> 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.
You're talking about the initrd.img file, or something else?
--Dave
--
David Guntner GEnie: Just say NO!
http://www.akaMail.com/pgpkey/davidg or key server
for PGP Public key
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
