 |
Additional information on the machine. screenshot_1709653513341.png (125,609 bytes) |
 |
Thank you for the report. We unfortunately don't have access to these types of machines. We will try to and attempt to investigate. In the meanwhile, could you please do a fresh installation of 9.3 and run the following: dnf install sos -y sos report --clean It will obfuscate system information as necessary and produce a tar ball that we can look over while we try to get access to a similar instance. If possible as well, we'd like to see the output from keyctl. We don't expect secure boot, but it doesn't hurt to know whether or not this is the case. dnf install keyutils keyctl show %:.platform cat /proc/keys |
 |
It is not secureboot related, we don't have signed shim for aarch64 out yet , and just to be clear, you do reach grub menu and then you select the new kernel and it just goes blank? or you don't reach grub menu? |
|
|
Thank you for looking at this. I reinstalled with Rocky 9.3 from vault and it works fine: kernel-5.14.0-362.8.1.el9_3.aarch64 grub2-common-2.06-70.el9_3.1.rocky.0.2.noarch grub2-tools-minimal-2.06-70.el9_3.1.rocky.0.2.aarch64 grub2-tools-2.06-70.el9_3.1.rocky.0.2.aarch64 grubby-8.40-63.el9.aarch64 grub2-efi-aa64-2.06-70.el9_3.1.rocky.0.2.aarch64 shim-aa64-15.6-1.el9.rocky.0.2.aarch64 I am not sure whether this is grub2 or kernel. My gut tells me it is actually kernel. I will see if I can find a time slot to debug a bit more or maybe get Hetzner to help. |
|
|
I apologize that I wasn't able to debug further until now. I can confirm that the issue is gone with current rocky: kernel-core-5.14.0-427.18.1.el9_4.aarch64 grub2-efi-aa64-2.06-77.el9.aarch64 shim-aa64-15.8-2.el9.aarch64 |
- Anonymous
