Mailing List Archive

Kernel boot problem using PXELinux boot
This is a multi-part message in MIME format.

------=_NextPart_000_00A6_01C19ED4.A927FCB0
Content-Type: text/plain;
charset="big5"
Content-Transfer-Encoding: quoted-printable

I used pxelinux.0 to boot my kernel, then the kernel began to boot. =
However, it cannot mount nfs root. I checked the nfs root=20
is exported OK!
The last screen is as followed:

serial sub-system self-test: passed.
internal registers self-test: passed.
ROM checksum self-test: passed (0x04f4518b).
eepro100.c:v1.09j-t 9/29/99 Donald Becker =
http://cesdis.gsfc.nasa.gov/linux/dri
ver/eepro100.html
eepro100. $Revison: 1.20.2.10 $ 2000/05/31 Modified by Andrey V. =
Svochkin <
aw@sw.com.sg> and others
eepro100.c: VA Linux custom, Dragan Stancevic visitor@valinux.com =
2000/11/15
Partiton Check:
hda: hda1
Looking up port of RPC 100003/2 on 140.111.161.1
RPC: sendmsg returned error 101
Protmap: RPC call returned error 101
Root-NFS: Unable to get nfsd port number from server, using default
Lookingup port of RPC 100005/1 on 140.111.161.1
RPC: sendmsg returned error 101
Protmap: RPC call returned error 101
Root-NFS: Unable to get mountd port number from server, using default
RPC sendmsg returned error 101
Mount: RPC call returned error 101
Root-NFS: Server returned error !V101 while mounting =
/export/home/diskless
VFS: Unbale to mount root fs via NFS, trying floppy.
(Warnig, this kernel has no ramdisk support)
VFS: Insert root floppy and press ENTER


=
Sincerely,
=
Ying-Nan Chen (ynchen@mail.fgu.edu.tw)

------=_NextPart_000_00A6_01C19ED4.A927FCB0
Content-Type: text/html;
charset="big5"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dbig5">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>I used pxelinux.0 to boot my kernel, then the kernel =
began to=20
boot. However, it cannot mount nfs root. I checked the nfs root =
</FONT></DIV>
<DIV><FONT size=3D2>is exported OK!</FONT></DIV>
<DIV><FONT size=3D2>The last screen is as followed:</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>serial sub-system self-test: passed.<BR>internal =
registers=20
self-test: passed.<BR>ROM checksum self-test: passed=20
(0x04f4518b).<BR>eepro100.c:v1.09j-t 9/29/99 Donald Becker <A=20
href=3D"http://cesdis.gsfc.nasa.gov/linux/dri">http://cesdis.gsfc.nasa.go=
v/linux/dri</A><BR>ver/eepro100.html<BR>eepro100.=20
$Revison: 1.20.2.10 $ 2000/05/31 Modified by Andrey V. Svochkin =
&lt;<BR><A=20
href=3D"mailto:aw@sw.com.sg">aw@sw.com.sg</A>&gt; and =
others<BR>eepro100.c: VA=20
Linux custom, Dragan Stancevic <A=20
href=3D"mailto:visitor@valinux.com">visitor@valinux.com</A> =
2000/11/15<BR>Partiton=20
Check:<BR>hda: hda1<BR>Looking up port of RPC 100003/2 on =
140.111.161.1<BR>RPC:=20
sendmsg returned error 101<BR>Protmap: RPC call returned error =
101<BR>Root-NFS:=20
Unable to get nfsd port number from server, using default<BR>Lookingup =
port of=20
RPC 100005/1 on 140.111.161.1<BR>RPC: sendmsg returned error =
101<BR>Protmap: RPC=20
call returned error 101<BR>Root-NFS: Unable to get mountd port number =
from=20
server, using default<BR>RPC sendmsg returned error 101<BR>Mount: RPC =
call=20
returned error 101<BR>Root-NFS: Server returned error &iexcl;V101 while =
mounting=20
/export/home/diskless<BR>VFS: Unbale to mount root fs via NFS, trying=20
floppy.<BR>(Warnig, this kernel has no ramdisk support)<BR>VFS: Insert =
root=20
floppy and press ENTER<BR></FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; Sincerely,</FONT></DIV>
<DIV><FONT size=3D2>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; Ying-Nan Chen (<A=20
href=3D"mailto:ynchen@mail.fgu.edu.tw">ynchen@mail.fgu.edu.tw</A>)</DIV><=
/FONT></BODY></HTML>

------=_NextPart_000_00A6_01C19ED4.A927FCB0--
Kernel boot problem using PXELinux boot [ In reply to ]
陳應南 wrote:

> I used pxelinux.0 to boot my kernel, then the kernel began to boot.
> However, it cannot mount nfs root. I checked the nfs root
> is exported OK!
>
> Looking up port of RPC 100003/2 on 140.111.161.1
> RPC: sendmsg returned error 101
> Protmap: RPC call returned error 101
> Root-NFS: Unable to get nfsd port number from server, using default
> Lookingup port of RPC 100005/1 on 140.111.161.1
> RPC: sendmsg returned error 101
> Protmap: RPC call returned error 101
> Root-NFS: Unable to get mountd port number from server, using default
> RPC sendmsg returned error 101
> Mount: RPC call returned error 101
> Root-NFS: Server returned error ¡V101 while mounting /export/home/diskless
> VFS: Unbale to mount root fs via NFS, trying floppy.
> (Warnig, this kernel has no ramdisk support)
> VFS: Insert root floppy and press ENTER
>


Error 101 is ENOTUNREACH, which implies you don't have the proper
netmask or gateway setup; so it's probably a DHCP configuration problem.

Note to everyone: I recommend using the kernel's own DHCP service, and
*NOT* using IPAPPEND in most cases. The IPAPPEND option is supported
because of some DHCP configurations where that would obtain two
different IP addresses.

-hpa