I don’t know what will work.
At least your keyboard is working as a keyboard.
I would downgrade the BIOS so it removes the keyboard firmware warning message, and then contact FW support.
You could try and make a new vfat sda1 partition on it, but I think that would be risky, as it might break even the working bits of the keyboard that you have now.
WARNING: attempting to partition the FW keyboard disk has reports of bricking the device entirely, so don’t do it.
Honestly, anything outside of hitting “yes” on the firmware upgrade sounds like a support ticket to me. Regardless of whether you can fix it or not, it’s not something you should have to and you could help represent others who can’t fix it themselves and would likely struggle to communicate the problem.
I ain’t contacting support, this is my last Framework product, had enough of these BIOS issues and the quiet/silent communication from them
3.04 - FTR/FTH issues
3.05 - all previous issues
3.06 - FTR/FTH issues happen less frequently but now the battery doesn’t report it’s percentage correctly unless I’ve configured it to 100%
3.07 - all previous issues and stuttery performance/jittery when gaming at full load ( iGPU only, no dGPU )
4.01 - all previous issues and now keyboard ( although I think it’s just the keyboard )
Maybe I missed something in reading through the whole thread; is there a reason that the BIOS update could not have part of its script to check AFTER it updates the hardware devices to then go and update the Keyboard/Numpad/MacroPad firmware?
Just thinking in terms of user satisfaction to make it one update that does the checks and applies the fixes as needed. It is already applying multiple firmware patches to several components, adding a few more into the mix even after reboot should be possible and makes this easier for users that may not know they need to run an entirely different update to avoid warnings and errors upon POST.
I loaded optimized defaults and tried to change settings.
For me, nothing changed. from power on to the first boot message, it takes 45 to 60 seconds.
I toggled quick boot to check, but nothing changed.
It’s a bit strange.
I reflashed the bios and thought it’s working now. It took “only” about 8 seconds from power up until the screen shows my memory.
I put my FW back and attached my docks. Now I’m back to 60 seconds.
When I remove all USBs attached to my docks, I’m at 12 seconds.
It stays at 12 seconds if I attach all USB devices except my Stream Deck.
As soon as my Stream Deck is connected, it takes 60 seconds to show the first sign of life.
I don’t know if that was happening with 3.x also as my FW16 is running 24/7 normally except when I travel and then this doesn’t happen as I have no devices connected.
It is unfortunate to see that even up to 4.1Beta there are still issues present. I do like to see that some folks are reporting the power studder/jitter seems to have improved. But only seeing reports for the 180w thus far. Curious if it solved the 240w? I’m hesitant to update seeing that some folks are having boot/post and expansion module issues.
Artem_Puzikov posted the 240w stutter issue has been resolved in this version up above.
And in my mind, anything below the 180w supply should not be expected to provide good gaming performance on a dGPU, so I would let those issues go.
I have not updated to this bios yet, but I really hope all the weird throttling and power glitches have been resolved. Has anyone checked if it still has errant throttling statuses applied when it shouldn’t? I have not seen anyone reporting with any actual technical tests to determine if this bios is actually good or not.
Sorry, must have missed that one. Skimming this thread and slightly lacking sleep. Thanks for catching it. I don’t use anything other than my 180w personally. I was just curious for other folks on results of update. Good call on the throttling issue though. Along with you, I’ll be awaiting folks to post with testing results.
I also use a 130W Dell charger sometimes, I haven’t noticed any issues with it so far. Granted, I also use it less than my 180W.
I did have some odd gpu TDP issues last night that I got around via using a different port, which pokes a tiny hole in my bad-cable theory. Hopefully it doesnt’ get bigger.
Sorry to bump my own reply, but I think this needs to be addressed: are people who are going to buy only the 5070 ad an upgrade missing out on GSYNC only or are we missing the MUX/Optimus feature by running Gen1 display with the 5070?
Ok so I had time to do the new BIOS 4.1 Beta and keyboard firmware flash. So far BIOS is working without a hitch.. haven’t done any serious testing yet as I moved on to the keyboard flash. I downloaded the file and ran the .exe and CMD came up doing its thing saying it flashed it successfully. However, when I put the keyboard into bootloader and checked the info file on the drive, it still says “UF2 Bootloader v3.0” in the text? Did I do something wrong? Is it not installed properly?
Edit (addition): I am currently testing sleep/resume variables (from what I can remember reading in other threads), and thus far not seeing clock speeds reduced with this BIOS.
Edit 2: Scratch any testing I am doing.. I was reading the reports on GitHub and they found that the issue was supposedly linked to the dGPU.. I am not using one so my tests are unreliable. Someone else please look into this?
You might want to explain what this is and where you saw it being supported by Framework. The only ones who will know are Framework themselves, and inside that, probably only the engineers. As far as I know, the MUX is and has to be software based to support the different dGPU options so I would assume this is not supported.
