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.
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
all
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
ind 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]
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
''
>--further action ab
ee 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
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 ''
> --further action aborted
>
> I tried mucking around with the BIOS (i.e. turning on
]
/etc/isapnp.conf:93- fatal-IO range check attempted while device activated
/etc/isapnp.conf:93- fatal : error occured executing request ''
--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 av
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 i
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
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.
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
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
13 matches
Mail list logo
