some additional comments:
Jan,
I attached a zip file with some files. eth_trace1 is an ethereal capture file. By the way, when loading eepro100-rt.o it says 'Receiver lock-up woraround activated', but I saw that this code is not active. After running a while I can see the message 'rteth0: can't fill rx buffer (force 0)!'. May it be possible, that all problems are caused by this damned chip and a receiver lock-up?
In the eepro100-rt, there are a lot of mechanisms deactivated which normally handle overload situations (or the rx-bug). This is feasible as the driver is intendend to run in a dedicated network with limited load (due to control mechanisms like RTmac/TDMA).
In the non RT environment I'm using the open source driver (e100.o) from Intel without problems.
Our experience is that this driver is still not bug-free. Certain chip revisions of the 8255x do not work with the e100, while the "good old" eepro100 does.
Jan
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ RTnet-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/rtnet-users
