this post was submitted on 10 Jan 2024
16 points (94.4% liked)

Linux

48328 readers
540 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
AgreeableLandscape@lemmy.ml
nooter692@lemmy.ml
MarcellusDrum@lemmy.ml
cypherpunks@lemmy.ml
cyclohexane@lemmy.ml
d3Xt3r@lemmy.nz
16
Working instructions for OpenRazer on Fedora Silverblue? (lemmy.ca)
submitted 10 months ago* (last edited 10 months ago) by thayer@lemmy.ca to c/linux@lemmy.ml
4 comments fedilink hide all child comments
 

Probably a longshot, but hoping anyone here might have working instructions on getting OpenRazer running under Fedora Silverblue. I recently picked up some Huntsman V2s and while OpenRGB works for basic control, I'd like to see what other options are available.

Apparently there is a known incompatibility between Silverblue and how OpenRazer implements kernel modules (link). I've seen elsewhere that some users have tweaked the build files to work around this, but I couldn't find any detailed info. Any help would be appreciated.

EDIT:

I got it working, but it wasn't worth the trouble compared to simply running OpenRGB in a flatpak. For Razer keyboard users, you'll gain one or two RGB presets over OpenRGB, such as Reactive, and the ability to adjust the polling rate (the merits of which are highly debatable). You'll lose secure boot and kernel verification unless you also add the ublue repo and signing key rpm (ublue-os-akmods-addons).

If anyone wants to do it anyway, I had success by downloading and installing the following ublue-os akmod rpms from here:

  • akmod-openrazer-100.0.0.git.530.886f986d-1.fc39.x86_64.rpm
  • kmod-openrazer-100.0.0.git.530.886f986d-1.fc39.x86_64.rpm
  • openrazer-kmod-common-100.0.0.git.530.886f986d-1.fc39.x86_64.rpm

(Note: you might need to layer the kernel-devel package first; I had it layered already so I can't confirm.)

Add the openrazer repo, then install the daemon and frontend app:

curl -o - https://download.opensuse.org/repositories/hardware:/razer/Fedora_$(rpm -E %fedora)/hardware:razer.repo | sudo tee /etc/yum.repos.d/razer.repo
rpm-ostree install openrazer-meta razergenie

Add the plugdev group to /etc/group, then add your user to it:

sudo bash -c 'grep "plugdev" /lib/group >> /etc/group'
sudo gpasswd -a $USER plugdev

Finally, launch RazerGenie...

all 5 comments
sorted by: hot top controversial new old
[–] throwawayish@lemmy.ml 4 points 10 months ago* (last edited 10 months ago) (1 children)

It seems as if the uBlue images ship the required OpenRazer kmod by default. Therefore, I would suggest you to take a look at those. You still need to follow some additional steps though 😅. Which might not be very intuitive... Thus, I propose the following: if you'll rebase to uBlue, you might as well rebase to Bazzite. After the rebase has been completed, the (post-)installation software should already give you the option (it's just a simple toggle) to install OpenRazer. The toggle is clearly visible in this frame.

If you perceive Bazzite as too opinionated for your taste, then perhaps you might opt to the following instead:

install-openrazer:
    sudo wget https://download.opensuse.org/repositories/hardware:/razer/Fedora_$(rpm -E %fedora)/hardware:razer.repo -O /etc/yum.repos.d/hardware:razer.repo && \
    ublue-update --wait && \
    rpm-ostree install -y openrazer-meta razergenie && \
    if ! grep -q "plugdev" /etc/group; then \
      sudo bash -c 'grep "plugdev" /lib/group >> /etc/group' \
    ; fi && \
    sudo usermod -a -G plugdev $USER && \
    echo "Please reboot to apply needed changes."

Which should be the just-entry (and thus responsible) for whatever happens after the toggle is enabled*.

[–] thayer@lemmy.ca 2 points 10 months ago (2 children)

That's good to know, thanks! I'm quite content with vanilla Silverblue, but I'll take a look at their build files and see how they're pulling it off.

[–] throwawayish@lemmy.ml 2 points 10 months ago

Aight. I've changed the comment a bit 😅 since. Perhaps it's more useful for you now 😉.

[–] Guenther_Amanita@feddit.de 2 points 10 months ago* (last edited 10 months ago)

I wanted to make the same suggestion with uBlue. There's also the silverblue-main image, which is very vanilla and the one I use. The kmod is already pre-installed there.

Bazzite can also be great, but it's too opinionated for my taste. I like Silverblue also more like the devs intended.