I use hassos on a Thinkpad X240 laptop. It works flawlessly, but I want to adjust the charge start and stop thresholds of the battery. Unfortunately, this must be done on every boot. So I built my own hassos image and extracted the thinkpad_acpi.ko and its dependency ledtrig_audio.ko from the kernel build directory, installed them with insmod manually and they worked as expected.
Now, I want to have these modules also for newer versions of the OS without building them manually each time. I see two ways to achieve this but I’m not sure if either will be accepted by the maintainers:
add the modules to the nuc (for 5.13) or generic_x86_64 (for 6.x) configs
add a new device that uses the same configs but adds the two modules
Yes, I see my driver i need is also there’s it’s config_video_dev … But if I do “modprove video dev” I don’t see it loaded… How do you activate it then?
If I remember correctly the driver is loaded automatically by the kernel. Nothing to do here!
I think you should read on in Video4Linux documentation how to load the driver you need (config_video_dev enables only the V4L2 API, used by cameras, analog TV, video grabbers, radio devices and by some input devices.).
If you look into the buildroot project and search for config_video_dev, you will find three occurences (Search · config_video_dev · GitHub). May be your board is not configured for it (then you need to activate the module like I did for thinkpad_acpi) or doesn’t support it at all.
hmm, thats new to me, i runn HassOS on an esxi system… not sure how i can build the os? can i do that on a windows system ? insmod is indeed usefull to point to a .ko file, so no depmod is needed
maybe i need to add some extra config file here as descibed here :
### Kernel-Module
The kernel module folder `/etc/modules-load.d` is persistent and you can add your configuration files there. See [Systemd modules load](https://www.freedesktop.org/software/systemd/man/modules-load.d.html). You can add the modules configuration files in `/etc/modprobe.d` that is also persistent.
If have no idea why the driver is missing, really. My suggestion: open a ticket and describe your problem (including hardware information). Hope this helps!
I build a new HassOS and enabled the kernel modules before the build, that generated me the .ko file I wanted … copy pasted that file afterwards on my live HassOS system, I did insmod with that file, and it loaded successful :+)
