From: Josh Huber <huberj@wpi.edu>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Linux/PowerPC Devel List <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Lite-On ethernet controller
Date: Wed, 31 May 2000 09:45:20 -0400 [thread overview]
Message-ID: <20000531094520.B652@mclinux.com> (raw)
In-Reply-To: <3935145C.DE1F478D@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Wed, May 31, 2000 at 09:32:12AM -0400
[-- Attachment #1: Type: text/plain, Size: 1613 bytes --]
On Wed, May 31, 2000 at 09:32:12AM -0400, Jeff Garzik wrote:
> I don't understand what you mean here.
Sorry I wasn't clear.
The Tulip driver in the devel kernels is not working for me. Supposedly,
this card works with the driver in later 2.2 kernels. I can't get 2.2.x to
boot on this machine I have, which is why I'm using 2.4 pre versions.
What I meant by the newer tulip driver was the version available from Don
Becker's tulip development page.
> > Does anyone know of forward-ported tulip drivers?
>
> A tulip driver exists in the 2.4pre kernel. Are you having problems
> with that driver?
Yes.
> > 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?
Yes, here's the output from /proc/interrupts:
CPU0
1: 1820 i8259 keyboard
2: 0 i8259 82c59 secondary cascade
8: 2 i8259 rtc
16: 0 OpenPIC 82c59 cascade
27: 0 OpenPIC NMI
29: 4872 OpenPIC eth0
30: 4624 OpenPIC eth1
31: 6377 OpenPIC aic7xxx
eth0 is an actual DEC tulip card, which works great.
> > lspci -vv output attached because it's too wide.
> No attachment...
Heh, sorry. I'll attach it this time.
Josh
[-- Attachment #2: lspci.out --]
[-- Type: text/plain, Size: 808 bytes --]
00:05.0 Ethernet controller: Lite-On Communications Inc: Unknown device c115 (rev 25)
Subsystem: Asante Technologies, Inc.: Unknown device f001
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 8 min, 56 max, 32 set, cache line size 08
Interrupt: pin A routed to IRQ 30
Region 0: I/O ports at 1c00 [size=256]
Region 1: Memory at c3002000 (32-bit, non-prefetchable) [size=256]
Expansion ROM at c1240000 [disabled] [size=256K]
Capabilities: [44] Power Management version 1
Flags: PMEClk- AuxPwr- DSI- D1+ D2+ PME-
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
next prev parent reply other threads:[~2000-05-31 13:45 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 [this message]
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=20000531094520.B652@mclinux.com \
--to=huberj@wpi.edu \
--cc=jgarzik@mandrakesoft.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.