Click to view our Accessibility Statement or contact us with accessibility-related questions
PRODUCTS YOU MAY LIKE
Trending Posts in Mechanical Keyboards
lantz
Red Samurai on a 75%
Corsair K65 Plus Wireless GMK Red Samurai Moondrop Tactile Tessence
Apr 19, 2024
Keyled
My PRECIOUS!!!!
All that sweat and money paid off. I will use it wisely. Tokyo 60 GMK Serenity Gateron Oil KIng
Apr 19, 2024
TotallyJaded
How do you do per-key RGB lighting on a Shift V2?
I saw the online configurator that lets you do this on the Shift V1, where it spits out a compiled firmware file to flash. The V2 doesn't seem to have this function in the Windows configurator, though. I can't imagine the answer here is "you're going to have to manually write the hex for every key in QMK, compile it, and flash that".
Apr 18, 2024
AiheyStudio
Favorite Artisans
Dragon Pillar Artisan Keycaps Creative Resin Keycaps for 6.25u and 7u Space Bars
Discover the allure of our Dragon Pillar Artisan Keycaps – unique resin keycaps designed to adorn your 6.25u and 7u space bars. Crafted with creativity and precision, each keycap features an...
Apr 18, 2024
lwthunder
Drop CTRL V2 Mechanical Keyboard PCBA
If I want some hot-swap socket for replacement, where I can buy to ensure it fits this PCBA?
Apr 17, 2024
Drop Refurbished
Like-new products you can trustDrop Rewards
Get $5 for every 500 points you earn! Learn more
Drop Keyboard Club
Become a member and expand your keycap collectionCollaborate With Us
For Brands & DesignersFollow Drop
I have read that bad cables can cause problems like this, so I have ordered a new usb-c cable. Any thoughts on what it might be if that doesn't solve the problem? Anyone else have this problem?
It wouldn't bother me that much, but I primarily use this with my Arch laptop, and Arch does not function well with the QMK firmware for Planck, making it difficult to reflash the board on the road.
What could we do to help getting QMK working better with Arch?
The Arch problem is summed up in this issue: https://github.com/qmk/qmk_firmware/issues/3316. It's a consequence of Arch's rolling release schedule. If it affects more than a handful of people, it might be nice to detect the GCC version and issue a helpful warning message to anyone using GCC > 7.3 to compile firmware with audio features. On the other hand, if compatibility with newer GCC versions is coming, it probably isn't worth the effort.
Regardless, I appreciate the tip and the effort to improve QMK usability. Thanks for all the great work!