Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 21 Aug 1998 11:04:19 -0500
From:      Paul Saab <paul@mu.org>
To:        current@FreeBSD.ORG
Subject:   Re: Problems with vx0 (3Com)
Message-ID:  <19980821110419.A29556@mu.org>
In-Reply-To: <35DD7F0B.7EBFC645@webwizard.org.mx>; from Edwin Culp on Fri, Aug 21, 1998 at 09:07:08AM -0500
References:  <199808211319.JAA14105@skynet.ctr.columbia.edu> <35DD7F0B.7EBFC645@webwizard.org.mx>

next in thread | previous in thread | raw e-mail | index | archive | help
the vx driver will continue to work for the 3c590 and 3c595 cards.

paul

Edwin Culp (eculp@webwizard.org.mx) wrote:
> Anybody tried it with the 3c595, that poor folks like us might still have?
> 
> Thanks
> 
> ed
> 
> Bill Paul wrote:
> 
> > Of all the gin joints in all the towns in all the world, Charlie ROOT
> > had to walk into mine and say:
> >
> > > Hi
> > >
> > > Todays current doesn't see vx0 anymore... Help.
> >
> > Aw, couldn't you have provided more information that this? This is not
> > enough to help you. It's not even enough to make a guess. (Well, maybe,
> > but not an informed guess.)
> >
> > What kind of network card do you have that's supposed to be detected
> > by the vx driver? A new driver (xl) was added recently to handle all of
> > the 3Com Etherlink XL cards (3c900, 3c905 and 3c905B, which up until
> > now was not supported. The vx driver supported some of these cards,
> > but not fully and not very efficiently; support for the 3c90x cards
> > in the vx driver was disabled so that the xl driver would detect them
> > instead. Which one did you have, and did you look for xl0 instead of vx0?
> >
> > There are two things that could have gone wrong here:
> >
> > - The xl driver failed to detect your card, either because of a bug
> >   or because I screwed up somehow when I imported it (nobody else has
> >   complained about this so far though; I'll see if there's been a recent
> >   snapshot and snag a copy of the boot floppy to make sure it sees the
> >   cardson my systems).
> >
> > - You used an old kernel configuration file as opposed to GENERIC
> >   and your custom configuration doesn't specify the xl driver. If this
> >   is the case, add the following line your config file under where
> >   it says 'device vx0':
> >
> >         device xl0
> >
> >   You will also need to edit your rc.conf file to use xl0 instead of
> >   vx0.
> >
> > - The driver is in the kernel and it did detect your card, but all you
> >   saw were the error messages from the rc scripts saying that there was
> >   no such interface as xl0. Check the dmesg output, and edit your
> >   /etc/rc.conf file as necessary.
> >
> > NOTE: If your card is a COMBO (like the 3c900 COMBO) and the driver
> >       selects the wrong media, use the ifmedia options to select the
> >       right one:
> >
> >         # ifconfig xl0 media 10baseT/UTP    (for RJ-45 twisted pair)
> >         # ifconfig xl0 media 10base2/BNC    (for coax/thinnet)
> >         # ifconfig xl0 media 10base5/AUI    (for AUI)
> >
> >      You can also add the 'media foo' options to the 'interfaces'
> >      lines in your /etc/rc.conf to insure the right media is selected
> >      when the machine boots.
> >
> >      For the TPO cards there's only one possible media so it can't
> >      get that wrong, and for the 100Mbps cards it should autoselect
> >      the speed and duplex modes. (You can still force a particular
> >      mode if you want.)
> >
> > -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
> >
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message

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?19980821110419.A29556>