Date: Thu, 13 Jun 1996 08:48:16 -0700 (PDT) From: pluvius <pluvius@cyberflunk.com> To: current@freefall.freebsd.org Subject: Re: 3Com 590 not seen Message-ID: <Pine.SOL.3.93.960613083718.7178A-100000@rapture.cyberflunk.com> In-Reply-To: <199606130954.CAA10575@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
If it counts for anything, i had some pretty wierd behaviour with a 3c590
.. it was in the 960601-snap, when using the 3c590 (it was an asus mother
board, with ide disabled, and a aha2940W) it worked fine, and infact well
enough to do a network install via ftp from, but once the operating system
was installed, i experienced VERY odd behaviour:
o any outbound connections will hang after transfering approx 1K
(ie: telnet from the box, ftp from the box)
o all inbound (incoming telnet, incoming ftp) worked perfectly fine.
I decided to yank the 590 and put in a 3c509 and everything works just
fine.
J Wunsch <j@uriah.heep.sax.de>:
> As Beck Peccoz Amedeo wrote:
>
> > In the kernel config I added the line "options vx0" as suggested
> > from the LINT, but when starting up, the kernel didn't notice
> > the board, so I tried to contigure the kernel, i.e. type a "-c"
> > at the boot prompt, but in the network section only the usual
> > serial and parallel port drivers appeared.
>
> Only ISA drivers need to be configured with boot -c.
>
> > I'm running Snapshot with ctm 1873. What's wrong?
>
> Well, vx0 is a device, not an option. ;)
>
> device vx0
>
> - --
> cheers, J"org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SOL.3.93.960613083718.7178A-100000>