On Wed, Feb 14, 2018 at 12:15 PM, Jan Kiszka <jan.kis...@web.de> wrote:
> On 2018-02-14 07:42, Pintu Kumar wrote:
>> On Tue, Feb 13, 2018 at 11:56 PM, Greg Gallagher <g...@embeddedgreg.com> 
>> wrote:
>>> Did you get the output of lspci -knn as Jan suggested?
>>>
>>
>> Here, is the output of lspci:
>>
>> $ lspci -knn
>> 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC
>> [Natoma] [8086:1237] (rev 02)
>> 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA
>> [Natoma/Triton II] [8086:7000]
>> 00:01.1 IDE interface [0101]: Intel Corporation 82371AB/EB/MB PIIX4
>> IDE [8086:7111] (rev 01)
>>         Kernel driver in use: ata_piix
>>         Kernel modules: pata_acpi
>> 00:02.0 VGA compatible controller [0300]: InnoTek Systemberatung GmbH
>> VirtualBox Graphics Adapter [80ee:beef]
>>         Kernel driver in use: vboxvideo
>>         Kernel modules: vboxvideo
>> 00:03.0 Ethernet controller [0200]: Intel Corporation 82540EM Gigabit
>> Ethernet Controller [8086:100e] (rev 02)
>>         Subsystem: Intel Corporation PRO/1000 MT Desktop Adapter [8086:001e]
>>         Kernel driver in use: e1000
>>         Kernel modules: e1000, rt_e1000
>> 00:04.0 System peripheral [0880]: InnoTek Systemberatung GmbH
>> VirtualBox Guest Service [80ee:cafe]
>>         Kernel driver in use: vboxguest
>>         Kernel modules: vboxguest
>> 00:05.0 Multimedia audio controller [0401]: Intel Corporation 82801AA
>> AC'97 Audio Controller [8086:2415] (rev 01)
>>         Subsystem: Dell 82801AA AC'97 Audio Controller [1028:0177]
>>         Kernel driver in use: snd_intel8x0
>>         Kernel modules: snd_intel8x0
>> 00:06.0 USB controller [0c03]: Apple Inc. KeyLargo/Intrepid USB [106b:003f]
>>         Kernel driver in use: ohci-pci
>> 00:07.0 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI
>> [8086:7113] (rev 08)
>>         Kernel driver in use: piix4_smbus
>>         Kernel modules: i2c_piix4
>> 00:08.0 Ethernet controller [0200]: Intel Corporation 82540EM Gigabit
>> Ethernet Controller [8086:100e] (rev 02)
>>         Subsystem: Intel Corporation PRO/1000 MT Desktop Adapter [8086:001e]
>>         Kernel driver in use: e1000
>>         Kernel modules: e1000, rt_e1000
>
> Perfect. So, rt_e1000 is your driver. Now open /etc/rtnet.conf, read the
> comments in there, and adjust it to your system.
>

Ok thank you so much. I got a clue and something is working now. But
still not perfect.

I followed the following steps:
1) sudo ifconfig [eth0/eth1] down
2) Remove the existing ethernet driver (e1000) => modprobe -r e1000
3) Changed the rtnet.conf:
    RT_DRIVER="rt_e1000"
4) Blank ip address as per comments there => IPADDR=""
5) sudo /usr/xenomai/sbin/rtnet start
6) Got this:
    Waiting for all slaves...
7) Pressed ^C to stop

8) Now when I check : ifconfig, I got this:

$ ifconfig

rteth0    Link encap:Ethernet  HWaddr 08:00:27:52:ba:f1
          inet6 addr: fe80::a00:27ff:fe52:baf1/64 Scope:Link
          UP BROADCAST RUNNING  MTU:1500  Metric:1
          RX packets:1465 errors:0 dropped:1465 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:41332 (41.3 KB)  TX bytes:0 (0.0 B)

rteth0-mac Link encap:Ethernet  HWaddr 08:00:27:52:ba:f1
          inet6 addr: fe80::a00:27ff:fe52:baf1/64 Scope:Link
          UP BROADCAST RUNNING  MTU:1500  Metric:1
          RX packets:1465 errors:0 dropped:7 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:41332 (41.3 KB)  TX bytes:0 (0.0 B)

rtlo      Link encap:Ethernet  HWaddr 00:00:00:00:00:00
          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

vnic0     Link encap:Ethernet  HWaddr 08:00:27:52:ba:f1
          inet6 addr: fe80::a00:27ff:fe52:baf1/64 Scope:Link
          UP BROADCAST RUNNING  MTU:1496  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:578 (578.0 B)


