You're right. Someone somewhere used Tom Cruise as Superior Iron Man. (I'm uploading an image in the comments for the first time on Sync, so it might not work. Hopefully, it does)
redimk
That's so cool, how do you personalize it like that?
I've been using Fedora for a month (I just started using Linux a month and a half), and I can't seem to find a way to do it.
The blue one on the left is Blue Beetle, no idea who the right one is.
Sorry for my ignorance, but how does that work? I (think) I understand what a kernel is, but how am I using Fedora 39 with a 38 kernel? Is there a documentation I can read somewhere so I can understand how that works?
Today it got fixed somehow, I just booted up Fedora 39 and it just worked. Also thanks a lot for the answer!
Just shut down the damn app by this point, man.
I chose sysremd, I didn't have time to fix the issue as I needed my laptop for work so I just did a clean install of everything once again. I think I will keep trying Fedora but I will read the documentation of EOS first so I can understand what I'm doing, I can't afford to make the same mistake again lol. I think what happened is that I accidentally erased the Windows EFI partition somehow and that's why it was not going in.
Is there an actual difference between those? Is one better than the other or it's just the OS giving options?
This is what I'm thinking happened. I already said this in another comment but will expand here because this comments refers specifically to the EFI partition. Here's the weird thing, 3 days ago, I had 2 SSDs:
- 1 with 3 partitions of Windows, one EFI part., one recovery part, and the regular C: local where my files were.
- On my secondary SSD, I had Fedora installed. If I'm correct, I had a /boot, and /home(?) don't remember if anything else.
I decided to do a clean install of Win11. When I did, I had both SSDs connected to my laptop, and when I finished the installation, this was how it was divided:
- 1st SSD: one, full 2TB C: Local disk, with no partitions.
- 2nd SSD: One EFI partition, one recovery partition, and one "empty" partition.
It was highly confusing, because I thought I had Fedora there, my immediate thought was that Win11 just straight up ravaged both my SSDs and decided "fuck it, let's install wherever the fuck I want" and it did. HOWEVER I could still get into Fedora and use it normally. Still had all the apps and programs I installed, everything was correct. So I assumed the drive still belonged to Fedora.
When I installed EOS, I chose "Erase Disk" on the secondary SSD (the one with Fedora, the one that had this "EFI partition" that didn't have before. I think when I erased that SSD, I erased the Windows EFI partition and couldn't boot as a result. And that's why the BIOS was not recognizing the OS, but at the same time I could just mount the SSD in EOS and just look t my files normally. So I think that's what happened, but honestly I'm not even sure of how it happened.
I tried all orders, there were 2 Samsung SSDs (primary and secondary), and another one called "EFI" something... When I changed the order to SSD #1 it opened EndevourOS, when I changed to SSD #2 it said "checking media........ failed", and when I put the "EFI" as the first in the order, it just restarted and went again to EndevourOS. At the end, I had to do the easiest and fastest thing: start over.
I think that when I installed Win11, it took part of my Fedora partition somehow, I'm not even sure if that's what happened and if that is what actually happened I have no clue how it happened, but right before erasing my secondary SSD to install EOS, there was a mention of a Windows "EFI" partition there, even though I could still get into Fedora. So when I erased that, I think I erased something related to Windows that I shouldn't have erased
This is what I think happened that I wrote on another comment:
It's weird, but I had Fedora installed on my secondary SSD. Apparently when I did a clean Windows install, it installed in the primary SSD but took a part of Fedora on the secondary SSD as a Windows EFI partition. Then, when I installed EOS I selected "erase the disk" for the secondary SSD. I think it erased that EFI partition and I couldn't go back to windows, but since the primary SSD still had my files I could still see them. To be honest, something like that never happened before so I'm not even sure of what I'm saying.
Tbh I'm not even sure if that's what happened, I just didn't find an easy solution apart from starting over.
I was using UEFI I think? I used Rufus to make the bootable flash drive and it just gave me either MBR or GPT, when I selected GPT it showed me the UEFI option to the right (iirc). I spent all day seeing these comments and at the end of the day I had to delete everything in my hard drives and start over again...
It's weird, but I had Fedora installed on my secondary SSD. Apparently when I did a clean Windows install, it installed in the primary SSD but took a part of Fedora on the secondary SSD as a Windows EFI partition. Then, when I installed EOS I selected "erase the disk" for the secondary SSD. I think it erased that EFI partition and I couldn't go back to windows, but since the primary SSD still had my files I could still see them. To be honest, something like that never happened before so I'm not even sure of what I'm saying.
That's the problem not even the bios is reading windows after the EOS installation. I keep changing the order of things but when I boot from the other SSD it just says "checking media" and then "failed" and it gets looped over and over again.
But I can still see the windows drives and partitions from EOS... It's the weirdest ting that I've seen... Would you recommend just doing a clean install of everything in that case?
As someone who just started using Linux not so long ago, I'm just curious, why is anything to do with Flatpak a concern?