I'm trying to boot up my RaspberryPi to use as a remote for PlatformIO development on my Teensy4.1 (whole another can of worms).
I have the RaspberryPi 4B (2GB) and the 32GB raspberry pi micro SDcard. I've also tried with a 64GB sandisk USB and SD Card.
With no boot drive
Firstly, with no SD Card in and nothing connected to the Pi (except the monitor), the pi shows me the configuration screen. Both LEDs are solid red and solid green.
From the troubleshooting guide, it seems like the LED should blink green 4 times when no display is connected. This does not happen.
I followed the guide to restore the bootloader and that was successful (ended with continuously blinking green LED)
With Latest version of RaspberryPi OS 64 bit/32bit
If either one of the three storage devices are connected, the Pi briefly sends a signal to the monitor, then goes blank. (Too brief to read anything on screen). From this point, I cannot SSH into the Pi and, get no display. The red light remains solid and, the green light is blinking randomly.
I tried setting the hdm_force_hotplug=1 and config_hdmi_boost=4 but these did not work either
With RaspberryPi OS Legacy 32bit
The RaspberryPi successfully boots with this version of the OS on the boot drive. However, there is no output to the monitor.
I can SSH into the RaspberryPi and it works normally with SSH.
Then, following the same troubleshooting guide, once again, setting the the hdm_force_hotplug=1 and config_hdmi_boost=4 in the config.txt file, the RPI finally displays an image on the monitor.
However, the boot screen is displayed, then the screen goes black. I have to physically unplug the HDMI and reconnect it to get to the desktop screen (RPI is running the whole time). If I don't do this, the monitor goes to sleep and the RPI keeps running.
Additionally, if I try to change the display settings from the GUI/SSH the RPI "crashes" and reboots itself. Once this happens, I can't SSH into it nor get any display on the screen until I follow the steps above again.
Conclusion
I don't understand if this is a hardware issue or if I'm missing something? Seems to go against everything I've read on the troubleshooting page where the 4B is supposed to work with the latest OS and not the old versions.
I have the RaspberryPi 4B (2GB) and the 32GB raspberry pi micro SDcard. I've also tried with a 64GB sandisk USB and SD Card.
With no boot drive
Firstly, with no SD Card in and nothing connected to the Pi (except the monitor), the pi shows me the configuration screen. Both LEDs are solid red and solid green.
From the troubleshooting guide, it seems like the LED should blink green 4 times when no display is connected. This does not happen.
I followed the guide to restore the bootloader and that was successful (ended with continuously blinking green LED)
With Latest version of RaspberryPi OS 64 bit/32bit
If either one of the three storage devices are connected, the Pi briefly sends a signal to the monitor, then goes blank. (Too brief to read anything on screen). From this point, I cannot SSH into the Pi and, get no display. The red light remains solid and, the green light is blinking randomly.
I tried setting the hdm_force_hotplug=1 and config_hdmi_boost=4 but these did not work either
With RaspberryPi OS Legacy 32bit
The RaspberryPi successfully boots with this version of the OS on the boot drive. However, there is no output to the monitor.
I can SSH into the RaspberryPi and it works normally with SSH.
Then, following the same troubleshooting guide, once again, setting the the hdm_force_hotplug=1 and config_hdmi_boost=4 in the config.txt file, the RPI finally displays an image on the monitor.
However, the boot screen is displayed, then the screen goes black. I have to physically unplug the HDMI and reconnect it to get to the desktop screen (RPI is running the whole time). If I don't do this, the monitor goes to sleep and the RPI keeps running.
Additionally, if I try to change the display settings from the GUI/SSH the RPI "crashes" and reboots itself. Once this happens, I can't SSH into it nor get any display on the screen until I follow the steps above again.
Conclusion
I don't understand if this is a hardware issue or if I'm missing something? Seems to go against everything I've read on the troubleshooting page where the 4B is supposed to work with the latest OS and not the old versions.
Statistics: Posted by GeneralStatsky — Wed Mar 12, 2025 9:03 pm — Replies 0 — Views 8