#udev — Public Fediverse posts

Brest: Atelier d'été - Arch Linux, Le vendredi 24 juillet 2026 de 14h00 à 17h00. https://www.agendadulibre.org/events/35291 #brest #archlinux #linux #kernel #systemd #bootloader #xorg #udev #rencontre #discussion #distributions #distributionsGnuLinux #logicielsLibres #arch #infini #adieuWindows

I just ran into this again, and as a reminder. If you want to set a network interface name through a systemd.link file , e.g. /etc/systemd/network/70-foo.link , you need to not only set Name, but also disable NamePolicy . That is:

[Match]
MacAddress=c0:ff:ee:c0:ff:ee

[Link]
Name=coffee
NamePolicy=

It is well-documented in the man page of systemd.link . But slightly non-intuitive.

#udev #systemd #linux_networking

Okay today I managed to accidentally trigger “locked” function keys on my rather new M70 RK Royal Kludge. There is a modifier hotkey for this that I didn’t know of before (FN + LEFT CTRL) and I was lost for a hot minute how to turn it off again. Ah well, we’re still getting to know each other.

Anyway, I know from a previous attempt that RKGaming offers a webapp to configure the keyboard (especially it’s macro keys) on https://drive.rkgaming.com/. This works to this date only in Google Chrome (Webserial in Firefox is coming though). Here we can click a button and connect to the wireless receiver and… nothing. Ah yes, we’re on Linux PC and random browsers shall not write to our hardware devices. This is in principle a good idea and I did encounter this before with my Viture XR glasses so I had an idea where to start poking.

First things first: Confirming my theory I checked the browser console and sure enough it was not allowed to open the device:

[HID] Selected device: 2.4G Wireless Receiver vid=0x3554 pid=0xfa09
index-JWjn01Gh.js:1 NotAllowedError: Failed to open the device.

There is also this special chrome://device-log/ address in Chrome that has some more details:

HIDEvent[12:08:56] Failed to open '/dev/hidraw10': FILE_ERROR_ACCESS_DENIED
HIDEvent[12:08:56] Access denied opening device read-write, trying read-only.

With this information we do have the Vendor ID (0x3554) the Product ID (0xfa09) and the subsystem (hidraw) in question. This is btw the dmesg output for the connected device, confirming what we know already:

new full-speed USB device number 17 using xhci_hcd
New USB device found, idVendor=3554, idProduct=fa09, bcdDevice= 1.02
New USB device strings: Mfr=1, Product=2, SerialNumber=0
Product: 2.4G Wireless Receiver
Manufacturer: CX

And a quick check on /dev/hidraw10 confirms that we simply to not have permission to read or write to this hidraw device, since it belongs to root.

crw-rw----. 1 root root 241, 9  8. Jun 12:05 /dev/hidraw10

Now a quick and dirty fix for the current session would be to simply change the ownership of that device but I really want this to stick around after the next reboot so I created the udev rule file /usr/lib/udev/rules.d/72-rk-royal-kludge.rules:

# Udev processes rules in alphabetical/numerical order. The actual
# application of the uaccess tag happens in systemd's built-in
# 73-seat-late.rules so make sure this is run *before* by saving 
# this as e.g. 72-rk-royal-kludge.rules
# uaccess tag means that logind assigns the permissions to users
# dynamically via ACLs according to which session is currently active
SUBSYSTEM=="usb", ACTION=="add", ATTRS{idVendor}=="3554", ATTRS{idProduct}=="fa09", MODE="0660", TAG+="uaccess"
SUBSYSTEM=="hidraw", KERNEL=="hidraw*", ATTRS{idVendor}=="3554", ATTRS{idProduct}=="fa09", MODE="0660", TAG+="uaccess"

Changes in such files have to be reloaded with e.g. udevadm control --reload. After that… nothing happens. This is because the device exists already so it’s time to unplug that receiver briefly. Now udev kicks in and creates the device files with the new rules applied. There is now a slight difference:

crw-rw----+ 1 root root 241, 10  8. Jun 12:34 /dev/hidraw10

The “+” indicates additional ACL rules. If you did not know about ACLs before: Oh boy, you’re in for a ride. Anyway, I confirmed that I now have access to this by checking the ACLs with e.g. getfacl /dev/hidraw10

