Hi everybody, I have one Intel PC, that uses (on one of the few PCI slots) the same IRQ for the onboard network device and an additional PCI (eepro100) network device. I am using the latest rtai 3.3, kernel 2.6.15.4 and the latest SVN snapshot from rtnet. When starting the rtnet and configuring the driver (rtifconfig rteth up), the onboard net is "dead", however working locally on the PC still works fine. When rtnet is stopped (rtifconfig rteth down) everything is fine again.
This is probably caused by the same IRQ. However, I thought I read a while ago, that this shared interrupt issue should be solved?!? When I plugin the PCI NIC to another PCI slot it works fine. However, as new PCs have only very few PCI slots this not really a long-term option... Can the rt-eepro100 driver or the RTDM framework somehow be "tuned" to work with the shared interrupts? Thanks for any answer on that! Regards Mathias -- Mathias Koehrer [EMAIL PROTECTED] Viel oder wenig? Schnell oder langsam? Unbegrenzt surfen + telefonieren ohne Zeit- und Volumenbegrenzung? DAS TOP ANGEBOT JETZT bei Arcor: günstig und schnell mit DSL - das All-Inclusive-Paket für clevere Doppel-Sparer, nur 44,85 inkl. DSL- und ISDN-Grundgebühr! http://www.arcor.de/rd/emf-dsl-2 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ RTnet-users mailing list RTnet-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rtnet-users
