-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
eos_bootloader should not remove the only installed kernel (arm) #55
Comments
We never used that module on ARM. Are you allowing people to choose a bootloader? |
Well, I don't see why not, however, I only tried systemd-boot since its' configs are a bit easier to write and they're generally not autogenerated (unlike grub). All Snapdragon X laptops have UEFI, so it's basically the same setup as what x86-64 device would have. |
If your kernel is getting removed, it is possible it is incorrectly packaged. kernels should depend on You may need to repackage to fix the dependencies if that is the case. |
If there is interest in getting this working and available .. we could start a new repo for it. Mixing x86 and arm is confusing to me. |
My kernel package depends on coreutils, kmod, mkinitcpio>=0.7, systemd-ukify and x1e-firmware, so I removed dracut from dependencies. Maybe I should switch to it instead though. |
Right, the eos_bootloader removes |
From a Calamares perspective, it sounds like these snapdragon machines are more similar to x86 where they are using UEFI. |
Thanks, I'll try. Does |
Nope. It is totally different. That being said, dracut is quite a bit better at detecting what it needs to add to the initramfs. |
Arch wiki suggests to use |
Okay, there is
Nope, it wasn't enough. Apparently, it now tries to execute mkinitcpio hook (and obviously fails since Which packages I would need to install for dracut to actually work? I do have Here is what I used to build the image: https://github.com/anonymix007/arch-image-builder/tree/x1e |
Is your feature request related to a problem? Please describe.
eos_bootloader module removes the custom kernel needed to boot on Snapdragon X which leads to an unbootable system
Describe the solution you'd like
If package is explicitly listed in
netinstall.yaml
, eos_bootloader shouldn't even try to remove itDescribe alternatives you've considered
Maybe create a separate ARM config in this repo?
Additional context
I was trying to build a more or less generic EndeavourOS ARM image for Snapdragon X laptops. As of now, they require custom kernel and firmware, so here is my repo will all the required packages: x1e-alarm
Calamares config (basically, just removed packages missing in aarch64 repos): config.tar.gz
Installation logs: endeavouros.log.tar.gz
What could I do to make it work as expected?
The text was updated successfully, but these errors were encountered: