-
Notifications
You must be signed in to change notification settings - Fork 61
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
Keyboard Disabled Fedora 34 #87
Comments
@Lucrecious you can simply reboot you PC and it will use the default hid_apple module if you were unloading the original one manually with |
The first thing I tried was rebooting the PC but nothing changed. The keyboard is still unresponsive - very weird! Luckily, this is a fresh Fedora install, so worst case scenario I can just re-install. |
You need to provide more information. What you did, what hardware/macbook do you have and etc. Based on you messages I suppose you have installed the patched version via DKMS before running this command., haven't you? If yes, then the modprobe command is not the reason of problems, but the fact that patched version of hid-apple module does not work properly in your case for some reason. Before reinstall or something - try to connect USB keyboard and check if it works. This way you can remove installed DKMS module and get the default one working again in the worst case scenario. |
I'm on OSX I went through the install via DKMS instructions on the github page, up until this step: This command wasn't available on Fedora 37, and instead I used this instruction: After that I tried to run: And that's when my keyboard stopped working. Also, unfortunately, I do not currently have an extra keyboard available to plug in. It's weird because even the virtual keyboard on the desktop doesn't work, but the virtual keyboard during login, does. |
After I ran this comment from the github page:
sudo modprobe -r hid_apple; sudo modprobe hid_apple
I thought running this with the
;
would reenable the keyboard.My keyboard was disabled, how do I turn it back on?
The text was updated successfully, but these errors were encountered: