Created attachment 1792895 [details] last output before bootloop with debug=all Description of problem: After creating live USB with dd, I booted from the Aarch64 boot disk on Lenovo Flex 5g. Secure boot was disabled. The grub menu was displayed. after selecting any option, whether it be safe graphics, or regular, it immediately bootloops back to the grub menu. I attempted to get information by setting "debug=all". I have attached a screen image below of some of the last debug messages that were shown. Version-Release number of selected component (if applicable): Fedora-Workstation-Live-aarch64-34-1.2 How reproducible: easily reproducible Steps to Reproduce: 1. Boot a USB of Fedora workstation 34 Aarch64 2. select any boot option 3. Actual results: System immediately reboots back to the grub menu Expected results: system boots from the USB properly Additional info: (screen image attached)
By looking at the shared output, GRUB is executed up to when the control is passed to the kernel by jumping directly to the PE/COFF entry point: ... pe = (void *)((unsigned long)kernel_addr + lh.hdr_offset); handover_offset = pe->opt.entry_addr; ... grub_err_t grub_efi_linux_boot (void *kernel_addr, grub_off_t handover_offset, void *kernel_params) { grub_efi_loaded_image_t *loaded_image = NULL; handover_func hf; int offset = 0; #ifdef __x86_64__ offset = 512; #endif /* * Since the EFI loader is not calling the LoadImage() and StartImage() * services for loading the kernel and booting respectively, it has to * set the Loaded Image base address. */ loaded_image = grub_efi_get_loaded_image (grub_efi_image_handle); if (loaded_image) loaded_image->image_base = kernel_addr; else grub_dprintf ("linux", "Loaded Image base address could not be set\n"); grub_dprintf ("linux", "kernel_addr: %p handover_offset: %p params: %p\n", kernel_addr, (void *)(grub_efi_uintn_t)handover_offset, kernel_params); hf = (handover_func)((char *)kernel_addr + handover_offset + offset); hf (grub_efi_image_handle, grub_efi_system_table, kernel_params); return GRUB_ERR_BUG; } So the issue should be on the boot protocol used by GRUB, or very early in the kernel boot process. More investigation will be needed to figure that out.
Moving this to the kernel component, since as mentioned it hangs after GRUB has jumped to the Linux PE/COFF entry point.
I don't think there has been any serious work on booting Linux on these devices since https://github.com/aarch64-laptops/build At the moment the easiest way to "run" Linux on them is via hyper-v which works with a slight out of tree patch here: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1393
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. Thank you for reporting this bug and we are sorry it could not be fixed.