You are not logged in.
Pages: 1
Hello,
Something like 2 years ago, I installed an arch on a laptop for a friend. At that time, I already had some difficulties to install the bootloader. Recently, an update broke the boot process. No big deal in theory, but I can't manage to fix it. I read multiple time the arch wiki, but I obviously did something wrong, and I cannot manage to fix it, no matter witch bootloader I try, neither grub, nor systemd-boot works. In both cases, arch cannot start. When `arch-chrooting` from an usb key, everything seems to works fine. I even tried to un-install grub, format the uefi partition, and then install `bootctl`.
Could a kind stranger give me some advices on how to install a boot manager, on the most simple way possible.
Her config is a thinkpad laptop with an intel cpu. There is no lvm, no encryption, no btrfs, no nothing special. Except for UEFI (bios just worked, uefi was always a pain to set-up in my experience, I don't know what I'm doing wrong).
I created 2 partitions, the first for `/` (no separate partition for `/` and `/home`) in `ext4`, and the second for the efi in fat32. Is it the simplest choice? What is the most basic setup for single boot, single user? Having a separate partition for `efi`, or a single partition for everything? If `efi` need to be in another place, where should I mount it? In `/boot/EFI` or just `/boot`?
What bootmanager is the closest to 0 config? What is the minimal steps to have that kind of computer. Is there anything to do about microcode (and if yes, why? She don't have an exotic cpu architecture).
Basically what I tried (excluding non-bootloader stuff) was
mkfs.ext4 /dev/sda2 # the / partition
mkfs.fat -F32 /dev/sda1 # the efi partition
mount /dev/sda2 /mnt
mount /dev/sda1 /mnt/boot
pacstrap /mnt base linux linux-firmware intel-ucode
arch-chroot /mnt
bootctl install
exit
reboot
I will probably install manjaro instead, but I would have liked to understand the right procedure.
Offline
Looks like you missed configuring it.
Offline
I don't know what I'm doing wrong
Other than installing an arch system for someone else who doesn't know how it works while you yourself don't seem to really know how it works? Well, that's the biggest problem.
What is the minimal steps to have that kind of computer.
Follow the installation guide and linked pages. There are no shortcuts (that work).
Is there anything to do about microcode (and if yes, why? She don't have an exotic cpu architecture).
Yes. Because. "Exotic" architectures have nothing to do with it.
I will probably install manjaro instead, but I would have liked to understand the right procedure.
The right procedure for arch is thoroughly documented in the wiki. Read it. Ask specific follow up questions is needed, but don't expect anyone here to read it to you. As for manjaro, we can't tell you anything about that here; ask on their forums.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
> The right procedure for arch is thoroughly documented in the wiki. Read it.
I know I either missread something in either grub or systemd-boot wiki's pages. I successfully installed arch on 5 different pc since 2011 for myself. I successfully helped a friend two install arch on 2 of his machine, and 2 times for another friend. Arch is my daily driver. I never had any issue, except installing the bootloader (and only since uefi exists, I didn't had any issue with bios). There is no way I could have installed successfully arch 9 times without reading and understanding the arch wiki. However, bootloading is still dark magic for me. I didn't wanted to say that in the OP, since it really look that "I'm the kind of guy that think he knows everything, but in fact he doesn't".
> Ask specific follow up questions is needed, but don't expect anyone here to read it to you.
My issue isn't that "I don't know how to do something" (you can ask a question for that), but that "I don't know what I don't do" (you can't ask a question for that). It's why I posted the codeblock at the end of my post to describe what I did. If something obvious is missing, then please tell me.
> As for manjaro, we can't tell you anything about that here; ask on their forums.
I should not have mentioned manjaro. It's just that I'm really frustrated to have to switch OS, just because I can't install a bootloader. I also know that if I install a dual boot with ubuntu, only to have grub installed (from ubuntu), just to be able to boot arch it will work, but it's anything but ideal. Oh, and by "right procedure", I meant "right procedure [to install a bootloader with archlinux]".
Offline
As mentioned by Scimmia, the obvious thing that is missing that you didn't add a configuration for systemd boot. https://wiki.archlinux.org/index.php/Sy … figuration
You need at least a entry file specifiying the loading parameters for the kernel you intend to start and will for completeness sake have to specify a loader.conf to define the default and a selection timeout.
Offline
Thanks a lot, I will check that.
Offline
What i dont get is how it was working before, without a loader conf?
Can you please paste it here if it exists? And also check the systemd-boot status?
I live at the Internet
-Edward Snowden
Offline
Pages: 1