From: Knut Petersen <Knut_Petersen@t-online.de>
To: Carlos Carvalho <carlos@fisica.ufpr.br>
Cc: trond.myklebust@fys.uio.no, linux-kernel@vger.kernel.org
Subject: Re: nfsroot doesn't work with intel card since 2.6.12.2/2.6.11
Date: Mon, 06 Feb 2006 16:49:35 +0100 [thread overview]
Message-ID: <43E7700F.6080702@t-online.de> (raw)
In-Reply-To: <17383.24476.747110.629245@fisica.ufpr.br>
Carlos Carvalho wrote:
>Yes, this works fine. The kernel gets it from pxelinux directly via
>option IPAPPEND.
>
>Here's what I copied manually from the screen after the IP-Config:
>line:
>
>
>
That was not what I asked. Please test without ipappend
and use ip=dhcp as a kernel parameter instead. Don´t forget
to enable dhcp autoconfiguration in the kernel config ...
I bet that you will see that the same dhcp server that proved to
work correctly by providing your server ip etc to the
pxe bootrom and via ipappend to the kernel is unable to
give that same information to the linux ipconfig code
directly. Please try and report.
I assume that you do not have any problem to pxeboot good
old DOS and memtest. Right?
Please give board name, bios version, pxe rom version, and
lspci -vv.
>Trond asked about using tcp. I prefer to use udp because it has less
>overhead. This is a computing cluster, all machines are in the same
>room connected to a HP 4108gl gigabit switch. It's not a cable or
>switch port problem, all machines exhibit the same behavior.
>
>
If I am right with my bet the problem is unrelated to the tcp / udp
choice and unrelated to ipconfig, portmap lookup and nfsroot code.
cu,
Knut
next prev parent reply other threads:[~2006-02-06 15:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 8:42 nfsroot doesn't work with intel card since 2.6.12.2/2.6.11 Knut Petersen
2006-02-06 14:39 ` Carlos Carvalho
2006-02-06 15:49 ` Knut Petersen [this message]
2006-02-06 20:40 ` Carlos Carvalho
-- strict thread matches above, loose matches on Subject: below --
2006-02-05 21:54 Carlos Carvalho
2006-02-06 2:19 ` Trond Myklebust
2006-02-13 3:52 ` H. Peter Anvin
2006-02-13 8:19 ` Rogier Wolff
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=43E7700F.6080702@t-online.de \
--to=knut_petersen@t-online.de \
--cc=carlos@fisica.ufpr.br \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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