linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scott@broadlink.com>
To: "linuxppc-dev@lists.linuxppc.org" <linuxppc-dev@lists.linuxppc.org>
Subject: DEC Tulip not working in B&W G3
Date: Fri, 03 Sep 1999 14:59:42 -0700	[thread overview]
Message-ID: <37D044CE.B31A1907@broadlink.com> (raw)


I have a NetGear FA-310TX (DEC 21141) NIC in my new B&W G3 running kernel
2.2.6.
The kernel detects the card and gives me an eth1 interface, but I can't 
pass any traffic into or out of the interface, and I get some strange
kernel
messages:

eth0: BMAC+ at 00:50:e4:20:d7:43
  The PCI BIOS has not enabled this device!  Updating PCI command
0000->0005.
tulip.c:v0.89H 5/23/98 becker@cesdis.gsfc.nasa.gov
eth1: Digital DS21140 Tulip at 0x1080, 40 00 35 05 fc db, IRQ 23.
eth1:  MII transceiver found at MDIO address 0, config 1000 status 7809.
eth1:  Advertising 01e1 on PHY 0, previously advertising 01e1.

>---snip---<

phy registers:
 0800 7809 7810 0001 01e1 40a1 0003 0000
 0000 0000 0000 0000 0000 0000 0000 0000
 0000 0002 0000 1000 0048 0010 0000 0002
 0001 0000 0000 0000 0000 0000 0000 0000

I'm not certain exactly what causes this message to be printed, though. 
Has
anyone else got the Tulip NICs to work in a B&W G3??

-- 
+---------------------+----------------------+
|     Scott Wood      |   Systems  Engineer  |
|=====================+======================|
|           BroadLink Communications         |
+--------------------------------------------+

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

                 reply	other threads:[~1999-09-03 21:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=37D044CE.B31A1907@broadlink.com \
    --to=scott@broadlink.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 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).