this post was submitted on 04 Jan 2024
631 points (94.8% liked)

linuxmemes

21180 readers
992 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
    [email protected]
    [email protected]
    [email protected]
    631
    It happens 🤷 (sh.itjust.works)
    submitted 10 months ago by [email protected] to c/[email protected]
    199 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 1 points 10 months ago* (last edited 10 months ago)

    If it takes too long to load the EFI binaries, that might be BIOS setup issue. Have you tried other filesystems except FAT32 for the EFI partition? I've had luck with just FAT (FAT16) on some rigs that just refused to read FAT32 (still don't know why).

    Also, make sure the drives are in AHCI mode. Though this is mostly the default nowadays, I've seen weird BIOSes that defaulted to IDE mode.