The images was written to the SD card with dd - I followed this guide:
Some booting activities can be seen on the green led - but after around 30 sec is start blinking with a constant rate.. and the ethernet leds not blinking at all, although it is connected to a working router with dhcp.
What files should be checked on the SD card to verify the successful image writing? Unfortunately I dont have HDMI to check the console..
12 Answers
I am using the Raspberry PI Imager as well as Balena Etcher but had this black screen not booting condition on my Raspberry PI 4B no matter which distribution I burned. Luckily I still had an SD card with a working distro on it. So I began comparing the entries in the config.txt on the new burns to the working burn. And one by one I changed the settings until I found the one problem entry. I don't know the reason it's this way for you, only something you might look at and try.
The Raspberry PI Imager is putting the dtoverlay parameter in the config.txt file like this:
dtoverlay=vc4-kms-V3dHowever, I noticed in the working build I had this entry had the letter “f” in front of the “kms” part. So I edited the config.txt and changed the dtoverlay entry as follows and the boot process continued and I was up and running on the new images:
dtoverlay=vc4-fkms-v3dMaybe someone can explain this parameter and why the imagers are putting out a code that appears to hang up the Raspberry Pi 4B boot process. I just know this is how I finally got these images to boot. Hope this helps someone.
2Start over, using a better guide specifically for Ubuntu:
Ubuntu Desktop (this method requires Pi4, keyboard, and display)
Ubuntu Server (this includes the non-display you seek)
