From: Ray Olszewski <ray@comarre.com>
To: linux-newbie@vger.kernel.org
Subject: RE: kernel compilation problem
Date: Tue, 23 Dec 2003 08:51:33 -0800 [thread overview]
Message-ID: <5.1.0.14.1.20031223084227.01f4cec0@celine> (raw)
In-Reply-To: <3BEEE23D31CAD2118D920008C75D8946059FF59E@NPRI54EXC21.NPT.N UWC.NAVY.MIL>
At 08:46 AM 12/23/2003 -0500, Pacheco Jason NPRI wrote:
> > Hi,
> > I was compiling the 2.4.18 kernel as a practice run and when I booted
> > thru it I recieved a message during boottime:
> > Kernel panic: VFS unable to mount root fs on 03:05.
> > any clues why?
Where is the host's actual root filesystem? 03:05 says the kernel is
looking for it on /dev/hda5 ... is that the right place or not? (It's not
typical for a Debian install, but not impossible either.)
If it is correct -- what filesystem type is it? (ext2, most likely). Make
sure your kernel has support for that filesystem type compiled in.
If it is incorrect -- what partition should it be? Are you compiling the
kernel on the same system you are trying to boot it on? What happens if you
specify the correct partition at the lilo (or grub or whatever you use for
a bootloader) prompt? Are you booting from hda?
>Did you copy over your /usr/src/linux/System.map file into /boot? Also,
>did you build an initial ramdisk via mkinitrd? A lot of times that last
>step is overlooked but is necessary because it loads the initial drivers
>needed to mount the hard disk partitions.
No it's not. It is only necessary if the kernel does not have ide support
compiled in (not usual) or dos not have support for your filesystem type
compiled in (again unusual, if the filesysystem is ext2). Typical,
"vanilla" systems do not need the initrd step to boot/init.
> > I run the Debian woody release.
[rest omitted]
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next parent reply other threads:[~2003-12-23 16:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3BEEE23D31CAD2118D920008C75D8946059FF59E@NPRI54EXC21.NPT.N UWC.NAVY.MIL>
2003-12-23 16:51 ` Ray Olszewski [this message]
2003-12-24 4:45 ` kernel compilation problem joy
2003-12-24 6:46 ` Beolach
2003-12-24 13:22 Pacheco Jason NPRI
-- strict thread matches above, loose matches on Subject: below --
2003-12-23 13:46 Pacheco Jason NPRI
2003-12-23 10:46 joy
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=5.1.0.14.1.20031223084227.01f4cec0@celine \
--to=ray@comarre.com \
--cc=linux-newbie@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