From owner-freebsd-questions Fri Oct 13 9:26:52 2000 Delivered-To: freebsd-questions@freebsd.org Received: from new-urth.wamnet.com (ns.wamnet.com [208.50.249.20]) by hub.freebsd.org (Postfix) with ESMTP id 350B337B66F; Fri, 13 Oct 2000 09:26:42 -0700 (PDT) Received: from ndm.wamnet.com([172.17.38.2]) (3920 bytes) by new-urth.wamnet.com via sendmail with P:esmtp/R:inet_hosts/T:smtp (sender: ) id for ; Fri, 13 Oct 2000 11:26:41 -0500 (CDT) (Smail-3.2.0.104 1998-Nov-20 #1 built 1998-Dec-7) Received: from ds.cops.wamnet.com (ds.cops.wamnet.com [172.17.31.2]) by ndm.wamnet.com (8.9.1a/8.9.1) with ESMTP id LAA2447316; Fri, 13 Oct 2000 11:26:40 -0500 (CDT) Received: from y.cops.wamnet.com (y.cops.wamnet.com [172.17.31.43]) by ds.cops.wamnet.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via SMTP id LAA63938; Fri, 13 Oct 2000 11:26:40 -0500 (CDT) Date: Fri, 13 Oct 2000 11:26:21 -0500 (CDT) From: Lee J Carmichael X-Sender: lcarmich@y.cops.wamnet.com Reply-To: Lee J Carmichael To: Piotr Kucharski , avatar@ultra.ultra.net.au Cc: freebsd-questions@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: network interface problem In-Reply-To: <20001013151727.J12744@sgh.waw.pl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello Everyone, I found that on the newer IBM 4500R the AMD ethernet chipset version is an new version(which 'Am79C975'). The newer version does not have a freebsd driver. I did some investgation and found that in Linux the new driver didn't seem to do anything different from the previous version. (it had set the same vars, it just handled detecting of the new chipset version and setting the new chipset name.) But I didn't try to hack the driver in FreeBSD because I still don't understand the structure and what the driver does well enough. It seems that it could be added in, '/usr/src/sys/i386/isa/if_lnc.c' and in the header '/usr/src/sys/i386/isa/if_lnc.h' as a new 'Chip Type'. Any helpful hints, links to FreeBSD device drivers how tos, etc? The other thing that seems odd to me is that these drivers still live under ISA and not under the PCI tree, it doesn't seem to matter but I was wondering why. Thanks, -------- Lee Carmichael WAM!NET Inc. System Engineer 655 Lone Oak Rd Building E 651-256-5292 Eagan, MN 55121 On Fri, 13 Oct 2000, Piotr Kucharski wrote: > Hey > > I have the same problem. Did you manage to get over it? > > p. > > On Wed, Sep 20, 2000 at 02:45:18PM -0500, Lee J Carmichael wrote: > > Date: Wed, 20 Sep 2000 14:45:18 -0500 (CDT) > > From: Lee J Carmichael > > To: freebsd-questions@FreeBSD.ORG, freebsd-net@FreeBSD.ORG > > Subject: network interface problem > > > > Hello Everyone, > > > > I am having a problem with a network interface driver for a netfinity > > 4500R. The ethernet interface on this box is a AMD PCnet chip set(at least > > AMD). The issue is that ethernet interface is detected correctly on the > > PCI bus, but it logs the following message in dmesg: > > > > lnc0: port 0x2000-0x201f mem > > 0xfeb7fc00-0xfeb71c1f irq 11 at device 2.0 on pci0 > > lnc0: driver is using old-style compatability shims > > > > I edited the kernel config to only have: > > > > device lnc0 # without the ?isa parameters > > > > and, I tried > > > > device lnc # like other pci ethernet devices > > > > I did read through both '/usr/src/sys/i386/isa/if_lnc.c' and > > '/usr/src/sys/i386/pci/if_lnc_p.c'. But they didn't yield anything > > helpful. This could be due to my lack of understanding with how these > > drivers are loaded at boot time. > > > > One last piece of info, in my /etc/rc.conf file, I have: > > > > network_interfaces="lo0 lnc0" > > ifconfig_lnc0="inet xxx.xxx.xxx.xxx" > > > > Not that this really matters, since it just generates a 'lnc0 interface > > not found' or something like that. > > > > Any Ideas? Thanks for the help, in advance. > > -------- > > Lee Carmichael WAM!NET Inc. > > System Engineer 655 Lone Oak Rd Building E > > 651-256-5292 Eagan, MN 55121 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message