Two Keyboard Drivers
Ronald Frison
One problem with Safe Mode is it still loads a list of drivers, however it uses a new configuration for them and only loads "official" drivers; If you boot into a recovery mode from an installation media however, it will load Window's default drivers and config, while still letting you edit the config on the installed system.
The last thing, that sounds dumb, but it's worked in the past... Change USB ports to a port that has never had a Keyboard or mouse on it. When a new device is recognized Windows associates that port with a device type and driver so just changing ports (or moving from "USB2 to USB3 or vice versa) may help; also reboot the computer with them in different ports so the Kernal loads them (but start by changing them while the system is running, and give Windows time to associate the port and driver (5 mins)).
You might not even need the USB, just press F8 (I believe) while it's booting up windows and there should be some options (including the "Repair computer" one) available. You'll need to disable "Fast boot" (or whatever it's called now) though.
The question leave out important detail on what driver is disabled. If it's just kbdhid/mouhid then suggestions related to RDP login will probably work. If it's kbdclass/mouclass then the only way I can think of is to boot into WinPE/recovery environment and use "reg add [keyname] /v Start /t REG_DWORD /d 3 /f" to enable them again.
Being the very-smart, highly-intelligent person that I am () I tried to install the Windows Bootcamp drivers on the machine manually. What I mean by manually is, I opened the Bootcamp installer in 7-zip and found what looked like they keyboard drivers' setup component. I extracted this piece and ran the .exe.
Because it was not installed in the conventional manner, I didn't get any prompts and, at first, I didn't notice it did anything, presumably because there were other components I didn't install. Eventually I realized that my many of my Function keys (any with other controls on them, such as F1-F4 & F7-F12) didn't seem to work. I later found out that they only work when pressing the "fn" button above the arrow keys on the keyboard.
I've tried manually uninstalling the Keyboard drivers from the Device Manager in Windows. The device manager shows two keyboard devices (no idea why), so I've de-installed both and re-installed them. This didn't change anything at all.
This should display every driver windows considers compatible with your hardware, hopefully the list will include a few items one of which will be the original driver.
If what you are looking for does not appear there, you can uncheck the "show compatible hardware" box and look through the whole list, mainly under the "(standard keyboards)" category.
This time, when it looks for a keyboard driver, it will not find the Bootcamp one that is considered to be newer (and thus presumably better). Therefore it will search for the next best driver it can, building a new cache and driver database, and then install whatever you used before.
It would be worth a try to install the drivers as they were meant to be, then uninstall them the right way.At least, once their install correctly, there is probably an option in the program to use the F-Keys as normal, and using the "Fn" key as a modifier.
I have recently installed Ubuntu on my Mac book Pro 2016, and noticed that the built in keyboard, and the track-pad are frozen. I have looked up how to install the drivers but I don't understand a how to use GitHub and got lost really quick.
Now run sudo dkms install -m apple-bce -v r183.c884d9c. If on a live ISO, use sudo dkms install -m apple-bce -v r183.c884d9c -k x.x.x-mbp instead and change x.x.x-mbp to the kernel that you have installed, as by default dkms will try to build the module for the kernel that the live ISO is using, which will most likely be older.
If you don't want (for example) the touch bar modules, you can omit them from this command. brcmfmac is needed to use the internal Wi-Fi chip, refer to the Wi-Fi guide for details on how to set that up.
Did you enable "Install third-party software for graphics and WIFI hardware and additional media formats" during installation? Also, if you have a external mouse, can you try using that? Theres also "Additional Drivers" in the "Software & Updates app, see if the drivers for the trackpad/keyboard are there.
I recently bought a new keyboard, it was cheap and of an unknown brand but i wasn't particularly worried. I found out that on linux pressing shift, super, left-ctrl or left-alt with this keyboard made no difference, it always take it as shift. I made some researches and it turns out the problem is the chipset used by the keyboard. I read that the only way to solve the problem is to write a driver for the keyboard, but, while working on it i found out that running sudo modprobe usbmon and then opening wireshark as sudo, unexpectedly fixes the problem... someone knows why this happen? and if there is a simpler way to trigger this change?
Treating all modifier keys as shift keys might be caused by the system initially using the simplified boot keyboard protocol (the usbkbd module) instead of the main HID protocol, combined with the fact that the boot keyboard protocol support might be poorly implemented in that particular keyboard. But this is just a wild guess.
Apparently you might see a message like USB HIDBP Keyboard 14cf:0056 in dmesg output if the boot protocol is getting used. What does sudo dmesg grep HID tell you? (Please add the results into your original question.)
Wireshark can also monitor USB traffic, and starting Wireshark with sudo might in fact trigger the loading of the usbmon module. But the fact that the usbmon module causes the problem to be fixed is intriguing... perhaps it causes a re-detection of USB devices so the full-featured usbhid driver module will get the keyboard for itself, or changes the timing of USB traffic just enough that whatever causes the "all modifiers are Shift" dumbness of this keyboard gets avoided.
I attempted to install Kaspersky Anti-Virus 2017. The install process failed and the Kaspersky install app claimed to back out changes it had made up to that point. However, my keyboard and touchpad no longer worked. Looking on the HP website, I found instructions for restoring the keyboard drivers. I went to Device Manager, Viewed hidden devices, expanded Keyboards, uninstalled each driver listed under Keyboards, then Restarted my laptop. The keyboard still did not work so i went back into Device Manager to look at the drivers under Keyboards again. This time two have yellow triangle indicators with an "!" - HID Keyboard Device and Standard PS/2 Keyboard. When I right-click on each of thes and view the properties, I see the messages:
So far I tried to install the keyboard drivers but the install failed. I am now in the process of backing up my data to an external drive and locating the sources for addition software that I use. Once I complete that and can be sure I won't need access to any files or my browser for a couple days, I will follow the instructions you provided to restore my system.
Thank you so much for providing such clear instructions. I am just sorry that the keyboard driver install didn't work, but I am very hopeful that I will be able to restore my system by following the instructions you gave me. I will give you an update on my progress in a few days.
Evidently they have a known issue but were reluctant to share the fix when I first reported my issue. I don't expect their instructions to help at this point but I will try out of curiosity and hoping still to avoid having to reload all software which was not part of my original system. Having said that, I do expect, and am fully confident that your instructions on restoring my system to its original state will work and therefore I have a strong "safety net" when these latest instructions fail.
Unfortunately just loading the keyboard and mouse drivers did not work. Kaspersky acknowledged that they have a problem for which they do not have a good solution. Their tech support tried working with me to create a rescue disk and boot from that in order to repair the problems their software had caused on my laptop. The end result was that I not only couldn't use my keyboard nd mouse but I lost all network and internet access!
I finally bit the bullet and followed the instructions you sent to restore my system to its original state - worked like a champ and didn't take near as long as I had imagined. Then I quickly reloaded my other software and I am mow "back in business". Thank you so much for the help and the detailed steps!
After boot on Arch I can just unplug and plug my keyboard and it works fine again.
There's some way to soft reset my keyboard driver?
I'm thinking this could be a solution to my issue.
I've tried hubpower 001:005 power and I get an error message saying that this device isn't a hub.
So I've tried hubpower 001:001 and all my usb devices went off. I can't turn it on again cause I can't write because my mouse and keyboard is gone.
You need to figure out which port to switch exactly. Run lsusb -t, this will print connections between devices and hub port numbers in addition to normal output. So if the keyboard turns out to be on, say, port 3 of hub 1:1, you need:
Sorry, you need to additionally run "hubpower xx bind" at the end. It seems that the first thing "hubpower power" does is unbinding (disabling) Linux drivers for all devices on the hub and "hubpower bind" reverses this.
However, a bad news is that your root hub seems to ignore power-off requests - it still says "Power-On" after the first command. But, it seems that there is another hub (Dev 2) sitting between port 1 of the root hub and actual USB ports on the motherboard. So, you can try "hubpower 1:2 power 4 off ; ..." - maybe this second hub supports power switching.
c80f0f1006