From: Mark Felder <felderado@gmail.com>
To: Luke-Jr <luke@dashjr.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PCI bridge missing
Date: Thu, 28 Sep 2006 16:52:49 -0500 [thread overview]
Message-ID: <20060928165249.ab5b7bbe.felderado@gmail.com> (raw)
In-Reply-To: <200609281624.16082.luke@dashjr.org>
I have Dell Optiplex GX1's at the school district I'm covering at. I can test some stuff out with various live CDs if that would help.
Mark
On Thu, 28 Sep 2006 16:24:15 -0500
Luke-Jr <luke@dashjr.org> wrote:
> This applies to Debian sarge kernels kernel-image-2.4.27-2-686, 2.6.8-3-686,
> 2.6.16-2-686, and 2.6.17-2-686...
> I am trying to setup a Dell Optiplex GX1p system, which has a daughterboard
> PCI bridge for its PCI and ISA slots:
> 00:0f.0 PCI bridge: Digital Equipment Corporation DECchip 21152 (rev 03)
>
> 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.
>
> How could I go about troubleshooting the problem? Has anyone experienced
> something like this before?
>
> Thanks,
>
> Luke-Jr
>
> P.S. Please CC me if possible.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2006-09-28 21:52 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 [this message]
2006-09-28 23:14 ` Alan Cox
2006-09-29 0:17 ` Luke-Jr
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=20060928165249.ab5b7bbe.felderado@gmail.com \
--to=felderado@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luke@dashjr.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.