| Summary: | IPFire kernel 4.14.x does not boot on AWS ARM | ||
|---|---|---|---|
| Product: | IPFire | Reporter: | Michael Tremer <michael.tremer> |
| Component: | --- | Assignee: | Arne.F <arne.fitzenreiter> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | Crash | ||
| Priority: | Will only affect a few users | CC: | peter.mueller, peter.mueller |
| Version: | 2 | ||
| Hardware: | unspecified | ||
| OS: | Unspecified | ||
| Attachments: | Boot Log | ||
What is the status of this issue? (In reply to Peter Müller from comment #1) > What is the status of this issue? I didn't try again, because I did not think that it was worth investing the time. Since we have a couple of updated kernels, I could try this again. I uploaded an image again today, but unfortunately there is not a single characters being shown on the serial console. I have no idea how we can debug this. According to Mathew, this could have fixed it: > https://lists.ipfire.org/pipermail/development/2020-September/008335.html I tested this image on AWS this morning: > https://nightly.ipfire.org/next/2020-09-17%2018:53:16%20+0000-b04f532f/aarch64/ And unfortunately did not even get the output from GRUB. Any idea what could have caused that? Okay, I was too impatient. After about 10 minutes, I got the same output as before. Last line is:
> EFI stub: Exiting boot services and installing virtual address map...
Since I am currently walking through Bugzilla again: Any news on this? :-) No, but since ARM on AWS is skyrocketing right now, I am interested in fixing this hopefully with the new kernel. > Loading Linux 4.14.211-ipfire ...
> Loading initial ramdisk ...
> EFI stub: Booting Linux Kernel...
> EFI stub: Using DTB from configuration table
> EFI stub: Exiting boot services and installing virtual address map...
This still does not boot.
Today, AWS released serial console access for all instances. Unfortunately I do not see any output with core155. Not even the bootloader and I do not see it on the "system log" output anymore either. Did we change anything? I think not. Runs amazon the image in uEFI or legacy mode? In uEFI mode the uEFI-firmware should redirect the output to the serial console and in legacy it should output on VGA and COM1 and first boot and you have to choose the correct menuentry to continue use serial port. I believe they are using EFI for ARM. I am aware that I need to select something if I want to see the boot process, but shouldn’t I see GRUB? I assume this has been fixed with Core Update 159 and Linux kernel 5.10.x Please reopen, if necessary. |
Created attachment 646 [details] Boot Log The current aarch64 image does not boot on Amazon's new ARM-based VMs. See the attached log. The kernel does not seem to be able to come up. This has been tested with kernel 4.14.72 and .83 and both show the same log output.