From owner-freebsd-stable Thu Oct 12 17:47: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from fremont.bolingbroke.com (adsl-216-102-90-210.dsl.snfc21.pacbell.net [216.102.90.210]) by hub.freebsd.org (Postfix) with ESMTP id F25BD37B503 for ; Thu, 12 Oct 2000 17:47:00 -0700 (PDT) Received: from fremont.bolingbroke.com (fremont.bolingbroke.com [216.102.90.210]) by fremont.bolingbroke.com (Pro-8.9.3/Pro-8.9.3) with ESMTP id RAA28104; Thu, 12 Oct 2000 17:46:52 -0700 (PDT) Date: Thu, 12 Oct 2000 17:46:52 -0700 (PDT) From: Ken Bolingbroke To: Chris Byrnes Cc: stable@FreeBSD.ORG Subject: Re: Hrm! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You'd want to check the dmesg output and see if your kernel is detecting your network card, probably. For what it's worth, I did a recent upgrade through 3.x and got bit by my 3COM NIC getting the kernel driver changed from vn0 to xl0, could be the same with yours. Ken On Thu, 12 Oct 2000, Chris Byrnes wrote: > I have another machine which is having a problem that I just can't figure > out. > > I cvsup it to the latest 3.5-STABLE src. I make buildworld, I make > installworld, I 'config NS1', 'cd ../../compile/NS1', 'make depend', > 'make', 'make install', reboot. > > It doesn't boot up. > > Well, it does, but the network connections are fried. > > Then, if I unload kernel and load kernel.old, it's fine. And back at > 3.4-STABLE, of course. > > Any idea how to resolve or determine what the problem is? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message