It could be that the chipset on the rigblaster advantage is causing problems. info from dmesg :
) [ 3.321021] usb 2-1.6.1: new full-speed USB device number 4 using ehci-pci [ 3.414671] usb 2-1.6.1: New USB device found, idVendor=2405, idProduct=0003 [ 3.414675] usb 2-1.6.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 3.414678] usb 2-1.6.1: Product: West Mountain Radio RIGblaster Advantage [ 3.414680] usb 2-1.6.1: Manufacturer: Silicon Labs [ 3.414682] usb 2-1.6.1: SerialNumber: 54ddaac5 [ 3.484888] usb 2-1.6.2: new full-speed USB device number 5 using ehci-pci [ 3.516766] ata6: SATA link down (SStatus 0 SControl 300) [ 3.582213] usb 2-1.6.2: New USB device found, idVendor=2405, idProduct=0002 [ 3.582215] usb 2-1.6.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 3.582216] usb 2-1.6.2: Product: RIGblaster Advantage Audio [ 3.582217] usb 2-1.6.2: Manufacturer: West Mountain Radio [ 3.583475] input: West Mountain Radio RIGblaster Advantage Audio as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6.2/2-1.6.2:1.3/0003:2405:0002.0004/input/input8 [ 3.583665] hid-generic 0003:2405:0002.0004: input,hidraw3: USB HID v1.00 Device [West Mountain Radio RIGblaster Advantage Audio] on usb-0000:00:1d.0-1.6.2/input3 The related bugs on bugs.launchpad.net: https://bugs.launchpad.net/ubuntu/+source/wsjt/+bug/1488906 https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1488890 This bug is a ear old, but it is confirmed.: https://bugs.launchpad.net/ubuntu/+source/wsjt/+bug/1315769 Den 29. aug. 2015 17:43, skrev KI7MT: > That what I use in my scripts, as the WSJT autotools / m4 macros need a > bit of updating. > > For Debian/Ubuntu based distros: > > For x86 > ./configure \ > --with-portaudio-lib-dir=/usr/lib/i386-linux-gnu \ > --with-portaudio-include-dir=/usr/include \ > PYTHON=/usr/bin/python3 \ > F2PY=/usr/bin/f2py3 > > For x86_64 > ./configure \ > --with-portaudio-lib-dir=/usr/lib/x86_64-linux-gnu \ > --with-portaudio-include-dir=/usr/include \ > PYTHON=/usr/bin/python3 \ > F2PY=/usr/bin/f2py3 > > That should prevent any need to manually edit the Makefile. > > Be aware, the default install --prefix is /usr/local. If a different > install location is desired, the user should add --prefix="" as desired. > > More than likely, the PObjext error was result of having python-numpy > (python-2.7.x version) installed and not specifying the which F2PY to > use at configure time. > > I removed my Linux Mint 17.1 install, but If need be I can simply add it > to a partition do some testing. I do know, WSJT, WSPR and WSJT-X all > worked properly Linux Mint 17.1 the last time I tested it, which was a > couple months back. > > > 73's > Greg, KI7MT > > > On 08/29/2015 05:35 AM, Bill Somerville wrote: >> On 29/08/2015 12:19, Richard Bown wrote: >>> Edit the Makefile >>> >>> change the python and f2py lines to this:- >>> # WSJT specific Fortran flags >>> FFLAGS += -O2 -fbounds-check -fno-second-underscore -Wall >>> -Wno-conversion -Wno-character-truncation >>> CFLAGS += -I. -DBIGSYM -DHAVE_STRUCT_TIMESPEC -fPIC >>> >>> PYTHON ?= /usr/bin/python3 <<<<< >>> F2PY ?= /usr/bin/f2py3.4 <<<<< >>> >>> run make >> There should be no need to change the Makefile directly. Makefile >> variables can be overridden from the make command line: >> >> $ make PYTHON=/usr/bin/python3 F2PY=/usr/bin/f2py3.4 >> >> I am no expert in WSJT building so even this my not be necessary but if >> it is then this is the safest way to do it. >> >> 73 >> Bill >> G4WJS. > > ------------------------------------------------------------------------------ > _______________________________________________ > wsjt-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > -- ----------- Håken Hveem ------------------------------------------------------------------------------ _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
