Hide Forgot
Description of problem: X won't start Version-Release number of selected component (if applicable): xorg-x11-server-Xorg-1.18.4-5.fc24.x86_64 xorg-x11-drv-intel-2.99.917-24.20160712.fc24.x86_64 How reproducible: startx Steps to Reproduce: 1.startx 2. 3. Actual results: [ 97799.240] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets: i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45, 4 Series, G45/G43, Q45/Q43, G41, B43 [ 97799.240] (II) intel: Driver for Intel(R) HD Graphics: 2000-6000 [ 97799.240] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100 [ 97799.240] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200, 6200, P6300 [ 97799.385] (EE) No devices detected. .......... Expected results: Additional info: 00:02.0 VGA compatible controller: Intel Corporation HD Graphics P530 (rev 06)
Created attachment 1229533 [details] Xorg log
I tried using the VESA driver, but that didn't work because the P530 was bound to the i915 kernel module: [119500.984] (II) VESA: driver for VESA chipsets: vesa [119500.984] xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted) [119500.984] vesa: Ignoring device with a bound kernel driver [119500.984] (WW) Falling back to old probe method for vesa [119500.984] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support [119500.984] (EE) Screen 0 deleted because of no matching config section. [119500.984] (II) UnloadModule: "vesa" [119500.984] (EE) Device(s) detected, but none match those in the config file. I then tried it without the vesa conf. Oddly, it generated a different xorg log than before. Again the intel driver did not detect the P530, but it defaulted to the framebuffer driver. But now it failed because of glamor: [119689.247] (==) Depth 24 pixmap format is 32 bpp [119689.248] (WW) glamor0: Failed to get GLSL version [119689.248] (EE) modeset(0): Failed to initialize glamor at ScreenInit() time. [119689.248] (EE) Fatal server error: [119689.248] (EE) AddScreen/ScreenInit failed for driver 0 mesa-libGL-12.0.3-2.fc24.x86_64 I've attached the log from this last try. I'd appreciate any help on getting X working.
Created attachment 1230660 [details] Xorg log with glamor error
Created attachment 1232297 [details] $ dmesg | grep drm The kernel seems to find the P530 without a problem.
For anybody who finds this, it seems redhat removed support for SKL from the intel driver !!! To get it working, edit the src.rpm to remove patch 2. Rebuild. That will work.
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.