version 1, including all changes.
.
Rev |
Author |
# |
Line |
1 |
perry |
1 |
ISAPNP |
|
|
2 |
!!!ISAPNP |
|
|
3 |
NAME |
|
|
4 |
SYNOPSIS |
|
|
5 |
DESCRIPTION |
|
|
6 |
ERRORS |
|
|
7 |
FILES |
|
|
8 |
BUGS |
|
|
9 |
WARNING |
|
|
10 |
AUTHOR |
|
|
11 |
AVAILABILITY |
|
|
12 |
REFERENCES |
|
|
13 |
SEE ALSO |
|
|
14 |
---- |
|
|
15 |
!!NAME |
|
|
16 |
|
|
|
17 |
|
|
|
18 |
isapnp - Configure ISA Plug-and-Play devices. |
|
|
19 |
!!SYNOPSIS |
|
|
20 |
|
|
|
21 |
|
|
|
22 |
__isapnp__ [[ --help ] [[ --version ] |
|
|
23 |
''conffile'' |
|
|
24 |
!!DESCRIPTION |
|
|
25 |
|
|
|
26 |
|
|
|
27 |
__isapnp__ will carry out the instructions provided in |
|
|
28 |
the ''conffile'' to configure ISA PnP cards. |
|
|
29 |
__isapnp__ must read in the entire configuration file |
|
|
30 |
successfully before it will execute the commands: this is to |
|
|
31 |
ensure the instructions are consistent and valid. |
|
|
32 |
The format of the configuration file is described in |
|
|
33 |
__isapnp.conf(5)__. |
|
|
34 |
|
|
|
35 |
|
|
|
36 |
In version 1.16 and later of __isapnptools__, |
|
|
37 |
__isapnp__ checks resources are available as the devices |
|
|
38 |
are configured. If there is a conflict, a diagnostic message |
|
|
39 |
is given, and the program can be made to abort if required |
|
|
40 |
by placing the appropriate settings in the configuration |
|
|
41 |
file. |
|
|
42 |
|
|
|
43 |
|
|
|
44 |
In version 1.18 and later of __isapnptools__, |
|
|
45 |
''conffile'' may be '-', meaning read the configuration |
|
|
46 |
file from stdin. |
|
|
47 |
|
|
|
48 |
|
|
|
49 |
__isapnp__ will run with real-time scheduling if possible |
|
|
50 |
to achieve the required IO timings. This will lock out all |
|
|
51 |
normal programs while it executes. In version 1.19 and later |
|
|
52 |
of __isapnptools__, __isapnp__ will only run in this |
|
|
53 |
mode for 5 seconds, it then reverts to standard scheduling |
|
|
54 |
like any other program. Previous versions should only be run |
|
|
55 |
from a standard console as ^C will kill it from there. If |
|
|
56 |
you run the command remotely (and X counts as remote), you |
|
|
57 |
will not be able to kill it as no other programs can |
|
|
58 |
run. |
|
|
59 |
|
|
|
60 |
|
|
|
61 |
__Options__ |
|
|
62 |
|
|
|
63 |
|
|
|
64 |
''-h, --help'' |
|
|
65 |
|
|
|
66 |
|
|
|
67 |
Show a help summary. |
|
|
68 |
|
|
|
69 |
|
|
|
70 |
''-v, --version'' |
|
|
71 |
|
|
|
72 |
|
|
|
73 |
Print the isapnptools version number on stderr. |
|
|
74 |
!!ERRORS |
|
|
75 |
|
|
|
76 |
|
|
|
77 |
If the configuration file cannot be opened, the program |
|
|
78 |
aborts immediately with a suitable message. |
|
|
79 |
|
|
|
80 |
|
|
|
81 |
If an error occurs later, a message is printed to standard |
|
|
82 |
error in the form: |
|
|
83 |
|
|
|
84 |
|
|
|
85 |
''file'':''lineno'' -- ''Warning/Fatal'' - |
|
|
86 |
''message'' |
|
|
87 |
|
|
|
88 |
|
|
|
89 |
where |
|
|
90 |
|
|
|
91 |
|
|
|
92 |
file |
|
|
93 |
|
|
|
94 |
|
|
|
95 |
The configuration file being read ('-') for |
|
|
96 |
stdin. |
|
|
97 |
|
|
|
98 |
|
|
|
99 |
lineno |
|
|
100 |
|
|
|
101 |
|
|
|
102 |
The line number that the error occured at (or |
|
|
103 |
noticed). |
|
|
104 |
|
|
|
105 |
|
|
|
106 |
Warning/Fatal |
|
|
107 |
|
|
|
108 |
|
|
|
109 |
Warning if the error was not serious and execution can |
|
|
110 |
continue, Fatal if the program cannot proceed. |
|
|
111 |
|
|
|
112 |
|
|
|
113 |
message |
|
|
114 |
|
|
|
115 |
|
|
|
116 |
The error message, hopefully meaningful, see |
|
|
117 |
below. |
|
|
118 |
|
|
|
119 |
|
|
|
120 |
Unable to allocate memory for action list |
|
|
121 |
processing |
|
|
122 |
|
|
|
123 |
|
|
|
124 |
The program has run out of memory and will abort. Fit more |
|
|
125 |
memory, or add more swap space. This is extremely unlikely |
|
|
126 |
as isapnp is normally run during boot up, when there are no |
|
|
127 |
users logged on. |
|
|
128 |
|
|
|
129 |
|
|
|
130 |
ISOLATE called twice, or after CSN - clearing board |
|
|
131 |
count |
|
|
132 |
|
|
|
133 |
|
|
|
134 |
You had an (ISOLATE..) after a previous occurance of |
|
|
135 |
(ISOLATE..) or (CSN..). The program will rescan for boards. |
|
|
136 |
You should fix your script to only scan for boards once, by |
|
|
137 |
removing one of the above statements. |
|
|
138 |
|
|
|
139 |
|
|
|
140 |
IRQ2 is not a valid selection, changing it to IRQ9 (See |
|
|
141 |
clarifications 4.6.2) |
|
|
142 |
|
|
|
143 |
|
|
|
144 |
Your configuration file attempted to configure a board to |
|
|
145 |
use IRQ2. This is invalid according to the clarifications to |
|
|
146 |
the PnP ISA spec v1.0a, and should be changed to use IRQ9, |
|
|
147 |
which has been done. You should change your configuration |
|
|
148 |
file to use IRQ9 in the first place. |
|
|
149 |
|
|
|
150 |
|
|
|
151 |
resource conflict allocating IRQx (see |
|
|
152 |
...) |
|
|
153 |
|
|
|
154 |
|
|
|
155 |
Your configuration file has attempted to program a board to |
|
|
156 |
use an IRQ line which is already used by something else. The |
|
|
157 |
see ... bit tells you where the IRQ line was first flagged |
|
|
158 |
as being in use. Change the script to use a different IRQ |
|
|
159 |
line, or fix the information being provided if the line |
|
|
160 |
really isn't already used. |
|
|
161 |
|
|
|
162 |
|
|
|
163 |
resource conflict allocating n bytes of IO at x (see |
|
|
164 |
...) |
|
|
165 |
|
|
|
166 |
|
|
|
167 |
Your configuration file has attempted to program a board to |
|
|
168 |
use IO ports which are already used by something else. The |
|
|
169 |
see ... bit tells you where the ports were first flagged as |
|
|
170 |
being in use. Change the script to use different ports, or |
|
|
171 |
fix the information being provided if the ports really |
|
|
172 |
aren't already used. |
|
|
173 |
|
|
|
174 |
|
|
|
175 |
IO range check attempted while device |
|
|
176 |
activated |
|
|
177 |
|
|
|
178 |
|
|
|
179 |
Your configuration file has attempted to carry out an IO |
|
|
180 |
range check on a device which has already been configured |
|
|
181 |
and activated. You must either not attempt the check, or |
|
|
182 |
deactivate the device before the check. This error is a sign |
|
|
183 |
that you are on shakey ground. If the device is already |
|
|
184 |
activated, and you are running isapnp for the first time, |
|
|
185 |
then some other program has already activated the device |
|
|
186 |
(may be the BIOS, or some of the cleverer kernel drivers). |
|
|
187 |
You probably shouldn't be attempting to configure the device |
|
|
188 |
at all. There could already be drivers accessing the |
|
|
189 |
card. |
|
|
190 |
|
|
|
191 |
|
|
|
192 |
IO range check failed for n bytes of IO at |
|
|
193 |
x |
|
|
194 |
|
|
|
195 |
|
|
|
196 |
The IO range check failed. This is a sign that there is a |
|
|
197 |
conflict of port addresses with some other device. Reassign |
|
|
198 |
the IO ports for this device (or the other one if you know |
|
|
199 |
what is is and how to do it). |
|
|
200 |
|
|
|
201 |
|
|
|
202 |
resource conflict allocating DMAx (see |
|
|
203 |
...) |
|
|
204 |
|
|
|
205 |
|
|
|
206 |
Your configuration file has attempted to program a board to |
|
|
207 |
use a DMA line which is already used by something else. The |
|
|
208 |
see ... bit tells you where the DMA line was first flagged |
|
|
209 |
as being in use. Change the script to use a different DMA |
|
|
210 |
line, or fix the information being provided if the line |
|
|
211 |
really isn't already used. |
|
|
212 |
|
|
|
213 |
|
|
|
214 |
resource conflict allocating Memory at a (see |
|
|
215 |
...) |
|
|
216 |
|
|
|
217 |
|
|
|
218 |
Your configuration file has attempted to program a board to |
|
|
219 |
use memory addresses which are already used by something |
|
|
220 |
else. The see ... bit tells you where the addresses were |
|
|
221 |
first flagged as being in use. Change the script to use |
|
|
222 |
different addresses, or fix the information being provided |
|
|
223 |
if the addresses really aren't already used. |
|
|
224 |
|
|
|
225 |
|
|
|
226 |
The following messages may also occur: |
|
|
227 |
|
|
|
228 |
|
|
|
229 |
REALTIME operation timeout exceeded - Switching to |
|
|
230 |
normal scheduling |
|
|
231 |
|
|
|
232 |
|
|
|
233 |
The program has been running for more than 5 seconds, so |
|
|
234 |
something is probably wrong. Rather than lock up your |
|
|
235 |
machine, it is switching out of real-time mode so that other |
|
|
236 |
programs can run again. The program will now probably run |
|
|
237 |
slower. If this message occurs, you may want to kill |
|
|
238 |
isapnp. |
|
|
239 |
|
|
|
240 |
|
|
|
241 |
Couldn't clear real-time scheduling, may continue to use |
|
|
242 |
all CPU for a while |
|
|
243 |
|
|
|
244 |
|
|
|
245 |
The program has been running for more than 5 seconds, but |
|
|
246 |
the attempt to leave real-time mode failed (impossible !), |
|
|
247 |
so there will be a further 5 second delay, then if it hasn't |
|
|
248 |
finished by then the program will kill itself. |
|
|
249 |
|
|
|
250 |
|
|
|
251 |
Time expired - aborting program |
|
|
252 |
|
|
|
253 |
|
|
|
254 |
The above happened (even though it's impossible !). The |
|
|
255 |
program is killing itself. |
|
|
256 |
|
|
|
257 |
|
|
|
258 |
Port address xx (0x..) out of range |
|
|
259 |
0x203..0x3ff |
|
|
260 |
|
|
|
261 |
|
|
|
262 |
You have provided an invalid READPORT address - fix |
|
|
263 |
it. |
|
|
264 |
|
|
|
265 |
|
|
|
266 |
READPORT not set |
|
|
267 |
|
|
|
268 |
|
|
|
269 |
You have not specified a READPORT, and not done an |
|
|
270 |
(ISOLATE..) which would find one, so the program cannot |
|
|
271 |
proceed. Either specify a READPORT or carry out an |
|
|
272 |
(ISOLATE..). |
|
|
273 |
|
|
|
274 |
|
|
|
275 |
Read port x cannot be allocated - resource conflict (see |
|
|
276 |
...) |
|
|
277 |
|
|
|
278 |
|
|
|
279 |
The READPORT is already in use. Choose another. |
|
|
280 |
|
|
|
281 |
|
|
|
282 |
Timeout attempting to read resource data - is READPORT |
|
|
283 |
correct ? |
|
|
284 |
|
|
|
285 |
|
|
|
286 |
The status bit to signal the resource data was valid never |
|
|
287 |
got set, this could be due to a conflict with your choice of |
|
|
288 |
READPORT address, try another. |
|
|
289 |
|
|
|
290 |
|
|
|
291 |
LD setting verify failed, this may not be a problem. Try |
|
|
292 |
adding (VERIFYLD N) to the top of your |
|
|
293 |
script |
|
|
294 |
|
|
|
295 |
|
|
|
296 |
Reading back the logical device selection register failed. |
|
|
297 |
It appears some boards do this if you access the devices in |
|
|
298 |
the wrong order. Do like it says, and add (VERIFYLD N) to |
|
|
299 |
the top of your script and see if the board configures |
|
|
300 |
ok. |
|
|
301 |
|
|
|
302 |
|
|
|
303 |
Can only poke bytes |
|
|
304 |
|
|
|
305 |
|
|
|
306 |
You've tried to poke a value outside the range 0..255. Fix |
|
|
307 |
your script. |
|
|
308 |
|
|
|
309 |
|
|
|
310 |
Don't know what to do with ... on or around line |
|
|
311 |
x |
|
|
312 |
|
|
|
313 |
|
|
|
314 |
You've got a syntax error somewhere. If the word is a valid |
|
|
315 |
command, you've probably got braces not matching. Fix your |
|
|
316 |
script. |
|
|
317 |
|
|
|
318 |
|
|
|
319 |
Unable to get io permission for |
|
|
320 |
WRITE_DATA |
|
|
321 |
|
|
|
322 |
|
|
|
323 |
You are not superuser. Only superuser has the required |
|
|
324 |
permissions to run isapnp. |
|
|
325 |
|
|
|
326 |
|
|
|
327 |
nanosleep failed |
|
|
328 |
|
|
|
329 |
|
|
|
330 |
Impossible ! If it happens, the program will to run in |
|
|
331 |
real-time mode. |
|
|
332 |
!!FILES |
|
|
333 |
|
|
|
334 |
|
|
|
335 |
/sbin/isapnp |
|
|
336 |
|
|
|
337 |
|
|
|
338 |
The executable. |
|
|
339 |
|
|
|
340 |
|
|
|
341 |
/etc/isapnp.conf |
|
|
342 |
|
|
|
343 |
|
|
|
344 |
The standard place for the ''conffile''. |
|
|
345 |
|
|
|
346 |
|
|
|
347 |
/etc/isapnp.gone |
|
|
348 |
|
|
|
349 |
|
|
|
350 |
The standard place for describing resources that are |
|
|
351 |
unavailable, but not flagged as such in /proc/* etc. The |
|
|
352 |
format of this file is explained in the example provided |
|
|
353 |
with __isapnptools__. |
|
|
354 |
!!BUGS |
|
|
355 |
|
|
|
356 |
|
|
|
357 |
Check http://www.roestock.demon.co.uk/isapnptools/ for |
|
|
358 |
latest information and FAQ. |
|
|
359 |
|
|
|
360 |
|
|
|
361 |
If you think you have found one not mentioned in the latest |
|
|
362 |
version, please send a report to |
|
|
363 |
isapnp@roestock.demon.co.uk. |
|
|
364 |
!!WARNING |
|
|
365 |
|
|
|
366 |
|
|
|
367 |
This program can reset all your Plug-and-Play devices. It |
|
|
368 |
can also lock up your machine. Use at your own |
|
|
369 |
risk. |
|
|
370 |
!!AUTHOR |
|
|
371 |
|
|
|
372 |
|
|
|
373 |
__isapnp__ has been written by Peter Fox |
|
|
374 |
__ |
|
|
375 |
!!AVAILABILITY |
|
|
376 |
|
|
|
377 |
|
|
|
378 |
The latest version of the sources may be obtained by ftp |
|
|
379 |
from ftp://ftp.demon.co.uk/pub/unix/linux/utils |
|
|
380 |
Or follow the pointer from my web page at |
|
|
381 |
http://www.roestock.demon.co.uk/ |
|
|
382 |
!!REFERENCES |
|
|
383 |
|
|
|
384 |
|
|
|
385 |
Plug and Play ISA Specification, Version 1.0a, May 5, 1994. |
|
|
386 |
Available from |
|
|
387 |
ftp://ftp.microsoft.com/developr/drg/Plug-and-Play/Pnpspecs |
|
|
388 |
!!SEE ALSO |
|
|
389 |
|
|
|
390 |
|
|
|
391 |
pnpdump(8), isapnp.conf(5) |
|
|
392 |
---- |