this post was submitted on 21 Jan 2024
1742 points (97.8% liked)
linuxmemes
20880 readers
3 users here now
I use Arch btw
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
Community rules
- Follow the site-wide rules and code of conduct
- Be civil
- Post Linux-related content
- No recent reposts
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Hard to tell from the info you provided. It might be a mixup between legacy MBR and UEFI boot. Try enabling legacy boot in UEFI and make sure the boot order is correct, if your PC is really that old it might just be that your Windows install is still booting from the MBR.
I'll try that, it's actually the opposite, it has an uefi switch in the bios since it's so old it probably was the standard to use legacy boot, guessing by the CPU (core 2 duo, idk what model though) it's probably a 2007/08 prebuilt (by the weird PSU)
It would make sense that it would be a problem with windows if it didn't have the uefi setting on, but it still doesn't explain the "Ubuntu success" message I got instead (and that was the case when the Linux drive was completely disconnected )
Will reply after I try it out, if it doesn't work I'll try the CMOS instead, if that doesn't work either then I guess I fucked up my computer beyond repair
Unlikely, only misconfigured. The "Ubuntu success" message might show because your PC tries to boot from a GPT partition on a different disk or you have inadvertently overwritten the Windows bootloader. Booting from a live USB should work but it might take a couple of tries depending on what settings you have changed in the UEFI; also check if your flashdrive is working properly. Apps like the Fedora Media Writer or Rufus can check if the image is not corrupted after writing it to the drive.
Idk, in Rufus I set it to MBR (well it set to that automatically if I'm not mistaken) since I didn't know if it would support GPT (it's an old pc as I said), also I only had a single sata cable available so I installed it without the windows drive connected, the error message popped up only after I replaced the drives and tried to boot to the windows one, which wss supposed to be untouched, also as I said no bootable media (I made with Rufus, I could try balena etcher or what you said) but it just skips the boot media when i turn it on, even if i set it to the highest priority in bios (tried Debian, mint, kubuntu, but I'll try fedora to see if it's any different)
When I was making the drives in Rufus it didn't say anything when writing to the drive