Date: Thu, 15 Mar 2001 05:20:58 -0800 From: Peter Wemm <peter@netplex.com.au> To: Jonathan Lemon <jlemon@flugsvamp.com>, cnielsen@pobox.com, net@FreeBSD.ORG Subject: Re: Intel PRO/100+ PCI problem Message-ID: <200103151320.f2FDKwh83702@mobile.wemm.org> In-Reply-To: <200103151147.f2FBlZh83021@mobile.wemm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Peter Wemm wrote:
> Jonathan Lemon wrote:
> > In article <local.mail.freebsd-net/20010314145108.Q38002@cassie.foobarbaz.n
et
> > you write:
> > >On Wed, Mar 14, 2001 at 08:47:57AM -0600, Jonathan Lemon wrote:
> > >> On Wed, Mar 14, 2001 at 02:28:47PM +0100, Jeroen Ruigrok/Asmodai wrote:
> > >> > -On [20010308 22:02], Rafael Tonin (rafael.tonin@terra.com.br) wrote:
> > >> > >I'm having some problems on configuring my just purchased
> > >> > >Intel PRO/100+ PCI (reported by Intel as being P#: 689661-004).
> > >> > >
> > >> > >When booting, FreeBSD 4.2 reports:
> > >> > >
> > >> > >fxp0: <Intel Pro 10/100B/100+ Ethernet> at device 13.0 on pci0
> > >> > >fxp0: could not map memory
> > >> >
> > >> > You might want to try the latest sources Jonathan Lemon [cc:'d] came u
p
> > >> > with. I've looked at the diffs and he did some nice cleanups to bring
> > >> > the driver into the present. This might also fix your problem.
> > >> >
> > >> > Jona, did you already have tarball for 4-STABLE which people can just
> > >> > extract and compile a new kernel with?
> > >>
> > >> Hmm, no. I should probably generate one. However, I do have the
> >> miibus.ko and if_fxp.ko binary modules for 4-STABLE, if you want
> > >> to just drop those in a system and use it.
> > >>
> > >> http://www.flugsvamp.com/~jlemon/fbsd/drivers/
> > >
> > >I have a -stable box with a pair of 82559s on the motherboard
> > >that I can use for testing, if you need/want testers for -stable.
> >
> > I've had a bunch of people test it already, thanks. However, I would
> > still like to hear from someone whos card did not work before the
> > driver was upgraded, but does work now.
>
> FYI, on a REALLY OLD fxp:
>
> fxp0: <Intel Pro 10/100B/100+ Ethernet> 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: <DP83840 10/100 media interface> 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 detected.
> 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.
I spoke too soon:
[machine 1, 10.0.0.18, ping 10.0.0.16]
05:14:13.248353 arp who-has 10.0.0.16 tell 10.0.0.18
05:14:14.258430 arp who-has 10.0.0.16 tell 10.0.0.18
05:14:15.268516 arp who-has 10.0.0.16 tell 10.0.0.18
05:14:16.278597 arp who-has 10.0.0.16 tell 10.0.0.18
[nsphy fxp, 10.0.0.16]
05:13:43.662723 arp who-has 10.0.0.16 tell 10.0.0.18
05:13:43.662895 arp reply 10.0.0.16 is-at 0:a0:c9:49:aa:d3
05:13:44.672965 arp who-has 10.0.0.16 tell 10.0.0.18
05:13:44.673169 arp reply 10.0.0.16 is-at 0:a0:c9:49:aa:d3
[the timestamps are out of sync, that makes no difference]
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?)
$ dmesg | tail
...
Thu Mar 15 05:06:51 PST 2001
fxp0: device timeout
fxp0: device timeout
fxp0: device timeout
fxp0: device timeout
...
This is an Intel PR440FX motherboard, so I can't send you the card. :-)
Dual PPro-200MHz system, with onboard 82557 w/ real natsemi phy.
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200103151320.f2FDKwh83702>