The Kernel loads your OS, the BIOS loads low level drivers for your specific hardware. They are not the same and mostly work independently.
That’s odd, because support contacted me about my battery flipping ticket (which is still open) and suggested I try installing this BIOS to see if it fixes it.
However, I see that there’s a lot of issues with this BIOS (FN lock? Supervisor password breaking? USB-C display out breaking!?) so I am going to skip this one 
Yes agreed.
The boot chain looks like UEFI > bootloader > OS.
For Linux the bootloader would usually be grub and OS would be the Linux kernel who will detect and load the drivers for your hardware and then start the init system. The init system will in turn start the services required to bring up a graphical session.
The UEFI does do some device initialization and load a minimal set of drivers to get its UI running but AFAIK the drivers part gets thrown away when the Linux kernel starts and it will load its own drivers for any device found on the machine.
It emerges from earlier in this thread that, seemingly, one Framework BIOS messes up external monitors unless one has a particular kernel.
Oh, also: welcome to the community!
1 Like
It was an overly simple explanation that wasn’t very well managed.
1 Like
Thank you very much! Happy to be part of this nice community 
I had to hold off on kernels starting with 6.13.X because the display crashes due to buggy drivers. Any news on that front?
Am still on 6.12.15 because of that. And will forgo this firmware until the above issue is fixed.
1 Like
My external display stopped working with kernel 6.14.0-28-generic after updating the BIOS, but everything works fine with 6.8.0-1032-oem. My laptop’s internal display has always worked, so the problem only affects the external monitor. I think this suggests that it is mainly a kernel/display driver issue rather than a firmware issue—the firmware may have only exposed an incompatibility with the newer kernel’s display drivers. If you are stable on 6.12.15, it is probably best to stick with that for now. I’m no expert on BIOS or kernels, but if I can help in any way, please let me know.
2 Likes
Just updated via fwupd from 3.05 to 3.16; no issues so far, 80% battery limit stayed enabled, external monitors still work
2 Likes
I ran into the same issue and tested my external USB-C display (Lenovo ThinkVision P27h) with a number of configurations:
| system firmware | linux 6.8.12 | linux 6.14.0-35-generic | linux 6.17.8 |
|---|---|---|---|
| 3.09 | ??? | detected | detected |
| 3.16 (installed via fwupdmgr) | not detected | not detected | not detected |
| 3.16 (installed via EFI on USB) | detected | ??? | detected |
Basically, it seems like somehow the outcome is better if system firmware 3.16 is installed via EFI on a USB thumb drive. More info: BIOS 3.16 broke external monitor (USB-C DisplayPort Alt Mode) and caused severe boot regression on FW13 AMD 7040 · Issue #96 · FrameworkComputer/SoftwareFirmwareIssueTracker · GitHub
1 Like
Speaking of updates via EFI, does anyone have experience booting the updater via Ventoy, or is that a bad idea? (I’m guessing there could be some fireworks if it, say, tries to instruct the firmware to reboot into itself again, only to find Ventoy in that place. But then it does have to boot in a situation where USB ports might not work, so presumably it should accomplish things like that in some other way… I don’t want to guess unless I have to, is my point.)