Date: Sat, 19 Sep 1998 15:13:14 -0400 (EDT) From: Bill Paul <wpaul@skynet.ctr.columbia.edu> To: kong@kong.spb.ru (Hostas Red) Cc: current@FreeBSD.ORG Subject: Re: strange things: xl driver Message-ID: <199809191913.PAA19911@skynet.ctr.columbia.edu> In-Reply-To: <Pine.BSF.3.96.980919222120.307J-100000@kong.dorms.spbu.ru> from "Hostas Red" at Sep 19, 98 10:29:33 pm
next in thread | previous in thread | raw e-mail | index | archive | help
Of all the gin joints in all the towns in all the world, Hostas Red had
to walk into mine and say:
> Hi!
>
> On Sat, 19 Sep 1998, Bill Paul wrote:
>
> > The vx driver doesn't use DMA!
> >
> > - The subject line doesn't even mention the xl driver, which means it
> > was only by pure chance that I happen to find this thread in my mail
> > backlog.
>
> Hmm... This problem may be not the problem of xl driver.
If the OACTIVE flag is set on the interface, then it probably is.
> > - Nobody has mentioned what version of the xl drive they are using.
> > For all I know you downloaded an old version from www.freebsd.org
> > and are complaining about bugs that are already fixed. Run, don't
> > walk, to /sys/pci/if_xl.c and show me the RCS $Id$ string so I have
> > some idea what's going on here.
>
> I'm cvsupping once a day at least, sometimes 2-3 times. Here the RCS ID:
>
> * $Id: if_xl.c,v 1.11 1998/09/08 23:42:10 wpaul Exp $
>
>
> > - Nobody has bothered to describe the hardware they're using. What kind
> > of CPU do you have? What other PCI devices do you have?
>
> CPU: P5/166 on ASUS TX97X, other devices - DEC 21143 PCI Lancard, that's
> all (it doesn't work under freebsd on 10 mbit, so i'm using 3c905)
>
> > - Nobody has told me EXACTLY WHAT 3COM CARD THEY HAVE! Is it a 3c905-TX?
> > 3c900? 3c905B? 3c980?
>
> 3C905-TX
>
> > - Nobody has bothered to show a dmesg output with the probe information
> > from the xl driver.
>
> xl0: <3Com 3c905 Fast Etherlink XL 10/100BaseTX> rev 0x00 int a irq 10 on
> pci0.11.0
> xl0: Ethernet address: 00:a0:24:d8:a4:81
> xl0: autoneg not complete, no carrier
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This implies that the card was not plugged in at the time you
booted the machine. The autoneg code will only set the card's
modes correctly if it says 'autoneg complete.'
So now we have more missing information:
- Does the driver _always_ say 'autoneg not complete' or was this just
a one-time occurance and you happened to just pick this particular
message to show me?
- Have you tried rebooting the machine with the card plugged in?
- Did you try to force the mode to 10Mbps/half duplex with the command
ifconfig xl0 media 10baseT/UTP mediaopt half-duplex?
- How do you have the interface configured in /etc/rc.conf?
- What does netstat -in say?
- Have you tried putting the card in a different slot? (Yes, it can make
a difference.)
-Bill
--
=============================================================================
-Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu
Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research
Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City
=============================================================================
"It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness"
=============================================================================
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199809191913.PAA19911>