this post was submitted on 21 Jan 2024
1732 points (97.8% liked)

linuxmemes

21291 readers
875 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
  •  

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.

    founded 1 year ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 2 points 9 months ago* (last edited 9 months ago) (3 children)

    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.

    [–] [email protected] 1 points 9 months ago (2 children)

    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

    [–] [email protected] 2 points 9 months ago (1 children)

    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.

    [–] [email protected] 1 points 9 months ago

    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