public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Eddy" <edmc@snowline.net>
To: "Linux-Kernel" <linux-kernel@vger.kernel.org>,
	"Alan Cox" <alan@lxorguk.ukuu.org.uk>
Subject: Re: Linux 2.2.18 almost...
Date: Mon, 11 Dec 2000 01:26:28 -0800	[thread overview]
Message-ID: <000901c06354$7732e240$598d7ece@snowline.net> (raw)
In-Reply-To: <E144syy-0005sE-00@the-village.bc.nu>

did we lose ip=autoconf. I see dhcp and arp transmitting infinitely. I was
able to boot only after completely entering nfsroot= and ip= boot commands.

2.2.17 worked thusley.

root=/dev/nfs ether=0,0,eth0

2.2.18-pre26 works only

root=/dev/nfs
nfsroot=192.168.50.11:/tftpboot/191.168.50.2,rsize=8192,wsize=8192
ip=192.168.50.2:192.168.50.11:::Eddys486:eth0:off ether=0,0,eth0

for some reason

root=/dev/nfs ether=0,0,eth0   gives this result

Dec 10 22:48:24 Eddys dhcpd: BOOTREQUEST from 00:50:ba:05:7b:fb via eth0
Dec 10 22:48:24 Eddys dhcpd: BOOTREPLY for 192.168.50.2 to eddys486
(00:50:ba:05:7b:fb) via eth0
Dec 10 22:48:26 Eddys dhcpd: BOOTREQUEST from 00:50:ba:05:7b:fb via eth0
Dec 10 22:48:26 Eddys dhcpd: BOOTREPLY for 192.168.50.2 to eddys486
(00:50:ba:05:7b:fb) via eth0
Dec 10 22:48:29 Eddys dhcpd: BOOTREQUEST from 00:50:ba:05:7b:fb via eth0
Dec 10 22:48:29 Eddys dhcpd: BOOTREPLY for 192.168.50.2 to eddys486
(00:50:ba:05:7b:fb) via eth0
Dec 10 22:48:36 Eddys dhcpd: BOOTREQUEST from 00:50:ba:05:7b:fb via eth0
Dec 10 22:48:36 Eddys dhcpd: BOOTREPLY for 192.168.50.2 to eddys486
(00:50:ba:05:7b:fb) via eth0
Dec 10 22:48:47 Eddys dhcpd: BOOTREQUEST from 00:50:ba:05:7b:fb via eth0
Dec 10 22:48:47 Eddys dhcpd: BOOTREPLY for 192.168.50.2 to eddys486
(00:50:ba:05:7b:fb) via eth0

and

root=/dev/nfs ip=both ether=0,0,eth0     gives this result

Dec 10 22:50:52 Eddys dhcpd: DHCPDISCOVER from 00:50:ba:05:7b:fb via eth0
Dec 10 22:50:52 Eddys dhcpd: DHCPOFFER on 192.168.50.2 to 00:50:ba:05:7b:fb
via eth0
Dec 10 22:50:55 Eddys dhcpd: DHCPDISCOVER from 00:50:ba:05:7b:fb via eth0
Dec 10 22:50:55 Eddys dhcpd: DHCPOFFER on 192.168.50.2 to 00:50:ba:05:7b:fb
via eth0
Dec 10 22:51:00 Eddys dhcpd: DHCPDISCOVER from 00:50:ba:05:7b:fb via eth0
Dec 10 22:51:00 Eddys dhcpd: DHCPOFFER on 192.168.50.2 to 00:50:ba:05:7b:fb
via eth0
Dec 10 22:51:09 Eddys dhcpd: DHCPDISCOVER from 00:50:ba:05:7b:fb via eth0
Dec 10 22:51:09 Eddys dhcpd: DHCPOFFER on 192.168.50.2 to 00:50:ba:05:7b:fb
via eth0


-
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/

  parent reply	other threads:[~2000-12-11  9:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-09 23:00 Linux 2.2.18 almost Alan Cox
2000-12-09 23:12 ` Tom Rini
2000-12-09 23:36   ` Eyal Lebedinsky
2000-12-09 23:32 ` Michael Rothwell
2000-12-10  0:17   ` Keith Owens
2000-12-10  0:23   ` Andre Hedrick
2000-12-10  1:11   ` Alan Cox
2000-12-10  8:29   ` Tigran Aivazian
2000-12-10  8:34     ` Tigran Aivazian
2000-12-10 18:20     ` Alan Cox
2000-12-10 16:34 ` Vasil Kolev
2000-12-11  9:26 ` Eddy [this message]
2000-12-11 13:03   ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2000-12-11 10:44 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='000901c06354$7732e240$598d7ece@snowline.net' \
    --to=edmc@snowline.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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