# file: dev/hidraw10
# owner: root
# group: root
user::rw-
user:beko:rw-
group::rw-
mask::rw-
other::---

And presto. My user beko has read-write access. Another visit to https://drive.rkgaming.com/ yields a far better result:

[HID] Selected device: 2.4G Wireless Receiver vid=0x3554 pid=0xfa09
index-JWjn01Gh.js:2388 Device [2.4G Wireless Receiver] is open

Now I can configure my keyboard on Linux PC via a gorram web application like any other cool kid in 2026. I say this because the app will probably have a half-life of 2 years and stop working soon enough again.

What a time to be alive.

#Linux #JustLinuxThings #udev #keyboard #RoyalKludge

This content is licensed under a Creative Commons Attribution 4.0 International license.

I want the same #gaming #performance as #CachyOS but I stay on #Arch. CachyOS is basically Arch with preconfigured tweaks. I build the same setup myself, so I know what every single #screw does and why it is there. No #ballast I do not understand, full #control. If something breaks, I know exactly where to look.

My #plan:

1. #CachyOS #repo and #BORE #kernel
2. #sysctl tweaks
3. #udev #scheduler rules
4. #amdpstate, preferred core
5. split lock off
6. #ananicy
7. #gamemode
8. #GEProton
9. #mesagit
10. #RADV transfer queue
11. #GPU performance level
12. #EXPO in the #BIOS

Funny detail: the #CachyOS #wiki itself has a #guide for Arch users who do not want to switch but want full control.

https://wiki.cachyos.org/features/optimized_repos/

What do you think?

#LinuxGaming #FOSS #Gaming #Freedom

I just released game-devices-udev 1.0 ◝(ᵔᗜᵔ)◜

Took a while .. 7 month …and it's mostly an import of what was in Valves steam-devices. It also includes some little improvements, such as the usage of meson and a new icon (both completely useless ദ്ദി◝ ⩊ ◜.ᐟ)

See the full changelog here:
https://codeberg.org/fabiscafe/game-devices-udev/releases/tag/1.0 𖹭.ᐟ

#gameDevicesUdev #udev #steam #linuxgaming

Mein Linux-Notebook bleibt im Performance-Modus, auch wenn ich im Zug sitze - und der Akku ist nach 90 Minuten leer.

Die Lösung: eine kleine udev-Regel, die automatisch zwischen Performance und Balanced umschaltet, sobald das Netzkabel dran oder ab ist.

Funktioniert auf GNOME, KDE und Cinnamon, also auf jedem aktuellen Ubuntu, Linux Mint oder Fedora.

Anleitung mit allen Codeblöcken im neuen Artikel auf Rüegger's Log:
https://rueegger.me/ubuntu-mint-fedora-energieprofile-automatisch-mit-udev-umschalten/

#Linux #Ubuntu #LinuxMint #Fedora #GNOME #KDE #udev

Post 2/2
I told Kay it was amazing to hear about the "highest ranks" of the industry from the source.
He just laughed: "Highest ranks? It was more like **Kindergarten**." 😂
Attached: A legendary selfie. Kay with the @Suse mug, me beaming, and a fellow passenger in the back blissfully sleeping through a Linux history summit. 😴
Next stop: Prague! See you all at the playground. 🇨🇿✨
#SUSECON #TechLife #Systemd #Udev #GeekoOnTour

Would you like to contribute something easy to a little project?

My game-devices-udev is missing out some udev-rules already in steam-devices. This would be a good chance to kill some time and do some MR :D (and even learn git, markdown, udev in the process!)

https://codeberg.org/fabiscafe/game-devices-udev/issues/73

#gaming #udev #Linux #LinuxGaming #LazyMe

