Description of problem: Only one 16:9 resolution is identifed (the main one 3200x1800) on Asus Skylake UX305UA Version-Release number of selected component (if applicable): 2.99.917-23.20160512.fc24.x86_64 kernel-4.5.5-300.fc24.x86_64 i915, PCI 8086:1916 How reproducible: Always Steps to Reproduce: 1. Run Gnome at full resolution 3200x1800 2. Display Settings -> Built-in display -> Resolution 3. Actual results: See only 3200x1800 (16:9) All others are (4:3) or (5:4) Expected results: All resolutions e.g. 1920x1080 (16:9) etc Additional info: On boot if I force video=1920x1080 then one other 16:9 resolution will appear 3200 x 1800 (16:9) ...(4:3) stuff... 1920 x 1080 (16:9) ...(5:4) and (4:3) stuff This applies to other 16:9: it seems if I "kick" modesetting on boot then it will remember that 16:9 resolution, e.g. if I use video=1600x900 on boot then 3200 x 1800 1600 x 900 will appear and 1920x1080 will be forgotten
CPU: Intel Core i7-6500 CPU @ 2.50 GHz Notebook : Asus UX305UA dmidecode: American Megatrends Inc. UX305UA.201
Exact same issue here after upgrading from Fedora 23 to 24. Dell XPS 13 9350 Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz Skylake Host Bridge Intel Corporation HD Graphics 520 (rev 07) kernel-4.5.7-300.fc24.x86_64 xorg-x11-drv-intel-2.99.917-23.20160512.fc24.x86_64
Created attachment 1177038 [details] Xorg.0.log - for information
Created attachment 1177039 [details] Journalctl -b I know other errors exist in the journal, such as ACPI and will report as I delve further into F24.
On F25 + Wayland, this issue doesn't exist. All 16:9 and 16:10 resolutions appear. Mesa 13.0.2, Intel Skylake 00:02.0 0300: 8086:1916 (rev 07) .
I have the exact same issue. 00:02.0 0300: 8086:191b (rev 06) (prog-if 00 [VGA controller]) Subsystem: 1028:06e4 Flags: bus master, fast devsel, latency 0, IRQ 127 Memory at db000000 (64-bit, non-prefetchable) [size=16M] Memory at 70000000 (64-bit, prefetchable) [size=256M] I/O ports at f000 [size=64] [virtual] Expansion ROM at 000c0000 [disabled] [size=128K] Capabilities: [40] Vendor Specific Information: Len=0c <?> Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [100] Process Address Space ID (PASID) Capabilities: [200] Address Translation Service (ATS) Capabilities: [300] Page Request Interface (PRI) Kernel driver in use: i915 Kernel modules: i915 xorg-x11-drv-intel-2.99.917-26.20160929.fc25.x86_64 Linux dellxps 4.9.3-200.fc25.x86_64 #1 SMP Fri Jan 13 01:01:13 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux I would just run Wayland as it does not have the issue, but I am heavily reliant on VMware for work, and cut-copy-paste does not work in Wayland for VMware workstation between host and guests, so I must run Xorg until VMware fixes it up. I am not sure where to get Wayland logs - it does not print anything to the journal like th emodelines in Xorg (already posted by Richard and David).
I reported this upstream for Haswell years ago. https://bugs.freedesktop.org/show_bug.cgi?id=89996 The "intel" driver is no longer maintained, but the "modesetting" driver is. The modesetting driver has the same problem in that common 16:9 resolutions are not provided.
Ping. Is there a better upstream to report this to?
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle. Changing version to '27'.
Created attachment 1313764 [details] RFC Patch against 1.19.3 I have created a patch for consideration. It works on my Intel Iris 5100 (Haswell) system. Xrandr/Gnome now report all modes and mode switching works. I will wait a week for feedback before submitting this upstream. Xrandr before: Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 8192 x 8192 eDP-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 294mm x 165mm 2560x1440 59.95*+ 1920x1440 60.00 1856x1392 60.01 1792x1344 60.01 1600x1200 60.00 1400x1050 59.98 1280x1024 60.02 1280x960 60.00 1024x768 60.04 60.00 960x720 60.00 928x696 60.05 896x672 60.01 800x600 60.00 60.32 56.25 700x525 59.98 640x512 60.02 640x480 60.00 59.94 512x384 60.00 400x300 60.32 56.34 320x240 60.05 DP-1 disconnected (normal left inverted right x axis y axis) HDMI-1 disconnected (normal left inverted right x axis y axis) HDMI-2 disconnected (normal left inverted right x axis y axis) Xrandr after: Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 8192 x 8192 eDP-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 294mm x 165mm 2560x1440 59.95*+ 1920x1440 60.00 1856x1392 60.01 1792x1344 60.01 2048x1152 59.95 1920x1080 59.95 1600x1200 60.00 1400x1050 59.98 1600x900 59.95 1280x1024 60.02 1280x960 60.00 1368x768 59.95 1280x720 59.95 1024x768 60.04 60.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.95 960x540 59.95 800x600 60.00 60.32 56.25 864x486 59.95 700x525 59.98 640x512 60.02 640x480 60.00 59.94 720x405 59.95 640x360 59.95 512x384 60.00 400x300 60.32 56.34 320x240 60.05 DP-1 disconnected (normal left inverted right x axis y axis) HDMI-1 disconnected (normal left inverted right x axis y axis) HDMI-2 disconnected (normal left inverted right x axis y axis)
The patch above has been rejected upstream. https://lists.x.org/archives/xorg-devel/2016-February/048866.html It was suggested to add these modes to "extramodes" instead: https://bugs.freedesktop.org/show_bug.cgi?id=37858#c4 But that doesn't seem to have happened since 2011.
Created attachment 1379229 [details] [PATCH] xfree86: add default modes for 16:9 and 16:10 Patch submitted to xorg-devel. See also upstream bug https://bugs.freedesktop.org/show_bug.cgi?id=37858
Martin, thanks for your work. I tried submitting the 1.0 patch again a few months ago and it was rejected again. I have tried your 2.0 patch and the full set of modes are available for me on modesetting+Haswell (Iris 5100) graphics. I do not see your patch on xorg-devel yet, though. You may need to resubmit. If you have any problems I don't mind submitting it for you.
(In reply to Michael Cronenworth from comment #13) > I do not see your patch on xorg-devel yet, though. You may need to resubmit. > If you have any problems I don't mind submitting it for you. I'm not subscribed, so the message is currently awaiting moderator approval.
https://lists.x.org/archives/xorg-devel/2018-January/055556.html
Finally accepted. Would anyone object if I added this patch to 1.19 in Fedora 27+ ?
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle. Changing version to '28'.
xorg-x11-server-1.19.6-6.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-c49b5e47b4
xorg-x11-server-1.19.6-6.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-c27082f100
xorg-x11-server-1.19.6-6.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-c27082f100
xorg-x11-server-1.19.6-6.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-c49b5e47b4
xorg-x11-server-1.19.6-6.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.
xorg-x11-server-1.19.6-6.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.