Arch Install Gone Wrong, Need Clarification

i've been on arch for more than a year, but this time i'm installing on uefi and i'm losing my mind. when i boot my laptop, systemd-boot only shows one option, to boot into the bios. i can't figure out where i had gone wrong but i think it might be how i mounted the esp. i installed off a usb plugged into my laptop. i have a a boot partition in fat32, mounted at /mnt/boot/efi, a swap and an encrypted root partition on the third partition, mounted at /mnt. should i have mounted at /efi & / or maybe at /boot/efi & /? where did i go wrong? when installing systemd-boot i went bootctl install without options. did i mount right?

Black Rifle Cuck Company, Conservative Humor Shirt $21.68

DMT Has Friends For Me Shirt $21.68

Black Rifle Cuck Company, Conservative Humor Shirt $21.68

  1. 2 months ago
    Anonymous

    linux mint could save you

    • 2 months ago
      Anonymous

      *vomits

    • 2 months ago
      Anonymous

      Yes there is boot-repair on mint livecd I use to unfrick my grub periodically

    • 2 months ago
      Anonymous

      No need I don't want tranies to join Linux.

  2. 2 months ago
    Anonymous

    >systemd-boot
    There's your problem. Use EFISTUB.

    • 2 months ago
      Anonymous

      ok. not the point tho, i have the same issue with grub. im doing something wrong.

      • 2 months ago
        Anonymous

        1. Make sure you have an initramfs that can open encrypted volumes.
        2. Arch will install your kernel to /boot (or /mnt/boot from the iso).
        The kernel looks like "vmlinuz*"
        Because /boot is not your efi partition, systemd-boot won't be able to find it.

        Grub is capable of detecting kernels on ext4, but it can't decrypt and find it (technically it can, but not in most normal configurations).
        So the problem is that your initramfs and kernel are in /boot instead of /boot/efi
        The Archtard solution: reinstall but mount your efi to /boot
        The Gentooman solution: compile your own kernel instead of using arch packages and put it and the initramfs in /boot/efi
        The Slacker solution: mv /boot/vmlinuz* /boot/initramfs* /boot/efi

  3. 2 months ago
    Anonymous

    USE ARCHINSTALL

    • 2 months ago
      Anonymous

      i probably will anyway but i'd still like to find out where i was wrong

    • 2 months ago
      Anonymous

      *UNINSTALL

  4. 2 months ago
    Anonymous

    Is your boot partition in /mnt/boot or /mnt/boot/efi? Here is mine for comparison.

  5. 2 months ago
    Anonymous

    >systemd-boot
    when will you learn that systemd is bugware?

  6. 2 months ago
    Anonymous

    you probably haven't made your arch.conf on esp/loader/entries
    I fell for that too when installing with systemdboot, there is an example on the wiki

  7. 2 months ago
    Anonymous

    imbecile wojakposter, there's a thread for linux questions

  8. 2 months ago
    Anonymous

    >pic
    Sorry, I'd rather be a chud than a cuck

  9. 2 months ago
    Anonymous

    have you tried mounting it at /mnt/boot only?
    and specifying bootctl's path?
    bootctl --path=/boot install

    • 2 months ago
      Anonymous

      (op here) actually, this might be the solution. looking at how archinstall went about it, it seems it had done exactly that. they also used partuuid instead of uuid in the config file but that's probably not important.

      • 2 months ago
        Anonymous

        You don't understand *why* though, which is the problem. Arch babbies refuse to learn Linux.
        You can't boot an encrypted kernel - (well GRUB can, but this is for advanced users only).
        pacman installs your kernel in /boot
        So if /boot is on the encrypted root partition, and unencrypted boot is on /boot/efi, then there is no unencrypted kernel for you to boot into.

        • 2 months ago
          Anonymous

          what if i mounted the esp partition at /mnt/efi and ran bootctl install whitout options like it says in the manual?

  10. 2 months ago
    Anonymous

    filtered

  11. 2 months ago
    Anonymous

    Hi, I am here because I noticed what appears to be a soijak in the OP thumbnail. I am not reading that image or your post, however I would like to extend my deepest hopes that you are unable to solve this problem.

  12. 2 months ago
    Anonymous

    /boot/efi/ /boot still holds some configs i dont know anyone that uses systemd-boot yuck this might help heres my steamdick layout
    ls /boot/
    amd-ucode.img efi grub initramfs-linux-neptune-61-fallback.img initramfs-linux-neptune-61.img vmlinuz-linux-neptune-61
    sudo ls /boot/efi
    [sudo] password for deck:
    EFI SteamOS

  13. 2 months ago
    Anonymous

    Edit /etc/default/grub to your liking,

    grub-install --target x86_64-efi --efi-directory=/boot --bootloader-id=brainlet

    grub-mkconfig -o /boot/grub/grub.cfg

Your email address will not be published. Required fields are marked *