Cp201x kernel

Hardware Support
1

I'm trying to get my OS to communicate with a ham radio tranceiver. The rig uses a cp201x usb interface. My pc sees the radio and gives the usb port its own usb identity tty/USB0. The cp201x kernal appears to be installed, loaded and running. But, it won't connect. Thoughts?

2

Hmm ...This seems like something more for the Ham Radio community This forum is more for installs troubles and such of Zorin OS not many here will have knowledge on HAM communications like the HAM community will have

3

Welcome to the Forum!

Is this a real Kernel that You have installed? Can You post the Oupt of the Command uname -r please? Are Secure Boot and Fast Boot in BIOS disabled? Does Your System runs in Wayland or X11? You can check that with the Terminal Command echo $XDF_SESSION_TYPE

4

this kernel came with the Zorin OS. I will take be at my pc later this evening and will try your suggestions

5

I remember seeing in the announcements with the release of version 7.0 of the Linux kernel, all networking packages were deprecated/redacted, and that included support for Ham Radio, by the Linux maintainer responsible for network driver submissions.

All of the current network drivers were compiled in Linux kernel 7.0.x using A.I.!!!

1 Like
6

he may not have updated to 7.0 maybe he is on 6.17 the drivers are in the kernel if i understand what i am reading on this

7

the following is suggested by AI caution is advised

AI Overview

The CP210x USB-to-UART driver is already built directly into the Zorin OS Linux kernel by default. You do not need to download, compile, or install external drivers to use CP210x microcontrollers or serial chips. [1, 2]

Verifying Connection

  • Plug your CP210x device into a USB port.

  • Open your terminal and run dmesg | grep cp210x or lsmod | grep cp210 to see if the kernel loads the module and assigns a device node (like /dev/ttyUSB0).

  • Ensure your user account has permission to access serial ports by adding yourself to the dialout group using sudo usermod -aG dialout $USER, then log out and back in. [1, 2, 3, 4]

1 Like
8

uname -r reports 7.0.0-29-generic. System runs in Wayland. Secure boot is disabled. Should I load a different version?

2 Likes
9

Thanks, Ive seen this from AI

2 Likes
10

Yes, I would roll back to an earlier kernel. Always advisable to hold on to the earlier kernels and also to have Timeshift installed.

You can invoke a hold function to prevent 7.0.0 up from being installed.

1 Like
11

You can try it with booting in an older Kernel. To do that, choose on Startup in the GRUB Menu ''Advanced Options'' and there an older Kernel (without Recovery Mode).

Another Try could be to switch from Wayland to X11/Xorg to see if it works better. To do that, go to the Login Screen. click there on Your Profile so that the Password Field appears. When it is appeared, You should see in the bottom right Corner a Gear Icon. Click on it and choose the Option ''Zorin Desktop on Xorg'' and then log in.

1 Like
12

none of the kernels listed in the GRUB menu worked any differently. I was not able to use mainline to load 6.17 any thoughts?

1 Like
13

What Kernels were listed? Was there even a 6.17 Kernel? If not, Yopu could install an older one from the Repo. The Downside is that the 6.17 Kernel will not receive any Updates because the Support has ended.

1 Like
14

Here are my choices:
Zorin OS, with Linux 7.0.0-29-generic
Zorin OS, with Linux 7.0.0-29-generic (recovery mode
Zorin OS, with Linux 7.0.0-28-generic
Zorin OS, with Linux 7.0.0-28-generic (recovery mode

1 Like
15

Okay, I understand. Okay, then let's try it with the 6.17 Kernel first. Depending how that works, we could try then the 6.8 Kernel. In Comparison with the 6.17 Kernel, it still get's Updates.

So, to install the 6.17 Kernel type in Terminal:

sudo apt install linux-headers-6.17.0-42-generic linux-image-6.17.0-42-generic linux-modules-6.17.0-42-generic linux-modules-extra-6.17.0-42-generic

When installed, reboot and then choose the Kernel.

16

I was able to install 6.17 and boot into it. Same issue persists. the systems sees USB0 but the app won't connect. I removed brltty and disabled modem manager, btw
I am in the dialout group. Other usb ports work well too.

1 Like
17

hmm do you have to obtain permission from the dialout group in order to connect?

18

Here the dependencies for the app i'm usiing. Could any of this be interfering?
sudo apt install -y libfltk1.3-dev libjpeg9-dev libxft-dev libxinerama-dev libxcursor-dev libsndfile1-dev libsamplerate0-dev portaudio19-dev libpulse-dev libusb-1.0-0-dev texinfo libudev-dev build-essential

1 Like
19

If i type "groups", dialout appears in the list

1 Like
20

What App do You use?

1 Like