On Thu, Apr 5, 2018 at 2:05 AM, Tim via users <users@xxxxxxxxxxxxxxxxxxxxxxx> wrote: [...] > Are you able to rename the input socket used on the TV? On some sets, > if you name it "PC," it will switch off overscan. I've looked for options to change without much luck. The TV has "PC" assigned to a VGA port - I will see if there is a way to move the name. > Your "zooming" problem is probably related. I did not have this zooming issue with the old NUC, so I think it is unlikely to be related. But never say never.... >> The third issue is that sometimes I lose the display more-or-less >> completely. I switch the receiver to the NUC, and I get a black >> screen. If I reboot (via a ssh session), I get nothing. To get the >> display back, I have to poweroff and cold boot. The login screen is >> fine, but after logging-in, KDE seems to be set for a lower >> resolution (800x600?) than the TV is using (1080i), and I have go >> into "System Settings" to correct it - which is difficult when you >> can't really read the display very well! > > I've seen that kind of thing where Linux is setting resolutions > automatically based on the monitor's capabilities. But, at the time > that X was figuring this information out, the monitor hadn't come out > of standby mode, and wasn't responding to probes. > > Does that sound like the timing of events with your issue? There is a delay when switching before the display comes up - 3-5 seconds maybe? But that is every time I switch. And in my case the monitor isn't in standby - the delay is just the switch-over (I assume the delay is caused by HDMI negotiations, X and/or video driver figuring out the monitor that just got connected, etc.). I was hoping to force the resolution in the X config and the KDE config, so that at least it couldn't confuse itself anymore. Maybe I succeeded in doing so, but have been too focused on the "zoom" issue to realize? _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx