Re: [Discuss-gnuradio] can not connect USRP2 with UHD drivers

[Abhijeet Mate]

Hi Ron,

Thank you very much for your help. when i try to do ethtool eth0

Supported ports: [ TP MII ]

Supported link modes:   10baseT/Half 10baseT/Full 

                       100baseT/Half 100baseT/Full 

Supports auto-negotiation: Yes

Advertised link modes:  10baseT/Half 10baseT/Full 

                       100baseT/Half 100baseT/Full 

Advertised pause frame use: No

Advertised auto-negotiation: Yes

Link partner advertised link modes:  10baseT/Half 10baseT/Full 

                                    100baseT/Half 100baseT/Full 

Link partner advertised pause frame use: No

Link partner advertised auto-negotiation: Yes

Speed: 100Mb/s

Duplex: Full

Port: MII

PHYAD: 0

Transceiver: internal

Auto-negotiation: on

Supports Wake-on: pumbg

Wake-on: g

Current message level: 0x00000033 (51)

Link detected: yes

this is the output i get i have

 Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)

Ethernet driver.

how can i change it to gigabit. i tried it with

 sudo ethtool -s eth0 speed 1000 duplex full autoneg on

but it is not working.

Thanks,

Abhijeet. 

On Wed, Apr 6, 2011 at 11:31 PM, Ron Hall <address@hidden> wrote:

Ab:

Your driver setup may be a factor. The 'lsmod' command will list what drivers are loaded.  Be sure the Ethernet driver you have is Gig capable.  For my system it is an e1000e for Intel. Reloading the driver may help "clean up" the connection. Run modprobe -r driver name followed by modprobe driver name. Also, ensure that the Ethernet connection is configured for Gig. The command ethtool eth0 (provide correct designator for you system) should list the current configuration for you system. Finally, be sure that the ifconfig for the eth0 (provide correct designator for you system) is set up to communicate on the 192.168.10.255 network...192.168.10.1 is recommended as the host ip address. If this is all sound, consider running Wireshark to monitor the connection activity between the host and USRP. You may see an ARP when the USRP comes on line and you should see the communication between the host and the USRP. Then there is always the host and USRP reboot.

Walking through these steps has helped re-establish connectivity for my system when No UHD devices found or Discovered device ignored is returned by the uhd_find_devices utility.

Ron H

---

Date: Wed, 6 Apr 2011 20:01:45 -0400
From: address@hidden
To: address@hidden
Subject: [Discuss-gnuradio] can not connect USRP2 with UHD drivers

hello,

 I can't connect to the USRP2 using the latest version of the UHD driver from the git repository. I am using Ubuntu 10.04 and I have followed the instruction at http://www.ruby-forum.com/topic/213259 but still when I connect usrp2 to computer and check the output

uhd_find_devices

linux; GNU C++ version 4.4.3; Boost_104000; UHD_003.000.001-e2cd276

No UHD Devices Found

can anyone help me with this.

Thanks,

Abhijeet.

_______________________________________________ Discuss-gnuradio mailing list address@hidden http://lists.gnu.org/mailman/listinfo/discuss-gnuradio

--
Abhijeet S Mate
Graduate Student
Polytechnic Institute of New York University