From owner-freebsd-questions Thu Aug 23 16:10:47 2001 Delivered-To: freebsd-questions@freebsd.org Received: from web10405.mail.yahoo.com (web10405.mail.yahoo.com [216.136.130.97]) by hub.freebsd.org (Postfix) with SMTP id 30A1D37B409 for ; Thu, 23 Aug 2001 16:10:45 -0700 (PDT) (envelope-from damage_z@yahoo.com) Message-ID: <20010823231045.66652.qmail@web10405.mail.yahoo.com> Received: from [63.165.242.21] by web10405.mail.yahoo.com; Thu, 23 Aug 2001 16:10:45 PDT Date: Thu, 23 Aug 2001 16:10:45 -0700 (PDT) From: Damage Subject: 4.4-RC1 update dropped 2nd fxp interface To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello all, I have a Compaq DL380 I upgraded from 4.3-STABLE to 4.4-RC1 via make world and installing a new kernel (GENERIC has always worked from update to update, and I used GENERIC here). There are two interfaces. One is an integrated Intel EEPro/100, and I have a secondary NC3123 PCI NIC (Compaq's version of EEPro/100). Both were working fine as fxp0 and fxp1 prior to the update. After the update, fxp1 is gone. After running MAKEDEV, et al, I can't get the system to see this interface anymore. Admittedly I'm a little short on sleep, and I think I overlooked something obvious. I have other systems (non-Compaq) with dual integrated EEPro/100's, which updated fabulously. A secondary side effect of this upgrade has left my floppy drive hosed. Mounting the drive spews out a lot of errors, and 'mount' saturates the CPU and won't kill -9. This leaves me wondering what the hell happened. Any suggestions are greatly appreciated. TIA, Dylan __________________________________________________ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message