this post was submitted on 06 Mar 2026
20 points (100.0% liked)

Linux Gaming

24744 readers
137 users here now

Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.

This page can be subscribed to via RSS.

Original /r/linux_gaming pengwing by uoou.

No memes/shitposts/low-effort posts, please.

Resources

WWW:

Discord:

IRC:

Matrix:

Telegram:

founded 2 years ago
MODERATORS
 

As noted in the title, I am trying to figure out the safest way to update the firmware on my recently purchased Keychron K1 QMK V6 keyboard. I was finally able to get the web based Keychron Launcher app to talk to my KB after using chmod to give the correct HIDRAW device read-write access but it looks like the new firmware needs another utility to be installed and only the Windoze directions are provided.

From my own online research it looks like there is a terminal-based method but it wasn't really explained. I am not super concerned about updating the firmware since the preloaded version works well enough for my needs but I am still wondering if anyone knew of a tutorial on how to do this without bricking my shiny new keyboard.

I am using Fedora 43 Workstation if that makes any difference. Thanks in advance for any tips or advice!

you are viewing a single comment's thread
view the rest of the comments
[–] MrQuallzin@lemmy.world 10 points 19 hours ago (2 children)

Why do you need to update the firmware? They say explicitly to not do it unless there's a need to do so. From their website:

Note: If everything works fine with your keyboard. Please don’t update the firmware. There is a chance it can damage your keyboard.

[–] chippydingo@lemmy.world 1 points 16 hours ago

I don't "need" to really...just noticed that there is a newer version with added functionality and was curious about the process since I had never done it before. I have been using basic keyboards like membrane and chichlet styles but I have been interested in getting a mechanical model for a long time. Finally decided to go for it after having to reset my 13 year old MS curve for the 3rd time this week in order to log into my computer.

So this also purges one more element of the despicable microslop ecosystem from my life and gives me what is shaping up to be a better typing experience as well. Based on the feedback, it looks like I should just hold off on making any changes until something more groundbreaking or critical needs to be done to my keeb.

[–] just_another_person@lemmy.world 1 points 19 hours ago (1 children)

When they do this, they know they have a problem with their flash utils and process 🤣

I'd leave it alone.

[–] breadsmasher@lemmy.world 5 points 19 hours ago (4 children)

Or maybe its because flashing firmware is inherently risky. Any power loss mid flash would brick the device.

[–] A_Random_Idiot@lemmy.world 1 points 8 hours ago* (last edited 8 hours ago)

Unless you live in a place with inherently unreliable power, or are flashing in the middle of a thunderstorm/tornado/hurricane/typhoon/earthquake/etc, Flashing is relatively safe as long as you follow directions.

And those risk could be completely eliminated with a dual bios setup, where even if there WAS a failure, it could fall back on the other bios and still work flawlessly. or even better, let you flash the currently inactive one, and switches that to primary upon successful flash. I think even flashback lets you recover from a corrupted bios, too?

So yes, it circles around back to them being cheap and having problems with their process, because they are cheap.

[–] starblursd@lemmy.zip 2 points 18 hours ago

If the brain is functioning as expected, a brain transplant is ill-advised as risk to reward doesnt make sense.... But computers

[–] Chronographs@lemmy.zip 1 points 19 hours ago

Yeah I see that all the time for firmware updates. They don’t want to have to replace your product if you’re an idiot and unplug it or something.

[–] just_another_person@lemmy.world 0 points 19 hours ago (1 children)

Nah, it's not that risky if your tooling and process is solid. I have thousands of edge devices out in the field doing firmware updates on carrier boards from a specific manufacturer and have never had one fail or brick in update. Why? Because their tooling is absolutely fantastic and pretty bulletproof.

Even a simple {checksum>transfer>checksum>write>checksum} is pretty safe, UNLESS...you know the carrier you're flashing doesnt have the ability to do so, in which case, you definitely put a warning like this on your product because you know it has a penchant for failure.

[–] breadsmasher@lemmy.world 0 points 17 hours ago

And I assume all of those devices have a UPS