I have been procrastinating this for a long time. I have three operating systems on my Surface Laptop 3 13.5”: Windows, Linux Mint 21.1 Cinnamon, and Fedora Linux (6.4.14-200.fc38.x86-64) 38 (Workstation Edition). Fedora was installed after Linux Mint. When I installed Fedora, Linux Mint wouldn't boot from the GRUB installed by Fedora, but it would still boot from the GRUB installed by Linux Mint (but that's not the issue I am concerned with here).One day (around 6 months ago), I wanted to allocate more storage to the Windows partition and less to the partition containing Fedora. I did this from GParted on a live USB containing Fedora Linux 37 (Workstation). It worked, but after doing so, I noticed that my Fedora would no longer boot from GRUB. Because Windows would still boot, I didn't give this much attention for a while.Now, around six months later, I've come back to this issue. I notice that Fedora will still not boot, but for some reason Linux Mint is able to boot from the GRUB installed by Fedora now. Using Linux Mint as well as the GRUB (version 2.06) command line, I was able to see that the partition used to access vmlinuz-6.4.14-200.fc38.x86_64 and initramfs-6.4.14-200.fc38.x86_64.img still contained those files and retained the same UUID. The root partition for Fedora also contained the same files and retained the same UUID as before. When I boot Fedora without the "rhgb quiet" option, the boot hangs at "Booting a command list".Perhaps more concerning is the fact that I could no longer boot from the exact same live USB as before. Thinking it might be a live USB issue, I tried using Fedora Media Writer to create a live USB with the same exact version of Fedora that it contained previously, but the result was the same (hangs when trying to boot from GRUB).Any ideas?(for tldr, just read the title of this post)
Maybe update UEFI or try with rEFInd.
>stealthbumping
>>1522046man, i just dualbooted first time recentlydidn't know you could triple bootstill wondering why i can't access windows w/o turning off secure boot, even did the weird key thing as perplexity.ai suggestedmaybe my windows went not updated for so long/unrelated
>>1522046Get your hex tools out, you have to reshuffle some bytes, happened to me but recovered boot locations pretty easily. Good luck, ask deepseek for help because I'm not going to "Please wait a while before posting"
>>1528269>Good luck, ask deepseek for help because I'm not going to "Please wait a while before posting"You already did.
b
>>1522046Doesn't surface need a special kernel to work fully on Linux?https://wiki.ultramarine-linux.org/en/anywhere/surface/
what if you copypaste op post into https://www.perplexity.ai
>>1529282buy an ad
>>1522046Can you post “parted -l” output
>>1526378you probably got a rootkit or bootkit, it won't boot without secure boot because the OS or bootloader on the drive have been tampered with
>>1533004i meant with secure boot***
>>1522046Two recommendations:First, try chrooting into your Fedora partition from Linux Mint or a live CD and then running update-grub (mkconfig-grub if you don't have update-grub) with os-prober enabled in /etc/default/grub. This should regenerate the GRUB entry in /boot or /efi and fix the mistakes introduced when you shrunk the Fedora partition and then GRUB will just work. Now, if that doesn't work, you can manually boot/chainload from GRUB, where you issue a series of commands issue options, the kind of stuff GRUB is meant to automate. I did this a few times to get into a FreeBSD partition and it was a bit of a hassle but you can figure it out.Worst case scenario, take what's valuable from the Fedora partition and reinstall it.
>>1526378>why i can't access windows w/o turning off secure bootYour Linux OS could have updated the SecureBoot dbx, which holds the list of revoked keys. Microsoft have probably revoked the old key used to sign your Windows install, or maybe it expired.Updating Windows should allow you to turn SecureBoot back on.This can happen in the other direction, too, or between two Linux installs.
>>1522046You probably have three bootloaders installed (2 grub + 1 Windows), and at different times you pick "the other grub" thus booting the distro you thought didn't work anymore.Unfortunately, Linux distros configure grub in a very naive way where they assume that only one Linux distro can be installed on the machine. This is wrong and stupid, the Windows installer could identify multiple installs since at least XP.The solution that I use is to configure grub manually and disable the `update-grub` functionality of each distroso they don't override my config.
It's been SIX MONTHS since OP made this thread, if he hasn't fixed it by now he never will.
>>1540580If you read the OP carefully, you'll notice that he has a tendency to revisit things after 6 months.
