From owner-freebsd-net Fri Mar 16 2:31:12 2001 Delivered-To: freebsd-net@freebsd.org Received: from peter3.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id E712437B718 for ; Fri, 16 Mar 2001 02:31:08 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from mobile.wemm.org (mobile.wemm.org [10.0.0.5]) by peter3.wemm.org (8.11.0/8.11.0) with ESMTP id f2GAV8p58110 for ; Fri, 16 Mar 2001 02:31:08 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f2GAV7h94432; Fri, 16 Mar 2001 02:31:07 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200103161031.f2GAV7h94432@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Jonathan Lemon Cc: Ollivier Robert , cnielsen@pobox.com, net@FreeBSD.ORG Subject: Re: Intel PRO/100+ PCI problem In-Reply-To: <20010315110343.B82645@prism.flugsvamp.com> Date: Fri, 16 Mar 2001 02:31:07 -0800 From: Peter Wemm Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jonathan Lemon wrote: > On Thu, Mar 15, 2001 at 05:20:58AM -0800, Peter Wemm wrote: > > > fxp0: port 0xff20-0xff3f mem 0xff800000 -0xf > > f8fffff,0xffbde000-0xffbdefff irq 2 at device 6.0 on pci0 > > > fxp0: using memory space register mapping > > > fxp0: Ethernet address 00:a0:c9:49:aa:d3 > > > fxp0: PCI IDs: 8086 1229 0000 0000 > > > nsphy0: on miibus0 > > > nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > > > bpf: fxp0 attached > > > > > > This actually does have the NatSemi phy on it and it is correctly detecte d. > > > Unfortunately, I just locked that machine up with SMPng. oops. I can't > > > verify that it works just yet.. We have another old machine with a NS > > > phy on it (pII based instead of PPro based) and are working on it now. > > > > It appears that the nsphy version is unable to actually transmit packets. > > It is recieving OK, just not sending. (or, the other machines are unable > > to see it, maybe the switch is dropping the packets as "damaged" or > > something?) > > Try this following patch to mii/nsphy.c. It appears that we need to > toggle some undocumented bits in order to get this PHY to work with > the fxp driver. > -- > Jonathan [patch trimmed] That did the trick! fxp0: port 0xff20-0xff3f mem 0xff800000-0xff8fffff,0xffbde000-0xffbdefff irq 2 at device 6.0 on pci0 fxp0: Ethernet address 00:a0:c9:49:aa:d3 nsphy0: on miibus0 nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: at device 7.0 on pci0 [2:28am]~-108# ping 10.0.0.1 PING 10.0.0.1 (10.0.0.1): 56 data bytes 64 bytes from 10.0.0.1: icmp_seq=0 ttl=255 time=0.655 ms 64 bytes from 10.0.0.1: icmp_seq=1 ttl=255 time=0.430 ms 64 bytes from 10.0.0.1: icmp_seq=2 ttl=255 time=0.469 ms ^C --- 10.0.0.1 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.430/0.518/0.655/0.098 ms [2:28am]~-109# ifconfig -a fxp0: flags=8843 mtu 1500 inet 10.0.0.16 netmask 0xffffff00 broadcast 10.0.0.255 ether 00:a0:c9:49:aa:d3 media: autoselect (100baseTX ) status: active supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP 100baseTX [2:30am]~-118# arp -an ? (10.0.0.1) at 0:d0:b7:1e:7b:de [ethernet] ? (10.0.0.2) at 0:90:27:58:45:32 [ethernet] ? (10.0.0.3) at 0:90:27:58:45:e4 [ethernet] ? (10.0.0.4) at 0:c0:2:51:69:31 [ethernet] ? (10.0.0.5) at 0:60:1d:f0:d5:86 [ethernet] ? (10.0.0.16) at 0:a0:c9:49:aa:d3 permanent [ethernet] ? (10.0.0.17) at 0:2:b3:15:84:20 [ethernet] ? (10.0.0.18) at 0:e0:81:11:25:e0 [ethernet] Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message