On 2012-06-07 10:01, Anisha Kaul wrote: > In continuation with the previous mail I have also noticed the following: > ` > linux-y3pi:~ # ethtool -i eth0 > driver: r8169 > version: 2.3LK-NAPI > firmware-version: > bus-info: 0000:01:00.0 > ` > > So, this means that my driver's name is "r8169", and not "8139too" as > mentioned in this page: > http://www.xenomai.org/index.php/RTnet:Installation_%26_Testing > ? > > Now, `rmmod r8169` works. > > That webpage also says the following: > /"The RT_DRIVER should be the realtime equivalent of the module you > removed nl. rt_8139too."/
8169 != 8139. The latter is a very old 100-MBit NIC, the former a 1-GBit adapter. > > In my case since it seems that the driver is `r8169`, which > corresponding real time driver should be used out of the following? > > linux-y3pi:/usr/local/rtnet/modules # ls > rt_8139too.ko rtcfg.ko rt_eepro100.ko rt_loopback.ko rtnet.ko > rtudp.ko > rtcap.ko rt_e1000.ko rtipv4.ko rtmac.ko rtpacket.ko > tdma.ko You need to enable the experimental 8169 in the RTnet configuration. But this thing may expose some known problems, be warned. Jan
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________ RTnet-users mailing list RTnet-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rtnet-users
