Hello: I am attempting to use an Adaptec AHA-2940UW SCSI host adapter and a 3Com 905B 10/100 ethernet adapter on a box with an older motherboard that refuses to assign separate IRQs to PCI expansion cards. The motherboard is a circa 1996 FIC PA-2002, rev 1.21 that I won in raffle; it came with an AMD K5-100 installed. The PCI bud is supposed to allow more than one device to use an IRQ but, still, such a condition can cause problems (on older hardware). Donald Becker wrote the 3Com driver. His webpage "Resolving Linux PCI Interrupt Conflicts" webpage at <<A HREF="http://cesdis.gsfc.nasa.gov/linux/misc/irq-conflict.html"><A HREF="http://cesdis.gsfc.nasa.gov/linux/misc/irq-conflict.html</A">http://cesdis.gsfc.nasa.gov/linux/misc/irq-conflict.html</A</A>>> has this to say: ". . . If the card is reporting a valid IRQ, but that IRQ is being used by another device you have an interrupt conflict. The easiest and generally best solution is to put the conflicting device on another IRQ line. This can only be done through the PCI BIOS setup. Unlike ISA cards, PCI cards have no way of setting their own IRQ. That is done at boot time by the PCI BIOS, and the BIOS reports its selection. . . ." Anyone solved something like this before? I am running SuSE 5.2, kernel 2.0.33. Bill Parker, <bparker@dc.net> - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archiv at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>