Hey,
>When rtmac is loaded, RT payload frames are still standard (if using
>UDP/IP e.g.), just additional meta frames pop up, and some of them may
>contain tunneled non-RT frames from Linux. But that's only for
>clarification.
Thanks for the info... reading rtnet/Documentation/README.rtmac I noticed
that one can just leave out the RTmac module and send regular ethernet
frames. That is exactly what I was looking for :)
I can't tell what was doing wrong in my way of loading the rt_e1000.ko
module, but somehow I managed to not get this error anymore. The only minor
issue is the following... I have a (non real-time) ethernet card (tg3) that
I use to connect from a remote computer, a quad port intel (rt_e1000) card
and an additional single port ethernet card (rt_e1000). i.e. ifconfig lists
eth0, rteth0, rteth1, rteht2, rteth3, and rteth4, which is great. However,
in order to get all interfaces up I have to us the command
# insmod /usr/local/rtnet/modules/rt_e1000.ko
InterruptThrottleRate=0,0,0,0,0,0 RxIntDelay=200,200,200,200,200,200
RxAbsIntDelay=750,750,750,750,750,750 XsumRX=1,1,1,1,1,1
TxIntDelay=0,0,0,0,0,0 TxAbsIntDelay=0,0,0,0,0,0 cards=1,1,1,1,1,1
which has 6 instead of just 5 values for each parameter. When I only provide
5 then the last ethernet card (rteth4) does not come up properly. I guess
this has to do with cards=1,1,1,1,1,1, does it ?
about the last issue with the configure. After reinstalling RTnet I did a
make menuconfig and I was able to disable the RTmac.
Besides that, I am finally communicating with a total 38 controller cards on
5 networks in realtime at 500Hz. That is really cool !!
THANKS again,
Peter
On Wed, Sep 9, 2009 at 6:33 AM, Jan Kiszka <jan.kis...@web.de> wrote:
> Peter Pastor wrote:
> > Hey again,
> >
> > I figured out that one can actually use RTnet without changing the
> ethernet
> > frame by simply no loading rtmac module. From what I have read in
> > README.rtmac, as long as rtmac.ko is not loaded the ethernet frame should
> > not change.
>
> When rtmac is loaded, RT payload frames are still standard (if using
> UDP/IP e.g.), just additional meta frames pop up, and some of them may
> contain tunneled non-RT frames from Linux. But that's only for
> clarification.
>
> >
> > However, after compiling, installing and loading the modules rtnet,
> > rtpacket, rtipv4, and rt_e1000 I got the problem that dmesg showed
> >
> > [ 146.489750]
> > [ 146.489751] *** RTnet 0.9.11 - built on Sep 1 2009 00:10:51 ***
> > [ 146.489752]
> > [ 146.489755] RTnet: initialising real-time networking
> > [ 163.476567] RTcfg: init real-time configuration distribution protocol
> > [ 175.701815] Intel(R) PRO/1000 Network Driver - version 7.1.9
> > [ 175.701819] Copyright (c) 1999-2006 Intel Corporation.
> > [ 175.701864] rt_e1000 0000:06:04.0: PCI INT A -> GSI 26 (level, low) ->
> > IRQ 26
> > [ 175.701899] rt_e1000: probe of 0000:06:04.0 failed with error -5
> > [ 175.701911] rt_e1000 0000:06:04.1: PCI INT B -> GSI 27 (level, low) ->
> > IRQ 27
> > [ 175.701928] rt_e1000: probe of 0000:06:04.1 failed with error -5
> > [ 175.701940] rt_e1000 0000:06:06.0: PCI INT A -> GSI 28 (level, low) ->
> > IRQ 28
> > [ 175.701955] rt_e1000: probe of 0000:06:06.0 failed with error -5
> > [ 175.701967] rt_e1000 0000:06:06.1: PCI INT B -> GSI 29 (level, low) ->
> > IRQ 29
> > [ 175.701981] rt_e1000: probe of 0000:06:06.1 failed with error -5
> >
> > (I use a intel pro/1000 MT Quad Port Server Adapter)
>
> Could you try the experimental e1000 driver as well?
>
> >
> > I guess this is the problem why rtifconfig rteth0 up 192.168.2.1 fails
> with
> > "ioctl: No such device".
>
> Exactly.
>
> >
> > Also, I noticed that the "./confgure" option -enable-rtmac=no had no
> impact
> > since it still was build. What am I doing wrong here ?
>
> Did you use 'configure' or 'make *config' to configure the RTnet build?
> Disable it via the same mechanism - or simply do not load rtmac.ko when
> starting RTnet.
>
> Jan
>
>
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
RTnet-users mailing list
RTnet-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rtnet-users
