There are multiple ways to fix this, here's some of the methods of the top of my head ranked best to worst: 1: Write a udev rule to unbind the 0000:00:14.0 dev

There are multiple ways to fix this, here's some of the methods of the top of my head ranked best to worst: 1: Write a udev rule to unbind the 0000:00:14.0 device when detected. This is the best solution, and a google search can show you how. But does require some underlying knowledge of devices and udev. [A][B][C] 2: Create a systemd startup service that runs your above commands at startup. This is less elegant than the above, but the end result would mostly be the same. [H] 3: Configure sudo to not require a password, then create an xdg-autostart script that runs your command. [W][X] [A] https://wiki.gentoo.org/wiki/Udev https://wiki.gentoo.org/wiki/Udev [B] https://www.linuxquestions.org/questions/linux-software-2/udev-rules-for-hid-binding-unbinding-of-custom-driver-4175685728/ https://www.linuxquestions.org/questions/linux-software-2/ud... [C] https://github.com/Roboy/flexrayusbinterface/issues/13 https://github.com/Roboy/flexrayusbinterface/issues/13 [H] https://wiki.archlinux.org/title/systemd#Writing_unit_files https://wiki.archlinux.org/title/systemd#Writing_unit_files [W] https://phpraxis.wordpress.com/2016/09/27/enable-sudo-without-password-in-ubuntudebian/ https://phpraxis.wordpress.com/2016/09/27/enable-sudo-withou... [X] https://specifications.freedesktop.org/autostart-spec/autostart-spec-latest.html https://specifications.freedesktop.org/autostart-spec/autost...