From: (Chip Schweiss) chip@innovates.com
To: luca.montecchiani@teamfab.it
Cc: alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org
Subject: RE: Re: 2.2.18pre21 - IP kernel level autoconfiguration
Date: Fri, 17 Nov 2000 09:17:56 -0600 [thread overview]
Message-ID: <H00000650001a074.0974474275.dublin.innovates.com@MHS> (raw)
[-- Attachment #1: BDY.TXT --]
[-- Type: text/plain, Size: 1328 bytes --]
The problem seems to be deeper than that. I first encountered the
problem with only bootp compiled in. In my configuration I am not able
to supply kernel parameters on the client which may be why you were
able to get bootp to execute.
Chip
> It seem somewhere between 2.2.17 and the current 2.2.18 kernel, IP
> kernel level autoconfiguration has been broken. Upon kernel loading
> the Ethernet card is detected and loaded properly, but the bootp code
> never seems to be executed and mounting the root partion via NFS then
> fails from lack of IP configuration.
> I haven't had any luck tracing down the root of this problem.
> Anyone else experience this problem or have a patch to fix it?
Hi!
I've the same behavior here:
server kernel : 2.2.17
dhcpd : 2.0b1pl29
client kernel : 2.2.18-21
client cmdline: root=/dev/nfs nfsroot=/foo/bar ip=bootp
After some quick tests seem that if you want bootp
you _need_ to compile the client's kernel with _only_ bootp,
if you have also dhcp, it doesn't work :(
Dhcp into kernel is COOL and I hope that someone is
porting on 2.4 ;), doesn't seem that hard
hope this help,
luca
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-11-17 15:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-17 15:17 chip [this message]
2000-11-17 15:32 ` Luca Montecchiani
2000-11-20 17:03 ` [PATCH] " Luca Montecchiani
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=H00000650001a074.0974474275.dublin.innovates.com@MHS \
--to=chip@innovates.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.montecchiani@teamfab.it \
/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
all inboxes | Powered by JetHome®