@ab77 sorry for the delayed response.
Just having no luck with any versions other than 2.51.1. The device isn’t booting, the partitions are not expanding out, HDMI shows a blank screen though some output (white characters on a black background) has been observed for the briefest of moments sporadically while powered on (not long enough to read).
I am taking delivery of some new top spec SD cards this week and will try with them for the removal of doubt but I’m inclined to say there is no issue with the one’s I have in use.
Very odd indeed. For now 2.51.1 is working for me and will do while I continue development.
Sorry to hear you are still having issues. Please let us know how the new SD cards work for you. Another thing you can try to debug this issue is enable uart on config.txt in the SD card and try to see if you get any output from the console when trying to boot v2.56. Here are some instructions on how to do that
Also, are you getting this issue with multiple PI4? Or just one?
Thanks for the link, I’ll have a go at connecting with a terminal.
I have two pi4 model b 8GB, same behaviour on both devices and with across different SD cards.
I’m also experiencing a weird booting problem with my raspberry pi 4 that could be related:
When trying to boot balenaOS 2.56 or 2.58 on my raspberry pi 4 with a keyboard attached, the device will not boot. This happens both with a fresh image and when upgrading from the dashboard. I’ve got an HDMI monitor connected that turns the backlight on and off in a loop. This is strange as it works on 2.51.1 and below. When plugging out the keyboard (Apple USB Wired Keyboard) everything the pi boots fine
What sort of power supply are you powering this up with?
5V 3A => 15W, so I do not think that this could be the problem. I’ve also never seen the lightning bolt that would indicate an under-voltage. Booting the latest Raspbian also works with the keyboard plugged in.
Thank you, we’ll have to try and reproduce this and figure out what is causing this issue in balenaOS > 2.51.1.
Hi Steffen, does this happen only on first boot or also once you plug the keyboard into a device again that has booted successfully before ?
Are you able to try this on
This both happens on first boot as well as when restarting a device that has already booted. I’ve tried this on
2.58.6+rev1. As these are the only versions available on the dashboard I omitted the last digit above
Hey, can you try and connect serial cable and capture the output of the serial port when booting with and without keyboard? If there is no output in the serial, can you check whether there is a splash screen in the HDMI monitor? We couldn’t reproduce any of the issues unfortunately, and we will attempt to reproduce them again and investigate why this might be happening.
With the default config in balenaOS disable_splash is set as far as I know. I’ll disable this and check if I see a splash screen.
I will try to get the Pi connected to a USB serial adapter (never did that with a Pi before) and let you know what I find out
Sounds good, it will be interesting to know what serial port output you get with and without the keyboard attached.
When the device is booted, the Keyboard seems to take about 5 attempts until it is actually connected. But this behavior is actually the same on 2.51.1.
This is the output on 2.51.1 when the keyboard is attached. The Pi does not seem to initialize the USB controller and therefore the problem maybe does not appear?
Just as a quick side node: I’m only using this setup for development. In production this specific keyboard will not be attached to the pi, so there won’t be any problem (for me).
I’ve opened an issue on GitHub (https://github.com/balena-os/balena-raspberrypi/issues/561) so that you can track progress on this.
It looks like you are using an Apple keyboard - does this problem still occur if you use different keyboards?
This seems to be specific to this keyboard (Apple MB110D/B with built-in USB Hub), I could not reproduce it with another USB keyboard I have.
@steffend glad you were able to resolve this your end.
From my side, I still absolutely cannot get most recent versions of BalenaOS to boot up on my raspberry pi 4s.
This is from a fresh flash onto new SD cards. I really cannot identify what I am doing wrong but evidently something because it doesn’t look like many others are having issues.
Hi Henry, it seems we had a couple of issues mixed in this same thread and that makes the conversation hard to follow.
Some things that you could check:
- I assume that the EEPROM firmware is unchanged and you are booting v2.51 and newer with the same firmware. It would be nice to confirm though.
- Then we will need you to plug an USB serial to your device and see what comes up when booting a non-working version.
- If there’s nothing, please try to modify a the BalenaOS image in the SD card and change the
config.txtfile in the resin-boot partition to remove the
disable_splash=1variable. Then plug in an HDMI monitor and see if there is anything on the screen.
- If there’s nothing, please report the LED blinkins patterns (see https://www.raspberrypi.org/forums/viewtopic.php?p=1485558#p1485558)