From: "Hans-Jürgen Koch" <hjk@linutronix.de>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: What's needed for a PCIe card to be recognized?
Date: Sat, 16 Feb 2008 22:59:32 +0100 [thread overview]
Message-ID: <20080216225932.22460d31@dilbert.local> (raw)
I'm playing around with a vanilla 2.6.25-rc1, adding patches to make it
work on an Asus EeePC. That one has the problem that its Mini PCIe WLAN
module doesn't show up in lspci. That brought up a few questions that I
couldn't answer yet:
How can they "hide" a PCIe card?
What could be their motive to do that?
How can I make it appear?
I found some solutions googling around, but they all seem to be funny
workarounds, like unloading pciehp and then loading it again with
pciehp_force=1, then switching WLAN off and on again
(through /proc/acpi/asus/wlan, I've got that one meanwhile)... This
doesn't look like a clean solution to me, but I must admit that I don't
know enough about PCIe hotplug to understand what's going on. I'd
appreciate it if someone could give me a few hints or point me to good
documentation.
Output of lspci:
00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 04)
00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 04)
00:02.1 Display controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 04)
00:1b.0 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 (rev 04)
00:1c.1 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 2 (rev 04)
00:1c.2 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 3 (rev 04)
00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 04)
00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 04)
00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 04)
00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 04)
00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 04)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev d4)
00:1f.0 ISA bridge: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge (rev 04)
00:1f.2 IDE interface: Intel Corporation 82801FBM (ICH6M) SATA Controller (rev 04)
00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller (rev 04)
03:00.0 Ethernet controller: Attansic Technology Corp. L2 100 Mbit Ethernet Adapter (rev a0)
(The WLAN card should show up at 01:00.0, according to info found on
the web).
Thanks,
Hans
next reply other threads:[~2008-02-16 21:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-16 21:59 Hans-Jürgen Koch [this message]
2008-02-16 22:39 ` What's needed for a PCIe card to be recognized? Arjan van de Ven
2008-02-17 0:54 ` Hans-Jürgen Koch
2008-02-17 2:29 ` Arjan van de Ven
2008-02-17 12:37 ` Hans J. Koch
2008-02-17 15:29 ` Arjan van de Ven
2008-02-17 16:47 ` Hans J. Koch
2008-02-17 22:05 ` Mark Lord
2008-02-17 22:09 ` Mark Lord
2008-02-17 23:03 ` Hans-Jürgen Koch
2008-02-17 18:48 ` Hans J. Koch
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=20080216225932.22460d31@dilbert.local \
--to=hjk@linutronix.de \
--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