Kernel 5.10 actually has a lot of issues. It’s been reported multiple times on this forum and other forums. And also reported multiple times on Freedesktop GitLab. Some people are just lucky that it works 100% with their hardware.
@pretzelbrain , when asking for help on the forums, please stay polite, regardless of other people’s comments. If you are aggressive, no one is going to want to help you. Certain people might not give answers you like, but others can chime in throughout the day.
Unfortunately, I do not know what gpg key they use to import. Other option is to skip the signature check, but I don’t know how to do that. There is a way to totally ignore all signature checks by editing the pacman.conf file. You can try doing that temporarily for that one package, then remove the edit:
OK, I believe you. I just don’t have any problems whatsoever.
Edit:
As I mentioned, I do not experience any glitches, but I know my experience and other people’s might differ. I’m not calling anyone a liar. I just said I didn’t know, because, well, because I don’t know. Not to be aggressive.
Also, just an FYI to everyone, linux-lts is currently Kernel 5.4 in BOTH Arch and Manjaro. wireguard-lts is needed for this, I do not know why the package was removed from Manjaro.
I’ll try explaining what I think is the issue here.
You are on linux54 because linux510 is not stable enough for you. That’s fine.
And you want to use a kernel module, that is not packaged in Manjaro for linux54.
wireguard-lts is in the Arch repo’s, because it follows the Arch linux-lts package, which does not exist in Manjaro.
This means that you will have to build that module yourself. The easiest way to build kernel modules in Arch/Manjaro is by using DKMS. Thankfully, there’s a dkms module package for wireguard, called wireguard-dkms
Installing wireguard-dkms will build the wireguard kernel module for the kernels you have installed. Just be sure that you have the kernel headers that match your kernel, eg linux54-headers if your kernel is linux54.
First of all, Arch has their own kernel packages, linux (latest stable) and linux-lts (latest LTS) . Manjaro has it’s own versioned kernel packages. Our linux-lts is a meta package and has no relation to the Arch package.
We don’t import the wireguard-lts package because it depends on Arch’s linux-lts. If you have our linux-lts meta package installed and you want to install wireguard-tools with the kernel modules, you would do the following:
linux-lts got added to Manjaro recently iirc. Because it keeps trying to replace my kernel 5.8 (that I haven’t removed yet) with linux-lts when I upgrade.
That’s not the Arch package. linux-lts is a meta package in Manjaro, making sure the user rolls to the newest LTS kernel available, without doing it manually. It does not serve the same purpose.
Ah, I see. Maybe we should rename this meta package? It can cause confusion because I noticed that linux-lts comes up on a number of Arch Wiki pages, and a lot of Manjaro users reference the Arch Wiki.
Couldn’t @pretzelbrain install the client package that’s on TorGuard’s website? It also has browser extensions, which wouldn’t need any system installation.
Thank you @Strit! I really appreciate the explanation!
I understand it better as well now.
The most important thing to remember it, as @Yochanan said, Arch is not Manjaro and Manjaro is not Arch. Even though the share a lot of things. Just like I have legs and you have legs (I hope, else this is going to be one catastrophic comparison), but we each have our own legs with their own, unique features that sets them apart, in the same way Manjaro and Arch is the same, yet at the same time each is unique and totally different. Some things work the same and some don’t. In the same way some of the things available to Arch is the same thing available to Manjaro, and some not. It pays to keep that in mind, and I’ll do my best to do so.