ZimaBlade - ZimaOS 1.7.1 installer black screen during boot unless nomodeset is used
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 55/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- linux
- Área
- operating-systems
Línea de trabajo
Start with /EFI/BOOT/grub.cfg on the installer USB and compare the default kernel command line with the working nomodeset workaround. Reproduce the black screen on a ZimaBlade, then investigate the Intel graphics/KMS initialization mentioned in the report. Done means the installer boots visibly without manual EFI edits, or provides a working safe-graphics boot option.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Summary
The ZimaOS installer does not boot correctly on my ZimaBlade using the default kernel parameters.
The installer starts normally, reaches:
Populating /dev using udev:
and then the display goes black.
I reproduced the same behavior with both ZimaOS 1.7.1 and ZimaOS 1.7.0.
After adding nomodeset to the ZimaOS installer kernel command line, the installer boots successfully and ZimaOS can be installed normally.
This appears to be related to Intel graphics / Kernel Mode Setting (KMS) initialization on ZimaBlade.
Hardware
- Device: ZimaBlade
- Internal storage: 32 GB onboard eMMC
- eMMC model: A3A551
- Display: HDMI
- Installation media: USB flash drive
- Installer USB created with Balena Etcher
- No SATA drives connected during troubleshooting
ZimaOS versions tested
- ZimaOS 1.7.1
- ZimaOS 1.7.0
Both versions showed the same behavior.
BIOS configuration
The following BIOS settings were tested:
Boot Mode: UEFI
CSM Support: Disabled
Boot Option Filter: UEFI
Secure Boot: Disabled
USB Boot: Enabled
Legacy USB Support: Enabled
XHCI Hand-off: Enabled
USB Mass Storage Driver Support: Enabled
SDIO Access Mode: Auto
eMMC: Auto
The USB installer was explicitly booted using the UEFI entry:
UEFI: Mass Storage Device 1.00, Partition 1
Problem
With the default ZimaOS installer configuration, boot proceeds normally at first.
The installer shows:
Booting 'ZimaOS Installer'
and then starts the early userspace services:
Starting syslogd: OK
Starting acpid: OK
Starting klogd: OK
Running sysctl: OK
Populating /dev using udev:
At this point the video output goes black.
In some attempts the system also appeared to reboot and repeat the installer boot process.
Screenshot 1 - ZimaOS stops during early boot
Ubuntu comparison test
To determine whether the problem was caused by the eMMC, CasaOS, USB controller, or general hardware failure, I booted Ubuntu 24.04.3 Desktop on the same ZimaBlade.
Ubuntu using the normal graphics boot path also resulted in a black screen.
However, Ubuntu boots successfully using:
Ubuntu (safe graphics)
Screenshot 2 - Ubuntu Safe Graphics works
This strongly suggests that the issue is related to graphics initialization rather than storage or the ZimaBlade being unable to boot Linux.
eMMC detection
Ubuntu Safe Graphics detects the onboard eMMC successfully.
lsblk shows:
mmcblk0 28.9G
├─mmcblk0p1 512M vfat
├─mmcblk0p2 26.5G ext4
└─mmcblk0p3 1.9G swap
The kernel also initializes the eMMC correctly:
mmc0: SDHCI controller on PCI [0000:00:1c.0] using ADMA 64-bit
mmc0: new HS200 MMC card at address 0001
mmcblk0: mmc0:0001 A3A551 28.9 GiB
mmcblk0: p1 p2 p3
This indicates that the onboard eMMC and SDHCI controller are working correctly.
The issue therefore does not appear to be caused by CasaOS blocking access to the device.
Graphics-related kernel messages
While Ubuntu was booted using Safe Graphics, the following messages were visible:
simple-framebuffer simple-framebuffer.0: [drm] Initialized simpledrm
and:
snd_hda_codec_hdmi hdaudioC0D2: No i915 binding for Intel HDMI/DP codec
There were also these messages:
ee1004 2-0050: Failed to select page 0 (-6)
EDAC pnd2: Failed to register device with error -22
I am including these only as diagnostic information.
I am not claiming that these messages are necessarily the direct cause of the ZimaOS installer failure.
Screenshot 3 - Ubuntu kernel messages
Workaround
I mounted the EFI partition of the ZimaOS installer USB and inspected:
/EFI/BOOT/grub.cfg
The original file contained:
set default="0"
set timeout="0"
menuentry "ZimaOS Installer" {
linux /bzImage console=tty1 quiet splash loglevel=0 vt.global_cursor_default=0
}
I modified the kernel line by adding:
nomodeset
The resulting configuration was:
set default="0"
set timeout="0"
menuentry "ZimaOS Installer" {
linux /bzImage console=tty1 quiet splash loglevel=0 vt.global_cursor_default=0 nomodeset
}
After this change, the ZimaOS installer booted successfully.
Screenshot 4 - ZimaOS installer works after adding nomodeset
Installation result
After booting the installer with nomodeset, installation to the onboard eMMC proceeded normally.
The installer correctly selected:
/dev/mmcblk0
and successfully wrote the ZimaOS root data.
Screenshot 5 - ZimaOS installation in progress
ZimaOS was successfully installed and configured afterward.
Steps to reproduce
- Use a ZimaBlade with the onboard 32 GB eMMC.
- Download the ZimaOS 1.7.1 installer image.
- Flash the installer image directly to a USB drive using Balena Etcher.
- Configure BIOS for UEFI boot and disable Secure Boot.
- Boot the USB using the UEFI boot entry.
- Allow the ZimaOS installer to boot with its default kernel parameters.
- Boot reaches approximately:
Populating /dev using udev:
- Video output goes black and the installation interface never becomes visible.
- Mount the installer EFI partition on another Linux system.
- Edit:
/EFI/BOOT/grub.cfg
- Change:
linux /bzImage console=tty1 quiet splash loglevel=0 vt.global_cursor_default=0
to:
linux /bzImage console=tty1 quiet splash loglevel=0 vt.global_cursor_default=0 nomodeset
- Boot the installer again.
- The ZimaOS Installation Tool now appears.
- Installation proceeds normally.
Expected behavior
Because ZimaBlade is officially supported hardware, the ZimaOS installer should boot successfully without requiring users to manually edit the installer EFI partition.
Suggested improvement
Please investigate Intel graphics / i915 / Kernel Mode Setting initialization during the ZimaOS installer boot process on ZimaBlade.
It may also be useful to provide an additional installer boot option such as:
ZimaOS Installer (Safe Graphics)
which would automatically use:
nomodeset
This would provide a fallback for ZimaBlade systems or HDMI/display combinations that fail during normal graphics initialization.
Result
Default boot
ZimaOS Installer
↓
Populating /dev using udev:
↓
Black screen
With workaround
ZimaOS Installer + nomodeset
↓
Installer UI loads successfully
↓
ZimaOS installs successfully to /dev/mmcblk0
Conclusion
The problem is reproducible on this ZimaBlade with both ZimaOS 1.7.0 and 1.7.1.
The onboard eMMC is detected correctly by Ubuntu and does not appear to be the cause.
Ubuntu also fails during normal graphics initialization but boots successfully using Safe Graphics.
Adding nomodeset to the ZimaOS installer kernel parameters completely resolves the installer boot problem.
- Lenguaje dominante
- Shell
- Estrellas
- 3.1k
- Forks
- 129
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de IceWhaleTech/ZimaOS
-
[1.8.0] zimaos-local-storage runs `smartctl -s on` every ~3 min, waking HDDs from standby (disk standby never works)Posiblemente ocupada @yeabow la tomó hace 1 día. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
IceWhaleTech/ZimaOS#639 · 2 asignados ·
-
zimaos-local-storage sets dev.raid.speed_limit_min=500000, which overheats NVMe arrays during resyncPosiblemente ocupada @yeabow la tomó hace 1 día. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
IceWhaleTech/ZimaOS#638 · 2 asignados ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
IceWhaleTech/ZimaOS#630 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
IceWhaleTech/ZimaOS#582 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
IceWhaleTech/ZimaOS#575 ·
Todos los issues de IceWhaleTech/ZimaOS
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
nexu-io/html-anything#164 ·
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 85/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
heroku/heroku-buildpack-php#1024 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
openSUSE/rpm-config-SUSE#98 ·