On Wed, Oct 23, 2002 at 06:58:27PM -0700, Tony Alfrey wrote:
> On Wednesday 23 October 2002 06:40 pm,[EMAIL PROTECTED] wrote:
[...]
> > So, tell it to use IRQ 9. ISAPNP will do that, won't it? On the other
> > hand, 2.4 has real PnP support in it, so you may not need ISAPNP.
>
> Alright, I think you have 'hit the nail on the head'. I can nuke the
> isapnp.conf file and something STILL initializes the card. I get the
> same dmesg with the same interrupt conflict. So how is PnP support
> happening with 2.4.x? I'm running this silly Caldera LTP which I think
> was a 3.x precursor so I'll bet the two boot similarly.
$ grep PNP $KERNEL/.config
CONFIG_PNP=y
CONFIG_ISAPNP=y
# CONFIG_IP_PNP is not set
# CONFIG_BLK_DEV_ISAPNP is not set
So, I'm guessing enabling (or not) ISAPNP in your kernel may (or may not)
fix your problem. ;-)
Kurt
--
IBM had a PL/I,
Its syntax worse than JOSS;
And everywhere this language went,
It was a total loss.
_______________________________________________
Linux-users mailing list
[EMAIL PROTECTED]
Unsubscribe/Suspend/Etc -> http://www.linux-sxs.org/mailman/listinfo/linux-users
