[Patch: clarity] Re: PNP0303 can't assign resources
zhuravlev alexander wrote:
vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0
unknown: PNP0303 can't assign resources
unknown: PNP0c02 can't assign resources
unknown: PNP0501 can't assign resources
unknown: PNP0501 can't assign resources
unknown: PNP0401 can't assign resources
unknown: PNP0700 can't assign resources
ad0: 4125MB FUJITSU MPB3043ATU E [8940/15/63] at ata0-master UDMA33
acd0: CDROM CREATIVECD3220E at ata0-slave PIO4
Mounting root from ufs:/dev/ad0s2a
- end
is this normal ?
It is if you have your BIOS configured incorrectly with
regard to whether you are running a PNP OS.
It's also normal if you have more hardware in a box
than it's possible to handle simultaneously, e.g. if
you had a bunch of slots full of resource hungry
hardware.
Probably you will need to fiddle with your BIOS.
Try the following patch; the failure message will be
somewhat less cryptic, since it will tell you the
proximal reason for failure out of the 5 possibles
for the message you are seeing. 8-).
-- Terry
Index: isa_common.c
===
RCS file: /usr/cvs/src/sys/isa/isa_common.c,v
retrieving revision 1.16.2.1
diff -u -r1.16.2.1 isa_common.c
--- isa_common.c16 Sep 2000 15:49:52 - 1.16.2.1
+++ isa_common.c24 Feb 2002 21:07:23 -
@@ -387,15 +387,20 @@
struct isa_device *idev = DEVTOISA(child);
struct isa_config_entry *ice;
struct isa_config config;
+ char *reason = Empty ISA id_configs;
bzero(config, sizeof config);
TAILQ_FOREACH(ice, idev-id_configs, ice_link) {
+ reason = memory;
if (!isa_find_memory(child, ice-ice_config, config))
continue;
+ reason = port;
if (!isa_find_port(child, ice-ice_config, config))
continue;
+ reason = irq;
if (!isa_find_irq(child, ice-ice_config, config))
continue;
+ reason = drq;
if (!isa_find_drq(child, ice-ice_config, config))
continue;
@@ -403,6 +408,7 @@
* A working configuration was found enable the device
* with this configuration.
*/
+ reason = no callback;
if (idev-id_config_cb) {
idev-id_config_cb(idev-id_config_arg,
config, 1);
@@ -414,7 +420,7 @@
* Disable the device.
*/
bus_print_child_header(device_get_parent(child), child);
- printf( can't assign resources\n);
+ printf( can't assign resources (%s)\n, reason);
if (bootverbose)
isa_print_child(device_get_parent(child), child);
bzero(config, sizeof config);
Re: [Patch: clarity] Re: PNP0303 can't assign resources
This is a multi-part message in MIME format. --741846253D1D9002AE8EAD96 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit zhuravlev alexander wrote: vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: PNP0303 can't assign resources unknown: PNP0c02 can't assign resources unknown: PNP0501 can't assign resources unknown: PNP0501 can't assign resources unknown: PNP0401 can't assign resources unknown: PNP0700 can't assign resources ad0: 4125MB FUJITSU MPB3043ATU E [8940/15/63] at ata0-master UDMA33 acd0: CDROM CREATIVECD3220E at ata0-slave PIO4 Mounting root from ufs:/dev/ad0s2a - end is this normal ? It is if you have your BIOS configured incorrectly with regard to whether you are running a PNP OS. It's also normal if you have hints loaded for things that could have been autoconfigured, which is what the above seems to suggest. -- To announce that there must be no criticism of the president, or that we are to stand by the president, right or wrong, is not only unpatriotic and servile, but is morally treasonable to the American public. - Theodore Roosevelt To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: [Patch: clarity] Re: PNP0303 can't assign resources
Michael Smith wrote: It is if you have your BIOS configured incorrectly with regard to whether you are running a PNP OS. It's also normal if you have hints loaded for things that could have been autoconfigured, which is what the above seems to suggest. OK. 8-). I've always seen it when my PNP OS setting was wrong. The card IDs made me pretty sure it wasn't 8 muti-I/O cards. 8-). -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: [Patch: clarity] Re: PNP0303 can't assign resources
In the last episode (Feb 24), Terry Lambert said: zhuravlev alexander wrote: vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: PNP0303 can't assign resources unknown: PNP0c02 can't assign resources unknown: PNP0501 can't assign resources unknown: PNP0501 can't assign resources unknown: PNP0401 can't assign resources unknown: PNP0700 can't assign resources ad0: 4125MB FUJITSU MPB3043ATU E [8940/15/63] at ata0-master UDMA33 acd0: CDROM CREATIVECD3220E at ata0-slave PIO4 Mounting root from ufs:/dev/ad0s2a - end is this normal ? It is if you have your BIOS configured incorrectly with regard to whether you are running a PNP OS. Not many BIOSes even give you this option anymore.. -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: [Patch: clarity] Re: PNP0303 can't assign resources
* Terry Lambert [EMAIL PROTECTED] [020224 13:12] wrote: Try the following patch; the failure message will be somewhat less cryptic, since it will tell you the proximal reason for failure out of the 5 possibles for the message you are seeing. 8-). Cool explanation, the attached patch was committed but had to be modified because it wouldn't apply cleanly. Was it meant for -stable? -Alfred To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: [Patch: clarity] Re: PNP0303 can't assign resources
Alfred Perlstein wrote: * Terry Lambert [EMAIL PROTECTED] [020224 13:12] wrote: Try the following patch; the failure message will be somewhat less cryptic, since it will tell you the proximal reason for failure out of the 5 possibles for the message you are seeing. 8-). Cool explanation, the attached patch was committed but had to be modified because it wouldn't apply cleanly. Was it meant for -stable? Ugh. Should have done a context diff. Yeah, it was against 4.5-stable on my machine here. I can't upgrade that particular machine for you-know-why. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
