Bret Yen-Ting Lin schrieb:
Hi Jan
Its me again, Ok. In that case I tried setting up my other station to act as a client.But it requires a 3c59x driver. I am not sure if the 3c59x-rt driver is not doing its job or my hardware is faulty, error shows when I rtifconfig, which then the system goes into a crash situation. I wrote few printk lines inside the RTCap.c file and found that after running the signal handling twice.. it goes to halt. howcome ? Has it got to do with the bus error ?
The printk is as shown below
RTnet: initialising real-time networking RTnet: stack-mgr started PCI Found IRQ 10 for deice 00:0f.0 3c59x for RTnet: Donald Becker and others www..... 00:0f.0:3com PCI 3c900 Boomerang 10Mbps Combo at 0xfc40 vers LK1.1.16 RTnet:registered rteth0 RTcap: real-time capturing interface rteth0:Host error, FIFO diagnostic register 2000 rteth0:PCI bus error, bus status 00a00029 RTnet:unknown layer-3 protocol <system goes to halt>
That has probably something to do with your hardware/driver problem. The 3c59x-rt is not officially supported by us as it has some real-time quirks, however, there are some users around who are successfully running it in (uncritical) real-time projects.
... My other computer that runs as a Master uses the epro100 driver and never showed any error. However it seems to be doing a inifinite loop printing out the "unknown layer-3 protocol" line
You are no longer able to use some console of that system? What is the rate of that message, one per second or much more? Is it regular?
.. What is RTcap suppose to show when up and working ? Is there any possible ways in checking the kind of packages receiving for the Master computer (thats is working - only waiting for client i suppose ? ).
RTcap is just a service layer which creates a read-only linux network device to be used with standard sniffers like tcpdump or Ethereal.
Currently I can only reboot the computer when it goes into this infinite loop. Is there any chance I can break out of the function or what it is doing ?
I am really running out of idea in how to fix the problem. What do you think I should do ?
Did you already verified with some RTAI example if that part is running without problems?
If yes: on the master, you could try to step into the loading process of RTnet. This would to insert first only rtnet.o and loopback-rt.o, configure your loopback device (rtifconfig rtlo up 127.0.0.1) and run e.g. insmod examples/frag-ip/frag-ip.o. This should now transmit and receive some data locally and check if at least the core is ok. Then you may proceed with loading a Ethernet driver and doing this test against some remote node - still without RTmac or RTcfg. If this works, you may have to dig deeper into what the rtnet script does and do this manually to see where it stops.
On the client, you have to resolve this hardware issue first (take some other card e.g.).
Jan
------------------------------------------------------- This SF.Net email is sponsored by: SourceForge.net Broadband Sign-up now for SourceForge Broadband and get the fastest 6.0/768 connection for only $19.95/mo for the first 3 months! http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click _______________________________________________ RTnet-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/rtnet-users
