I run debian here, and just added sid to my apt source list to pickup v2.3.0 on debian, on apt update and upgrade.
On Thu, 25 Feb 2021, 1:11 pm Kevin Hass, <[email protected]> wrote: > I wanted to pass along my experience in getting wsjtx to run on Slackware > 14.2. > I'm actually using the "current" Slackware version, which is in "process", but > more current the just v14.2. > > BTW, v14.2/current appears to also include the Burr-Brown CODEC module, so the > issue concerning installing those drivers are resolved when using the latest > version of Slackware. > > I didn't see any real info from others concerning WSJTX on Slackware, so > hopefully > this will help others who might be running Slackware, and hope to get WSJTX > running > on their system. I've been running Slackware since 1994, and it's too late > for me > to change now :) > > I first tried downloading the compiled executable RPM for wsjtx v2.3.0, and > used > Slackware's "rpm2tgz" to convert the RPM to Slackware's installation archive > files. > It installed, but you can't run it due to library dependencies, so I decided > to > compile from source. > > I downloaded wsjtx v2.3.0 source, and compiled it w/o errors. I did alter > the > configure script's default directory from /usr/local to /usr. > > > Then I ran into the hamlib error, which displayed: > "rig.c(745):rig_open return > while opening connection to rig" > > Line 745 of rig.c is attempting to open the USB device file. > But I didn't even know if I had chosen the correct device in > the File/Settings/Radio serial port configuration - it had > three devices to choose from. > > For my system, the device file was /dev/ttyUSB0 - owned by root, and group > "dialout".. > But the device only exists when my rig (Yaesu FT-991A) is connected and > powered. > Otherwise the device file vanishes. > > My first hope was to change the permissions to allow "others", but since the > device > file is short lived, that was not an option. > > I hate to admit it, but the answer was to add my user account to the > "dialout" group. > It's something I learned in Unix 101 (~1989-90), but forgot due to lack of > use. > > > I edited the group file ( located here: /etc/group ). I changed the line > for > "dialout", by adding my account to the "dialout" group. You need root access > to edit > this file, or use the "sudo" method as most do today. > > Original line: dialout:x:16:uucp > > Edited line: dialout:x:16:uucp,kevin [ My account is "kevin" ] > > > > That stopped the errors I was getting, and now WSJTX runs fine on Slackware > 14.2. > > I still do get the hamlib error if I run wsjtx before connecting and powering > the Yaesu, > but all I need to do now is turn the rig on, and the error goes away. > > I just hope documenting how I was able to get WSJTX to run on Slackware 14.2 > might help > others that may also try it. It might have saved me a day or two of errors > and head > scratching. Maybe it will help others! > > Kevin > WB0DPN > > _______________________________________________ > wsjt-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wsjt-devel >
_______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
