From owner-freebsd-questions Wed Dec 29 9:50:11 1999 Delivered-To: freebsd-questions@freebsd.org Received: from dns.sunline.net (dns.sunline.net [207.30.56.2]) by hub.freebsd.org (Postfix) with ESMTP id 8D3801520C for ; Wed, 29 Dec 1999 09:50:08 -0800 (PST) (envelope-from scorpio@sunline.net) Received: from sunline.net (scorpio@jeff.sunline.net [207.30.56.254]) by dns.sunline.net (8.8.8/8.8.8) with ESMTP id MAA04403; Wed, 29 Dec 1999 12:47:47 -0500 (EST) Message-ID: <386A49C3.AF19F0DB@sunline.net> Date: Wed, 29 Dec 1999 12:49:55 -0500 From: Jeff Palmer X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Annelise Anderson Cc: Arcady Genkin , freebsd-questions@FreeBSD.ORG Subject: Re: ed0 recognized as ed1 References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For what it's worth, I have a PCI ne2k compliant card, (Realtek 8029) I run 3.4-STABLE and I have the same thing happen to me. Luckily, for me, I can simply edit rc.conf to fix this, I don't know why or how, but it's not just prevelant in -CURRENT Jeff Palmer scorpio@sunline.net Annelise Anderson wrote: > Arcady, this happens to me and other people too. > > And it seems to vary with the version of FreeBSD or how recent the > -current sources are. My September 15 -current did ed1 but by > December 9 it was back to ed0. > > This is a problem on a remote reboot, because if rc.conf is wrong, the > network won't come up. And then you can't get to the machine to fix > it. > > I therefore have a little script in /usr/local/etc/rc.d called > saveme.sh that's executable and runs the commands with ed1 > instead of ed0 to get stuff going. I put both ed0 and ed1 in > network interfaces in rc.conf. > > My understanding of why this happens is that the first instance of > the driver (the one identified in the kernel config file) is assigned > to isa, so an increment of one is applied for pci. But this is not > clearly and consistently the case, obviously. For a while I had -current > with ed1 and 3.3-stable (on another drive on the same machine) using ed0. > I think you'd find, though, that if you compiled the kernel with ed1 > instead of ed0, your card would turn up with ed2. > > Whenever you upgrade or compile new kernel sources, you should in this > situation have a backup like I do or plan to be there so you can adjust > for changes. > > Annelise > On 29 Dec 1999, Arcady Genkin wrote: > > > Hi all: > > > > I have a PCI NE2000 compatible card. In kernel config file I just > > specified "device ed0". However, at boot time the card gets recognized > > as "ed1". It works properly if configured as "ed1". > > > > What's up with that? FWIW, I also have a "rl0" device. Running 3.4-R. > > -- > > Arcady Genkin http://wgaf.dyndns.org > > "'What good is my pity? Is not the pity the cross upon which he who > > loves man is nailed?..'" (Zarathustra - F. Nietzsche) > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-questions" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message