I decided to bring out my raspberry pi 4 and install a new download of the dietpi image. I format my sd card, and flash the latest image of dietpi. when i pulg my raspberry pi 4 into power and plug in the hdmi cable, i get red and green lights, but no display. I even tried multiple sd cards, and same result
did you tried to reach the system via SSH/network?
Yes
and?
doesnt connect, because it has not been setup
I dont even get the boot up txt on the screen
If nothing is displayed on the screen and there is no Ethernet connection, you may need to connect a UART adapter.
Just tried on my RPi4B and first initial boot is working without issue. I tried with Wifi instead of Ethernet but this should not matter.
Does your LED blinking has some kind of code?
It just blinks red and green like it’s rrading the sd card. I wanted to see if the sd card was the issue, I formatted the sd card with the dietpi image on it, and put the official raspberry pi image, and plugged it in, nd the initial boot came on the display
If the system doesn’t boot up, the green LED should eventually stop lighting up.
Is it still flashing, or is it lit up green all the time?
At the moment I’m not able to replicate, for me a fresh install is working without any issue.
It still flashes green the whole time, and my computer monitor would not get any input from it. But when I put in a different image, in my case; I tried the original raspberry pi software, and my monitor would detect the signal and show the boot uo text. Bit when I plug in the dietpi image, it would keep flashing green, but wouldn’t get input to the monitor, where i dont see the boot up text
does it have any off these flashing codes https://www.raspberrypi.com/documentation/computers/configuration.html#led-warning-flash-codes
I ge5 the first one
But only for the dietpi image
hmm generic boot issue. Could be everything.
Quite strange behaviour as the image is working for me on RPi4B and RPi Zero2 W
Maybe the image got damaged while downloading. Can you try again to download a fresh image? As well which tool you use to burn the image to SD card?
@MichaIng any ideas?
And my monitors turn on automatically when there is input
the system stuck with a generic issue. so of course there is nothing on the monitor.
The image is already more than 3 weeks old, so generally, it boots.
You said earlier that the green remains just lid instead of blinking, if I understood correctly, and later that you see the first flashing pattern, i.e. 3 short blinks in a row. Can you clarify, also whether it e.g. changes? What would be interesting is whether it boots into the kernel at all, at least at first, or never. While this should be seen on the HDMI screen: on first boot, if it boots into kernel and init system, the root partition and filesystems are expended, and an ext4 journal added. This can take a while on slower and larger SD cards, and it should cause the green LED to remain almost lid, or with high frequency flashing, but not boot error pattern with a ~2 seconds pause.
Otherwise, common issue is insufficient PSU: We boot with initial_turbo=20, i.e. CPU is at max frequency for the first 20 seconds, while RPi OS starts with the “ondemand” CPUFreq governor, as far as I can see. If the PSU is at the border of sufficient, some power peaks at boot in combination with maxed CPU frequency+voltage could theoretically make the difference. Could be tested by removing or commenting out the initial_turbo line in config.txt (on the FAT partition).
Otherwise, as Joulinar said, only serial console output via UART adapter could reveal more.
I got it to work by going into config.txt and uncommenting hdmi_force_hotplug=1, and uncommenting hdmi_group=1 and hdmi_mode=1 and changed it to 16. saved the file, put the sd card into the raspberry pi, dietpi booted up and was being shown on the display. but ive never had to edit the config.txt before to make it work
usually this is not needed. How does it behave if you try booting without monitor attached? does it show up on your network?
I wouldn’t know because I use wlan( wireless) and dont have access to the router ethernet. But I know, ota strange. Ive never had to edit the config before to get it to work