On Fri, 2002-05-24 at 18:58, Petro wrote: > On Fri, May 24, 2002 at 09:50:29AM -0500, Ken Causey wrote: > > > On 05/24 05:07 Ken Causey wrote: > > > > VFS: Cannot open root device "802" or 08:02 > > > > Please append a correct "root=" boot option > > > > Kernel panic: VFS: Unable to mount root fs on 08:02 > > > > I have a single SCSI drive (2 partitions, first is swap, second is > > > root) > > > > connected via an Adaptec 29160. > > > I didn't see any Adaptec's message before the above lines. > > > Did you have Adaptec driver support in the kernel? You can't have it > > > in a > > > module. > > > Oki > > > >RAMDISK: cramfs filesystem found at block 0 > > > >RAMDISK: Loading 1988 blocks [1 disk] into ram disk... done. > > and it resides on the scsi hd. Or is this something else? > > I haven't dealt all that much with the initrd stuff, but don't you > also have to tell the kernel to load the right module somehow? Like > in modules.conf (or whatever the equivalent is for initrd). >
testserver:/# cat /initrd/loadmodules modprobe -k ext3 modprobe -k ext2 modprobe -k aic7xxx loadmodules is sourced by /initrd/linuxrc (oh and of course /initrd is my mount of the initrd.img file). Ken P.S. I've got to assume that modprobe has an internal alias that translates block-major-8 to sd_mod. I don't see any reference in either /etc/modules.conf to this alias, but nevertheless modprobe -c shows the alias. And there is a sd_mod.o in the initrd... > -- > My last cigarette was roughly 32 days, 14 hours, 29 minutes ago. Congratulations! > YHBW > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]