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 .. lrwxrwxrwx 1 root root 13 Sep 26 13:25 usb-Inside_Out_Networks_Edgeport_8_04-15-000842-if00-port0 -> ../../ttyUSB2 lrwxrwxrwx 1 root root 13 Sep 26 13:25 usb-Inside_Out_Networks_Edgeport_8_04-15-000842-if00-port1 -> ../../ttyUSB3 lrwxrwxrwx 1 root root 13 Sep 26 13:25 usb-Inside_Out_Networks_Edgeport_8_04-15-000842-if00-port2 -> ../../ttyUSB4 lrwxrwxrwx 1 root root 13 Sep 26 13:25 usb-Inside_Out_Networks_Edgeport_8_04-15-000842-if00-port3 -> ../../ttyUSB5 lrwxrwxrwx 1 root root 13 Sep 26 13:25 usb-Inside_Out_Networks_Edgeport_8_04-15-000842-if00-port4 -> ../../ttyUSB6 lrwxrwxrwx 1 root root 13 Sep 26 13:25 usb-Inside_Out_Networks_Edgeport_8_04-15-000842-if00-port5 -> ../../ttyUSB7 lrwxrwxrwx 1 root root 13 Sep 26 13:25 usb-Inside_Out_Networks_Edgeport_8_04-15-000842-if00-port6 -> ../../ttyUSB8 lrwxrwxrwx 1 root root 13 Sep 26 13:25 usb-Inside_Out_Networks_Edgeport_8_04-15-000842-if00-port7 -> ../../ttyUSB9 lrwxrwxrwx 1 root root 13 Sep 26 13:25 usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_IC-7610_12004465_A-if00-port0 -> ../../ttyUSB0 lrwxrwxrwx 1 root root 13 Sep 26 13:25 usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_IC-7610_12004465_B-if00-port0 -> ../../ttyUSB1 Oh? My 7610 is on /dev/ttyUSB0 and /dev/ttyUSB1? Great news... I wonder why I can't just pick that straight from a dropdown in the software? Wouldn't that be much easier for those who aren't quite as *NIX savvy? 73 de AI8W, Chris -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS/CM/CC/E/IT/TW d-@ s+:+ !a C++$@ UBLVSCX*++++(on)$>$ P++>$ L+++$ E+@ W++>$ N+++ o+@ K+++ w@ O+@ M-@ V@>$ PS+@ PE@ Y+ PGP++ t+ 5+ X++ R@* tv++ b+>$ DI++ D+ G++ e h r+++ y+++ ------END GEEK CODE BLOCK------ On Sat, Sep 26, 2020 at 8:39 PM Topher Petty <ai8...@gmail.com> wrote: > 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+:+ !a C++$@ UBLVSCX*++++(on)$>$ P++>$ L+++$ E+@ > W++>$ N+++ o+@ K+++ w@ O+@ M-@ V@>$ PS+@ PE@ Y+ PGP++ t+ 5+ X++ R@* tv++ > b+>$ DI++ D+ G++ e h r+++ y+++ > ------END GEEK CODE BLOCK------ > > > On Wed, Sep 23, 2020 at 11:35 AM DG2YCB, Uwe <dg2...@gmx.de> wrote: > >> 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 Linux versions have problems with some AMD >> CPUs/GPUs, and despite lots of efforts ther is NO FIX so far. Unfortunately >> my hardware (AMD A8-5600k) is one of these AMD computers. This bug means >> that immediately after the boot screen, monitor gets dark "no signal" and >> computer hangs (not even possible to push the On/Off switch a long time). >> Only workaround is either booting in recovery mode, or adding >> "radeon.modeset=0" or "nomodeset" to the kernel boot command. But then, of >> course there is no hardware accelaration. It is not possible anymore to >> install AMD's proprietary video driver, as it supports only versions >> until Ubuntu 14.04. Really a nighmare! Frankly, I've experienced a lot of >> things when usind Windows over the years, but something like that I've >> never seen before: Any up to date Linux OS is NOT able to boot on such AMD >> computers unless hardware acceleration is disabled. Unbelievable! >> >> >> 73 de DG2YCB, Uwe >> >> Am Donnerstag, den 24.09.2020, 00:07 +1000 schrieb Adrian: >> >> 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 sudo wsjtx...? >> >> >> _______________________________________________ >> wsjt-devel mailing list >> wsjt-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >> >
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
