I can assist with that. Just let me know what part you're struggling with and I'll guide you through it.
I can assist with that. Just let me know what part you're struggling with and I'll guide you through it.
I'm attempting to set up Arch Linux on my ASUS Chromebook C100P. The installation went through initially, but after a reboot via Ctrl+U, the Network Service and Load/Save RF Kill Switch failed repeatedly, causing endless attempts without success. I've enabled the debug shell for troubleshooting. Someone might have useful advice. The image quality is poor, but thanks for your assistance. I followed the installation guide you linked. My system runs Chrome OS 84.0.4147.136 on an Asus Chromebook Flip C100P with these specs: ARM Mali 760 GPU, 16GB SSD, and 10.1" display.
Ensure you have an arch USB drive and enter the chroot environment. From there, begin diagnosing issues.
You can find the USB file by checking your device downloads folder or the source website where you received it. Let me know if you need further help!
visit the arch website, choose a repository to download the image, flash it onto a USB stick, insert the drive, boot from it, use lsblk to list your block devices, pick the main drive where Arch was installed (adjust based on size), then run chroot /dev/sdX (replace sdX with your label) to enter installation mode and begin troubleshooting your network manager.
Thank you for your input. It seems challenging to start from a USB on your Chromebook since it lacks standard BIOS support and no alternative BIOS was found. I've attempted various solutions online, but none resolved the issue. I've also tried using a custom ISO with the recovery tool, though results remain inconsistent. Please let me know if you'd like further assistance.
skip setting up the primary disk first, instead place it in a mount point such as mnt and then apply chroot there
Hey there, user from x64 and 86 Arch. I saw some strange looping failures earlier, but after checking a bit, it makes sense. When systemd set up multi-user, it usually forces systemd-networkd to run automatically on failure. That’s likely why you’re seeing this behavior. Unfortunately, unless systemd-networkd works properly, normal login will fail. But you can still access the rescue shell (systemd’s rescue.target), which doesn’t require networkd. You might also try enabling debug logs in systemd and manually starting systemd-networkd until you fix things. Once resolved, you should be able to return to a standard login. If you need help, refer to the Archlinux ARM documentation for troubleshooting tips.