Jan Kiszka wrote: >> I had a look at rt_8139too.c and found the parameter description: >> MODULE_PARM_DESC(media, "8139too: Bits 4+9: force full duplex, bit 5: >> 100Mbps"); >> But I am not quite shure what to do with that... > > Try "modprobe rt_8139too media=0". If I parse the code correctly ATM, > that should make it switch to 10Mbps/half-duplex. > > Hmm, something is fishy here anyway. Looks like we are currently locked > to FD/100Mps due to "media" being initialised with -1. Ah, that's due to > Fabian's changes for media selection: > > http://rtnet.svn.sourceforge.net/viewvc/rtnet/trunk/rtnet/drivers/rt_8139too.c?r1=983&r2=1014 > > Fabian, can we choose a different default for "media" to get > auto-negotiation working? Otherwise, more documentation work would be > required here to deal with non-100Mps and non-FD cases more user-friendly.
Hey, sorry I'm not quite following the ML at the moment, so sorry for the delay. Yes something needs to be done here to make it more comfortable. The actual auto-negotiation is commented out as far as I remember. I only needed my usecase as a module parameter so I didn't care about also getting the auto-sensing to work. I don't have time to do that right now, but I'll need to get back to RTnet soon I guess. We have a new board with rtl8139DL chipsets and Rtnet does not yet seem to like them... CU Fabian Koch TabascoEye ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ RTnet-users mailing list RTnet-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rtnet-users
