Hide Forgot
Description of problem: While installing fedora 24 (25, rawhide) X11 detects 82865G-graphics chipset. Graphics are initialized with max. resolution 1024x768. xrandr reports only resolutions 1024x768 and 800x600. X11 uses 1024x768. Adding "vga=ask" to kernel command line, I am asked what resolution I'd like to have. I can find all of them up to 1920x1200@32. Since my monitor is only capable of 1600x1200@32 I give 0x35a at the prompt. The kernel loads i915.ko, initializes the framebuffer interface to use 1600x1200@32 with rgb 8,8,8. plymouth takes this resolution and does not have any problem with it. X11 takes graphics and cuts them down to 1024x768@32. I've tried: - using driver "vga", "vesa", "fbdev", "intel" - "vga": this driver didn't only allow for 1024x768 - "vesa": did not work at all: screen was blanked, no input possible, trying to switch to a console using Ctrl-Alt-Fx did not work at all. Even Ctrl-Alt-Del didn't help. I had to reboot hard. - fbdev: it was not possible to advice this driver to take /dev/fb0. It told me over and over again there where no framebuffer device. After forcing use of /dev/fb0 the first third of the screen was distorted and unreadable. Trying to force 1600x1200 lead to a blank screen with blinking cursor at the upper left corner. - intel: detected the chipset, but cased to work with it. Error message "no screen found". I've tried with /etc/X11/xorg.conf, without one. No way. Maximum display size 1024x768. Version-Release number of selected component (if applicable): Any PC with 82865G graphics. I had systems from Fujitsu-Siemens SCENIC 300P to test. They come with a configurable max. 256MiByte graphics memory shared with system memory. How reproducible: I've tried: - Fedora 24, 25, rawhide - CentOS 6, 7 - Ubuntu 14.04.5, 16.04.1, 16.10 - FreeBSD 10.3, 11, CURRENT They all did only allow for a display size 1024x768 (or lower), while they all (except FreeBSD), let plymouth handle graphics with 1600x1200 while booting. Even grub could handle graphics with 1600x1200! As soon as X11 took over graphics where cut down to 1024x768. Windows 7 (and up) are capable to use 1600x1200! Windows XP is to, but needs an extra driver from Intel. Steps to Reproduce: 1. Install whatever Linux or BSD you want, install Xorg-X11 Actual results: Graphics are cut down to maximum screen size 1024x768 Expected results: Graphics are using what the monitor tells the system: in my case 1600x1200 Additional info: This bug is not fedora specific, all systems using Xorg-X11 are affected.
/etc/X11/xorg.conf (for intel-driver) -- bails out with "no screen found": Section "Module" Load "dbe" Load "freetype" Load "glx" Load "dri" Load "v4l" Load "GLcore" EndSection Section "Files" ModulePath "/usr/lib/xorg/modules" FontPath "catalogue:/etc/X11/fontpath.d" FontPath "built-ins" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "AutoRepeat" "500 30" Option "XkbRules" "xorg" Option "XkbModel" "pc104" Option "XkbLayout" "de" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/input/mice" Option "ZAxisMapping" "4 5 6 7" EndSection Section "Monitor" Identifier "Monitor0" HorizSync 32.0-85.0 VertRefresh 56.0-65.0 Modeline "1600x1200" 161.00 1600 1712 1880 2160 1200 1203 1207 1245 -hsync +vsync EndSection Section "Device" Identifier "Card0" Driver "intel" #Option "HWcursor" # [<bool>] #Option "Xinerama" # [<bool>] #Option "StaticXinerama" # <str> #Option "GuiLayout" # <str> #Option "AddDefaultMode" # [<bool>] #Option "RenderAccel" # [<bool>] #Option "DRI" # [<bool>] #Option "DirectPresents" # [<bool>] #Option "HWPresents" # [<bool>] #Option "RenderCheck" # [<bool>] Option "IgnoreEDID" "true" Option "DDCMode" "false" Option "NoDDC" Option "PanelSize" "1600x1200@60" Option "ConnectedMonitor" "CRT" BusID "PCI:0:2:0" EndSection Section "Screen" Identifier "Screen0" Device "Card0" Monitor "Monitor0" DefaultDepth 24 SubSection "Display" Depth 1 Modes "1600x1200" "1024x768" "800x600" "640x480" Viewport 0 0 EndSubSection SubSection "Display" Depth 4 Modes "1600x1200" "1024x768" "800x600" "640x480" Viewport 0 0 EndSubSection SubSection "Display" Depth 8 Modes "1600x1200" "1024x768" "800x600" "640x480" Viewport 0 0 EndSubSection SubSection "Display" Depth 15 Modes "1600x1200" "1024x768" "800x600" "640x480" Viewport 0 0 EndSubSection SubSection "Display" Depth 16 Modes "1600x1200" "1024x768" "800x600" "640x480" Viewport 0 0 EndSubSection SubSection "Display" Depth 24 Modes "1600x1200" "1024x768" "800x600" "640x480" Viewport 0 0 EndSubSection SubSection "Display" Depth 32 Modes "1600x1200" "1024x768" "800x600" "640x480" Viewport 0 0 EndSubSection EndSection Section "ServerLayout" Identifier "Layout0" Screen 0 "Screen0" InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" EndSection
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.