Re: PCI riser cards and PCI irq routing, etc
From: Krzysztof Halasa
Date: Wed Feb 21 2007 - 14:36:31 EST
Udo van den Heuvel <udovdh@xxxxxxxxx> writes:
> But the IRQ for the DVB-T card doesn't work.
That's because the card drives incorrect INT line. The system (BIOS,
Linux) thinks the card would drive INT_D (as seen at the MB PCI slot)
and and card drives (its INT_A) INT_B.
> I would need to test the DVB-T card alone to be sure it has working IRQ.
> If so, what would be the conclusion?
I'd expect it to work. Anyway, you'd need to change the mapping.
Of course, you have to select device # = 19 (0x13).
> What IRQ rerouting would I need to try? 1 of 3 choices?
> Or one best bet?
You can test if it works first by connecting lines INT B and INT D
on the motherboard (or on the device 0x14 slot). That's pins B7 and B8
(you may want to google PCI slot pinout, "B" is the "component side").
I think a small piece of conductive film (aluminum or so) placed
carefully with the card would do. Make sure not to damage the
connector pins and not to short any additional connectors.
It can a) work, b) not work, c) give you "interrupt stuck -> disabled"
messages (and perhaps make the system unusable until the film is
I'd verify my speculation WRT the riser card is correct and the lines
are indeed connected as follows:
(device 0x13=19) ABCD -> BCDA (MB slot = device 0x14=20).
That means pin A6 on device 0x13 connected to B7 on device 0x14 and on
edge connector going to MB slot, pin B7 on 0x13 to A7 on 0x14/MB,
pin A7 on 0x13 to B8 on 0x14/MB, pin B8 on 0x13 to pin A6 on 0x14/MB.
If that is the case and the alu film works, then (assuming you only
need a single IRQ for 0x13) you have to cut connection between A6 on
0x13 and B7 on 0x14 (B7 on 0x14 and B7 on edge connector should stay),
then connect that A6 on 0x13 to B8 on 0x14/MB.
I think the modification should rather be done by someone who knows
how to solder electronics.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/