From owner-freebsd-questions Thu Aug 13 09:37:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA22834 for freebsd-questions-outgoing; Thu, 13 Aug 1998 09:37:10 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from rubens.artisan.calpoly.edu (whistler.artisan.calpoly.edu [129.65.2.41]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA22817 for ; Thu, 13 Aug 1998 09:37:06 -0700 (PDT) (envelope-from kevin@polymail.cpunix.calpoly.edu) Received: (from kevin@localhost) by rubens.artisan.calpoly.edu (8.8.6 (PHNE_14041)/8.8.6) id JAA23167; Thu, 13 Aug 1998 09:36:34 -0700 (PDT) Message-ID: <19980813093633.A20135@rubens.artisan.calpoly.edu> Date: Thu, 13 Aug 1998 09:36:33 -0700 From: Kevin Pekarek To: freebsd-questions@FreeBSD.ORG Subject: problem with AMD Lance PCI network card (2.2.7-RELEASE) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anyone know of any reason that an AMD Lance PCI network card (NE 2100 compatible) (uses device lnc1) would: - not be recognized on boot (well... recognized, but hardware address not displayed, and ifconfig and netstat -i don't recognize it) - ifconfig down itself when attempting a freebsd install via ftp (give it all of the network info, it tries to contact ftp server, says "network is down" and shuts off the network). The network card is not subject, because after rebooting into NT (while not what I really want to be running), I can use the network. The card has no plug and play setting that is alterable by either software or a jumper (but it's PCI, and I thought the PCI controller took care of that anyway)... Thanks in advance... K To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message