
1366 x 768 monitors (and, presumably, your T.V.) are known to be using unusual HDMI timings - this is under investigation and there are other threads about the issue. (AIUI, it's been difficult to get hold of an "offending" monitor for direct testing - forum supplied edid info. has provided some clues for the engineers to work with.)SheaL wrote: My apologies. I'm using the HDMI0 port and the TV is 1366x768. I managed to find a service manual for it, so I've attached the specs page just in case. Model LC-32A29L
Code: Select all
hdmi_group=2
hdmi_cvt=1366 768 60
hdmi_mode=87Silly question I'm sure, I feel like I'm somewhat of a layman here, but I've only been able to get NOOBS to work properly. Using belenaEtcher with a 32gb card and Buster has only resulted in me getting a red light, an extraordinarily brief green flash, and nothing else, but ok, NOOBS it is. Anyways, The config.txt is already pre-filled with commented values, so I just un-commented and edited as necessary. The location of said commands/values doesn't really matter that much, right?kerry_s wrote: ↑Sat Mar 07, 2020 7:51 pmwelcome to the club.
add this to the bottom of /boot/config.txt:Code: Select all
hdmi_group=2 hdmi_cvt=1366 768 60 hdmi_mode=87
Oh very cool! It works like a charm now. Thank you so much, you have no idea how much I appreciate the help I've received here. Definitely learned a lot. If I could send you a brownie I'd definitely get started baking right now!kerry_s wrote: ↑Sun Mar 08, 2020 3:12 amyes & no, it's better you not mess with anything else.
try the new imager:
https://www.raspberrypi.org/blog/raspbe ... g-utility/
grab this image:
https://downloads.raspberrypi.org/raspbian_latest
after you make the sdcard edit the file, before you even put it in the pi.