$ dmesg -WH [Jan13 13:23] usb 1-2: new full-speed USB device number 13 using xhci_hcd [  +0.127202] usb 1-2: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice=81.33 [  +0.000009] usb 1-2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [  +0.000003] usb 1-2: Product: USB Serial [  +0.002694] ch341 1-2:1.0: ch341-uart converter detected [  +0.000410] usb 1-2: ch341-uart converter now attached to ttyUSB0 [  +0.548256] input: BRLTTY 6.4 Linux Screen Driver Keyboard as /devices/virtual/input/input47 [  +0.000857] usb 1-2: usbfs: interface 0 claimed by ch341 while 'brltty' sets config #1 [  +0.000452] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0 [  +0.000016] ch341 1-2:1.0: device disconnected

Apparently UFW is uncomplicated FW.  Re-ran dmesg with UFW suspended, now less FW chaff, but same result that cable attached to ttyUSB0, but then disconnects.

Pulled out the cable, another line added:

[Jan13 13:28] usb 1-2: USB disconnect, device number 13    Soooo, it disconnected in one sense, but was still "connected" until I physically removed it when it truly disconnected ?   IDK what I'm seeing :-D

Thanks guys!

*________________________*

*Greg Beyer greg@beyerusa.net*

------------------------------------------------------------------------ *From:* Gregory Beyer greg@beyerusa.net *Sent:* Monday, January 13, 2025 at 1:22 PM *To:* Dave B via Users *Subject:* [users] Re: Trouble with Linux USB port

Ran dmesg -WH, then plugged in cable:

$dmesg -WH [Jan13 13:06] usb 1-2: new full-speed USB device number 11 using xhci_hcd [  +0.127055] usb 1-2: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice=81.33 [  +0.000012] usb 1-2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [  +0.000004] usb 1-2: Product: USB Serial [  +0.002031] ch341 1-2:1.0: ch341-uart converter detected [  +0.000540] usb 1-2: ch341-uart converter now attached to ttyUSB0 [  +0.168438] [UFW BLOCK] IN=eno1 OUT= MAC=e0:70:ea:ef:a5:3c:e0:bb:9e:67:f9:de:08:00 SRC=192.168.254.18 DST=192.168.254.245 LEN=1344 TOS=0x00 PREC=0x00 TTL=64 ID=32786 DF PROTO=UDP SPT=3702 DPT=54283 LEN=1324 [  +0.052702] [UFW BLOCK] IN=eno1 OUT= MAC=e0:70:ea:ef:a5:3c:e0:bb:9e:67:f9:de:08:00 SRC=192.168.254.18 DST=192.168.254.245 LEN=1344 TOS=0x00 PREC=0x00 TTL=64 ID=32791 DF PROTO=UDP SPT=3702 DPT=54283 LEN=1324 [  +0.330900] input: BRLTTY 6.4 Linux Screen Driver Keyboard as /devices/virtual/input/input45 [  +0.000801] usb 1-2: usbfs: interface 0 claimed by ch341 while 'brltty' sets config #1 [  +0.000522] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0 [  +0.000031] ch341 1-2:1.0: device disconnected

Interesting that line 6 shows attached to ttyUSB0 then blah-blah, device disconnected at last line.  Also something that twiggs me - those "UFW BLOCK" outputs.  "UFW" could mean "uncomplicated firewall" which is the FW running on LinuxMint.   Wonder what happens if I suspend the firewall, then plug the cable in??  Stay tuned. . . .

*________________________*

*Greg Beyer greg@beyerusa.net*

KQ4AVZ

---

*From:* Dave B via Users users@lists.chirpmyradio.com *Sent:* Monday, January 13, 2025 at 12:28 PM *To:* users@lists.chirpmyradio.com *Cc:* Dave B *Subject:* [users] Re: Trouble with Linux USB port

...

Hi.

With recent Linux's, you can use...

dmesg -WH   in a command line session...

Where nothing appears to happen but if you plug something in, you'll see what the OS does with it.

If -WH errors, try -wH..    An initial splurge of info, then silence, untill you change what's plugged in.

(Ctrl+C exits the dmesg thing, Ctrl+D will close the terminal session.)

If you have a FTDI based adapter, you can create a udev rule, so it always shows up under a more easily recognizable device name, such as...   /dev/ttyMyAdapter!  Or other creative name, regardless of were you connect it.

Lesser chipsets without a unique serial number, you can do similar tricks, but you have to decypher the "path" to the device, and as I've recently found, with some OS/PC Hardware combinations, that can change at each boot!

Most application software these days will accept that sort of thing, CHIRP used to, but I've yet to try the latest incarnation.

Dave G0WBX. _______________________________________________ Users mailing list users@lists.chirpmyradio.com https://lists.chirpmyradio.com/postorius/lists/users.lists.chirpmyradio.com

To unsubscribe, send an email to users-leave@lists.chirpmyradio.com To report this email as off-topic, please email users-owner@lists.chirpmyradio.com List archives: https://lists.chirpmyradio.com/hyperkitty/list/users@lists.chirpmyradio.com/

Wow, Graham, that was it -- brltty! "brltty accessibility service for blind people that is installed in Ubuntu and Ubuntu derivatives (Mint etc.) by default and have priority over serial devices plugged into the system later. Simply disable or remove this service."    I removed it, plugged in the cable, it connected, and stayed connected.  Opened CHIRP, connected to ttyUSB0 port, cloned my radio down.  Problem solved!

Thanks very much!

*________________________*

*Greg Beyer greg@beyerusa.net*

------------------------------------------------------------------------ *From:* Graham Whaley graham.whaley@gmail.com *Sent:* Monday, January 13, 2025 at 1:43 PM *To:* CHIRP users list *Cc:* Gregory Beyer *Subject:* [users] Trouble with Linux USB port

It looks like there might be an app/service already running that might be causing the disconnect - see https://askubuntu.com/questions/1454633/dev-ttyusb0-device-connects-then-is-...

There are some hints on that page on how to disable that service afaict.

Graham

...

On 13 Jan 2025, at 18:32, Gregory Beyer via Users users@lists.chirpmyradio.com wrote:

usbfs: interface 0 claimed by ch341 while 'brltty' sets config #1