No need, I know how to blacklist a kernel module.
My question was not "how to blacklist a module" but how to I could find out why these modules are being loaded.

Because whatever EEPROM resides in my box* is ID'd as read-only and I have never had  a joystick attached/installed.
* same box since ~ 2015, running on Devuan since ~ 2017

Thanks for your input.

Best,

A.

It is very simple. Just read Debian wiki https://wiki.debian.org/KernelModuleBlacklisting

Running on Devuan Daedalus:

~$ uname -a
Linux devuan 6.1.0-31-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.128-1 (2025-02-07) x86_64 GNU/Linux
~$ 

At boot, dmesg prints out this:

~$ sudo dmesg
--- snip ---
[   24.257488] at24 0-0050: supply vcc not found, using dummy regulator
[   24.260227] at24 0-0050: 256 byte spd EEPROM, read-only
[   24.260817] at24 0-0051: supply vcc not found, using dummy regulator
--- snip ---
[   24.263031] at24 0-0051: 256 byte spd EEPROM, read-only
[   24.263475] at24 0-0052: supply vcc not found, using dummy regulator
[   24.264991] at24 0-0052: 256 byte spd EEPROM, read-only
[   24.265389] at24 0-0053: supply vcc not found, using dummy regulator
[   24.266865] at24 0-0053: 256 byte spd EEPROM, read-only
~$ 

And lsmod prints out this:

~$ lsmod
--- snip ---
joydev                 28672  0
--- snip ---
at24                   28672  0
--- snip ---
~$ lsmod

From what I understand (?) the at24 cannot be used in my system.
ie: 256 byte spd EEPROM, read-only

The kernel config file says ...

~$ cat /boot/config-6.1.0-31-amd64 | grep -i at24
CONFIG_EEPROM_AT24=m
~$ 

... that it is loaded as a module.

Same as joydev:

~$ cat /boot/config-6.1.0-31-amd64 | grep -i joydev
CONFIG_INPUT_JOYDEV=m
~$ 

The MB surely has an EEPROM, albeit read-only which the installer probably cannot ID as such.

With respect to joydev, I looked it up and it seems to be for joystick support which I don't need.
How can I find out if something in my box uses it?

If possible, I would like to keep those unused modules from loading.

Best,

A.