[Kernel-packages] [Bug 1762986] Re: Display resolution of monitor via HDMI incorrectly identified

2018-04-17 Thread thet
New theory: The monitor must be on, booted up and still not in sleep mode when the HDMI USB-C adapter is attached to the laptop. I could get the correct resolution already twice with this procedure. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug

[Kernel-packages] [Bug 1762986] Re: Display resolution of monitor via HDMI incorrectly identified

2018-04-12 Thread thet
I just tried another USB-C to HDMI adapter from a friend without any issues. I believe now that this isn't a problem with the kernel but the adapter. The issue can probably be closed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux

[Kernel-packages] [Bug 1762986] Re: Display resolution of monitor via HDMI incorrectly identified

2018-04-12 Thread thet
The issue did start appearing after an update on 17.10. I bought the Monitor on 29.11.2017, so it worked with the 17.10 kernel version around that time. Since HDMI on 4k only drives the Monitor @30Hz on my laptop, I bought a DP adapter. After the random screen black outs annoyed me too much I

[Kernel-packages] [Bug 1762986] Re: Display resolution of monitor via HDMI incorrectly identified

2018-04-11 Thread Joseph Salisbury
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16

[Kernel-packages] [Bug 1762986] Re: Display resolution of monitor via HDMI incorrectly identified

2018-04-11 Thread thet
Some additional notes: - The same problem existed in 17.10 as well as in 18.04 beta, with x-org and Wayland sessions. - There is another bug regarding DP issues by me - but should be unrelated to the HDMI problem: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762989 -- You received