From: Alex Williamson <alex.williamson@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: compiling 2.4.21 vanilla kernel
Date: Thu, 02 Sep 2004 15:25:16 +0000 [thread overview]
Message-ID: <1094138716.5156.25.camel@tdi> (raw)
In-Reply-To: <50C05B7AA7D6924FB5E384EF14BC647B0DB8C7@inba1mx2.corp.emc.com>
You're still applying the 2.4.21-ia64 patch, right? There are a
couple things to check:
1. The ia64 patch adds a -g build option, which makes all the
binaries very large. mkinitrd often silently fails if the
modules don't fit in the ramdisk. Use a '-v' option to mkinitrd
to see if you're being bitten by this. If you are, edit the
mkinitrd script to make a bigger ramdisk (search for ia64) or
build your kernel w/o -g.
2. Seems like RH renamed one of the sym53c8xx scsi modules, but I
forget the details. You may not be loading the right scsi
driver into your ramdisk. Running mkinitrd w/ the '-v' option
should shed some light on what's getting included.
If you're still having problem, please provide more details, like what
box this is and a console log of the failure. Also, there are much
newer kernels out there than 2.4.21...
Alex
On Thu, 2004-09-02 at 12:00 +0100, gowda_avinash@emc.com wrote:
> All:
> I have been trying to boot of a vanilla kernel (2.4.21) which I compiled.
> When I boot of my new kernel I get this message
>
> Kernel Panic: VFS: Unable to mount root fs on unknown-block(0,0)
>
> This looks like a trivial booking keeping elilo.conf issue, but I am not
> able to figure out what the problem is.
>
> This is a snapshot of my elilo.conf
>
>
> <snip>
>
> prompt
> timeout\x100
> default=2.4.21
>
> image=vmlinuz-2.4.21
> label=2.4.21
> initrd=initrd-2.4.21.img
> read-only
> append="root=LABEL=/"
>
> image=vmlinuz-2.4.21-15.0.4.EL
> label=hack
> initrd=initrd-2.4.21-15.0.4.EL.img
> read-only
> append="root=LABEL=/"
>
> image=vmlinuz-2.4.21-15.0.4.EL
> label=2.4.21-15.0.4.EL
> initrd=initrd-2.4.21-15.0.4.EL.img
> read-only
> append="root=LABEL=/"
>
> <snip>
>
> I am not able to boot off only the first one in the list.
>
> This is how I am compiling the kernel.
> make mrproper
> make clean
> make menuconfig
> make dep
> make vmlinux
> I copied the vmlinux to /boot/efi/efi/Redhat (where all my images are) and
> Lastly did the mkinitrd.
>
> I am wondering where I am going wrong.
>
>
>
> TIA
>
> avinash
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Alex Williamson HP Linux & Open Source Lab
next prev parent reply other threads:[~2004-09-02 15:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-02 11:00 compiling 2.4.21 vanilla kernel gowda_avinash
2004-09-02 15:25 ` Alex Williamson [this message]
2004-09-03 12:11 ` gowda_avinash
2004-09-03 21:29 ` FW: " gowda_avinash
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1094138716.5156.25.camel@tdi \
--to=alex.williamson@hp.com \
--cc=linux-ia64@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox