Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Booster breaks mouse input #206

Closed
ghost opened this issue Feb 10, 2023 · 5 comments
Closed

Booster breaks mouse input #206

ghost opened this issue Feb 10, 2023 · 5 comments

Comments

@ghost
Copy link

ghost commented Feb 10, 2023

After installing booster on Void Linux (musl), it booted without issue. However, logging into either Xorg or Wayland, the mouse doesn't respond to any inputs. This happens with both universal and non-universal initramfs.

Moreover, the issue persists when building booster from source.

I also tried to use a different mouse, however this didn't solve the issue either.

@ghost
Copy link
Author

ghost commented Feb 13, 2023

Tested with master, and the issue is still present.
Oddly enough, I borrowed a random wireless logitech mouse from my friend, and that works without issue, however my Logitech G Pro wiresless doesn't.
Here is the booster log
booster.log

@anatol
Copy link
Owner

anatol commented Feb 13, 2023

Interesting. Your mouse might require custom drivers.

Could you please try 2 things:

  • boot with booster (when the mouse does not work) and post content of lsmod
  • boot with working initramfs, when your mouse is OK and post lsmod again.

My guess is that the working configuration will have additional modules loaded. And booster might need to load it somehow as well.

@ghost
Copy link
Author

ghost commented Feb 13, 2023

Here is the output of lsmod.
The one where the mouse doesn't work is with booster, and the one where the mouse does work is with dracut
lsmod-booster.log
lsmod-dracut.log
I am unsure what I should be looking for, but nothing seems particularly different.

@ghost
Copy link
Author

ghost commented Feb 14, 2023

Solved this by adding:
modules_force_load: usbhid
to my booster.yaml
Heres the booster log and output of lsmod with the mouse working if it can help debug this issue.
booster.log
lsmod-booster-working.log

anatol added a commit that referenced this issue Feb 15, 2023
@anatol
Copy link
Owner

anatol commented Feb 15, 2023

Thank you for debugging it. usbhid is not part of the default modules. Once I add it to the list booster will add the module to image automatically.

@anatol anatol closed this as completed in e65981a Feb 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant