public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Knut Petersen <Knut_Petersen@t-online.de>
To: linux-kernel@vger.kernel.org
Subject: netboot broken ?
Date: Fri, 27 Jan 2006 08:16:21 +0100	[thread overview]
Message-ID: <43D9C8C5.3020902@t-online.de> (raw)

Hi everybody!

I spent too many hours trying to boot a machine via ethernet.
The nic includes a pxe boot rom, and without any problems I
manage to boot an old DOS disk image and memtest.

There are also no problems to _load_ the linux kernel.

But when it reaches the point of ip autoconfiguration
(I included ip=dhcp on the kernel command line and, of course,
I enabled dhcp autoconfiguration in the .config), nothing works.
It sends dhcp requests, dhcpd answers, and this repeats forever.
Well ... this is the second time dhcpd is asked ... without a
working and basically correct configured dhcpd the pxe boot
rom and pxelinux would have been unable to  load the kernel ?!

Ok, there is the possibility not to use dhcp autoconf but to
give the necessary information via ip=.... to the kernel. That
works. But after ip config the kernel needs to connect the server to
get the port of rpc 100003/2 and 100005/1. Both fail and timeout,
the kernel tells me to try the defaults, fails and panics.

Please don´t tell me that I forget to start nfsd or mountd, that I
did not export the filesystem the kernel tries to mount etc. I
have no problems to mount that directory from other machines
on the network.

I tried a number of recent kernels, the oldest was 2.6.14.

Any ideas? Can anybody please
 - confirm that network booting does still work
 - confirm that it is broken.

Yes, I read Documentation/nfsroot ... and I am willing to update
it if anybody tells me how to boot that machine.

cu,
 Knut

             reply	other threads:[~2006-01-27  7:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-27  7:16 Knut Petersen [this message]
2006-01-27  8:15 ` netboot broken ? Magnus Damm
2006-01-27 16:08 ` Bryan O'Sullivan
2006-02-12 19:03   ` H. Peter Anvin

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=43D9C8C5.3020902@t-online.de \
    --to=knut_petersen@t-online.de \
    --cc=linux-kernel@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