Re: initrd question
May be the simplest way is to build your own kernel.
On the other I guess that surch an information is somewhere in the
Steven Curtis wrote:
I'm not sure how to check that. I am using the kernel that is included
with the Debian package kernel-image version 2.6.7-2. How can you tell
what version of initrd was used to build it?
Jerome BENOIT wrote:
the package initrd-tools was recently updated [and if I remember well
important bugs were fixed]:
have you check that your kernel was built with the latest version ?
Steven Curtis wrote:
Stefan O'Rear wrote:
As to the first question, by examining the /tmp directory left by
using the -k switch on mkinitrd, I can verify that
/initrd/loadmodules contains the line 'modprobe -k aic7xxx' and that
exists. I cannot verify these things on the image itself because I
need to load loop support to mount the initrd image and when I
modprobe loop, its missing the symbols kunmap_high, create_bounce,
highmem_start_page, and kmap_high.
On Fri, Sep 10, 2004 at 07:58:53PM -0400, Steven Curtis wrote:
I'm trying to upgrade to the vmlinuz-2.6.7-1-k7 kernel and my
system has an Adaptec AIC7XXX EISA/VLB/PCI adapter. The stock
vmlinuz-2.6.7-1-k7 kernel has aic7xxx support compiled as a
module. I added the aic7xxx module line to /etc/mkinitrd/modules
and recreated the initrd image with 'mkinitrd -o
/boot/initrd.img-2.6.7-1-k7 2.6.7-1-k7'. I'm using grub as my boot
loader so I figured all is well. Booting the new kernel does not
load the module and thus upon trying to mount the root file system
produces the following:
VFS:cannot open root device "sda2"or unknown-block (0,0)
Please append correct "root=" boot option
Kernel panic: VFS Unable to mount root fs on unknown-block(0,0)
presumably because the SCSI module has not been loaded yet. I do
not see any of the probing messages my old 2.4.19 kernel outputs
which has aic7xxx support compiled in. Any advice or suggestions
on where to look for problems or what I have done wrong?
Is the actual module (.ko file) in /etc/mkinitrd?
Does the kernel give a message when loading the module?
As to the second question, I know that the SCSI card is not being
probed because when it is probed, the devices take their time when
responding. After the Kernel panic, I am unable to scroll back up to
see what messages may have been output before that point. From what
is visible on the screen, there are no messages of any modules
getting loaded. The only mention of a ramdisk is a line that reads:
'RAMDISK driver initialized: 16 RAM disks of 8192K size 1024
blocksize'. The last screen visible before the panic starts with
'devfs: boot_options: 0x0'. I've read that devfs can cause problems,
but the same behavior is observed with the 'devfs=nomount' boot