From: David Woodhouse <dwmw2@infradead.org>
To: Andy Grover <agrover@groveronline.com>
Cc: jgarzik@mandrakesoft.com, linux-kernel@vger.kernel.org
Subject: Direct PCI access broken in 2.4.10-pre
Date: Wed, 19 Sep 2001 12:55:19 +0100 [thread overview]
Message-ID: <30185.1000900519@redhat.com> (raw)
2.4.10-pre3 and later fail to boot on my Compaq XL box. It claims that PCI
isn't supported. This board doesn't use the PCI BIOS because the entry
point is in high memory.
'cvs up -r v2_4_10-pre2 arch/i386/boot/pci-pc.c' fixes it.
A happy boot with the old pci-pc.c:
PCI: BIOS32 entry (0xc00fa000) in high memory, cannot use.
PCI: Using configuration type 2
PCI: Probing PCI hardware
An unhappy boot with the new one:
PCI: BIOS32 entry (0xc00fa000) in high memory, cannot use.
PCI: System does not support PCI
An unhappy boot with the new one and 'pci=conf2':
PCI: Using configuration type 2
PCI: Probing PCI hardware
PCI: device 00:01.0 has unknown header type 7f, ignoring.
PCI: device 00:02.0 has unknown header type 7f, ignoring.
PCI: device 00:03.0 has unknown header type 7f, ignoring.
PCI: device 00:04.0 has unknown header type 7f, ignoring.
PCI: device 00:05.0 has unknown header type 7f, ignoring.
PCI: device 00:06.0 has unknown header type 7f, ignoring.
PCI: device 00:07.0 has unknown header type 7f, ignoring.
PCI: device 00:08.0 has unknown header type 7f, ignoring.
PCI: device 00:09.0 has unknown header type 7f, ignoring.
PCI: device 00:0a.0 has unknown header type 7f, ignoring.
PCI: device 00:0e.2 has unknown header type 7f, ignoring.
PCI: device 00:0e.3 has unknown header type 7f, ignoring.
PCI: device 00:0e.4 has unknown header type 7f, ignoring.
PCI: device 00:0e.5 has unknown header type 7f, ignoring.
PCI: device 00:0e.6 has unknown header type 7f, ignoring.
PCI: device 00:0e.7 has unknown header type 7f, ignoring.
PCI: Cannot allocate resource region 0 of device 00:0e.0
PCI: Cannot allocate resource region 1 of device 00:0e.1
PCI: Cannot allocate resource region 2 of device 00:0e.1
PCI: Cannot allocate resource region 3 of device 00:0e.1
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
<deadlock>
--
dwmw2
next reply other threads:[~2001-09-19 11:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-19 11:55 David Woodhouse [this message]
2001-09-19 12:31 ` [PATCH] Re: Direct PCI access broken in 2.4.10-pre Brian Gerst
2001-09-19 14:51 ` David Woodhouse
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=30185.1000900519@redhat.com \
--to=dwmw2@infradead.org \
--cc=agrover@groveronline.com \
--cc=jgarzik@mandrakesoft.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