From: Sean Neakums <sneakums@zork.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Crash with 3c59x.o
Date: Tue, 24 Dec 2002 12:54:05 +0000 [thread overview]
Message-ID: <6uu1h3pogi.fsf@zork.zork.net> (raw)
In-Reply-To: <20021224123341.GA22985@kiwi.hjbaader.home> (Hans-Joachim Baader's message of "Tue, 24 Dec 2002 13:33:45 +0100")
commence Hans-Joachim Baader quotation:
> lspci:
> 00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03)
> 00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03)
> 00:07.0 ISA bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02)
> 00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01)
> 00:07.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01)
> 00:07.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 02)
> 00:09.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone] (rev 30)
> 00:0b.0 Serial controller: NetMos Technology 222N-2 I/O Card (2S+1P) (rev 01)
> 00:0f.0 Ethernet controller: 3Com Corporation 3c590 10BaseT [Vortex]
> 00:13.0 Unknown mass storage controller: Triones Technologies, Inc. HPT366 / HPT370 (rev 01)
> 00:13.1 Unknown mass storage controller: Triones Technologies, Inc. HPT366 / HPT370 (rev 01)
>
> As you can see, there are two 3Com cards which are both recognized by the
> driver.
Possibly this is not what you meant, but lspci output does not
indicate whether a PCI device has been recognised by a driver or not.
You would need to check e.g. dmesg output or ifconfig -a after loading
the driver module to verify that it sees both cards.
--
/ |
[|] Sean Neakums | Questions are a burden to others;
[|] <sneakums@zork.net> | answers a prison for oneself.
\ |
prev parent reply other threads:[~2002-12-24 12:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-24 12:33 Hans-Joachim Baader
2002-12-24 12:54 ` Sean Neakums [this message]
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=6uu1h3pogi.fsf@zork.zork.net \
--to=sneakums@zork.net \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®