02-06-2022, 03:31 AM
Both no and yes
No because I still don't know how to dynamically unload the kb151 module and getting the user land driver to work.
Yes because blacklisting the module in /etc/modprobe.d/blacklist.conf by adding a "blacklist kb151" enables me to use the userland driver after a reboot
I have also tried to add kb151.disable_input to the kernel parameters as suggested by megi's blog post: https://xnux.eu/log/#058
I did this by adding it to U_BOOT_PARAMETERS in /etc/default/u-boot then running u-boot-update and after a reboot confirming that it was added by examining /proc/cmdline
For some reason this wasn't enough and I then tried to outright blacklisting the module which work even if being somewhat static
No because I still don't know how to dynamically unload the kb151 module and getting the user land driver to work.
Yes because blacklisting the module in /etc/modprobe.d/blacklist.conf by adding a "blacklist kb151" enables me to use the userland driver after a reboot
I have also tried to add kb151.disable_input to the kernel parameters as suggested by megi's blog post: https://xnux.eu/log/#058
I did this by adding it to U_BOOT_PARAMETERS in /etc/default/u-boot then running u-boot-update and after a reboot confirming that it was added by examining /proc/cmdline
For some reason this wasn't enough and I then tried to outright blacklisting the module which work even if being somewhat static
