Guillaume wrote:
Hello,
I'm running FreeBSD 5.0-CURRENT since 2 days.
When I boot FreeBSD I get this error:
Feb 22 23:21:13 unix /boot/kernel/kernel: vga0: Generic ISA VGA at port
0x3c0-0x3df iomem 0xa-0xb on isa0
Feb 22 23:21:13 unix /boot/kernel/kernel: unknown: PNP0303 can't assign
resources
Feb 22 23:21:13 unix /boot/kernel/kernel: unknown: PNP0501 can't assign
resources
Feb 22 23:21:13 unix /boot/kernel/kernel: unknown: PNP0501 can't assign
resources
Feb 22 23:21:13 unix /boot/kernel/kernel: unknown: PNP0401 can't assign
resources
Feb 22 23:21:13 unix /boot/kernel/kernel: unknown: PNP0700 can't assign
resources
What is that and how can I fix this error?
The BIOS's PNP table i sreporting devices that you are also mentionning
in either your kernel config hints file, or in /boot/device.hints.
(or maybe even PCI devices). In either case, the one you mention in your
config gets allocated the ports and interrupts etc. so when the kernel
tries to allocate them for the PNP device, it can't. Since they
are refering to the same device, this doesn;t matter, in fact it's good.
(Or you'd have two driver instances pointing at teh same hardware).
if you remove the entries in /boot/device.hints that refer to the same
device, and let the PNP table be used instead to attach drivers (for those that
are recognised)
you'll get less of these.
Msmith mailed me a PNP device list.
I include it here for your assistance in identifying these.
Guillaume
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
--
__--_|\ Julian Elischer
/ \ [EMAIL PROTECTED]
( OZ) World tour 2000-2001
--- X_.---._/
v
This document is the ultimate source for Windows Generic Device IDs
and Plug and Play BIOS device type codes.
CONTENTS:
Plug and Play Vendor IDs and Device IDs
Generic Device IDs
Device Type Codes
==
PLUG AND PLAY VENDOR IDs AND DEVICE IDs
All non-BIOS enumerated devices must not use "PNP" in their Vendor and
Device codes. The vendor must register with EISA and have a vendor code
assigned (for example, CTL for Creative Labs). The "PNP" vendor code
is reserved for Microsoft and can only be used when defining a devices
CompatibleID after indicating the devices HardwareID in the Plug and
Play header.
Use of CompatibleIDs is strongly recommended for devices that use
device drivers provided with Microsoft Windows 95, such as a
"Standard PC COM Port" (PNP0500) or
"Sound Blaster 16 Sound Device" (PNPB003).
The following example output from ISOLATE.EXE of a Plug and Play
header is provided for your reference:
Vendor ID: XXX
Serial Number: 0001
Checksum (reported): 0x5E
PNP Version: 1.0
Vendor Ver.: 10
Device Description: IDE Port
Device ID: XXX0001
Doesn't Support I/O Range Checking
Vendor Defined Logical Device Control Registers: None
Compatible Device ID: PNP0600
Device Description: IDE
Dependent Function 0
...
Dependent Function 1
...
End of Dependent Functions
When the user is installing devices that use this method,
a dialog box appears at the beginning of the enumeration sequence
to suggest use of the default driver provided with Windows 95.
Windows 95 also provides the option for using a disk from the
manufacturer, in case the user wants to choose a manufacturer-supplied
driver.
For multifunction adapters, you should supply an INF file that chooses
the appropriate drivers (including default drivers) for all the
adapters devices. This prevents additional dialog boxes from again
requesting the default driver or a manufactures disk for the rest of
the devices on the adapter. When an INF file is used in this manner
for default driver selection, it must link the HardwareID (XXX)
to the appropriate compatible device driver from the Windows 95
distribution compact disc or installation disks.
If this is not done, Windows 95 will continue to query the user for
either the default driver or a new driver, thus defeating the purpose
of using the INF file in this way.
==
WINDOWS GENERIC DEVICE IDs
--
Many devices have no standard EISA ID, such as the interrupt controller
or keyboard controller. Also, a set of compatible devices, such as VGA
and Super VGA, are not actually devices, but define a compatibility
hardware subset. Yet another set of IDs needs to be used to identify
buses.
Microsoft has reserved an EISA prefix of "PNP" to identify various
devices that do not have an existing EISA ID, as well as defining
