[hpsdr] Having trouble with Hermes board. Software doesn't find eth0

Jim Lynch jim at k4gvo.com
Fri Jul 19 11:34:26 PDT 2013


unning Mint 13 on a 64 bit system.  Have wlan0 and eth0 interfaces. 
Compiled two different programs, QtHPSDRServer and ghpsdr. Both failed 
to compile correctly out of the box due to include directories either 
missing or incorrect, but eventually I got them to compile.

Laptop bin # ./ghpsdr --metis --interface eth0
ghpsdr Version 0.9
ozy_init
Looking for Metis card on interface eth0
No eth0 interface.
Laptop bin # ./ghpsdr --metis 0 --interface eth0
ghpsdr Version 0.9
ozy_init
Looking for Metis card on interface eth0
No eth0 interface.


eth0      Link encap:Ethernet  HWaddr 00:c0:9f:cc:df:15
           inet6 addr: fe80::2c0:9fff:fecc:df15/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:8228 errors:14 dropped:0 overruns:0 frame:0
           TX packets:113 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:1242549 (1.2 MB)  TX bytes:19120 (19.1 KB)
           Interrupt:18 Base address:0xa000

lo        Link encap:Local Loopback
           inet addr:127.0.0.1  Mask:255.0.0.0
           inet6 addr: ::1/128 Scope:Host
           UP LOOPBACK RUNNING  MTU:16436  Metric:1
           RX packets:299 errors:0 dropped:0 overruns:0 frame:0
           TX packets:299 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:0
           RX bytes:50444 (50.4 KB)  TX bytes:50444 (50.4 KB)

wlan0     Link encap:Ethernet  HWaddr 00:14:a5:13:d4:fd
           inet addr:192.168.2.117  Bcast:192.168.2.255 Mask:255.255.255.0
           inet6 addr: fe80::214:a5ff:fe13:d4fd/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:180105 errors:0 dropped:0 overruns:0 frame:0
           TX packets:89307 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:237191812 (237.1 MB)  TX bytes:9141950 (9.1 MB)

When I run QtHPSDRServer, switch to the configuration tab the interface 
selection only shows wlan0.  I changed the QtHPSDRServer.ini
to include interface=eth0, and ran the server, it still only shows 
wlan0.  And immediately rewrites the .ini file.  If I hit start, it 
looks like it's wanting to talk to something over the wlan0 port and 
segfaults out quickly.

There are link lights on both the laptop and the receiver and 
occasionally the data light will blip.  I've connected the laptop and 
Hermes via a cable (tested with two cables) and tried it with a 100T 
switch.  Nothing seems to make the software see the port.  I'm running 
as root, so I don't think it's a permission problem.

Also I tried:

./HPSDRProgrammer
Debug: "wlan0" "00:14:A5:13:D4:FD" "192.168.2.117"
Debug: Interfaces found  1
Debug:  : eth0
Debug:  : wlan0
Debug: USB bus number 1 : usbmon1
Debug: USB bus number 2 : usbmon2
Debug: USB bus number 3 : usbmon3
Debug: Pseudo-device that captures on all interfaces : any
Debug:  : lo
Debug: HPSDRProgrammer (ver 1.6)

It listed two but only found 1, wlan0.

I can't find anything in the logs that indicate a problem.  And last but 
not least,

sestatus
SELinux status:                 disabled

Any ideas?

I see lots of red lights lit on the hermes board.  A couple(at least) 
are flashing.  It's drawing about .5 amps (meter isn't accurate at that 
low a draw however)

Thanks,
Jim.




More information about the Hpsdr mailing list