From: Andrew Morton <akpm@zip.com.au>
To: Chris Meadors <clubneon@hereintown.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 3c556 basicly not working.
Date: Sun, 04 Nov 2001 01:30:39 -0800 [thread overview]
Message-ID: <3BE50ABF.B51F7590@zip.com.au> (raw)
In-Reply-To: <3BE4BFA0.4DBF213F@zip.com.au> <Pine.LNX.4.33.0111040418050.28366-100000@clubneon.clubneon.com>
Chris Meadors wrote:
>
>
> Anything else you can think of?
>
Yeah, but nothing which'll make your NIC work ;)
Please send me a copy of the `lspci -xxx' output for the device.
To do this, first run `lspci' with no args, to get this:
00:00.0 Host bridge: Intel Corporation 440BX/ZX - 82443BX/ZX Host bridge (rev 03)
00:01.0 PCI bridge: Intel Corporation 440BX/ZX - 82443BX/ZX AGP bridge (rev 03)
00:02.0 CardBus bridge: Texas Instruments PCI1450 (rev 03)
00:02.1 CardBus bridge: Texas Instruments PCI1450 (rev 03)
00:03.0 Ethernet controller: 3Com Corporation 3c556B Laptop Hurricane (rev 20)
00:03.1 Communication controller: 3Com Corporation: Unknown device 1007 (rev 20)
00:05.0 Multimedia audio controller: Cirrus Logic CS 4614/22/24 [CrystalClear SoundFusion
...
And then run
lspci -xxx -s 00:03.0
Where the bus/slot/function identifiers refer to the 3com
device. (Running lspci -xxx against all PCI devices is risky.)
-
next prev parent reply other threads:[~2001-11-04 9:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-04 3:33 3c556 basicly not working Chris Meadors
2001-11-04 4:10 ` Andrew Morton
2001-11-04 9:20 ` Chris Meadors
2001-11-04 9:30 ` Andrew Morton [this message]
2001-11-04 13:51 ` Tom Sightler
2001-11-04 21:01 ` Chris Meadors
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=3BE50ABF.B51F7590@zip.com.au \
--to=akpm@zip.com.au \
--cc=clubneon@hereintown.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 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.