linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Josh Huber <huberj@wpi.edu>
To: Linux/PowerPC Devel List <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Lite-On ethernet controller
Date: Wed, 31 May 2000 16:32:10 -0400	[thread overview]
Message-ID: <20000531163210.E652@mclinux.com> (raw)
In-Reply-To: <Pine.LNX.4.05.10005312154030.2148-100000@callisto.of.borg>; from geert@linux-m68k.org on Wed, May 31, 2000 at 10:10:56PM +0200


On Wed, May 31, 2000 at 10:10:56PM +0200, Geert Uytterhoeven wrote:
> Later the card seemed to work fine with the updated tulip driver, as you
> probably remember.  However, I just got a problem with the updated driver
> (2.3.99-pre3) for the first time:
[snip]

After updating to the newer tulip driver in the devel kernels, my problems
with my real tulip card went away.  I've been having trouble getting two
other cards working however -- the lite-on card that I mentioned before, and
another tulip clone (Kingston).  The kingston card was much worse -- it
dropped ~30% of packets under light load, and completely locked up under
medium-heavy load.

> Note that Josh is using a similar box as me, a CHRP LongTrail. In fact all
> people with LongTrails seem to have problems with Tulip chips. So it might be a
> motherboard problem.
Yeah, which would be unfortunate... :(

Josh

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-05-31 20:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-31 13:02 Lite-On ethernet controller Josh Huber
2000-05-31 13:32 ` Jeff Garzik
2000-05-31 13:45   ` Josh Huber
2000-05-31 18:40     ` Michel Lanners
2000-06-01 12:53       ` Josh Huber
2000-06-01 19:54         ` Geert Uytterhoeven
2000-05-31 20:10     ` Geert Uytterhoeven
2000-05-31 20:32       ` Josh Huber [this message]
2000-05-31 20:45         ` Jeff Garzik
2000-05-31 18:33   ` Michel Lanners

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20000531163210.E652@mclinux.com \
    --to=huberj@wpi.edu \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).