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

The bluetooth function (of the Defy) prevents the user to enter BIOS settings on boot up. #777

Open
benstor214 opened this issue May 6, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@benstor214
Copy link

Currently the Defy is looking for a bluetooth connection as soon as it receives power - even if the wireless function is set to off by the switches on the undersides (🛜=🟥). This leads to a unwanted user experience when trying to enter the BIOS settings on boot up, as the keyboard will not send any key press to the pc.

I understand this shortcoming when the keyboard is paired over bluetooth (and maybe RF), but when connected per USB the keyboard should act like any other wired keyboard.

Steps to reproduce the behavior:

  1. Shutdown the pc.
  2. Put the switches for the wireless function to the off position.
  3. Connect the keyboard to the pc per the neuron and the USB cables.
  4. Power on the pc.
  5. Try to enter the BIOS settings and feel miserable for failing.

Expected behavior
When connected per USB the keyboard should act like any other wired keyboard.

Desktop (please complete the following information):

  • OS: Arch Linux (kernel 6.8.9.arch1-1)
  • Bazecor Version: 1.4.0-rc.3

Additional context
Still quite happy with my purchase!

@benstor214 benstor214 added the bug Something isn't working label May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant