On Mon, 2006-06-12 at 06:38 +0000, Paul Davies wrote:
> I work on page tables (I have Adam Wiggins GPT running under 2.6.17-rc5) on 
> a clean
> page table interface (fed to linux-mm on May 30).  At the moment I just get
> the default page table to be chosen at compile time from a config.  But, one
> day (far off in time) it might be a nice idea to be able to put a page table 
> into
> a module.  Probably fantasy but there you go.

Oh, cool.

> > > 4) I ran a script mkinitrdramfs to create the image for the ram disk
> > > (WORKED)
> > > and copied it to /boot.
> >
> >Woah. What's this mkinitrdramfs script? Do you
> >mean /usr/sbin/mkinitramfs, which is shipped in the initramfs-tools
> >package? Is it a custom script?
> It is the custom script (not yaird or anything).  It is the equivalent of
> mkinitrd that ships with red hat.

erm. That could be a problem. It's entirely possible it's doing
something that either the kernel or the debian boot process isn't
grokking. But I have no idea what.

> >Also, how are you calling this script? Are you sure it's building an
> >initrd using the modules for your new kernel, and not grabbing the ones
> >for the kernel you're currently running?
> I just execute it as root.  It is grabbing the ones for the kernel I am 
> running.
> Very early in boot.  It claims it can't find modules.dep in the directory 
> that
> it ought to be in.
> 
> FATAL: Could not load /lib/modules/2.6.15.1/modules.dep: No such file
> or directory.

That FATAL message is what you get when you try to boot the new kernel?
In that case, your new kernel thinks it's version 2.6.15.1. I'm guessing
the old kernel that boots successfully is a different version, and your
mkinitrd tool is defaulting to creating an image containing modules for
the old kernel, 'cause that's what is running when it's doing its thing.
Your script should have an option to specify the kernel version that it
needs to build an image for.

> This is the correct file and directory, its just that initrd never mounted 
> properly
> (I THINK).

Again, if the FATAL message is happening when the new kernel is booting,
then the initrd is being read, it just doesn't contain what the kernel
is looking for.

> >What changes have you made to grub? What's the exact error you get?
> 
> Grub ORI
> 
> title                     Debian GNU/Linux, kernel 2.6.15-1-486
> root                     (hd0,4)
> kernel                /boot/vmlinuz-2.6.15-1-486  root =/dev/hda5 ro
> initrd                  /boot/initrd.img-2.6.15-1-486
> savedefault
> boot
> 
> New Entry
> 
> title                     Test Kernel
> root                     (hd0,4)
> kernel                /boot/vmlinuz-2.6.15-1  root =/dev/hda5 ro
> initrd                  /boot/ramdisk.img
> savedefault
> boot
> 
> EXACT ERROR message:
> 
> FATAL: Could not load /lib/modules/2.6.15.1/modules.dep: No such file or 
> directory.
> FATAL: Could not load /lib/modules/2.6.15.1/modules.dep: No such file or 
> directory.
> ALERT! /dev/hda5 does not exist.  Dropping to shell!

*nod* That all looks fine. grub's seems to be doing its thing. The
kernel boots, and you'd get an entirely different message if it can't
find its initrd at all. I'm definitely willing to put money on the wrong
kernel modules being in the image now.

Hope that helps.
-- 
Pete

-- 
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html

Reply via email to