From: Andrew Morton <akpm@zip.com.au>
To: Muli Ben-Yehuda <mulix@actcom.co.il>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 3com 3c905cx-tx-nm "unknown device"
Date: Sat, 11 May 2002 01:07:53 -0700 [thread overview]
Message-ID: <3CDCD159.8F9049C4@zip.com.au> (raw)
In-Reply-To: <20020511103650.A790@actcom.co.il>
Muli Ben-Yehuda wrote:
>
> Hello,
>
> I have new 3com PCI NIC, which purpots to be a "3c905cx-tx-nm". The
> 3c59x module (kernel 2.4.19-pre3-ac2, I'll try -pre8 in a bit) fails
> to recognize the card.
Well it would...
> lspci -vx (with the latest pci.ids file) shows:
>
> 00:09.0 Ethernet controller: 3Com Corporation: Unknown device ffff (rev 78)
> Flags: bus master, medium devsel, latency 64, IRQ 11
> I/O ports at 6500 [size=128]
> Expansion ROM at <unassigned> [disabled] [size=128K]
> Capabilities: [dc] Power Management version 2
> 00: b7 10 ff ff 07 00 10 02 78 00 00 02 08 40 00 00
> 10: 01 65 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 20: 00 00 00 00 00 00 00 00 00 00 00 00 ff ff ff ff
> 30: 00 00 00 00 dc 00 00 00 00 00 00 00 0b 01 1e 3f
PCI IDs are 0xffff. Normally that is supplied from the EEPROM (we think).
Try setting the NIC up with 3com's DOS-based setup program
ftp://ftp.3com.com/pub/nic/3c90x/3c90xx2.exe and also check your
BIOS power management settings, PnP OS settings, etc.
Try to work out why the EEPROM hasn't been powered up - could be
a dead card (test it under Windows) or a BIOS thing.
-
next prev parent reply other threads:[~2002-05-11 8:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-11 7:36 3com 3c905cx-tx-nm "unknown device" Muli Ben-Yehuda
2002-05-11 8:07 ` Andrew Morton [this message]
2002-05-11 10:32 ` Muli Ben-Yehuda
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=3CDCD159.8F9049C4@zip.com.au \
--to=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mulix@actcom.co.il \
/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.