this post was submitted on 05 Nov 2024
23 points (96.0% liked)

Linux

8091 readers
17 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

  1. Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.

  2. Be respectful: Treat fellow community members with respect and courtesy.

  3. Quality over quantity: Share informative and thought-provoking content.

  4. No spam or self-promotion: Avoid excessive self-promotion or spamming.

  5. No NSFW adult content

  6. Follow general lemmy guidelines.

founded 1 year ago
MODERATORS
MigratingtoLemmy@lemmy.world
23
OS Boots on one device but fails to boot on another (mander.xyz)
submitted 1 week ago* (last edited 5 days ago) by TonyTonyChopper@mander.xyz to c/linux@lemmy.world
11 comments fedilink hide all child comments
 

Hi, I just did my first Linux install (Kubuntu) onto an external NVME drive. It boots fine on my laptop but gives me a "MBR error, insert floppy" screen when I try to run it on my desktop. On the motherboard settings the drive shows as a bootable option but without a UEFI label. What issues could cause this? From what I've read it seems like a boot loader problem but I have no idea why it would be fine on one device but not another. I tried to update the motherboard firmware but the file the manufacturer provides wasn't working. It's running a 2021 version.

Edit: I figured it out. The issue had nothing to do with my Linux installation. My motherboard had a hidden option to change the UEFI boot order, which is entirely separate from choosing which drive to boot from.

you are viewing a single comment's thread
view the rest of the comments
[–] BCsven@lemmy.ca 2 points 1 week ago (1 children)

Is secure boot turned on? If so you will probably need to turn that off. EFI boot entries get set in the UEFI somehow, so once you get it booted it should see it. But how old is the PC? Could be a limitation if it is old.

[–] TonyTonyChopper@mander.xyz 1 points 1 week ago* (last edited 1 week ago) (1 children)

In the bios options it shows that secure boot is already disabled. It's not an old pc. I got it around 2021. Z590 motherboard. I've already run a system image off of a USB drive, which is how I installed the OS originally.

[–] BCsven@lemmy.ca 1 points 6 days ago (1 children)

Hmm. I did have one machine that would install from USB but would not boot after. Turned outbit was a hardware glitch deb and deb derived distros could not get past, so I found RPM based worked fine as did NixOS (weirdly)

[–] TonyTonyChopper@mander.xyz 2 points 5 days ago (1 children)

I figured it out. The issue had nothing to do with my Linux installation. My motherboard had a hidden option to change the UEFI boot order, which is entirely separate from choosing which drive to boot from.

[–] BCsven@lemmy.ca 1 points 5 days ago

Awesome