On Wednesday 23 October 2002 06:40 pm,[EMAIL PROTECTED] wrote: <snip> > > > > [root@noname /root]# cat /proc/interrupts > > CPU0 > > 0: 38618 XT-PIC timer > > 1: 161 XT-PIC keyboard > > 2: 0 XT-PIC cascade > > 5: 6332 XT-PIC ncr53c8xx > > 7: 0 XT-PIC soundblaster > > 9: 0 XT-PIC acpi <snip> > > > > cat /proc/interrupts thinks that the soundblaster is irq = 7 but > > then it looks like the module sb is testing irq=7 and failing. > > If you can shed some light on this, I would appreciate it greatly. > > The same isapnp.conf worked in 2.2.x (but it wanted irq=9) so > > something changed from 2.2.x to 2.4.x > > 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. > > Kurt -- Tony Alfrey [EMAIL PROTECTED] "I'd rather be sailing" _______________________________________________ Linux-users mailing list [EMAIL PROTECTED] Unsubscribe/Suspend/Etc -> http://www.linux-sxs.org/mailman/listinfo/linux-users
