this post was submitted on 07 Jan 2024
1006 points (97.7% liked)

linuxmemes

21434 readers
766 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
     
    (page 2) 50 comments
    sorted by: hot top controversial new old
    [–] Unyieldingly@lemmy.world 2 points 10 months ago
    [–] TheFerrango@lemmy.basedcount.com 2 points 10 months ago

    No need to fix it, the bootloader is safely installed on a write-protected floppy disk

    [–] rickyrigatoni@lemm.ee 1 points 10 months ago (4 children)

    I had used Arch for years before and never once messed up my bootloader. What are yinz doing over there?

    [–] 0x4E4F@sh.itjust.works 1 points 10 months ago

    You probably had it installed in MBR mode. UEFI boot is why there are so many problems of this kind nowadays. Switch to MBR, the problems go away.

    [–] pete_the_cat@lemmy.world 1 points 10 months ago

    My problems are usually during the installation, not necessarily related to Arch, but more so that EFI requires its own partition. I'll partition my disk, forget that I need a FAT32 partition and then have to destroy a partition so I can add in the EFS . The other problem I've had is that the bootloader entry sometimes doesn't get written after installation, so you reboot and then nothing, so you have to boot back into the ISO, remount everything, reinstall the bootloader (in my case, Grub), and reboot again.

    load more comments (2 replies)
    [–] cows_are_underrated@feddit.de 1 points 10 months ago

    Im happy that I haven't fucked up the bootloader so far. Don't want to fix that shit too.

    [–] redditReallySucks@lemmy.dbzer0.com 1 points 10 months ago (1 children)

    I just killed my desktop environment but the bootloader works.

    [–] 0x4E4F@sh.itjust.works 1 points 10 months ago

    That is good news actually.

    load more comments
    view more: ‹ prev next ›