I downloaded the official 2403-LTS-SP1 ISO and attempted to install it on a KP920 physical machine. The process froze right before entering the Anaconda installation interface. I waited nearly 10 minutes, but it remained unresponsive. Has anyone else experienced this?
From the screenshot, the service has entered the installation environment startup phase, but no clear failure reason is displayed. The last few lines are stuck at OpenSSH key generation, which doesn’t necessarily indicate an issue with SSH.
If there’s no specific business requirement or compatibility constraint forcing the use of SP1, you may want to first try the aarch64 standard installation image of openEuler 24.03 LTS SP3:
After downloading, it’s recommended to verify the ISO’s SHA256 checksum against the provided file to rule out corruption during download or storage.
Additionally, could you please provide the full server model and current installation method? Are you mounting the ISO via the BMC’s virtual optical drive, or booting from a USB drive? If using a USB drive, were you using Rufus, Ventoy, UltraISO (SoftEther), or the dd command to create it? Different creation methods can affect the boot process.
If currently booting from a USB drive, you may also try using the BMC virtual optical drive to directly mount the original ISO and compare results.
Just check whether SP3 can successfully reach the installation interface. If it still hangs, please share another screenshot from that moment, and specify the installation method used this time. I’ll then analyze the exact point of failure. If SP3 also fails and you’re willing to proceed further, we can also test with the SP4 image for comparison.
I also tried the 2203-SP3 ISO, and it got stuck at the same spot.
Installation method: Installed directly using the dd command to create a bootable USB drive.
I’ll give the two ISOs you mentioned a try as well.
Additionally, there are customized boards for the 5252C.
You can refer to the follow-up discussion on this kernel issue. Although the original title mentioned the Phytium D2000, subsequent comments reported similar issues where the screen froze around Starting OpenSSH rsa Server Key Generation. Others observed that although the screen stopped updating, the system had actually already booted. Therefore, it’s worth first distinguishing: is the installation environment truly stuck, or is it merely that the display output is no longer updating? Similar visuals alone are not sufficient to confirm it’s the same underlying issue.
I checked the actual GRUB configuration in the release directory, and indeed, the several images differ in their display parameters:
- 24.03 SP1 includes
video=efifb:off video=VGA-1:640x480-32@60me, with these settings preserved in the basic graphics mode—your tested 22.03 SP3 is the same. - 24.03 SP3 no longer includes these lines, but still provides basic graphics mode, using additional parameters like
nomodesetinstead.
Therefore, removing video=efifb:off as suggested in the older discussion cannot be directly applied to the current SP3, since that setting was never present in the first place. Next, you can try the following using the already-prepared SP3 boot media.
Try basic graphics mode first
In the boot menu, go to Troubleshooting --> and select:
Install openEuler 24.03-LTS-SP3 in basic graphics mode
Observe whether the installation interface proceeds normally.
If it still hangs at the same point, try text mode installation
Boot again, press e on the standard Install openEuler 24.03-LTS-SP3 option, and locate the line starting with linux /images/pxeboot/vmlinuz. Keep the existing parameters, add a space at the end, and append:
nomodeset inst.text
Then press Ctrl+X or F10 to boot. This change is temporary and doesn’t require rewriting the USB drive.
Here, nomodeset disables kernel-driven display mode settings, while inst.text instructs Anaconda to use a text-based installation interface. These two attempts can help determine if the issue is related to basic graphics mode or skipping the graphical installer altogether.
If both approaches still result in the system hanging, and your machine has a serial console or BMC serial-over-LAN (SOL) available, it’s recommended to monitor the serial output in parallel. The serial console may continue to show logs after the video screen freezes, which can help distinguish whether the problem is visual (e.g., display driver issue) or actual boot failure. The exact serial port and baud rate depend on your board’s configuration and cannot be assumed from other systems.
Please first report which step showed any change. If no change occurs, and you have access to serial logs, please share the output around the time of the freeze.
Okay, thank you. Using inst.text to enter text mode allows you to access the installation interface and proceed with the following steps.
We’ll need to add another console parameter as well.
If you’ve already successfully completed the installation, feel free to share the full kernel boot parameters you used during installation (the linux ... line in the GRUB menu on the installation disk), including any console= settings you added. This will help others who encounter similar issues in the future to reference your specific configuration and avoid unnecessary detours.
