Splash Screen Corrupted

When I boot up on Pi 3B+ the splash screen appears corrupted - not a big thing, but annoying!


The resolution is set to 1360x768@60Hz (mode 39) as this is the only thing the (old) TV will accept without cutting things off or having black bars.

/usr$ tvservice -s
state 0x12000a [HDMI DMT (39) RGB full 16:9], 1360x768 @ 59.94Hz, progressive
/usr$ tvservice -m CEA
Group CEA has 15 modes:
mode 1: 640x480 @ 60Hz 4:3, clock:25MHz progressive
mode 2: 720x480 @ 60Hz 4:3, clock:27MHz progressive
mode 3: 720x480 @ 60Hz 16:9, clock:27MHz progressive
mode 4: 1280x720 @ 60Hz 16:9, clock:74MHz progressive
mode 5: 1920x1080 @ 60Hz 16:9, clock:74MHz interlaced
mode 6: 720x480 @ 60Hz 4:3, clock:27MHz x2 interlaced
mode 7: 720x480 @ 60Hz 16:9, clock:27MHz x2 interlaced
(native) mode 16: 1920x1080 @ 60Hz 16:9, clock:148MHz progressive
mode 17: 720x576 @ 50Hz 4:3, clock:27MHz progressive
mode 18: 720x576 @ 50Hz 16:9, clock:27MHz progressive
mode 19: 1280x720 @ 50Hz 16:9, clock:74MHz progressive
mode 20: 1920x1080 @ 50Hz 16:9, clock:74MHz interlaced
mode 21: 720x576 @ 50Hz 4:3, clock:27MHz x2 interlaced
mode 22: 720x576 @ 50Hz 16:9, clock:27MHz x2 interlaced
mode 31: 1920x1080 @ 50Hz 16:9, clock:148MHz progressive
/usr$ tvservice -m Dmt
Group DMT has 8 modes:
mode 4: 640x480 @ 60Hz 4:3, clock:25MHz progressive
mode 6: 640x480 @ 75Hz 4:3, clock:31MHz progressive
mode 9: 800x600 @ 60Hz 4:3, clock:40MHz progressive
mode 11: 800x600 @ 75Hz 4:3, clock:49MHz progressive
mode 16: 1024x768 @ 60Hz 4:3, clock:65MHz progressive
mode 17: 1024x768 @ 70Hz 4:3, clock:75MHz progressive
mode 18: 1024x768 @ 75Hz 4:3, clock:78MHz progressive
(prefer) mode 39: 1360x768 @ 60Hz 16:9, clock:85MHz progressive

Any thoughts?

Does it stay that way, or will it get to a normal look if you are showing the menus?
What does the TV say its preferred mode is?
Have you tried CEA mode 16?
Derek

It seems odd that the native mode of the screen is CEA Mode 16 but it is preferring DMT Mode 39.

It is a very odd TV :wink:

Changing to CEA 16 resolved, thanks both very much!

I thought we fixed this some time ago. I’ll need to recheck.