, you don't mean that you pulled the sd card out of your Pi 3B and plugged it into your Pi 4B, do you? If so, that could be your problem. When you boot a new image, your os automatically does a bit of configuring, and maybe an SD card that's configured for your 3B won't actually run your 4B. Try a fresh install?I am using NOOBS which boots up nicely on the 3B
Nor would I expect it to be unless it had been explicitly declared/added manually. Raspbian Buster, whatever the Pi, attempts to obtain the display requirements from the TV/display's EDID info. after parsing. For a P4B, which, in the latter stages, can use a different "driver type" than for a P3B (by default) that can result in different behaviour - largely associated with the "tail" of a default /boot/config.txt :
Code: Select all
pi@raspiP4B4b-32GbP:~ $ tail /boot/config.txt dtparam=audio=on [pi4] # Enable DRM VC4 V3D driver on top of the dispmanx display stack dtoverlay=vc4-fkms-v3d max_framebuffers=2 [all] #dtoverlay=vc4-fkms-v3d enable_uart=1
That's not how it works. Computers, including the Raspberry Pi, query the monitor/TV for information about how best to set up the display. Most of the display hardware on the Pi 4 is different to previous models of Pi, and the firmware (and software) is still having problems fixed. There is most likely a way to get the Pi 4 working with your other monitor/TV, but it will take a bit of experimentation with settings.