pnpdump, isapnp, and isapnp.conf



With new MB, I can no longer access my older, analog phone line modem.

The isapnp startup had an older isapnp.conf file.

I assume one uses pnpdump to make a new one with the correct ISAPNP port. I
found an address 0213 in the /proc/ioports and I seem to get a sensible conf
file using this. However, when running isapnp startup, it kicks at that port,
cannot execute the READPORT 0x0213, no further action. (I had the same error
on the old file that had 273 instead.)

1. Should I even need this?
2. Am I missing something here?
3. lshal shows the card on the appropriate /dev/ttyS2 with its interupt 12.
4. I was not successful with a newer PCI modem either.

The MB is a huge and costly one with a pentium-4 dual core 3ghz with pc-
express Nvidia graphics interface, PCI slots and two legacy ISA. Rare bird
nowadays. Everything else Debian seems to run no problem.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
Archive: http://lists.debian.org/201103271603.06871.d_baron@xxxxxxxxxx



Relevant Pages

  • RE: yet another newbie ppp/modem question
    ... If PCI modem them and you are not using com1,2 ports ... To unsubscribe, ...
    (freebsd-questions)
  • Re: Modem in Debian
    ... I've never had a PCI modem, only ISA internal and external modems. ... Do PCI modems show up in dmesg with what ttyS? ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx ...
    (Debian-User)