public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <larry.finger@lwfinger.net>
To: LKML <linux-kernel@vger.kernel.org>
Cc: John Pierce <john.j35@gmail.com>,
	Broadcom Linux <bcm43xx-dev@lists.berlios.de>
Subject: Missing PCIe interface in lspci
Date: Mon, 24 Sep 2007 19:58:39 -0500	[thread overview]
Message-ID: <46F85D3F.5010400@lwfinger.net> (raw)
In-Reply-To: <aa73b9a0709231906s3bd7a2a0h3fbf5a751b531488@mail.gmail.com>

In the process of advising a user on getting a BCM4311 wireless device to work with bcm43xx rather
than ndiswrapper, the device stopped appearing in an lspci output. The 'lspci -vn' output
for this device before this failure was:

03:00.0 0280: 14e4:4311 (rev 01)
        Subsystem: 103c:1363
        Flags: fast devsel, IRQ 21
        Memory at b8000000 (32-bit, non-prefetchable) [size=16K]
        Capabilities: [40] Power Management version 2
        Capabilities: [58] Message Signalled Interrupts: Mask- 64bit-
Queue=0/0 Enable-
        Capabilities: [d0] Express Legacy Endpoint IRQ 0

Fortunately, the "customer" has two identical machines. Swapping the wireless cards showed that both
BCM4311s work in the other computer, but neither works in the problem machine. Kernel Version
2.6.22.4-65.fc7 is used on both.

Doing a line-by-line comparison of the dmesg outputs, the only thing that stands out is that the line

Allocate Port Service[0000:00:03.0:pcie03]

is missing on the faulty computer. This is the bridge that should connect to the device in question.

The BIOS has been reset and reflashed without helping the problem.

Is there anything other than some failure on the motherboard that would lead to this situation? Is
there anything that we can try? The BIOS in this machine doesn't have many options.


Thanks,

Larry

           reply	other threads:[~2007-09-25  0:58 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <aa73b9a0709231906s3bd7a2a0h3fbf5a751b531488@mail.gmail.com>]

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=46F85D3F.5010400@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=john.j35@gmail.com \
    --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