From owner-freebsd-questions Mon Jan 8 04:56:31 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA07402 for questions-outgoing; Mon, 8 Jan 1996 04:56:31 -0800 (PST) Received: from gemini.yars.free.net (gemini.yars.free.net [193.233.48.66]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id EAA07303 for ; Mon, 8 Jan 1996 04:55:57 -0800 (PST) Received: (from gray@localhost) by gemini.yars.free.net (8.6.12/8.6.12) id PAA12593; Mon, 8 Jan 1996 15:52:13 +0300 Date: Mon, 8 Jan 1996 15:52:12 +0300 (MSK) From: Serge Bezzubov To: Stefan Esser cc: FREEBSD-QUESTIONS@FreeBSD.ORG Subject: Re: driver for 3Com 3c590 adapter doesn't work In-Reply-To: <199601072056.AA01086@Sysiphos> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@FreeBSD.ORG Precedence: bulk > On Jan 6, 16:38, Serge Bezzubov wrote: > } Subject: driver for 3Com 3c590 adapter doesn't work > } Did anyone get the driver for 3Com 3c590 adapter to work properly under > } FreeBSD 2.1.0 Release? > } > } The compilation of the kernel with that driver included was successfull, but > } after rebooting with new kernel I got such message: > } > } vx0 <2com 3c590 EtherLink III PCI> rev0 int a irq?? on pci0:8 > ^ ^ > really ??? ! :-) bad !!! ^ I misspelled this !!! > There is an "irq??" printed above ... > > This indicates that no interrupt has > been assigned to the PCI slot you put > the 3c590 in! > > Use the PCI BIOS setup menu to assign > a unique value (conflicts with ISA > devices are currently not automatically > detected). Firstly thank you for your assistance. My freind configured a PCI bus using dedicated utility and now while system boots I get message: vx0 <3Com 3c590 EtherLink III PCI> rev 0 int a irq 5 on pci0:7 aui/bnc/utp [*UTP*] address ... It seems OK and even issuing ifconfig command system reports that the interface vx0 is configured properly, but no network connection at all and even when I issue any command regarding network operation the system hangs until I terminate that process. The network cable is attached to the BNC connector however the adapter driver reports that a network media is the UTP. We supposed that something's wrong with adapter. The appropriate driver under MSDOS reports correct media type, so adapter works just fine. Is this driver's problem? How could we fix it? Thank you in advance, Serge Bezzubov