Isapnp.conf
Isapnp startup script no longer works. The READPORT fails to read the isapnp port number due to resource conflict. (READPORT 0x0213) Only a limited range can be entered here and the one I placed was shown on the /proc/ioports file. There are two, the one labeled as write is outside the allowed range. ~$ cat /proc/ioports | grep -i pnp 0213-0213 : ISAPnP 0400-04bf : pnp 00:08 04d0-04d1 : pnp 00:01 0800-087f : pnp 00:01 0880-088f : pnp 00:01 0a79-0a79 : isapnp write The card in question may or may not be defective at this point but the only initialization being done is by BIOS. (Further?) initialization used to be done by isapnp. Any fix here? Is this all not needed or deprecated? (The card in question is an older ISA analog telephone modem. So far, no PCI modem, at least the older ones I have around, is recognized by the system. I am running Sid on a P4 on one of the few remaining MBs that has ISA.)
Re: Isapnp.conf
David Baron put forth on 4/21/2011 3:36 AM: Isapnp startup script no longer works. The READPORT fails to read the isapnp port number due to resource conflict. (READPORT 0x0213) Only a limited range can be entered here and the one I placed was shown on the /proc/ioports file. There are two, the one labeled as write is outside the allowed range. ~$ cat /proc/ioports | grep -i pnp 0213-0213 : ISAPnP 0400-04bf : pnp 00:08 04d0-04d1 : pnp 00:01 0800-087f : pnp 00:01 0880-088f : pnp 00:01 0a79-0a79 : isapnp write The card in question may or may not be defective at this point but the only initialization being done is by BIOS. (Further?) initialization used to be done by isapnp. Any fix here? Is this all not needed or deprecated? (The card in question is an older ISA analog telephone modem. So far, no PCI modem, at least the older ones I have around, is recognized by the system. I am running Sid on a P4 on one of the few remaining MBs that has ISA.) I never cared for internal soft modems, especially PCI soft modems. Too many problems. I always used an external serial modem--universal compatibility no matter what PC/OS you plug it into. I've not used a POTS modem for a decade, but I'd bet things haven't changed WRT internal soft modem headaches. Does the P4 box in question have an RS232 port? If so ~$30 buys you a brand new 56k external fax modem: http://www.newegg.com/Product/Product.aspx?Item=N82E16825134002 If you don't have a serial port, a USB modem would probably be better than an internal soft modem, especially an ISA PNP card. This Rosewill USB 56k modem gets great reviews with Linux, only $20: http://www.newegg.com/Product/Product.aspx?Item=N82E16825164005 -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4daff590.9060...@hardwarefreak.com
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-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201103271603.06871.d_ba...@012.net.il
isapnp.conf
My laptop has an expansion port containing a 3c509b ethernet card. The 2.2 kernel, LTSP boot disk windows recognise this as io 0c300 irq 10 work. The 2.4.20 kernel recognises it as 0x220 irq 5 doesn't 2.4 kernel says it uses isapnp but I cannot run it from root or find it or find a isapnp.conf file. How do I specify io = 0x300 irq = 10 in the new kernel? please Steve -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: isapnp.conf y Eicon DIVA 2.01 ISA
El Lun 22 Oct 2001 14:10, Javier Juez Santamaría escribió: Agracedería ayuda para inicializar esta tarjeta mediante las isapnp tools. He probado todas las combinaciones, y no acepta ninguna de las interrupciones que admite la tarjeta. Querido JJ: A lo mejor te vale con cargar algún módulo. Héchale un vistazo a Documentation/isdn/README.eicon de los fuentes del kernel.
Re: isapnp.conf problems
Dammit!! I shouldn't have wasted anytime trying to get that junk to work with linux... thanks for the *early* warning though..if you hadn't said anything I would still be probably trying to make that combo-card work. Ain't gonna happen. The aztechs don't work under Linux-- they're Packard Bell: 'nuff said. On Thu, 15 Feb 2001, john smith wrote: I am trying to revive an old isa pnp modem/soundcard and when I use pnpdump to try and configure my modem (not the soundcard yet) I see this error at /var/log and during boot-up when my card is being detected. Board 1 has identity of FF FF FF FF 003 054 07 AZT300 serial no-1 [checksum of ] /etc/isapnp.conf:93- fatal-IO range check attempted while device activated /etc/isapnp.conf:93- fatal : error occured executing request 'IORESCHECK' --further action aborted I tried mucking around with the BIOS (i.e. turning on/off pnp os and resources controlled by auto/manual) to no avail. Any suggestions? TIA _ Get your FREE download of MSN Explorer at http://explorer.msn.com -- Pardon me, but you have obviously mistaken me for someone who gives a damn. email [EMAIL PROTECTED] _ Get your FREE download of MSN Explorer at http://explorer.msn.com
isapnp.conf problems
I am trying to revive an old isa pnp modem/soundcard and when I use pnpdump to try and configure my modem (not the soundcard yet) I see this error at /var/log and during boot-up when my card is being detected. Board 1 has identity of FF FF FF FF 003 054 07 AZT300 serial no-1 [checksum of ] /etc/isapnp.conf:93- fatal-IO range check attempted while device activated /etc/isapnp.conf:93- fatal : error occured executing request 'IORESCHECK' --further action aborted I tried mucking around with the BIOS (i.e. turning on/off pnp os and resources controlled by auto/manual) to no avail. Any suggestions? TIA _ Get your FREE download of MSN Explorer at http://explorer.msn.com
Re: isapnp.conf problems
john smith wrote: I am trying to revive an old isa pnp modem/soundcard and when I use pnpdump to try and configure my modem (not the soundcard yet) I see this error at /var/log and during boot-up when my card is being detected. Board 1 has identity of FF FF FF FF 003 054 07 AZT300 serial no-1 [checksum of ] /etc/isapnp.conf:93- fatal-IO range check attempted while device activated /etc/isapnp.conf:93- fatal : error occured executing request 'IORESCHECK' --further action aborted I tried mucking around with the BIOS (i.e. turning on/off pnp os and resources controlled by auto/manual) to no avail. Any suggestions? TIA _ I have seen several pnp modems with jumpers that enable you to defeat the pnp function , so perhaps you should try that route first. If that is not possible consult /usr/doc/HOWTO//Plug-and-Play-HOWTO, which covers the subject pretty well. Be sure to check your jumper settings for comports. Typical modem settings are COM2 or COM4(ttyS01 or ttyS03) and IRQ3. Wdoze 9x likes to see modems on COM2 so use that as your prefered setting. I've seen isa plug and play refered to often as plug and pray- so good luck. Bernie
Re: isapnp.conf problems
Ain't gonna happen. The aztechs don't work under Linux-- they're Packard Bell: 'nuff said. On Thu, 15 Feb 2001, john smith wrote: I am trying to revive an old isa pnp modem/soundcard and when I use pnpdump to try and configure my modem (not the soundcard yet) I see this error at /var/log and during boot-up when my card is being detected. Board 1 has identity of FF FF FF FF 003 054 07 AZT300 serial no-1 [checksum of ] /etc/isapnp.conf:93- fatal-IO range check attempted while device activated /etc/isapnp.conf:93- fatal : error occured executing request 'IORESCHECK' --further action aborted I tried mucking around with the BIOS (i.e. turning on/off pnp os and resources controlled by auto/manual) to no avail. Any suggestions? TIA _ Get your FREE download of MSN Explorer at http://explorer.msn.com -- Pardon me, but you have obviously mistaken me for someone who gives a damn. email [EMAIL PROTECTED]
isapnp.conf
Hey, I'm trying to get my ethernet NE2000 clone to work in linux. The HOWTO said to read up about isapnptools, so I started looking at the README.debian, and it has someone's config file here. Anyways, I can't make any sense of it. It says: # EDI0119 Serial No 2368613654 [checksum 13] # ANSI string --PLUG PLAY ETHERNET CARD-- # Logical device id EDI0119 #Device support I/0 range check register (CONFIGURE EDI0119/236861364 (LD 0 Where can I find out what the logical device id (and serial no) are? Somewhere in /proc? Thanks, Cameron Matheson
Re: isapnp.conf
On Sun, May 21, 2000 at 22:35, Cameron Matheson wrote: Hey, I'm trying to get my ethernet NE2000 clone to work in linux. The HOWTO said to read up about isapnptools, so I started looking at the README.debian, and it has someone's config file here. Anyways, I can't make any sense of it. It says: # EDI0119 Serial No 2368613654 [checksum 13] # ANSI string --PLUG PLAY ETHERNET CARD-- # Logical device id EDI0119 #Device support I/0 range check register (CONFIGURE EDI0119/236861364 (LD 0 Where can I find out what the logical device id (and serial no) are? Somewhere in /proc? pnpdump --configure is your friend. Luck, Pann -- geek by nature, Linux by choice L I N U X .~. The Choice /V\ http://www.ourmanpann.com/linux/ of a GNU /( )\ Generation ^^-^^
Invoking /etc/isapnp.conf
This message was sent from Geocrawler.com by Howard Mann [EMAIL PROTECTED] Be sure to reply to that address. Hi, I am planning a move from RH to Debian. I will configure my eth interface during the installation. However, I use isapnptools for my ISA EtherEZ NIC, which works fine. In Debian, what is the best way to invoke the /ect/isapnp.conf file on bootup so that the NIC is recognized ? In Red Hat, this is invoked by default via the /etc/rc.d/rc.sysinit script. I presume I should put in a runlevel 2 -related rc.d directory. (I'll simply copy it from RH to the appropriate directory in Debian) Thanks, Howard Mann. Geocrawler.com - The Knowledge Archive
Re: Invoking /etc/isapnp.conf
On Wed, Dec 01, 1999 at 01:26:51PM -0800, Howard Mann wrote: In Debian, what is the best way to invoke the /ect/isapnp.conf file on bootup so that the NIC is recognized ? Install the isapnptools package. This will automatically setup scripts in /etc/init.d and symlinks from the proper rc?.d directories. The only symlink on my system (i haven't messed with the configs, so i assume this is the default for isapnptools 1.19-1) is /etc/rcS.d/S15isapnp, which will start it just after the root filesystem is remounted read-write. Modules are typically started from /etc/rcS.d/S20modutils, so by the time it tries installing your network card module isapnp will have been run. -- finger for GPG public key. 29 Nov 1999 - new email address added to gpg key pgpKTZ7WqTvYR.pgp Description: PGP signature
Re: Invoking /etc/isapnp.conf
On Wed, Dec 01, 1999 at 01:26:51PM -0800, Howard Mann wrote: In Debian, what is the best way to invoke the /ect/isapnp.conf file on bootup so that the NIC is recognized ? In Red Hat, this is invoked by default via the /etc/rc.d/rc.sysinit script. Just make sure you install the isapnptools package... it will automatically run /sbin/isapnp prior to configuring the network.