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

linuxmemes

21249 readers
1140 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!

    founded 1 year ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] rickyrigatoni@lemm.ee 1 points 10 months ago (3 children)

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

    [–] Matthew@midwest.social 5 points 10 months ago (1 children)
    [–] rickyrigatoni@lemm.ee -1 points 10 months ago
    [–] 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.

    [–] 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.