From owner-freebsd-hackers Wed Dec 6 00:45:54 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA23278 for hackers-outgoing; Wed, 6 Dec 1995 00:45:54 -0800 (PST) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA23256 for ; Wed, 6 Dec 1995 00:45:33 -0800 (PST) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id JAA21748; Wed, 6 Dec 1995 09:36:26 +0100 Message-Id: <199512060836.JAA21748@gilberto.physik.rwth-aachen.de> Subject: Re: BICC (C-LANCE) DE 205 To: matt@lkg.dec.com (Matt Thomas) Date: Wed, 6 Dec 1995 09:36:25 +0100 (MET) Cc: kuku@gilberto.physik.rwth-aachen.de, freebsd-hackers@freefall.freebsd.org In-Reply-To: <199512052005.UAA19110@whydos.lkg.dec.com> from "Matt Thomas" at Dec 5, 95 08:04:46 pm From: Christoph Kukulies Reply-To: Christoph Kukulies X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.ORG Precedence: bulk > > > In <199512051049.LAA17872@gilberto.physik.rwth-aachen.de> , you wrote: > > > Booting a 2.1.0 system I get > > [...] > > le0 not found at 0x300 > > lnc0 not found at 0x280 > > lnc1 at 0x300-0x30f irq 10 drq 0 on isa > > lnc1: BICC (C-LANCE) Ethernet controller, address 00:00:40:01:00:00 > > > > > > Later I'm trying to start the interface and get > > > > lnc1: Initialisation failed > > > > This is a ASUS PCI/I P54?? board. The Lance controller is a DEC > > DE 205 Etherworks III which works fine under Win95%/NT in that > > very same box. > > > > Any clues? The ethernet address looks a bit strange, doesn't it? > > The DE205 is not LANCE based, it is a DEC private chip called the LeMAC. > You must use the le driver to access it (and it obviosly didn't find it). > What are the settings being used under Windows NT? I put on my glasses and saw that it is a EtherWORKS DE 203, not a DE205. Excuse the misinformation but these imprinted into sheet letters in the back mounting panel are diffult to decipher sometimes. I just noticed that (due to some network card swapping it escaped to me) it wasn't yet running under NT but under Win95 it works and has the setting 0x300-0x31f/5/c8000-c87ff. > > Matt Thomas Internet: matt@lkg.dec.com > 3am Software Foundry WWW URL: > Westford, MA Disclaimer: Digital disavows all knowledge > of this message > > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de