From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Josh Huber <huberj@wpi.edu>
Cc: Linux/PowerPC Devel List <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Lite-On ethernet controller
Date: Wed, 31 May 2000 09:32:12 -0400 [thread overview]
Message-ID: <3935145C.DE1F478D@mandrakesoft.com> (raw)
In-Reply-To: 20000531090215.A652@mclinux.com
Josh Huber wrote:
>
> I have what appears to be a Lite-On ethernet controller, which is supported
> by the tulip driver. What it really is, is a Asante FriendlyNET card. I had
> heard that the card works in 2.2.14+, but I'm having trouble getting it to
> work in later kernels (devel).
>
> Because of the network driver interface change, I can't try out the newest
> tulip driver in 2.4pre.
I don't understand what you mean here.
> Does anyone know of forward-ported tulip drivers?
A tulip driver exists in the 2.4pre kernel. Are you having problems
with that driver?
> The particular error I'm seeing only happens with moderate load -- pings and
> other light traffic work 100%.
>
> Error information:
> NETDEV WATCHDOG: eth1: transmit timed out
> Transmit timed out, status e4660000, CSR12 000050ca, resetting...
>
> Device information:
> tulip driver output:
> eth1: Lite-On PNIC-II rev 37 at 0x1c00, 00:00:94:C5:EF:FF, IRQ 30.
IRQ 30? Is that ok for PPC?
> lspci -vv output attached because it's too wide.
No attachment...
Jeff
--
Jeff Garzik | Liberty is always dangerous, but
Building 1024 | it is the safest thing we have.
MandrakeSoft, Inc. | -- Harry Emerson Fosdick
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-05-31 13: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 [this message]
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
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=3935145C.DE1F478D@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=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).