You are not logged in.

#1 2024-07-25 13:49:19

paolomainardi
Member
Registered: 2024-05-08
Posts: 5

Custom hwdb.d entry does not start at boot

Hello everyone!

As reported in the subject, I am having trouble making a custom (simple)
hwdb.d entry rule to start at boot.

Instead, it works by running it manually, after logging in, which is quite
annoying:

sudo systemd-hwdb update
sudo udevadm trigger /dev/input/event*

This is the rule:

❯ cat /etc/udev/hwdb.d/90-logitech-mice.hwdb

# to use when hires is enabled.
# mouse:*:name:*Logitech * Mouse*:
#      MOUSE_WHEEL_CLICK_ANGLE=1
#      MOUSE_WHEEL_CLICK_COUNT=360              # lower is faster.
#      MOUSE_WHEEL_CLICK_ANGLE_HORIZONTAL=1
#      MOUSE_WHEEL_CLICK_COUNT_HORIZONTAL=50

# to use when hires is disabled.
mouse:*:name:*Logitech * Mouse*:
     MOUSE_WHEEL_CLICK_ANGLE=1
     MOUSE_WHEEL_CLICK_COUNT=160 # higher is slower but smoother.
     MOUSE_WHEEL_CLICK_ANGLE_HORIZONTAL=1
     MOUSE_WHEEL_CLICK_COUNT_HORIZONTAL=100

# This is just used when bluetooth is enabled.
mouse:*:name:*Logitech MX Master 3S*:
     MOUSE_WHEEL_CLICK_ANGLE_HORIZONTAL=1
     MOUSE_WHEEL_CLICK_COUNT_HORIZONTAL=100

The current systemd version in use is: systemd 256 (256.1-1-arch-g34ba18b^)

Sorry if this is not the right place to ask these kinds of questions;
please point me to the appropriate place if that's the case.

Best regards,
P.

Offline

#2 2024-07-25 18:25:08

seth
Member
Registered: 2012-09-03
Posts: 59,084

Re: Custom hwdb.d entry does not start at boot

Do you *have* to run "sudo systemd-hwdb update" to apply it?
This builds /etc/udev/hwdb.bin - check it's timestamps and md5sum around the boot - do you have /etc on some extra mount/subvolume?

Offline

Board footer

Powered by FluxBB