👀 Views: 92 💬 Answers: 1 📅 Created: 2025-06-29

linux archlinux kernel bash

This might be a silly question, but I'm relatively new to this, so bear with me. I'm experiencing a question with loading a custom kernel module on Arch Linux during boot. The module is supposed to be loaded with specific parameters, but it seems to ignore those parameters and fails to load properly. I’ve added the module to `/etc/modules-load.d/` by creating a file named `my_module.conf` with the following contents: ```bash my_module ``` To pass parameters, I tried creating a file under `/etc/modprobe.d/` named `my_module.conf` with this content: ```bash options my_module param1=value1 param2=value2 ``` However, at boot, I see the following behavior messages in the journal logs: ``` Failed to load module 'my_module': No such device ``` I also tried loading the module manually using `modprobe my_module` after booting, and it worked fine with the parameters set in the `modprobe.d` file. I verified that the module is compiled and available in `/lib/modules/$(uname -r)/`. Additionally, I checked the output of `dmesg` for any relevant messages but didn't find any clues. I have updated my initramfs using `mkinitcpio -P` to ensure that any changes are reflected, but the scenario continues. Does anyone know why the parameters are not being recognized during the boot process? I've tried looking through the Arch Wiki, but I'm still exploring. Any help would be appreciated. For context: I'm using Bash on macOS. I'd really appreciate any guidance on this. This is happening in both development and production on macOS. Any pointers in the right direction?