-
-
Notifications
You must be signed in to change notification settings - Fork 517
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
Driver isntall for GMMK2 not working #398
Comments
The current stable version of the Toolbox does not support the WB32 bootloader. Support has been merged but I haven't made a new release yet. |
any pointers to where I can find this and maybe make it myself? Do you also know of any method to just manually do this using wsl, powershell, or a native linux host? I would much rather do that. |
Flashing instructions for each bootloader are in the docs, but it doesn't have WB32. The beta version can be found in the releases tab, keep in mind you might have problems with it. |
One particular caveat is that you will need to clean out the |
thanks for that bit of info, i'll do that. |
deleted the whole QMK folder, ran the beta installer, opened it and tried to install drivers, got this:
should I try to reboot? It's running in the 0.2.2 folder which it recreated |
Try rebooting; hope it helps (debugging those Windows problems might be really hard). |
yeah that is why i'd prefer to do this on linux if possible |
a reboot fixed it! thank you very much, now my right control works on my gmmk2 :) i'd happily do some testing for this hardware/firmware if needed |
When my keyboard is in bootloader mode, it's recognized but it says the drivers are not installed. I tried installing through this toolbox and restarting, and that did not help.
Following error:
WB32 DFU device connected (NO DRIVER): WB Device in DFU Mode (342D:DFA0:0100)
Describe the Bug
System Information
Additional Context
followed this guide
https://www.gloriousgaming.com/blogs/guides-resources/gmmk-2-qmk-installation-guide
The text was updated successfully, but these errors were encountered: