Adrian:
You must have overlooked my use of a conditional clause...
I know it's small and easily overlooked, but looking for the word "if" can
sometimes avoid embarrassment.
Thanks for your concern..
On Sat, Sep 26, 2020, 21:24 Adrian wrote:
> You missed the boat on this one, It was described
You missed the boat on this one, It was described as rs-232 not usb,
usb, as in a usb-ser adaptor device,
which would have been ttyUSB* , was never mentioned, only rs-232 making
it ttyS* range.
This was also confirmed in a dmesg test
The issue was resolved with the user obtaining the correct
I really wish people would start allowing the serial-aliasing that exists
in modern Linux... It's really much easier to find where your stuff is
plugged in at...
chris@maximilian:/dev/serial/by-id$ ls -la
total 0
drwxr-xr-x 2 root root 240 Sep 26 13:25 .
drwxr-xr-x 4 root root 80 Sep 26 13:25 ..
Not sure if it's been mentioned, but if it's a USB serial, it's never
/dev/ttyS*...
You should be using /dev/ttyUSB*
You'll also want to make sure you add the user you're logging in as to the
"dialout" group.
73 de AI8W, Chris
-BEGIN GEEK CODE BLOCK-
Version: 3.1
GCS/CM/CC/E/IT/TW d-@ s+:
Adrian,
Yes, I can now start wsjtx normal as user "uwe". So, at the
moment there is no need for me to switch to pulse audio. Must have been
something wrong with the "dialout" permission .
I will now again fucusing myself on another very annoying Linux bug: the "no
signal" error. All the newer Lin
Can you start as user; Uwe instead of using sudo ? Pulseaudio etc will
probably be more friendly to your user profile .
On 23/9/20 11:32 pm, DG2YCB, Uwe wrote:
Looks like re-booting did the job. Is working now!
Btw. Why can't wsjt-x find any of the USB audio devices when launching
with sud
Mike,
sorry, that is incorrect on a couple of counts.
Unix devices are normally owned by root, the group they belong to is
usually used to control access to non-root users.
Changing the group of a device is pointless as it will revert on the
next reboot when the /dev filesystem is rebuilt. T
That implies your /dev device isn't part of the dialout group.
Look at it and it probably isn't owned by the dialout groupls -l
/dev/ttyUSB*crw-rw 1 root dialout 188, 0 Sep 22 15:54 /dev/ttyUSB0
If not,chgrp dialout /dev/ttyUSB*
Mike W9MDB
On Wednesday, September 23, 2020, 08:12:39
Re: Bill Somerville
> id
Fwiw, if `id` (groups in effect) and `id uwe` (groups as per
/etc/group) report different group memberships, you need to re-login.
Christoph
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforg
Hi Uwe,
did you log out of your Desktop session before trying to access the
port? A reboot is a sure way of picking up the new group. If that
doesn't work then something is unusual about your devices, what do the
following commands print?
ls -l /dev/tty*
id
73
Bill
G4WJS.
On 23/09/2020 14
Hi Bill and Adrian,Thanks for your replies. Yes, it seems indeed to be
a permission issue. When I start wsjtx with sudo, CAT works. However,
it is not yet cear to me what is denying the permission, because user
"uwe" is already a member of group "dialout". Hm...
Am Mittwoch, den 23.09.2020, 13:49 +
On 23/09/2020 11:34, DG2YCB, Uwe wrote:
Hi,
I'm currently trying to get WSJT-X to work on a Linux machine with 20
Mint Cinnamon 64-bit (with a Windows 10-like interface called
‘Linuxfx’). The computer has a PCIe card with two RS232 interfaces and
one parallel interface. My FT-991 is connecte
Sorry, I saw your dmesg test after I had already replied, but did you
try running wsjtx as root to test serial permissions (dialout group
acess ?) ?
Are you using a nullmodem cable or direct ?
On 23/9/20 9:03 pm, Adrian Fewster wrote:
Try adding you user to the dialout group, eg , sudo user
> Am 23.09.2020 um 12:34 schrieb DG2YCB, Uwe :
>
> Hi,
> I'm currently trying to get WSJT-X to work on a Linux machine with 20 Mint
> Cinnamon 64-bit (with a Windows 10-like interface called ‘Linuxfx’). The
> computer has a PCIe card with two RS232 interfaces and one parallel
> interface. My
Looks like you don’t have CAT selected.
Tom
WA2TP
From: Christoph Berg
Sent: Wednesday, September 23, 2020 6:44:52 AM
To: WSJT software development
Subject: Re: [wsjt-devel] CAT configuration on Linux
Re: DG2YCB, Uwe
> [0.790264] 00:06: ttyS0 at I/O 0x
Re: DG2YCB, Uwe
> [0.790264] 00:06: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a
> [6.712122] :02:00.0: ttyS4 at I/O 0xe0c0 (irq = 16, base_baud =
> [6.712346] :02:00.0: ttyS5 at I/O 0xe0c8 (irq = 16, base_baud =
>
> What am I doing wrong? Do I have to configure someth
Hi,
I'm currently trying to get WSJT-X to work on a Linux machine with 20 Mint
Cinnamon 64-bit (with a Windows 10-like interface called 'Linuxfx'). The
computer has a PCIe card with two RS232 interfaces and one parallel
interface. My FT-991 is connected via one of the RS232 interfaces (because
the
17 matches
Mail list logo
