From owner-freebsd-questions Sat Jun 13 11:00:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA16455 for freebsd-questions-outgoing; Sat, 13 Jun 1998 11:00:57 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from couatl.uchicago.edu (couatl.uchicago.edu [128.135.21.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA16400 for ; Sat, 13 Jun 1998 11:00:49 -0700 (PDT) (envelope-from sfarrell@couatl.uchicago.edu) Received: (from sfarrell@localhost) by couatl.uchicago.edu (8.9.0/8.9.0) id NAA06929; Sat, 13 Jun 1998 13:00:46 -0500 (CDT) To: "Richard J. Finn" Cc: freebsd-questions@FreeBSD.ORG Subject: Re: more on my funky problem (help?) References: <358194CE.31E19B94@hiwd.net> From: sfarrell+lists@farrell.org Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Date: 13 Jun 1998 13:00:46 -0500 In-Reply-To: "Richard J. Finn"'s message of "Fri, 12 Jun 1998 15:51:26 -0500" Message-ID: <87ra0tb2r5.fsf@couatl.uchicago.edu> Lines: 39 X-Mailer: Gnus v5.6.9/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Richard J. Finn" writes: > If you recall, I was having trouble getting 2.2.5 or 2.2.6 to get past > adding the route to my primary router during an upgrade from 2.2.2. > > I even tried configuring the install kernel to only enable the devices > I had (particularly the NIC). I only had my NIC enabled. It still > didn't work. > > I upgraded to 2.2.5 while in multiuser mode, rebooted, and rebuilt the > kernel. The machine wouldn't come back up with the new kernel. From > the console, it appeared that it was having (surprise) a problem talking > to the network. I rebooted with the GENERIC 2.2.5 kernel and it still > didn't work. I rebooted with the old 2.2.2 kernel and it works fine. > > From the 2.2.2 kernel: > > de0 rev 32 int a irq 5 on pci1:11 > > de0: Digital DE500-AA 21140A [10-100Mb/s] pass 2.0 > > de0: address 00:00:e8:2b:2b:2d > > The 2.2.5 kernels have the same message when it comes to the NIC, with > the addition of a line that looks something like: > > de0: <100BaseTX> status: active > > I'm thinking there might be a problem where 2.2.5 and 2.2.6 are forcing > my NIC to go 100BaseT (I believe its currently only on a 10BaseT > ethernet). > > Any ideas or pointers?... man ifconfig.... you want "media 10baseT/UTP" option to force 10baseT. But this doesn't sound like your whole problem... also, you should see error messages like "no carrier de0: cable problem?" if the media isn't correct. -- Steve Farrell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message