$ sudo /usr/xenomai/sbin/rtifconfig
rteth0    Medium: Ethernet  Hardware address: 08:00:27:52:BA:F1
          UP BROADCAST RUNNING  MTU: 1500

rtlo      Medium: Local Loopback
          IP address: 127.0.0.1
          UP LOOPBACK RUNNING  MTU: 1500


----------------------------------------------------------------------------
So, I still have the following queries:
1) Why only rteth0 is up, and not eth1 (earlier I have both eth0 and eth1) ?

2) Why IP address is not shown under rteth0 ?
     Earlier, the network was associated with :
           eth0 => inet addr:10.0.2.15
           eth1 => inet addr:192.168.56.101

---------------------------------------------------------------------------

These are the kernel logs during rtnet installation:

               *** RTnet for Xenomai v3.0.6 ***

[84221.150295] RTnet: initialising real-time networking
[84221.202520] Intel(R) PRO/1000 Network Driver - version 7.1.9
[84221.202523] Copyright (c) 1999-2006 Intel Corporation.
[84221.526522] e1000: 0000:00:03.0: e1000_probe: (PCI:33MHz:32-bit)
[84221.526525] 08:
[84221.526526] 00:
[84221.526528] 27:
[84221.526529] 52:
[84221.526531] ba:
[84221.526533] f1
[84221.575234] RTnet: registered rteth0
[84221.575237] e1000: rteth0: e1000_probe: Intel(R) PRO/1000 Network Connection
[84221.900806] e1000: 0000:00:08.0: e1000_probe: (PCI:33MHz:32-bit)
[84221.900810] 08:
[84221.900812] 00:
[84221.900814] 27:
[84221.900816] 19:
[84221.900818] 5b:
[84221.900819] dc
[84221.946479] RTnet: registered rteth1
[84221.946482] e1000: rteth1: e1000_probe: Intel(R) PRO/1000 Network Connection
[84221.976448] initializing loopback...
[84221.976458] RTnet: registered rtlo
[84221.982513] RTcap: real-time capturing interface
[84222.039892] ModemManager[10059]: segfault at 0 ip 0806f964 sp
bfb7bd80 error 4 in ModemManager[8048000+121000]
[84222.089678] RTcfg: init real-time configuration distribution protocol
[84222.149775] RTmac: init realtime media access control
[84222.177704] RTmac/TDMA: init time division multiple access control mechanism
[84222.179821] RTcfg: rtcfg_do_main_event() rtdev=1,
event=RTCFG_CMD_SERVER, state=RTCFG_MAIN_OFF
[84222.179824] RTcfg: next main state=RTCFG_MAIN_SERVER_RUNNING
[84224.194058] e1000: rteth0: e1000_watchdog: NIC Link is Up 1000 Mbps
Full Duplex
[84225.422825] ModemManager[10435]: segfault at 0 ip 0806f964 sp
bfb85f40 error 4 in ModemManager[8048000+121000]
[84225.434788] RTcfg: rtcfg_do_main_event() rtdev=1,
event=RTCFG_CMD_ADD, state=RTCFG_MAIN_SERVER_RUNNING
[84225.435376] RTcfg: rtcfg_do_main_event() rtdev=1,
event=RTCFG_CMD_ADD, state=RTCFG_MAIN_SERVER_RUNNING
[84225.435939] RTcfg: rtcfg_do_main_event() rtdev=1,
event=RTCFG_CMD_ADD, state=RTCFG_MAIN_SERVER_RUNNING
[84225.438018] RTcfg: rtcfg_do_main_event() rtdev=1,
event=RTCFG_CMD_WAIT, state=RTCFG_MAIN_SERVER_RUNNING
[84226.179858] RTcfg: error -11 while sending stage 1 frame
[84226.179870] RTcfg: error -11 while sending stage 1 frame
[84226.179872] RTcfg: error -11 while sending stage 1 frame
[84227.179861] RTcfg: error -11 while sending stage 1 frame
[84227.179877] RTcfg: error -11 while sending stage 1 frame
[84227.179879] RTcfg: error -11 while sending stage 1 frame
[84228.180889] RTcfg: error -11 while sending stage 1 frame
.......
.......

These error is flowing continuously in the kernel logs. What does this
indicates ?



Thanks,
Pintu


> Jan
>

_______________________________________________
Xenomai mailing list
Xenomai@xenomai.org
https://xenomai.org/mailman/listinfo/xenomai

Reply via email to