Evert Lammerts wrote: > Hi again, > >> Evert Lammerts wrote: >> >>> Hello, >>> >>> >>> This is my second message, I think my last didn't get through the >>> sourceforge servers. >> It made it now - three times. :) (don't know what happened at sf...) >> > > Sorry for the spam :) > > ... >>> >>> Any ideas? >>> >> IRQ conflict between the realtime NIC and some Linux-managed device? >> Check /proc/interrupts against what dmesg tells you when loading the >> RT-NIC driver. >> >> > > It seems you got it right there. We had four devices on IRQ 10, including > eth0 and 1, so three devices during rtnet start (shut down eth's, loaded > rt_nic). I disabled the two devices that might've caused the problem > (onboard sound card and USB) and now rtnet works fine. However, this is > not a very structural solution, and I have no experience in dealing with > IRQ's. Would some one know a better solution, one that makes sure we have > sound and can use USB?
Check the BIOS if you have a chance to move IRQs (typically not...). Is one of your NICs on a separate PCI / PC104+ card? If yes, switching slots / playing with jumpers etc. may help to nail it down to a different IRQ line. You "just" have to take care that RTnet NICs have exclusive IRQs, Linux is fine with sharing. Jan
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ RTnet-users mailing list RTnet-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rtnet-users
