You need to do this with the link to the USRP2 on and report that. Link
detected should say "yes".
Matt
Chukhman, Ilya A. wrote:
The Auto-negotiation is set to auto for eth0, which I believe is the
correct setting. The entire output of ethtool is below.
Ilya
Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Advertised auto-negotiation: Yes
Speed: Unknown! (65535)
Duplex: Unknown! (255)
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: g
Wake-on: d
Current message level: 0x000000ff (255)
Link detected: no
-----Original Message-----
From: Matt Ettus [mailto:[email protected]]
Sent: Monday, September 21, 2009 12:50 AM
To: Chukhman, Ilya A.
Cc: [email protected]
Subject: Re: [Discuss-gnuradio] USRP2 dies
Chukhman, Ilya A. wrote:
> Hello,
>
> My USRP2 dies during transmission when using interpolation rates less
> than 24. When that happens, the USRP2 does not respond to any commands,
> including find_usrps, until it is rebooted. Looking at previous threads
> on this list, I noticed that other people experienced similar problems,
> but it wasn’t apparent if they found solutions to them.
>
> I have the USRP2 directly connected to a Dell laptop that has a Broadcom
> NetXtreme BCM5755M chipset. I have enabled real-time scheduling in
> limits.conf and the _http://gnuradio.org/trac/wiki/USRP2GigEReports_
> indicates that my Ethernet chip is supported. What Ethernet
> flow-control settings do I need to set in Ubuntu 9.04 on my laptop?
Have you checked the flow control settings? What does ethtool report?
Matt
_______________________________________________
Discuss-gnuradio mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
