From: Luke-Jr <luke@dashjr.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
"Mark Knecht" <markknecht@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PCI bridge missing
Date: Fri, 29 Sep 2006 00:17:32 +0000 [thread overview]
Message-ID: <200609290017.34412.luke@dashjr.org> (raw)
In-Reply-To: <1159485255.13029.7.camel@localhost.localdomain>
On Thursday 28 September 2006 21:39, you wrote:
> Anyway, maybe you haven't cold booted the machine and could try that?
It's been cold-booted a few times, though I can't guarantee that for each
kernel I tried.
On Thursday 28 September 2006 23:14, Alan Cox wrote:
> Ar Iau, 2006-09-28 am 16:24 -0500, ysgrifennodd Luke-Jr:
> > However, this bridge is completely ignored and unseen by Linux. It does
> > not show up in lspci or dmesg (as far as I can tell) at all. The
> > daughterboard is plugged in, and the PCI cards on it are powered.
>
> lspci -vvxxx would be interesting
Will do tomorrow.
> Linux on PC assumes the BIOS did the work needed
pci=nobios doesn't bypass that assumption? (I tried that too)
> so if there is some custom "enabler" driver in the Windows for it that might
> explain problems.
Some old Debian (2.2) manual at least implied it worked at one point. That's
where I compared the lspci from. So this would be a regression, a hardware
failure, or a misconfiguration.
next prev parent reply other threads:[~2006-09-29 0:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-28 21:24 PCI bridge missing Luke-Jr
2006-09-28 21:39 ` Mark Knecht
2006-09-28 21:52 ` Mark Felder
2006-09-28 23:14 ` Alan Cox
2006-09-29 0:17 ` Luke-Jr [this message]
2006-09-29 11:36 ` Mark Brown
2006-09-29 17:28 ` Luke-Jr
2006-09-29 18:18 ` Alan Cox
2006-09-29 17:57 ` Luke-Jr
2006-09-29 18:53 ` Luke-Jr
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=200609290017.34412.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=markknecht@gmail.com \
/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