Yosef Meller wrote:
Muli Ben-Yehuda wrote:
On Sat, Jun 25, 2005 at 06:34:16PM +0300, Yosef Meller wrote:
I remmember that with (really) old hardware you needed to set the IRQ
using a jumper on a card, thus allowing to allocate the same IRQ to two
cards who can't handle it. That was back in the ISA days, though. Are
you saying that Linux knows how to handle such an issue?
Unlikely, as it's a problem with ISA devices, not any specific OS. Are
you saying that Windows interrupt collisions only happen with ISA
devices?
I'm not familiar withg all the ways you can screw up a windows install,
I just know this one :-)
I don't think it's an OS issue, the fact is that you can see IRQ
allocations when you start a machine even if you don't have an OS.
there's a table of them appearing for a split second after the bios
checks the memory. If you press the pause button at the right time you
can examine them.
Now I'm not a big expert and not really sure what IRQ is exactly, but
since I found out an old network card of mine is coliding somehow (not
necesserily IRQ collision) with the new sound card, I was adviced (by
windows users) to check IRQ collisions. The advice was, given a
collision exist, to change some BIOS settings, anyway, nothing about the OS.
My question was simply if I can check collision after linux had finished
booting.
It doesn't really metter anymore (though it would be nice to know).
Regards
Aviv
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
