TheAverageJoe

My apologies, the only other forum I use is quite busy so I wasn't used to that. I will look into h3disp and see if I can solve the issue, thank you!

Hey all, Sorry for the noob question, I posted this in another topic but it hasn't seen any action so I thought I would make a post. I have an Orange Pi PC, using the RetroOrangePi build which is based on Armbian. I'm having overscan issues on my 720p TV. I checked the options on the PC, there's no way to fix it there. They figured it out in this topic here (where I initially asked this question): The solution is to add code to u-boot in order to solve the overscan, or edit boot.cmd. My question is, will using u-boot be the best solution, or is it better to edit boot.cmd? Do I simply create a boot.cmd in something like notepad++ and compile it to boot.scr, or am I supposed to edit boot.scr and re-compile it with the appropriate code? I am not sure exactly how to compile boot.cmd into boot.scr. If u-boot is a good option, how do I get into u-boot to make those changes? My apologies for the foolish questions. I've been around computers a long time but Linux is a new creature for me. Thanks much everyone.

I know this is a necro-bump, but I cannot send private messages. Could you possibly tell me the exact steps you performed to boot into u-boot and fix the overscan? I bought an Orange Pi PC, and spent about 4 hours last night trying to fix the overscan. I must admit that while I'm not new to computers, Linux is a mystery to me and I found it difficult to find more precise instructions on fixing this issue. I'm sure this is a case of me being utterly dense, but I'm quite disheartened that I could not figure it out. Or is it better to edit boot.cmd? I could not find a boot.cmd on my system, and I'm not sure how to rebuild it into boot.scr. My apologies for the no-doubt foolish questions, but if you could let me know how to fix the overscan I would appreciate it very much. Thanks!