If you have a similar issue, open a new thread and reference this one; do not necrobump (as the Code of Conduct makes clear).
Closing.
All the best,
-HG
]]>Since you already know the issue was introduced between 4.6.1 and 4.6.2, it shouldn't take too long
There will be at least one issue introduced with the switch to gcc7 you should be able to find the relevant patch from a search engine query of the build error you encounter.
]]>man git-bisect
Since you already know the issue was introduced between 4.6.1 and 4.6.2, it shouldn't take too long
]]>What can I do to correct the resolution?
]]>Well...
The key is probably in the modeline you created. First, check the xorg log whether any preferred (but unused) modelines/parameters are listed for the desired resolution.
Second, you'll *very* likely have to use a modeline with reduced blanking, possibly 30fps, to get anywhere.
I'm using a Thinkpad 440p with Intel built in graphics. Output of lshw is
[root@titanic ~]# LANG=en_US lshw -class display
*-display
description: VGA compatible controller
product: 4th Gen Core Processor Integrated Graphics Controller
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
version: 06
width: 64 bits
clock: 33MHz
capabilities: msi pm vga_controller bus_master cap_list rom
configuration: driver=i915 latency=0
resources: irq:31 memory:f0000000-f03fffff memory:e0000000-efffffff ioport:3000(size=64) memory:c0000-dffff
After upgrading from 4.6.1-2 to 4.6.2-1 I found that my external monitor no longer supports 4K; the 3840x2160 mode no longer appears in xrandr output and I can't use it ("cannot find mode"). I'm stuck at HD. Downgrading the kernel fixes this.
My external monitor is connected by a cheap Amazon Basics MiniDP->HDMI converter; the product description claims it only supports 1920x1080 but I've been using it with 4K for months now without any trouble.
Has anyone else seen similar behaviour? Are there any workarounds? The thread I linked at the beginning of this post hints that the 4.7 kernels will have some fixes for Intel graphics hardware-related issues, but it seems like this is a new one.
]]>