Hi Fabian,
> 
> 1) If you have more than one PCI slot, try switching the cards. The IRQ lines 
> are on the mainboard and can't be changed. SO switching cards in the slots 
> can help.
This is what I eventually did to solve the problem. I am not really 
happy with the solution because I am afraid that it may not save my skin 
in the future.



> 
> 2) In your BIOS there are usually options to fiddle around with IRQ resource 
> management. Try those. (except in most laptops) 
I did but these seem to have no effect. IRQ 10 is what my PC likes and 
no matter what I do in the BIOS IRQ10 is what it assigns to the NICS.


> 
> 3) This one worked for me:
> In most modern Boards/CPUs there is a new Chips for IRQ handling. Back in the 
> XT Days there were 16 IRQ lines going into a PIC (programmable interrupt 
> controller). These days those PICs are replaced by a so-called APIC 
> (advanced...). If you every played around with Multiprocessor setups or 
> dualcores you might have heard of that.
I had read about this and know that it increases the number of IRQlines. 
It would have been my next step but I did not know how to apply it.

> 
> Anyway. Compile your kernel to enable APIC and especially APIC-IO support.
> (make menuconfig --> processor type&features --> local APIC for uniprocessor 
> --> APIC-IO support)
Thanks, this is the info I was lacking.


> I hope you have an APIC chip on your board.
How can I check before going to the effort of recompiling the kernel?

Would anyone know why the APIC is not set on as default in the kernel? 
Does it conflict if the board does NOT have an APIC?


Kind regards,

Roland.





> 
> back to work
> CU Fabian


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
RTnet-users mailing list
RTnet-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rtnet-users

Reply via email to