IRQ Assigning

Nov 26, 2005
15,194
403
126
Hello. After many scenarios, my best assumption is that my problem resides in my IRQ assigning. I have minimal options when it comes to manually assigning them. Also,I just received a single channel control-test controller card (29320ALP) and it too receives IRQ 11

MB = Asus A8R32 MVP Deluxe
SCSI Card(s) = Adaptec 39320 - R & Adaptec 29320ALP

Plug N Play O/S = No
IRQ Assign Options = 'To PCI' & 'Reserved' (if I reserve IRQ 11, the bios will just assign both the SATA & SCSI to a different IRQ with the same number e.g. IRQ 10 )
Allocate IRQ to PCI VGA = No (enabled, this assigned VGA to IRQ 11) I searched the boot error and came up with this: http://www.xtremesystems.org/f...howthread.php?t=116801 ...but even with the VGA card not on IRQ11 or other, Onboard SATA Raid doesn't work. I tested to see if Onboard Raid works with an old IDE drive and the Onboard SATA RAID bios showed up otherwise with the SCSI it just says the "No enough Space..."

With the SCSI Controller Card and the Onboard SATA Raid controller both receiving the same IRQ number no matter if specified IRQ is reserved or not, where does this point to? Asus or Adaptec?

sorry if this is a little garbled, this is my second time writing this

Thanks,

529th
 

Peter

Elite Member
Oct 15, 1999
9,640
1
0
We've just had that:

http://forums.anandtech.com/me...=2151130&enterthread=y

In short, the belief that shared interrupts constitutes a "conflict" is as widespread as it is wrong. You're barking up the wrong tree.

What you have there is, you've run out of space for 3rd party boot ROMs - just what the error message told you, didn't it? What brought you to "IRQ conflict" from there? Internet mythology? ;)

Now on to fixing the actual problem: You need to make up your mind which one you want to boot from, and disable bootROM support in the other device. Note that the device whose boot support you disable will still be usable by OS drivers, just no booting from it.