Nate Williams once stated:
=The 589D also has problems under heavy load, but I doubt many people
=are running heavily loaded applications on their laptops. (I did it
=once, and it tended to timeout and require a lot of ifconfig ep0
=up/down about every 3-4 minutes).
Reducing the MTU
> In message Dag-Erling Smorgrav writes:
> : Anybody using a 3c509 and expecting it to work reliably should be
> : taken out and shot in the back of the head.
>
> But what about a 3C589D? The ep driver supports them as well :-)
The 589D also has problems under heavy load, but I doubt many peopl
Warner Losh wrote:
> In message Dag-Erling Smorgrav writes:
> : Anybody using a 3c509 and expecting it to work reliably should be
> : taken out and shot in the back of the head.
>
> But what about a 3C589D? The ep driver supports them as well :-)
Or a 3C589E (AKA a 3CCE589ET)?
M
--
Mark Murray
In message Dag-Erling Smorgrav writes:
: Anybody using a 3c509 and expecting it to work reliably should be
: taken out and shot in the back of the head.
But what about a 3C589D? The ep driver supports them as well :-)
Warner
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe
On 1 May 1999, Dag-Erling Smorgrav wrote:
> Soren Schmidt writes:
> > [...]
> > There are lots of better cards out there, but stating that the 3c509
> > doesn't work, is totally out in the dark...
>
> Well, excuse me for breathing. I'll just take your word, and dismiss
> the problems I've had wi
It seems Dag-Erling Smorgrav wrote:
> Soren Schmidt writes:
> > [...]
> > There are lots of better cards out there, but stating that the 3c509
> > doesn't work, is totally out in the dark...
>
> Well, excuse me for breathing. I'll just take your word, and dismiss
> the problems I've had with flak
Soren Schmidt writes:
> [...]
> There are lots of better cards out there, but stating that the 3c509
> doesn't work, is totally out in the dark...
Well, excuse me for breathing. I'll just take your word, and dismiss
the problems I've had with flaky 3c509s (about two thirds of those
I've encounter
It seems Dag-Erling Smorgrav wrote:
> Alex Zepeda writes:
> > On Wed, 28 Apr 1999, Jim Bryant wrote:
> > > > Well, I'd chalk it up to buggy 3com h/w myself. Alas I'm still getting:
> > > > ep0 XXX: driver didn't set ifq_maxlen
> > > I still get that one too. Driver problem?
> > I'm guessing so.
> 3Com 3c509 NICs are unreliable. Some work, others don't. They are also
> known to be temperamental, in that the same card may perform well in
> one computer but poorly in another. Add to that the fact that the
> driver is buggy (search the mailing list archives!), and what you get
> is a hardware
Dag-Erling Smorgrav wrote:
> Alex Zepeda writes:
> > On Wed, 28 Apr 1999, Jim Bryant wrote:
> > > > Well, I'd chalk it up to buggy 3com h/w myself. Alas I'm still getting:
> > > > ep0 XXX: driver didn't set ifq_maxlen
> > > I still get that one too. Driver problem?
> > I'm guessing so. I wonder
Erwan Arzur writes:
> Dag-Erling Smorgrav wrote:
> > Anybody using a 3c509 and expecting it to work reliably should be
> > taken out and shot in the back of the head.
> would you please be more specific about that last sentence?
3Com 3c509 NICs are unreliable. Some work, others don't. They are al
Dag-Erling Smorgrav wrote:
> Alex Zepeda writes:
> > On Wed, 28 Apr 1999, Jim Bryant wrote:
> > > > Well, I'd chalk it up to buggy 3com h/w myself. Alas I'm still getting:
> > > > ep0 XXX: driver didn't set ifq_maxlen
> > > I still get that one too. Driver problem?
> > I'm guessing so. I wonde
Dag-Erling Smorgrav once wrote:
> > > > Well, I'd chalk it up to buggy 3com h/w myself. Alas I'm still
> > > > getting: ep0 XXX: driver didn't set ifq_maxlen
> > > I still get that one too. Driver problem?
> > I'm guessing so. I wonder if this is the cause of some odd network
> > behavior I'm
Leif Neland writes:
> Btw, why does boot write [*UTP*] ?
> The card is working nicely with bnc.
Your card is configured to use the UTP tranceiver. You probably have
-link1 in your ifconfig_ep0, which forces the card to switch to the
BNC tranceiver but does not actually reconfigure the card. 3Com
Alex Zepeda writes:
> On Wed, 28 Apr 1999, Jim Bryant wrote:
> > > Well, I'd chalk it up to buggy 3com h/w myself. Alas I'm still getting:
> > > ep0 XXX: driver didn't set ifq_maxlen
> > I still get that one too. Driver problem?
> I'm guessing so. I wonder if this is the cause of some odd netwo
On Wed, 28 Apr 1999, Jim Bryant wrote:
> > Well, I'd chalk it up to buggy 3com h/w myself. Alas I'm still getting:
> >
> > ep0 XXX: driver didn't set ifq_maxlen
>
> I still get that one too. Driver problem?
I'm guessing so. I wonder if this is the cause of some odd network
behavior I'm getti
In reply:
> On Wed, 28 Apr 1999, Jim Bryant wrote:
>
> > good question. when were your sources built? i'm running a kernel
> > from Thu Apr 8 10:40:17 CDT 1999.
> >
> > ep0 at 0x210-0x21f irq 10 on isa
> > ep0: aui/bnc[*BNC*] address 00:20:af:d2:e4:ae
>
> Well, I'd chalk it up to buggy 3com h
On Wed, 28 Apr 1999, Jim Bryant wrote:
> good question. when were your sources built? i'm running a kernel
> from Thu Apr 8 10:40:17 CDT 1999.
>
> ep0 at 0x210-0x21f irq 10 on isa
> ep0: aui/bnc[*BNC*] address 00:20:af:d2:e4:ae
Well, I'd chalk it up to buggy 3com h/w myself. Alas I'm still g
In reply:
> Btw, why does boot write [*UTP*] ?
> The card is working nicely with bnc.
>
> ep0 at port 0x300-0x30f irq 11 on isa0
> ep0: utp/bnc[*UTP*] address 00:60:08:09:c8:d9
> ep0: interrupting at irq 11
>
> device ep0 at isa? port 0x300 irq 11
>
> Leif
good question. when were your source
19 matches
Mail list logo
