Beyer Philipp wrote:
> Jan Kiszka wrote:
>> Beyer Philipp wrote:
>>   
>>> Jan Kiszka wrote:
>> What was different then?
>>
>>   
>>> The problem is, the best I got was to rtping the loopback and exchanging
>>> the MAC addresses at stage 1.
>>>     
>> Please report more details (precise description of your steps, output of
>> the stations, config files, etc.). And browse the archive of this list
>> for similar reports and possible solutions
>> (<your-favourite-search-engine> is your friend...).
>>
>>   
> OK more details: This is target2
> 
> kontron_xenomai:~# rtnet -v start
> Turning on verbose mode
> /usr/local/rtnet/sbin/rtifconfig rtlo up 127.0.0.1
> /usr/local/rtnet/sbin/rtcfg rteth1 server
> /usr/local/rtnet/sbin/rtifconfig rteth1 up 10.0.0.1
> /usr/local/rtnet/sbin/tdmacfg rteth1 master 5000
> /usr/local/rtnet/sbin/tdmacfg rteth1 slot 0 0
> /usr/local/rtnet/sbin/rtcfg rteth1 add 10.0.0.2 -stage1 -
> Waiting for all slaves.../usr/local/rtnet/sbin/rtcfg rteth1 wait
> 
> here it stops
> 
> Thats /var/log/messages
> 
> Sep  7 06:11:30 kontron_xenomai user.warn kernel:
> Sep  7 06:11:30 kontron_xenomai user.warn kernel: *** RTnet 0.9.4 -
> built on Aug 18 2006 12:57:33 ***
> Sep  7 06:11:30 kontron_xenomai user.warn kernel:
> Sep  7 06:11:30 kontron_xenomai user.warn kernel: RTnet: initialising
> real-time networking
> Sep  7 06:11:30 kontron_xenomai user.info kernel: Linux Tulip driver
> version 0.9.15-pre11-rt (May 11, 2002)
> Sep  7 06:11:30 kontron_xenomai user.info kernel: PCI: Found IRQ 10 for
> device 0000:00:09.0
> Sep  7 06:11:30 kontron_xenomai user.info kernel: PCI: Sharing IRQ 10
> with 0000:00:12.0
> Sep  7 06:11:30 kontron_xenomai user.info kernel: tulip0: Transceiver
> selection forced to MII.
> Sep  7 06:11:30 kontron_xenomai user.info kernel: tulip0:  EEPROM
> default media type Autosense.
> Sep  7 06:11:30 kontron_xenomai user.info kernel: tulip0:  Index #0 -
> Media MII (#11) described by a 21140 MII PHY (1) block.
> Sep  7 06:11:30 kontron_xenomai user.info kernel: tulip0:  Index #1 -
> Media 10baseT (#0) described by a 21140 non-MII (0) block.
> Sep  7 06:11:30 kontron_xenomai user.info kernel: tulip0:  Index #2 -
> Media 100baseTx (#3) described by a 21140 non-MII (0) block.
> Sep  7 06:11:30 kontron_xenomai user.info kernel: tulip0:  Index #3 -
> Media 10baseT-FDX (#4) described by a 21140 non-MII (0) block.
> Sep  7 06:11:30 kontron_xenomai user.info kernel: tulip0:  Index #4 -
> Media 100baseTx-FDX (#5) described by a 21140 non-MII (0) block.
> Sep  7 06:11:30 kontron_xenomai user.info kernel: tulip0:  MII
> transceiver #1 config 3100 status 7809 advertising 01e1.
> Sep  7 06:11:30 kontron_xenomai user.debug kernel: tulip0:  Advertising
> 03e0 on PHY 1, previously advertising 01e1.
> Sep  7 06:11:30 kontron_xenomai user.warn kernel: RTnet: registered rteth0
> Sep  7 06:11:30 kontron_xenomai user.info kernel: rteth0: Davicom
> DM9102/DM9102A rev 64 at 0x1000, 00:E0:4B:0E:3D:2A, IRQ 10.
> Sep  7 06:11:30 kontron_xenomai user.info kernel: PCI: Found IRQ 11 for
> device 0000:00:0a.0
> Sep  7 06:11:30 kontron_xenomai user.info kernel: tulip1: Transceiver
> selection forced to MII.
> Sep  7 06:11:30 kontron_xenomai user.info kernel: tulip1:  EEPROM
> default media type Autosense.
> Sep  7 06:11:30 kontron_xenomai user.info kernel: tulip1:  Index #0 -
> Media MII (#11) described by a 21140 MII PHY (1) block.
> Sep  7 06:11:30 kontron_xenomai user.info kernel: tulip1:  Index #1 -
> Media 10baseT (#0) described by a 21140 non-MII (0) block.
> Sep  7 06:11:30 kontron_xenomai user.info kernel: tulip1:  Index #2 -
> Media 100baseTx (#3) described by a 21140 non-MII (0) block.
> Sep  7 06:11:30 kontron_xenomai user.info kernel: tulip1:  Index #3 -
> Media 10baseT-FDX (#4) described by a 21140 non-MII (0) block.
> Sep  7 06:11:30 kontron_xenomai user.info kernel: tulip1:  Index #4 -
> Media 100baseTx-FDX (#5) described by a 21140 non-MII (0) block.
> Sep  7 06:11:30 kontron_xenomai user.info kernel: tulip1:  MII
> transceiver #1 config 3100 status 7809 advertising 01e1.
> Sep  7 06:11:30 kontron_xenomai user.debug kernel: tulip1:  Advertising
> 03e0 on PHY 1, previously advertising 01e1.
> Sep  7 06:11:30 kontron_xenomai user.warn kernel: RTnet: registered rteth1
> Sep  7 06:11:30 kontron_xenomai user.info kernel: rteth1: Davicom
> DM9102/DM9102A rev 64 at 0x1400, 00:E0:4B:0E:3D:2B, IRQ 11.
> Sep  7 06:11:30 kontron_xenomai user.warn kernel: initializing loopback...
> Sep  7 06:11:30 kontron_xenomai user.warn kernel: RTnet: registered rtlo
> Sep  7 06:11:30 kontron_xenomai user.warn kernel: RTcfg: init real-time
> configuration distribution protocol
> Sep  7 06:11:30 kontron_xenomai user.warn kernel: RTmac: init realtime
> media access control
> Sep  7 06:11:30 kontron_xenomai user.warn kernel: RTmac/TDMA: init time
> division multiple access control mechanism
> Sep  7 06:11:30 kontron_xenomai user.info kernel: rteth1: Using
> user-specified media MII.
> 
> In my opinion this looks ok
> 
> target1:
> 
> kontron_xenomai:~# rtnet -v start
> Turning on verbose mode
> /usr/local/rtnet/sbin/rtifconfig rtlo up 127.0.0.1
> /usr/local/rtnet/sbin/tdmacfg rteth1 slave
> /usr/local/rtnet/sbin/rtifconfig rteth1 up 10.0.0.2
> Stage 1: searching for master...$TDMACFG rteth1 slot 0 200;ifconfig
> vnic1 up $IPADDR $NETMASK_OPT
> /usr/local/rtnet/sbin/tdmacfg rteth1 slot 0 200

The execution of the last line indicates that the slave is receiving the
master's invitation. But it probably fails to send - for yet unknown
reasons.

> 
> and var/log/messages
> 
> Sep  8 02:02:36 kontron_xenomai user.warn kernel:
> Sep  8 02:02:36 kontron_xenomai user.warn kernel: *** RTnet 0.9.4 -
> built on Aug 18 2006 12:57:33 ***
> Sep  8 02:02:36 kontron_xenomai user.warn kernel:
> Sep  8 02:02:36 kontron_xenomai user.warn kernel: RTnet: initialising
> real-time networking
> Sep  8 02:02:36 kontron_xenomai user.info kernel: Linux Tulip driver
> version 0.9.15-pre11-rt (May 11, 2002)
> Sep  8 02:02:36 kontron_xenomai user.info kernel: PCI: Found IRQ 10 for
> device 0000:00:09.0
> Sep  8 02:02:36 kontron_xenomai user.info kernel: PCI: Sharing IRQ 10
> with 0000:00:12.0
> Sep  8 02:02:36 kontron_xenomai user.info kernel: tulip0: Transceiver
> selection forced to MII.
> Sep  8 02:02:36 kontron_xenomai user.info kernel: tulip0:  EEPROM
> default media type Autosense.
> Sep  8 02:02:36 kontron_xenomai user.info kernel: tulip0:  Index #0 -
> Media MII (#11) described by a 21140 MII PHY (1) block.
> Sep  8 02:02:36 kontron_xenomai user.info kernel: tulip0:  Index #1 -
> Media 10baseT (#0) described by a 21140 non-MII (0) block.
> Sep  8 02:02:36 kontron_xenomai user.info kernel: tulip0:  Index #2 -
> Media 100baseTx (#3) described by a 21140 non-MII (0) block.
> Sep  8 02:02:36 kontron_xenomai user.info kernel: tulip0:  Index #3 -
> Media 10baseT-FDX (#4) described by a 21140 non-MII (0) block.
> Sep  8 02:02:36 kontron_xenomai user.info kernel: tulip0:  Index #4 -
> Media 100baseTx-FDX (#5) described by a 21140 non-MII (0) block.
> Sep  8 02:02:36 kontron_xenomai user.info kernel: tulip0:  MII
> transceiver #1 config 3100 status 7809 advertising 01e1.
> Sep  8 02:02:36 kontron_xenomai user.debug kernel: tulip0:  Advertising
> 03e0 on PHY 1, previously advertising 01e1.
> Sep  8 02:02:36 kontron_xenomai user.warn kernel: RTnet: registered rteth0
> Sep  8 02:02:36 kontron_xenomai user.info kernel: rteth0: Davicom
> DM9102/DM9102A rev 64 at 0x1000, 00:E0:4B:0E:3D:28, IRQ 10.
> Sep  8 02:02:36 kontron_xenomai user.info kernel: PCI: Found IRQ 11 for
> device 0000:00:0a.0
> Sep  8 02:02:36 kontron_xenomai user.info kernel: tulip1: Transceiver
> selection forced to MII.
> Sep  8 02:02:36 kontron_xenomai user.info kernel: tulip1:  EEPROM
> default media type Autosense.
> Sep  8 02:02:36 kontron_xenomai user.info kernel: tulip1:  Index #0 -
> Media MII (#11) described by a 21140 MII PHY (1) block.
> Sep  8 02:02:36 kontron_xenomai user.info kernel: tulip1:  Index #1 -
> Media 10baseT (#0) described by a 21140 non-MII (0) block.
> Sep  8 02:02:36 kontron_xenomai user.info kernel: tulip1:  Index #2 -
> Media 100baseTx (#3) described by a 21140 non-MII (0) block.
> Sep  8 02:02:36 kontron_xenomai user.info kernel: tulip1:  Index #3 -
> Media 10baseT-FDX (#4) described by a 21140 non-MII (0) block.
> Sep  8 02:02:36 kontron_xenomai user.info kernel: tulip1:  Index #4 -
> Media 100baseTx-FDX (#5) described by a 21140 non-MII (0) block.
> Sep  8 02:02:36 kontron_xenomai user.info kernel: tulip1:  MII
> transceiver #1 config 3100 status 7809 advertising 01e1.
> Sep  8 02:02:36 kontron_xenomai user.debug kernel: tulip1:  Advertising
> 03e0 on PHY 1, previously advertising 01e1.
> Sep  8 02:02:36 kontron_xenomai user.warn kernel: RTnet: registered rteth1
> Sep  8 02:02:36 kontron_xenomai user.info kernel: rteth1: Davicom
> DM9102/DM9102A rev 64 at 0x1400, 00:E0:4B:0E:3D:29, IRQ 11.
> Sep  8 02:02:37 kontron_xenomai user.warn kernel: initializing loopback...
> Sep  8 02:02:37 kontron_xenomai user.warn kernel: RTnet: registered rtlo
> Sep  8 02:02:37 kontron_xenomai user.warn kernel: RTcfg: init real-time
> configuration distribution protocol
> Sep  8 02:02:37 kontron_xenomai user.warn kernel: RTmac: init realtime
> media access control
> Sep  8 02:02:37 kontron_xenomai user.warn kernel: RTmac/TDMA: init time
> division multiple access control mechanism
> Sep  8 02:02:37 kontron_xenomai user.info kernel: rteth1: Using
> user-specified media MII.
> 
> My rtnet differs from the original in the way, that i replaced all
> rteth0 with rteth1 and all vnic0 with vnic1 because I use one network
> card to boot via PXE. It a VIA RHINE statically in the kernel.
> 

That's something I do not understand yet. From the log above it seems
like your boxes have each at least two tulip compatible NICs. What does
the via-rhine have to do with it?

There is an IRQ conflict of the first detected NIC with some other
device (0000:00:12.0), so switching to the second NIC is recommended.
You can use the RT_DRIVER_OPTIONS for this:

        RT_DRIVER_OPTIONS="cards=0,1,0,0"

Patching should not be required as well (though I didn't see a
regression due to this in your logs).

But first I would suggest the simple, manual setup now (RTmac-less) as
described in the README. Also helps to get familiar with configuration
of RTnet.

Jan

Attachment: signature.asc
Description: OpenPGP digital signature

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
RTnet-users mailing list
RTnet-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rtnet-users

Reply via email to