> > - Monitor support was typically bad and caused problems, connecting to monitor, multiple monitors, resolution issues on wake, etc.
> Only issue I had with this was one TV wouldn't take HDMI output at the same time as displaying to my laptop screen.
I just wanted to throw out some non-Linux issues I've hit in the past couple years.
I believe I had a MacbookPro 2015 and Apple's USB-C to HDMI I consistently had RGB noise patterns and it worked terribly. I switched to a third-party USB-C to DisplayPort and it worked great. I heard about similar issues online. Some talked about it being specific to hardware configuration (that series of MacbookPros) and others pointed to OS updates that triggered it.
I've had trouble with a Windows desktop and an Nvidia card with detecting which port was used to send video signal to on boot. I think it assumed the first HDMI port when I had the intention of using the DisplayPort. I think it got extra confused if the monitor was off on boot (it was trying to detect the signal?) I would often get the BIOS to show up on one output, then Windows may try and use a different one.
> Only issue I had with this was one TV wouldn't take HDMI output at the same time as displaying to my laptop screen.
I just wanted to throw out some non-Linux issues I've hit in the past couple years.
I believe I had a MacbookPro 2015 and Apple's USB-C to HDMI I consistently had RGB noise patterns and it worked terribly. I switched to a third-party USB-C to DisplayPort and it worked great. I heard about similar issues online. Some talked about it being specific to hardware configuration (that series of MacbookPros) and others pointed to OS updates that triggered it.
I've had trouble with a Windows desktop and an Nvidia card with detecting which port was used to send video signal to on boot. I think it assumed the first HDMI port when I had the intention of using the DisplayPort. I think it got extra confused if the monitor was off on boot (it was trying to detect the signal?) I would often get the BIOS to show up on one output, then Windows may try and use a different one.