Which Linux distro are you using? Mint, LMDE-7, Debian 13, Arch
Which release version? Newest versions
(if rolling release without a release version, skip this question)
(If rolling release, last date updated?)
Which kernel are you using?
Which BIOS version are you using? 4.02
Which Framework Laptop 16 model are you using? (AMD Ryzen™ 7040 Series) AMD Ryzen 7040 Series
I was using Windows 11 25H2 when I updated to BIOS version 4.02. A couple of weeks later Windows started going crazy with my files. I had been thinking switching back to Linux. I took this as a hint. That was a week ago. I can’t get anything to install now. Mint , LMDE7 and Arch won’t load up the installer. And Debian 13 won’t install the GRUB bootloader. I even dismantled the laptop to make sure every component is set properly. I’m pulling out my hair because my Framework 16 is now a $2,000 boat anchor. Anybody have ANY suggestions? As for a preferred distro, I would either like to go with LMDE-7 or Debian 13.
Some distros require Secure Boot to be disabled (e.g. Bluefin LTS, Pop! OS, etc.). That’s true for ArchLinux and Mint, IIRC; that’d explain why your installer isn’t loading. Please disable Secure Boot in BIOS and give it another shot.
Also, have you tried installing any of the officially supported distros? Unless you’re strongly opposed to it, you’ll have the best shot at success if you pick one of the supported distros for your platform as outlined here.
I had already disabled Secure Boot before trying to install any Linux distro. I’ve used Mint and LMDE-6 before on the Framework 16 (Batch 2) with no problems. The anomalies only started showing up after I installed BIOS update 4.02. I thought it was Windows messing up. But now, with the trouble I have in installing any Linux distro, I’m thinking that it might be the BIOS update. Suggestions?
Did you reset the BIOS to its defaults? I always do that with new BIOS’s.
Also, as @Rob-i-di-bob suggested, get a live-dvd and boot into a live system and do some performance test etc. to see if the hardware is OK.
If the systems are messed up, it can also be a disk issue on the EFI partition.
No mention of how you made the boot media. So how did you make the boot media/live installation usb stick? What utility did you use in WIndows to do it? Also do you have the usb boot unlocked? I know I lock it as a security measure.
I used Rufus to create the media on my usb sticks. I tried both the MBR and GPT partition schemes. I also used the DD image mode option. I also have tried disks for the media using Nero Express. I have tried the default write speed (4x) and slower speeds and verified the write.
All methods gave the exact same results. Mint & LMDE-6 & 7 will not properly load the splash screen with the installer button. Debian 13 installs but will not install the GRUB bootloader. I even tried Arch and got so bogged down I couldn’t go anywhere and was unable to access the auto-installer.
The usb boot is unlocked. I am also rolling back the BIOS to 3.05 to see if the new BIOS is the problem. Jorg_Mertin suggested resetting the BIOS to defaults. How do I do that?
Where in BIOS do I reset BIOS settings? The only thing I saw was F9 - reset to default settings. I tried that and nothing changed.
When I try to reinstall the BIOS, I get these errors:
Error: cannot find a EFI system partition!
CapsuleApp: cannot find a valid file system on boot devices. Status - not found
CapsuleApp: failed to update capsule - not found
BTW: I have also tried Ubuntu 24.04.3 (officially supported). I had the same results as the other distros that I have tried. Everything that I have tried points to the issue being the BIOS update.
Try this method:
Ppress the chassis intrusion switch (to the bottom-left of the midplate connector) 10 times while powered (about two seconds each time) and it should reset the BIOS settings
This is usually reported when the disk is too large (partition).
Make sure your USB stick has a small partitions (512 MB EFI Vfat32 formatted)>
That’s where the EFI boot loader goes onto.
The rest, make sure the partition is not larger than 4GB (even though I never had an issue with that in the late ubuntu’s - I had these way in the past).
I bet Windows is making something to the EFI partition when it gets created. Could also be the USB drive to be bad.
FYI - I’m on the latest BIOS, and have no issues (AyrinOS and and KDE Neon) in dual boot.
Note that I’d never put Windows on my device.
And, just FYI - boot with the UEFI/GPT - MBR will cause the ubuntu to install the regular non EUFI capable grub.
Note: It can also be that Windows messed the secure boot keys on your device. But that, can’t say for sure, as I don’t use Windows. Happened on my work laptop where I had to clense the secure boot crap and reinit the TPM keys for it to work again. In the end, I didn’t know what I did that made it work again, but after a long evening raging against M$, it worked.
I experience the exact same issue. I tried installing Linux Mint 22.2, Ubuntu 25.10 and Ubuntu 24.04 LTS. All with the same errors. I flashed three different USB-sticks with Rufus in DD/GPT mode.
I had some success with Linux Mint changing the boot command using e, removing the quiet splash arguments and adding nomodeset argument. I could install Linux mint, but I kept having to add the nomodeset argument to the start argument in GRUB. I was hoping to fully leave Windows behind and hope somebody can help me with this.
@Martin_Winkel, were you using Windows when things started going sideways? I’ve been hearing reports that a recent update that Microsoft did started bricking a bunch of computers. I didn’t make the connection at first because I updated BIOS right around the same time. I just assumed that it was the BIOS update without realizing that it could have been the Windows update.
As to your question: No, it’s still a boat anchor. I was able to reinstall Windows, however it started messing up right away.
Why are you using Rufus here? The major Linux distributions provide bootable images which don’t need any custom partitioning - the image is just copied to some USB stick or CD verbatim. This isn’t like Windows installation media which needs special partitioning for USB.
This appears to be common to what is being described here, so you should rule it out by putting Debian or Fedora on a USB stick as instructed by their documentation.
@dileas, I have always used Rufus when using Windows. However, I always create a live media CD of the distro at the same time. In my experience, when one method doesn’t work, the other one usually will. Good idea though. I didn’t know that I could just copy the image verbatim. Thanks.
@Mark_E_Jeffries Never installed Windows, so it wasn’t the problem here.
I just had some success. I could directly install Ubuntu Server 25.10 using Ventoy without any trouble. After rebooting however… nothing.
Then I tried Ubuntu 25.10 from the Ventoy stick and this runs superb! I’m now typing this from my new 16 with Ryzen 9 390HX/96GB/RTX5070. Love it!
@dileas I used Rufus because the Framework guide recommended this. You could be right that Rufus has messed things up. Although I also tried Balena Etcher and Linux Mint with the same troubles, but then Linux Mint might be to old to support the new hardware.
Unlikely that Rufus messed anything up. My installation(s) were more involved as I installed 2 hard drives. One as primary and another secondary (a 2230 and a 2280). Both Win11 Pro and Fedora KDE. 1st Windows on Primary with Fedora on secondary, then wiped it all again and installed Fedora on Primary and Windows on Secondary. All worked perfectly fine using Rufus in all instances. Windows likes to mess with the Boot Manager.
Some basics:
Boot Laptop and keep hitting the F2 key. This should get you into the Bios. Go to Utilities and check that you can see all your devices. Specially your HDD(s), Correct amount of RAM…Exit without saving (or with saving if you haven’t changed anything). On reboot hit F12 key to select the OS that you want to boot into. Windows likes to mess with it and its Boot Manager might be pointing to a bad install, but there should be one that actually works.
If the one that you chose doesn’t work, reboot..F12 and choose the next line. Most likely one of them will work. BTW, I made zero changes in the BIOS while multi installing and wiping the OS’s. Ones all the OS’s were installed to my liking, I then did make one change in the Bios and ran a Grub command combo to ensure that my Fedora OS will boot as the default OS. Windows likes to force itself as the 1st boot option all the time.
Fedora was installed using RuFus..live version from a USB stick and then when running used the Fedora live OS to install on the HDD.
BTW..Framework’s instruction will install your OS smooth if followed to the letter. They are very good. I just deviated where needed for my specific requirement at a later stage on the 2nd round of installs.