From owner-freebsd-questions Fri Jun 12 13:59:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA12470 for freebsd-questions-outgoing; Fri, 12 Jun 1998 13:59:30 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from Gawain.Houston-InterWeb.COM (interweb.hou.neo.net [206.109.6.62]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA12172 for ; Fri, 12 Jun 1998 13:57:48 -0700 (PDT) (envelope-from rfinn@hiwd.net) Received: from hiwd.net (merlyn.houston-interweb.com [206.109.147.69]) by Gawain.Houston-InterWeb.COM (8.8.5/8.6.12) with ESMTP id VAA00876 for ; Fri, 12 Jun 1998 21:01:11 GMT Message-ID: <358194CE.31E19B94@hiwd.net> Date: Fri, 12 Jun 1998 15:51:26 -0500 From: "Richard J. Finn" Organization: Houston InterWeb Design, Inc. X-Mailer: Mozilla 4.04 [en] (X11; I; IRIX 6.2 IP22) MIME-Version: 1.0 Newsgroups: comp.unix.bsd.freebsd.misc,neosoft.users.freebsd,Daniel,Baker,,Brian,Stamper, To: freebsd-questions@FreeBSD.ORG Subject: more on my funky problem (help?) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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?... -- Richard J. Finn CTO/CIO Houston InterWeb Design, Inc. rfinn@hiwd.net http://www.houston-interweb.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message