From: James Gale <jimg@eskimo.com>
To: linux-kernel@vger.kernel.org
Subject: PCI: System does not support PCI
Date: Sun, 30 Jun 2002 16:49:32 -0700 [thread overview]
Message-ID: <20020630164932.B22175@eskimo.eskimo.com> (raw)
All,
I'm posting this in hope that someone can explain the problem
I am seeing, or corroborate my story. I'm not subscribed to this
list so please CC me on any replies. I've moved my old hard-disk
with a 2.4 kernel to a new computer and tried to boot it up. I
get a strange message when I do that:
PCI: System does not support PCI
I don't have a /proc/pci file after boot-up either.
The new computer is an Athlon based Shuttle FS40 motherboard which,
of course, has a PCI bus. So what would cause the kernel to think
that this board doesn't support PCI? I've fooled with a few different
kernels that all give this error, but mostly I'm trying to boot my
stock Debian 2.4.18 kernel. Has anybody else seen this problem?
Thanks,
Jim
next reply other threads:[~2002-06-30 23:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-30 23:49 James Gale [this message]
2002-07-01 2:37 ` System does not support PCI Matthew D. Pitts
2002-07-01 2:54 ` James Gale
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=20020630164932.B22175@eskimo.eskimo.com \
--to=jimg@eskimo.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