From owner-freebsd-questions Wed Dec 29 0:56:18 1999 Delivered-To: freebsd-questions@freebsd.org Received: from andrsn.stanford.edu (andrsn.Stanford.EDU [36.33.0.163]) by hub.freebsd.org (Postfix) with ESMTP id A6E36155AF for ; Wed, 29 Dec 1999 00:56:16 -0800 (PST) (envelope-from andrsn@andrsn.stanford.edu) Received: from localhost (andrsn@localhost.stanford.edu [127.0.0.1]) by andrsn.stanford.edu (8.9.3/8.9.1) with ESMTP id AAA28858; Wed, 29 Dec 1999 00:47:39 -0800 (PST) Date: Wed, 29 Dec 1999 00:47:39 -0800 (PST) From: Annelise Anderson To: Arcady Genkin Cc: freebsd-questions@FreeBSD.ORG Subject: Re: ed0 recognized as ed1 In-Reply-To: <87yaaei42m.fsf@main.wgaf.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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