Yellow Screen on Raspbian Buster 2019-06-20


Following the steps here
Found a HDMI issue which seems to be happening for Raspbian Buster lite 2019-06-20.

Steps followed -

  1. Setup mender-convert on local machine (git tag 1.2.0)
  2. Downloaded and copied to input folder
  3. Setup the environment variables as follows


  1. Attempt to shrink image (no visible change)

./docker-mender-convert raw-disk-image-shrink-rootfs
–raw-disk-image ${RAW_DISK_IMAGE}

  1. Prepare output images with mender-convert

./docker-mender-convert from-raw-disk-image
–raw-disk-image $RAW_DISK_IMAGE
–mender-disk-image $MENDER_DISK_IMAGE
–device-type $DEVICE_TYPE
–artifact-name $ARTIFACT_NAME
–bootloader-toolchain arm-buildroot-linux-gnueabihf
–server-url $SERVER_URL
–tenant-token $TENANT_TOKEN

The images are built successfully, although on powering up the Rpi 3B device, the HDMI screen shows Yellow output with text not in its usual place.

I have attached the images for the same.

Let me know if you need any other info.
Also please let me know if this can be fixed somehow ? otherwise I have no other option but to use Raspbian Stretch.


Check out the instructions here and let me know if it helps.

Because we have been trough this already and I was hoping it was fixed.

Aah, now I remember. We decided to only document the workaround and never actually made any code change because it might have unwanted effects to use the suggested workaround if e.g you are running a headless system. For this reason it is not the default.

Will be fixed by

Thank you @mirzak for your quick response !
I will try the suggested fix and get back if there is any issue.

I was under the impression that the HDMI Issue was ONLY happening with Raspbian Buster 2019-07-10 and NOT on Raspbian Buster 2019-06-20.

I now understand the issue between uboot and kernel due to the simple-framebuffer. hopefully the PR will merge soon and we can use Raspbian buster easily.

If the release with the fix will take a long time then please add the “Note: HDMI Issue” on Raspbian Buster 2019-06-20 as well so that future users may not be troubled.

Thank you !

I was under the same impression. I have updated the tutorial to have the “note” on both Buster releases.

I am having the same issue with Warrior Branch for both Raspberry Pi 3 and 4 when using DISABLE_VC4GRAPHICS set to 1, see more info here: Can you please tell me how to fix this issue? I see the changes are related to uboot here: . I just don’t know how to fix them for my configurations. Any help will be appreciated. I am looking now to see how to fix this issue.

Edit: Looks like meta-mender uses uboot 2019.01 which is patched but I still have that issue. Still investigating…


The linked patch is not in any of the meta-mender layers and you would have to add that patch in your layer.

The linked commit is only used by our “mender-convert” tool.

Can you elaborate on these unwanted effects ? Asking since I’m seeing the same issue as @ikkysleepy with Yocto Warrior on RPi3B+ and just had to patch U-Boot also.

You can find more information about this issue here,

1 Like