Floppy,
Did you remove the module r8169 (rmmod r8169) before loading the module
rt_8169? Otherwise the NIC can't be claimed by rtnet driver.
Att,
Renato M Monaro
On Thu, May 10, 2012 at 6:26 AM, florian rieger <flo...@linuxmail.org>wrote:
> Hi,
>
> I'm having some troubles with the recognition of my NIC, I'm running
>
> Linux Kernel: 2.6.38.8
> Xenomai: 2.6.0
> RTnet: 0.9.12 (git clone from may 07, 2012)
> NIC: 2x Realtek RTL-8110SC/8169SC Gigabit Ethernet (rev 10)
>
> The network device drivers are configured to be build as modules, when I'm
> loading them with
>
> $ modprobe r8169.ko
>
> everything works..
>
> [ 981.679298] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
> [ 981.679451] r8169 0000:00:09.0: (unregistered net_device): no PCI
> Express capability
> [ 981.680679] r8169 0000:00:09.0: eth0: RTL8169sc/8110sc at 0xf8154000,
> 00:30:18:b0:c3:67, XID 18000000 IRQ 5
> [ 981.680788] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
> [ 981.680927] r8169 0000:00:0b.0: (unregistered net_device): no PCI
> Express capability
> [ 981.682328] r8169 0000:00:0b.0: eth1: RTL8169sc/8110sc at 0xf8158000,
> 00:30:18:b0:c3:68, XID 18000000 IRQ 10
>
> I see an eth0 device, can ping and so on. After unloading the r8169 driver
> again I start up rtnet manually using the rt_r8169 driver, I do:
>
> $ mknod /dev/rtnet c 10 240
> $ insmod rtnet.ko
> $ insmod rtipv4
> $ insmod rtpacket
> $ insmod rt_loopback
> $ insmod rt_r8169.ko
>
> everything seems to work fine:
>
> [ 1072.844172] *** RTnet 0.9.12 - built on May 10 2012 10:07:11 ***
> [ 1072.844178]
> [ 1072.844657] RTnet: initialising real-time networking
> [ 1082.954890] initializing loopback...
> [ 1082.955354] RTnet: registered rtlo
> [ 1090.474296] Initializing rt_r8169 driver
>
> Then I'm trying to set up the network devices, `rtifconfig rtlo up
> 127.0.0.1` works as I can see an entry in /proc/rtnet/devices and I'm able
> to rtping and everything but `rtifconfig rteth0 up` fails with the message
> "ioctl: No such device". When I run `rtifconfig -a` just rtlo is listed..
> dmesg don't has any news for me either so I started to compare standard and
> real-time driver as suggested in the rtnet-users mailing list and found out
> that my rt_r8169.c is Version 2.2-04 <2005/08/22>. I guess it just requires
> some little fixes/updates in the rt_r8169 driver to recognize my card, only
> problem that I'm not that familiar with linux driver programming so any
> hint or suggestion where to focus would be very appreciated!
>
> Best regards,
>
> Floppy
>
>
> ------------------------------------------------------------------------------
> 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
>
--
Renato Machado Monaro
------------------------------------------------------------------------------
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
