From owner-freebsd-questions Wed Jan 24 16:29:47 2001 Delivered-To: freebsd-questions@freebsd.org Received: from silver.teardrop.org (silver.teardrop.org [205.181.101.128]) by hub.freebsd.org (Postfix) with ESMTP id 0095937B400 for ; Wed, 24 Jan 2001 16:29:24 -0800 (PST) Received: (from snow@localhost) by silver.teardrop.org (8.11.1/8.11.1) id f0P0TCW39325 for freebsd-questions@freebsd.org; Wed, 24 Jan 2001 19:29:12 -0500 (EST) (envelope-from snow@teardrop.org) Date: Wed, 24 Jan 2001 19:29:12 -0500 From: James Snow To: freebsd-questions@freebsd.org Subject: 4.0 -> 4.2-S broke my Ethernet card? Message-ID: <20010124192912.A37959@teardrop.org> Mail-Followup-To: freebsd-questions@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've got an old laptop with a Linksys Etherfast 10/100 PCMCIA card in it. This was working just dandy under 4.0. I just cvsup'd the box to 4.2-S and this card died. The machine reports the MAC address of the card erroneously (aa:aa:aa:aa:aa:aa), complains of device timouts, and corrupted NIC memory. It also reports the card as being an NE1000 (8 bit) where previously it had been reported as an NE2000 (16 bit). Swapped out the card to no avail. Though, oddly enough, booting off of the 4.2 boot floppies would make it all the way through an FTP install of 4.2. Once installed, it failed again as described above. Has anyone had any similar problems? I have verified that it's not an IRQ conflict, tested the card in another machine and swapped out the card. It's not the PCMCIA slot or controller as these both work fine when booted off the FreeBSD boot floppies. I can't think of anything else to try. -James To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message