Speedo has a auto-negotiation bug.Pull out the cable and put it back.It
should work fine.Alternately you can turn off the hub/switch also.If you
don’t need multicasting you can use the later version of speedo.
Speedo has a auto-negotiation bug.Pull out the cable and put it back.It
should work fine.Alternately you can turn off the hub/switch also.If you
don’t need multicasting you can use the later version of speedo.
Yes, the bug is present in 6.1 AND 6.2 (as far as I can tell with my
experience over here is that the 6.2 speedo driver is more broken or
perform worst than the 6.1 version). Bummer.
Speedo has a auto-negotiation bug.Pull out the cable and put it back.It
should work fine.Alternately you can turn off the hub/switch also.If you
don’t need multicasting you can use the later version of speedo.
Do you mean that the card is still shown as half-duplex? It certainly worked
for me.But since i had to work with Multicast i could not use both the
versions of the Driver(I use ns83815) .But still one of the Speedo in my
system which does not require multicast uses the new driver.The trick is to
wait for few seconds(In the order of 5 to 6) before putting the cable back
into the nic.Also check your /etc/system/enum/devices/net file and to see if
the options are proper.
None of the suggestions that you recommended worked. But I appreciate
them. Thanks.
For any one that may be have a comment or suggestion:
rtp6.1A and rtp6.2-NC: speedo driver does not operate at full duplex.
rtp6.1A and rtp6.2-NC: pcnet driver does not accept a telnet or ftp
connection to it when operating in an embedded system, TCP is not
reliable, and UDP drops packages periodically every 30 seconds or so.
Still investigating whether the latest behavior is a function of timing
or buffering.
I wonder if any one else has any comments on these?
To QSSL:
Would it be possible to obtain a copy of your latest speedo and pcnet
drivers for both rtp6.1A and rtp6.2? If it matters, I have to say that
we do have a developers seat for rtp6.1, and the news group is the only
means that I have to interact with QSSL.
To QSSL and everyone:
I am suggesting to my company to buy a second developer seat for the rtp
PE. Is the speedo and the pcnet driver broken on the released PE? I
wonder if any one with the Momentics PE could verify this? I will
appreciate it. Thanks.
Regards…
Miguel.
Sreekanth wrote:
Speedo has a auto-negotiation bug.Pull out the cable and put it back.It
should work fine.Alternately you can turn off the hub/switch also.If you
don’t need multicasting you can use the later version of speedo.
None of the suggestions that you recommended worked. But I appreciate
them. Thanks.
For any one that may be have a comment or suggestion:
rtp6.1A and rtp6.2-NC: speedo driver does not operate at full duplex.
rtp6.1A and rtp6.2-NC: pcnet driver does not accept a telnet or ftp
connection to it when operating in an embedded system, TCP is not
reliable, and UDP drops packages periodically every 30 seconds or so.
Still investigating whether the latest behavior is a function of timing
or buffering.
I wonder if any one else has any comments on these?
To QSSL:
Would it be possible to obtain a copy of your latest speedo and pcnet
drivers for both rtp6.1A and rtp6.2? If it matters, I have to say that
we do have a developers seat for rtp6.1, and the news group is the only
means that I have to interact with QSSL.
To QSSL and everyone:
I am suggesting to my company to buy a second developer seat for the rtp
PE. Is the speedo and the pcnet driver broken on the released PE? I
wonder if any one with the Momentics PE could verify this? I will
appreciate it. Thanks.
Regards…
Miguel.
Sreekanth wrote:
Speedo has a auto-negotiation bug.Pull out the cable and put it back.It
should work fine.Alternately you can turn off the hub/switch also.If you
don’t need multicasting you can use the later version of speedo.
FYI, we have the same problem with ns83815 in that it reports
half-duplex, even though it’s actually running in full duplex mode.
We’ve looked through the driver but this part of the functionality is
buried in a separate PHY library that we don’t have source for. Anyway,
even though the report is incorrect, the system appears to be working
properly, so we’ve been ignoring it for now. BTW, it’s the same in 6.1
and 6.2.
FYI, we have the same problem with ns83815 in that it reports
half-duplex, even though it’s actually running in full duplex mode.
We’ve looked through the driver but this part of the functionality is
buried in a separate PHY library that we don’t have source for. Anyway,
even though the report is incorrect, the system appears to be working
properly, so we’ve been ignoring it for now. BTW, it’s the same in 6.1
and 6.2.