Thank you for providing the additional details. Your system is running Torizon OS 7.6.1, and the overlay is confirmed as applied successfully.
Analysis of Your Situation
Based on your boot log and the fact that the display works after boot completes but the splash screen doesn’t appear, this is indeed an early boot initialization timing issue specific to the on-module LVDS path.
Key Observations
Looking at your configuration:
- Kernel command line includes
splash fbcon=map:3 which should enable the splash screen
- The overlay applies successfully (verified via
/proc/device-tree)
- Display functions correctly once the system is fully booted
- Only the early splash screen phase fails with on-module LVDS
Potential Root Causes
1. Framebuffer Console Mapping
The fbcon=map:3 parameter in your kernel command line maps the framebuffer console to a specific framebuffer device. With different display paths (parallel RGB vs. on-module LVDS), the framebuffer device enumeration order may differ.
Check this:
ls -la /dev/fb*
Compare the framebuffer devices available between your working (parallel RGB) and non-working (on-module LVDS) configurations. The splash screen may be attempting to render on the wrong framebuffer device.
2. Display Initialization Timing
The on-module LVDS controller may initialize later in the boot sequence than the parallel RGB path, missing the window when Plymouth (the splash screen service) attempts to display.
3. Device Tree Overlay Structure
Without seeing the actual content of your overlay, here are critical elements to verify:
Ensure your LVDS nodes have proper status:
&ldb1_phy {
status = "okay";
};
&ldb1 {
status = "okay";
};
&ldb1_ch0 {
status = "okay";
};
Check panel timing parameters are correctly defined in your overlay.
Recommended Troubleshooting Steps
1. Compare Framebuffer Enumeration
Boot both configurations and compare:
cat /proc/fb
dmesg | grep -i framebuffer
2. Adjust Framebuffer Console Mapping
If the framebuffer device number differs between configurations, you may need to adjust the fbcon=map: parameter. You can modify this using TorizonCore Builder by customizing the kernel command line(1).
3. Review Your Device Tree Overlay
Since I cannot access your attached .dts file, could you share the key sections of your LVDS overlay, particularly:
- The LVDS controller and PHY node configurations
- Panel timing definitions
- Any dependencies or references to other nodes
4. Check for Known Issues
There have been splash screen issues reported on various platforms. For reference, similar issues were fixed in recent releases:
- Splash screen issues on DSI-to-LVDS configurations have been addressed(2)(3)
- Platform-specific splash screen fixes continue to be implemented
5. Enable Early Console Output
Add earlyprintk to your kernel command line to get more detailed initialization logs that might reveal timing issues.
Next Steps
To help diagnose this further, please provide:
- Framebuffer device information from both working and non-working configurations
- Key sections of your LVDS device tree overlay (especially LVDS controller, PHY, and panel nodes)
- Comparison of
dmesg | grep -E "(lvds|ldb|display|framebuffer)" output between both scenarios
This will help identify whether it’s a framebuffer mapping issue, timing issue, or overlay configuration issue.
Best regards,
Toradex AI Assistant.
Did you like my answer? 
If I answered your question, please tick the “Solution” checkbox.
For follow-up questions to me, please use @ToradexAI in your post.
