Install openEuler-24.03-LTS-SP3-DevStation-x86_64-dvd

[whl571]

I encountered an error while installing openEuler-24.03-LTS-SP3-DevStation-x86_64-dvd.iso on a platform with an Intel I7-12700 processor. Has anyone else experienced this issue? Or are there specific steps required when installing this version? Any guidance would be greatly appreciated!

[euler_assistant (openEuler_Assistant)]

The content provided is AI-generated and for reference only:

Analysis and Recommendations for openEuler 24.03 LTS SP3 DevStation Installation Issues

Based on the information you’ve provided, you are attempting to install openEuler-24.03-LTS-SP3-DevStation-x86_64-dvd.iso on a platform equipped with an Intel i7-12700 processor (Alder Lake architecture), but encountering installation errors. Below is a comprehensive analysis of potential causes and recommended solutions.

---

Core Issue: Hardware Compatibility and Boot Mode

Although you haven’t directly shared the error log, given your use of a 12th-generation Intel processor (Alder Lake) and known behavior of openEuler, the installation failure is likely due to one or more of the following:

1. CPU Instruction Set Requirements (x86-64-v2)

The openEuler 24.03 series is built using newer binary standards (e.g., x86-64-v2), which require support for certain modern instruction sets such as SSE3, SSE4.1, SSSE3, SSE4.2, and POPCNT.

• The i7-12700 supports all these instruction sets , so compatibility should not be an issue in theory.
• However, some older openEuler images or specific branches (especially developer editions) may lack compatibility optimizations and could trigger initialization errors during boot.

Recommendation: Ensure you are using the official standard image, not a custom or trimmed version.

---

2. Boot Mode: UEFI vs BIOS

Your BIOS screenshot shows AMI UEFI BIOS (version 6157I106), indicating your system is running in UEFI mode.

• The official openEuler ISO (especially from 24.03 onward) fully supports UEFI.
• However, if the bootable USB was created with incorrect tools or settings (e.g., forced MBR partitioning), it may result in boot failure or kernel loading issues.

Note: Even though your machine supports UEFI, if the USB drive was created in Legacy BIOS mode or misconfigured by tools like Ventoy/Rufus, it can still cause installation interruption.

---

3. Kernel Panic or DNF Installer Errors (Common in DevStation Editions)

The DevStation variant is designed for development and testing, and its kernel, package manager (e.g., DNF), or graphical installer (Anaconda) may include experimental updates.

Possible error types include:

• Kernel panic after boot
• DNF errors: missing packages, dnf.exceptions.Error
• Anaconda installer crashes or freezes
• systemd-shutdown loop (as seen in your screenshot)

The repeated systemd-shutdown messages and device unmounting logs at the end of your log are likely traces of the system automatically shutting down after installation failure, not the root cause itself.

---

Common Solutions and Troubleshooting Steps

1. Verify Image Integrity

Ensure the ISO file is not corrupted:

# Download the corresponding SHA256 checksum file
sha256sum openEuler-24.03-LTS-SP3-DevStation-x86_64-dvd.iso

Compare the output with the official hash value available at https://repo.openeuler.org under the correct release path.

---

2. Correctly Create Bootable USB (Recommended Tools)

Tool	Recommended	Notes
Rufus	Use with caution	Run as Administrator; select “DD mode” or “ISO mode” to avoid filesystem issues
balenaEtcher	Recommended	Cross-platform, reliable, and safe
Ventoy	Recommended	Supports multiple ISOs, excellent compatibility
dd command	Recommended (Linux)	Lowest-level write, no compatibility issues

Error: “Unable to create file: [0x00000052]” indicates insufficient permissions or USB device being used in Windows — always run Rufus as Administrator.

---

3. Modify Kernel Parameters to Avoid Graphics Issues (Critical!)

Try editing the boot entry in GRUB by pressing e at startup, and add one of the following parameters:

Recommended parameter combination:

nomodeset quiet splash intel_iommu=off

Or simply:

nomodeset

Purpose:

• nomodeset: Prevents the kernel from loading graphics drivers; uses basic framebuffer display
• The 12th-gen Intel integrated graphics (UHD 770) sometimes conflicts with open-source drivers, causing black screen or installation freeze

After adding the parameter, press Ctrl + X to boot. Check if you can reach the installer interface.

---

4. Try Text-Based Installation Mode (Text Mode)

At the boot menu, choose:

“Test this media & install openEuler”
or
“Troubleshooting → Install in basic graphics mode”

This skips the graphical environment and uses minimal drivers for installation.

---

5. Check BIOS Settings

Enter BIOS (you’ve already provided a screenshot), and confirm the following settings:

Setting	Recommended Value
Secure Boot	Disabled (to avoid signature verification failures)
CSM (Compatibility Support Module)	Disabled (enforce pure UEFI mode)
Fast Boot	Disabled
SATA Mode	AHCI
Virtualization Technology	Enabled (if running virtual machines)

Your BIOS version is relatively recent (July 2024), so compatibility issues are unlikely.

---

6. Try the Non-DevStation Version

The DevStation edition is a development build and less stable than the standard version (Standard or Everything).

We recommend switching to:

openEuler-24.03-LTS-SP3-everything-x86_64-dvd.iso

This version includes more complete drivers and debugging tools, making it better suited for production environments or complex hardware setups.

---

Reference Cases (From Community Reports)

• Users reported openEuler 24.03 failing to install on MacBook M-series chips → Not supported (ARM architecture)
• Multiple users successfully installed in VMware/VirtualBox, but failed on physical machines → Boot media or driver issues
• Installation failed with Rufus → Permission or mode error (must use DD mode)
• Kernel Panic occurred on NVIDIA NF5270M5 server during 24.03 install → Similar hardware compatibility issue (like yours)

---

Summary Recommendations (Action Checklist)

Action	Required?
Verify ISO SHA256 hash	Mandatory
Recreate bootable USB using balenaEtcher or Ventoy	Strongly recommended
Add nomodeset parameter in GRUB at boot	Critical step
Disable Secure Boot and CSM in BIOS	Recommended
Try Everything version instead of DevStation	Recommended
Access detailed logs via Ctrl+Alt+F2 during install	For further diagnostics

---

Still Not Working?

Please provide the following details for deeper analysis:

1. Exact error text or screenshot from the installation failure (especially English error messages)
2. Can you switch to a console (Ctrl+Alt+F2) to view logs?
3. Which tool did you use to create the USB boot drive?
4. Have you tried the nomodeset parameter?

---

Official Resources:

• Image Download: https://repo.openeuler.org
• Documentation Center: https://docs.openeuler.org
• Community Forum: https://bbs.openeuler.org

Wishing you a successful installation! If you have additional logs, feel free to share them for further assistance.

[xiejirong]

“Reached target system halt”

It’s not clear why it stopped—whether you issued a shutdown command yourself or not, you’d still end up here.

Were there any other messages in between? No error messages at all?

[whl571]

I started the installation with a USB drive, and immediately got stuck on this screen. It’s strange because I didn’t perform any power on/off actions.

[whl571]

The issue has been resolved.

Using Ventoy to boot the ISO file for devstation installation fails and shows an error. However, writing the devstation ISO to a USB drive using Rufus and then booting from the USB drive works fine for installation.