Yocto: Persistently disable kernel console logs on Verdin iMX8MP at first boot (works only via manual fw_setenv)

Technical Support
, , , , ,
18

Plymouth vs Weston Service Order

Based on the Toradex documentation, Plymouth runs from an initial minimal root file system (initramfs) very early during boot (1). This means Plymouth appears before Weston starts, which is exactly what you want for early splash screen display.

Plymouth Boot Timing

The documentation explains that Plymouth is started from an initial minimal root file system (initramfs) very early during boot (1). This makes it ideal for showing a splash screen immediately when the bootloader finishes, before any other services including Weston start.

Plymouth vs Weston Conflicts

Community discussions indicate there can be conflicts between Plymouth and Weston (2). The documentation suggests ensuring that Plymouth completes its boot animation before Weston starts (2). You can manage this by adjusting the systemd service order and checking the dependencies between Plymouth and Weston services (2).

Service Configuration

To ensure proper service order:

  1. Service Order: Ensure that Plymouth completes its boot animation before Weston starts (2)
  2. DRM Settings: Verify that your system’s Direct Rendering Manager (DRM) settings are compatible with both Plymouth and Weston (2)
  3. Configuration Files: Review the configuration files for both Plymouth and Weston to ensure no conflicting settings (2)

Plymouth Implementation for Your BSP

For your Verdin iMX8MP with BSP 7.5.0, Plymouth appears very early during boot from the initramfs (1), which means it will display before:

  • Weston service starts
  • Your application starts
  • Any other userspace services

This timing makes Plymouth the ideal solution for your requirement of showing a splash screen at the earliest possible moment during boot, replacing the disabled console logs space.

Key Points

  1. Plymouth starts first: It runs from initramfs very early in boot (1)
  2. Before Weston: Plymouth displays before Weston and other services start (2)
  3. Early display: Perfect for replacing the disabled console log space with your logo (1)
  4. Service management: Proper systemd service ordering prevents conflicts (2)

Plymouth is specifically designed to provide early boot graphics before the full userspace graphics stack (including Weston) initializes, making it the perfect solution for your silent boot with logo requirement.

Best regards, Toradex AI Assistant.

Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.