#packetradio using #digirig #aprs #direwolf #xastir #socat #packetradio #nixos #configurationdotnix #udev #ft818 #yaesuft818 #hamradio #resilientcommunication #Notfallkommunikation detailed setup video --->
https://youtu.be/smrTgJLs9Hg?si=i-F-vbtN7xKqZQTA
[ background info also under
https://themodernham.com/packet-radio-101-the-ultimate-guide/ (slow link)
https://youtu.be/V0FAzMIsxMg?si=vnqJyVgwbIoq-Gnm ]

#HIVEMIND: What would be the best way to give a #Linux user with no admin rights (i.e. no access to sudo) have full access to external block devices?

These users need to be able to repartition and put images on USB sticks, but not internal drives.

I'm thinking #udev should be able to do the job, but I don't know if there's a way to specify "all USB block devices." I guess an alternative would be to say "anything but NVMe drives" or "only /dev/sdx drives," but that feels too imprecise.

If there's a better way then I'm all ears.

#AskFedi #LazyWeb

First time renaming something at the #udev level (NAME=) instead of adding an alternative name (SYMLINK+=).

That was fun… regardless of the relative order of the TAG+=, ENV{}=, and NAME= directives, I couldn't do more than renaming…

Turns out this isn't an all-or-nothing thing, you might get the new name, without the rest (environment variables)… until you figure out your KERNEL== filter needs to accept the new name as well. Otherwise, you're out of luck.

That was fun…

Wer irgendwann in letzter Zeit mal testweise die Remote-Desktop-Software NX NoMachine installiert hatte, sollte seinen Linux-Rechner auf Überbleibsel dieser Installation kontrollieren:

wiki.archlinux.org/title/NoMac…

Die verbliebene Gerätekonfigurationsregel /etc/udev/rules.d/99-virtualgl-dri.rules hatte mir die Berechtigungen für /dev/dri/renderD128 dergestalt verbogen, dass Vulkan nicht richtig funktionierte.

#NoMachine #VulkanAPI #udev

Recently, when I dealt with some package issues around probe-rs, I found that some developers and packagers may have some misunderstandings about #systemd #udev giving some users access permission. systemd udev rules have two kinds of permission mechanisms: one is like chown, which can set the device file's owner to some user or group (normally #plugdev system group); another is #uaccess, systemd will give the active user session permission via ACL.

#UDEV ゴシックフォント、 #Homebrew からインストール出来たのか。
アップデートが降りてくるからこれでインストールしなおした :tony_smiling:

https://formulae.brew.sh/cask/font-udev-gothic-nf#default

Consistent Device Names for USB Disks and Partitions

https://blog.hardill.me.uk/2025/03/21/consistent-device-names-for-usb-disks-and-partitions/

I’ve been playing with a really small scale ZFS server to host volumes shared via NVMEoF and iSCSI. These are then mounted on Virtual Machines or as Physical Volumes in my Kubernetes cluster.

The test server is a Raspberry Pi 4 and 2 identical 64Gb USB flash drives.

The problem with using USB drives is that their device names are assigned based on the order they are inserted or the order […]

#Linux #udev #usb

Yay, I have defeated the udev demons to work out how give consistent device names to USB sticks, and their partitions.

I will write up this deep black magic after I've been and got dinner and a beer

#linux #udev #usb

Quand c'est pas #systemd qui me prend la tête, c'est #udev . Mais comment ça a fait pour devenir aussi merdique #Linux ? Ça marchait mieux et plus simplement ya 20 ans :(

Ils ont perdu le #KISS les devs ? Faudrait voir à retomber sur terre hein...

Погружаемся в initrd

Приветствую! Меня зовут Валерий, я инженер операционных систем в секторе клиентской и мобильной ОС. Сегодня хочу затронуть фундаментальные вопросы: - процесс загрузки операционной системы в автоматизированное рабочее место (АРМ), - распаковку начального образа оперативной памяти, - подробный разбор initrd, что это такое и с чем его едят. Этот материал поможет понять как природу загрузки ОС Astra Linux Special Edition в частности, так и загрузку GNU/Linux в целом.

https://habr.com/ru/companies/astralinux/articles/851056/

#initrd #grub #скрипт #udev #переменные_окружения #каталог #операционная_система #автоматизированное_рабочее_место #оперативная_память

I try to give the audio interface of my radio some human friendly name. Using some udev rules, I managed to do so for ALSA using `ATTR{id}`. Now I want the same for graphical applications (like for example in volume control).

I recall that it was possible to set `ENV{SOUND_DESCRIPTION}` which does not work. I am on Linux mint 22 which uses Pipewire.

Can anybody point me into the right direction?

#fedihelp #pipewire #udev #linux #audio