From: Matt Porter <porter@cox.net>
To: Khai Trinh <kqtrinh@yahoo.com>
Cc: Dan Kegel <dkegel@ixiacom.com>,
"'linuxppc-embedded@lists.linuxppc.org '"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: in_ntoa built error
Date: Fri, 24 May 2002 16:40:39 -0700 [thread overview]
Message-ID: <20020524164039.A21633@home.com> (raw)
In-Reply-To: <20020524230359.33739.qmail@web11507.mail.yahoo.com>; from kqtrinh@yahoo.com on Fri, May 24, 2002 at 04:03:59PM -0700
On Fri, May 24, 2002 at 04:03:59PM -0700, Khai Trinh wrote:
>
> By the way, the snippet of the failing log of the
> kernel when it was downloading are captured below:
<snip>
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
>
> kmod: failed to exec /sbin/modprobe -s -k
> block-major-22, errno = 2
>
> VFS: Cannot open root device "" or 16:01
>
> Please append a correct "root=" boot option
>
> Kernel panic: VFS: Unable to mount root fs on 16:01
This is normal behavior for your configuration. On the ebony
port, the default ROOT_DEV is 16:01 (/dev/hda1) if you
don't have CONFIG_BLK_DEV_INITRD or CONFIG_ROOT_NFS
configured. You can even see kmod trying to load
an ide driver for you.
With CONFIG_ROOT_NFS enabled, it will attempt to root from 00:ff,
the nfs pseudo root device.
Regards,
--
Matt Porter
porter@cox.net
This is Linux Country. On a quiet night, you can hear Windows reboot.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-05-24 23:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-24 22:45 in_ntoa built error Dan Kegel
2002-05-24 23:03 ` Khai Trinh
2002-05-24 23:40 ` Matt Porter [this message]
2002-05-24 23:54 ` Khai Trinh
2002-05-25 0:10 ` Matt Porter
-- strict thread matches above, loose matches on Subject: below --
2002-05-24 21:57 Khai Trinh
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=20020524164039.A21633@home.com \
--to=porter@cox.net \
--cc=dkegel@ixiacom.com \
--cc=kqtrinh@yahoo.com \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).