If the configuration file cannot be opened, the program
aborts immediately with a suitable message.
If an error occurs later, a message is printed to standard error in
the form:
file:lineno -- Warning/Fatal - message
where
\fCfile
The configuration file being read ('-') for stdin.
\fClineno
The line number that the error occured at (or noticed).
\fCWarning/Fatal
Warning if the error was not serious and execution can continue,
Fatal if the program cannot proceed.
\fCmessage
The error message, hopefully meaningful, see below.
\fCUnable to allocate memory for action list processing
The program has run out of memory and will abort. Fit more memory, or
add more swap space. This is extremely unlikely as isapnp is normally
run during boot up, when there are no users logged on.
\fCISOLATE called twice, or after CSN - clearing board count
You had an (ISOLATE..) after a previous occurance of (ISOLATE..) or
(CSN..). The program will rescan for boards. You should fix your
script to only scan for boards once, by removing one of the above
statements.
\fCIRQ2 is not a valid selection, changing it to IRQ9 (See clarifications 4.6.2)
Your configuration file attempted to configure a board to use
IRQ2. This is invalid according to the clarifications to the PnP ISA
spec v1.0a, and should be changed to use IRQ9, which has been
done. You should change your configuration file to use IRQ9 in the
first place.
\fCresource conflict allocating IRQx (see ...)
Your configuration file has attempted to program a board to use an IRQ
line which is already used by something else. The see ... bit tells
you where the IRQ line was first flagged as being in use. Change the
script to use a different IRQ line, or fix the information being
provided if the line really isn't already used.
\fCresource conflict allocating n bytes of IO at x (see ...)
Your configuration file has attempted to program a board to use IO
ports which are already used by something else. The see ... bit tells
you where the ports were first flagged as being in use. Change the
script to use different ports, or fix the information being provided
if the ports really aren't already used.
\fCIO range check attempted while device activated
Your configuration file has attempted to carry out an IO range check
on a device which has already been configured and activated. You must
either not attempt the check, or deactivate the device before the
check. This error is a sign that you are on shakey ground. If the
device is already activated, and you are running isapnp for the first
time, then some other program has already activated the device (may be
the BIOS, or some of the cleverer kernel drivers). You probably
shouldn't be attempting to configure the device at all. There could
already be drivers accessing the card.
\fCIO range check failed for n bytes of IO at x
The IO range check failed. This is a sign that there is a conflict of
port addresses with some other device. Reassign the IO ports for this
device (or the other one if you know what is is and how to do it).
\fCresource conflict allocating DMAx (see ...)
Your configuration file has attempted to program a board to use a DMA
line which is already used by something else. The see ... bit tells
you where the DMA line was first flagged as being in use. Change the
script to use a different DMA line, or fix the information being
provided if the line really isn't already used.
\fCresource conflict allocating Memory at a (see ...)
Your configuration file has attempted to program a board to use memory
addresses which are already used by something else. The see ... bit
tells you where the addresses were first flagged as being in
use. Change the script to use different addresses, or fix the
information being provided if the addresses really aren't already
used.
The following messages may also occur:
\fCREALTIME operation timeout exceeded - Switching to normal scheduling
The program has been running for more than 5 seconds, so something is
probably wrong. Rather than lock up your machine, it is switching out
of real-time mode so that other programs can run again. The program will
now probably run slower. If this message occurs, you may want to kill
isapnp.
\fCCouldn't clear real-time scheduling, may continue to use all CPU for a while
The program has been running for more than 5 seconds, but the attempt
to leave real-time mode failed (impossible !), so there will be a
further 5 second delay, then if it hasn't finished by then the program
will kill itself.
\fCTime expired - aborting program
The above happened (even though it's impossible !). The program is
killing itself.
\fCPort address xx (0x..) out of range 0x203..0x3ff
You have provided an invalid READPORT address - fix it.
\fCREADPORT not set
You have not specified a READPORT, and not done an (ISOLATE..) which
would find one, so the program cannot proceed. Either specify a READPORT
or carry out an (ISOLATE..).
\fCRead port x cannot be allocated - resource conflict (see ...)
The READPORT is already in use. Choose another.
\fCTimeout attempting to read resource data - is READPORT correct ?
The status bit to signal the resource data was valid never got set,
this could be due to a conflict with your choice of READPORT address,
try another.
\fCLD setting verify failed, this may not be a problem. Try adding (VERIFYLD N) to the top of your script
Reading back the logical device selection register failed. It appears
some boards do this if you access the devices in the wrong order. Do
like it says, and add (VERIFYLD N) to the top of your script and see
if the board configures ok.
\fCCan only poke bytes
You've tried to poke a value outside the range 0..255. Fix your
script.
\fCDon't know what to do with ... on or around line x
You've got a syntax error somewhere. If the word is a valid command,
you've probably got braces not matching. Fix your script.
\fCUnable to get io permission for WRITE_DATA
You are not superuser. Only superuser has the required permissions to
run isapnp.
\fCnanosleep failed
Impossible ! If it happens, the program will to run in real-time mode.