Assuming you are running Bookworm or Bullseye.
probably the old TV does not respond to the request for EDID data sent from the pi to the TV.
as such, the pi does not know what resolution to set, so it doesn't set one. thus, no display.
you can:
Set resolution manually: (under KMS driver only)
in /boot/cmdline.txt (add to the front/end of the line, NOT a new line)
-- IMPORTANT NOTE: for Bookworm, the file is at /boot/firmware/cmdline.txt !!
video=HDMI-A-1:1024x768@60D
(or whatever resolution you want)
also note that config.txt settings are ignored in the bullseye and Bookworm release if you are running the new (KMS) driver.
you can tell by the following lines in the config.txt file:
# Enable DRM VC4 V3D driver
dtoverlay=vc4-kms-v3d
max_framebuffers=2
(above is KMS driver)
# Enable DRM VC4 V3D driver
dtoverlay=vc4-fkms-v3d
# NOTE the FKMS in the above line for the FKMS driver (fake kms?)
probably the old TV does not respond to the request for EDID data sent from the pi to the TV.
as such, the pi does not know what resolution to set, so it doesn't set one. thus, no display.
you can:
Set resolution manually: (under KMS driver only)
in /boot/cmdline.txt (add to the front/end of the line, NOT a new line)
-- IMPORTANT NOTE: for Bookworm, the file is at /boot/firmware/cmdline.txt !!
video=HDMI-A-1:1024x768@60D
(or whatever resolution you want)
also note that config.txt settings are ignored in the bullseye and Bookworm release if you are running the new (KMS) driver.
you can tell by the following lines in the config.txt file:
# Enable DRM VC4 V3D driver
dtoverlay=vc4-kms-v3d
max_framebuffers=2
(above is KMS driver)
# Enable DRM VC4 V3D driver
dtoverlay=vc4-fkms-v3d
# NOTE the FKMS in the above line for the FKMS driver (fake kms?)
Statistics: Posted by terribleted — Sat Jan 06, 2024 2:29 am