Hmm. So, yep, it failed.
Since you say you've had it working in the last, I wonder if the trouble is a
newer version of isapnptools attempting to be more careful than before. What
happens if you try the following for isapnp.conf:
(READPORT 0x0203)
(ISOLATE CLEAR)
(IDENTIFY *)
(VERBOSITY 2)
(CONFIGURE BNK1361/-1 (LD 0
(NAME "BNK1361/-1[0]{K56 SVD/SP }")
))
(CONFIGURE BNK1361/-1 (LD 1
(IO 0 (SIZE 8) (BASE 0x0200) (CHECK))
(INT 0 (IRQ 12 (MODE +E)))
(NAME "BNK1361/-1[1]{K56 SVD/SP }")
(ACT Y)
))
(WAITFORKEY)
The isapnptools home page has an interesting snippet:
>>>>>
5-Jun-1999: Please also note that the error message
/etc/isapnp.conf:46 -- FATAL - IO rangecheck attempted while device
activated.
is completely different from the problem reported on 28-May-1999, which was that
IO resources were being reported as in use when they shouldn't be. The message
above means what it says. If you want to reconfigure a device already
activated, you should deactivate it first using (ACT N), see also (CHECK).
<<<<<
You'e not managine to run isapnp twice somehow, are you? Something like
originally running it from a user rc script at startup, and now your upgraded
Linux runs it already in one of the standard startup scripts?
I'm dammed if I can see why it should find something else allocated at 0x200.
The above modified isapnp.conf might get round this anyway; ISOLATE CLEAR is
supposed to reset all hardware back to their default settings.
If the hint from the isapnptools page is right, I suppose putting:
(CONFIGURE BNK1361/-1 (LD 1
(NAME "BNK1361/-1[1]{K56 SVD/SP }")
(ACT N)
))
before the (CONFIGURE ... ACT Y)) might be worth a go as well.
--
Jim Hague - [EMAIL PROTECTED] (Work), [EMAIL PROTECTED] (Play)
Never trust a computer you can't lift.
--
SLUG - Sydney Linux Users Group Mailing List - http://www.slug.org.au
To unsubscribe send email to [EMAIL PROTECTED] with
unsubscribe in the text
