06-11-2021, 03:50 AM
(This post was last modified: 06-11-2021, 03:57 AM by dsimic.
Edit Reason: Wording
)
Hello,
As probably already known, support for the PineBook Pro's video console has recently been included in the U-Boot packaged by Manjaro ARM. That's awesome and, for someone coming from the x86 world, makes the PineBook Pro feel much more like a "real" computer that isn't silent early in the boot process.
The support for the video console is currently in form of a patch, but the patch should be merged into one of the next releases of U-Boot.
However, this new U-Boot feature isn't issue free. In the first couple of seconds after powering up the PineBook Pro, before any text is displayed, there are some weird screen artifacts that last for a split second. After the U-Boot messages are displayed and right after the kernel image is loaded and started, the same screen artifacts become visible again, this time much better and lasting for a bit longer. These artifacts are probably caused by some mode switching and the old, gargabe contents of the framebuffer memory.
Before digging a bit deeper into this, I'd like to ask if anyone else sees the same visual artifacts? The attached pictures show the screen contents right after the kernel image is started, with the very start of the artifacts in the first picture and the "fully developed" artifacts in the second.
As probably already known, support for the PineBook Pro's video console has recently been included in the U-Boot packaged by Manjaro ARM. That's awesome and, for someone coming from the x86 world, makes the PineBook Pro feel much more like a "real" computer that isn't silent early in the boot process.
The support for the video console is currently in form of a patch, but the patch should be merged into one of the next releases of U-Boot.However, this new U-Boot feature isn't issue free. In the first couple of seconds after powering up the PineBook Pro, before any text is displayed, there are some weird screen artifacts that last for a split second. After the U-Boot messages are displayed and right after the kernel image is loaded and started, the same screen artifacts become visible again, this time much better and lasting for a bit longer. These artifacts are probably caused by some mode switching and the old, gargabe contents of the framebuffer memory.
Before digging a bit deeper into this, I'd like to ask if anyone else sees the same visual artifacts? The attached pictures show the screen contents right after the kernel image is started, with the very start of the artifacts in the first picture and the "fully developed" artifacts in the second.
