Re: gcc compiler version / kernel problems

[Greg Julius <fromRedHat outtacyte com>]

Thomas, 

I tried as you noted but nothing showed up.

Earlier Rick S suggested capturing the mkinitrd output and this is what I
got:
The -v option shows

Using modules:

Using loopback device /dev/loop0

/sbin/nash -> /tmp/initrd.nFeFdj/bin/nash

/sbin/insmod.static -> /tmp/initrd.nFeFdj/bin/insmod

I gather that coupled with the results of your commands means that
there are no modules in the thing.  So why is it needed (meaning why
do I Kernel Panic VFS without it)?

I look into the /initrd/linuxrc file and find:

#!/bin/nash

echo Mounting /proc filesystem

mount -t proc /proc /proc

echo Creating block devices

mkdevices /dev

echo Creating root device

mkrootdev /dev/root

echo -x-1-- > /proc/sys/kernel/real-root-dev

echo Mounting root filesystem

mount -o defaults --ro -t ext3 /dev/root /sysroot

pivot_root /sysroot /sysroot/initrd

umount /initrd/proc

What is the loop device?  and what is it used for? 
especially in context with mount?
Does some of this stuff need to be done elsewhere?

I set ext3 to be built in, and I don't have a raid/lvm.  I don't
even have a scsi drive.  I do note in my /boot/grub/grup.conf 
that the end of my kernel line has hdc=ide-scsi.  I also noted via
lsmod that scsi_mod has a used by of 2 and [sr_mod ide-scsi] but each of
these have a used by of zero.  Might this be a hint?

Now I know what the /sbin/nash -> /tmp/initrd.nFeFdj/bin/nash 
line means from above.
/initrd unmounted and /tmp/initrd.img trashed
Once I removed the offending CONFIG_SCSI_SIM710 causing my modules build
to fail I was able to install the rawhide SRPM.  So I tried the
2.4.20 from kernel.org - it also compiled in gcc 3.2-7.  Running it
now.

-g

At 01:31 PM 1/14/03, you wrote:
> Greg Julius wrote:
> > Greetings smart ones out
> > there...
> > I finally got 2.4.20 to boot.  I used the rawhide SRPM to build
> > it.
>
> I guess you figured it out :)
>
> > I tried to boot without the
> > mkinitrd because I don't have SCSI but I get the following
> > errors
>
> There's more on the initrd that just SCSI these days. Not sure why ext3
> isn't builtin, but that's Red Hat's choice.
>
> >     VFS: Cannot open
> > root device "LABEL=/" or 00:00     Please
> > append a correct "root=" boot option    
> > Kernel panic: VFS: Unable to mount root fs on 00:00
> That might also be software RAID/LVM too, those drivers are
> also modules on the initrd.
>
> > When I built the initrd image I was
> > able to boot.
> >
> > Question1:  What is in my initrd that I should incorporate (=y) in
> > the kernel?  Or is it something that I will always need?  How
> > can I find out what it included?
>
> You can look at the initrd, see what's there, and decide what you are
> using from that.
>
> cp /boot/initrd-2.4.20<some thing>.img /tmp/initrd.img.gz
> gunzip /tmp/initrd.img.gz
> mount -o loop /tmp/initrd.img /initrd
> grep insmod /initrd/linuxrc
>
>
> (don't forget to unmount /initrd and delete /tmp/initrd.img when you're
> done :) )
>
>    -Thomas