tetsuo55 wrote:Deathlike2 wrote:tetsuo55 wrote:As you can see in your screenshot basically ALL your hardware is sharing IRQ9.
You are starting to trigger massive franpa alerts, and that's not a good sign. Nowhere in the picture is what you are suggesting. Sure there is IRQ sharing, but certainly not with IRQ9. I've seen systems that do this but this is not one of them.
In the screenshot you see a Microsoft acpi-compliant system on IRQ9
This bsaically works as a load balancer that adds IRQ 16-23 at the cost of losing IRQ9
Most devices don't care but soundcards and network cards are more picky
See here:
http://support.microsoft.com/?kbid=252420
Ummm, no.
If the devices are listed as on the same IRQ, they're on the same IRQ.
Otherwise, it's no different than the old AT hack(you know, it's why you can't use IRQ2?). Cascading interrupt handlers is nothing new, and there's nothing wrong with it. Otherwise, IRQs 8-15 would have had severe performance issues, making them TOTALLY unsuitable for hard drive controllers and math coprocessors.
And ACPI is Advanced Configuration and Power Interface.
That's the interrupt for any power management features. It's got nothing to do with shared interrupts or cascaded interrupt controllers.
It's also a hard-coded IRQ. ACPI ALWAYS uses IRQ9, and it doesn't share.
ALL POWER MANAGEMENT FEATURES USE IRQ9, AND NOTHING ELSE CAN USE IRQ9.
You might notice that it's on the ISA bus. That should ring a lot of bells right there.
APIC is the new interrupt controller standard. And it's a flat standard. There are no cascaded interrupt controllers on a modern system.
You're right that he would probably need to reformat, but he does seem to have enough free IRQ's for most of his devices. As long as video, sound and nic are on a unique IRQ he should be fine
U R RONG!