Hide Forgot
Description of problem: No F24 install image has successfully booted here on an Intel NUC Skylake except the Live workstation image. Beginning with the first alpha and through today, all alphas,all beta candidates, and numerous nightly composes -- other than the Live Workstation -- as well as server netinst and workstation netinst, fail to boot in consistent identical fashion. The Anaconda GUI does not appear. The stream of boot messages stalls after the initial Plymouth-related messages appears. Ctrl-alt-f2 does work to get to a console. The Xorg log shows this in all cases: 10.752] (EE) modeset(0): drmSetMaster failed: Invalid argument [ 10.752] (EE) Fatal server error: [ 10.752] (EE) AddScreen/ScreenInit failed for driver 0 [ 10.752] (EE) [ 10.752] (EE) I have successfully installed MATE and Cinnamon by: 1. booting a netinst image with nomodeset 2. installing a "Minimal Image", 3. Removing nomodeset on the reboot 4. Adding base-x and MATE/Cinnamon via group install 5. systemctl set-default multi-user.target 6. Create an ~/.xinitrc and use startx successfully. If I subsequently set a graphical.target on one of those installs, the boot fails -- lightdm does not appear -- and the same nomodeset-related error messages appear in Xorg's log. Same behavior on DVD (portable on a USB port) or USB stick. Ditto with the pre-release Fedora kernels or the 4.6 RC's from rawhide nodebug. Ditto in UEFI or BIOS. The machine is an Intel NUC6i5SYH,i5-6260u, Iris 540 graphics. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Burn any F24 pre-release ISO other than workstation to DVD/USB 2. Boot 3. Fail Actual results: Expected results: Additional info:
I think this was just fixed by xorg-x11-drv-intel update, at least lightdm works for me now. There's this bit in the changelog: * Thu May 12 2016 Hans de Goede <hdegoede> - 2.99.917-23.20160512 - Update to 20160512 snapshot - This fixes laptops with switchable graphics hanging after a dpms off of the lcd screen (rhbz#1334581) - Fix fd-leak when falling back to mode-setting on skylake, this fixes Xorg exiting with a "drmSetMaster failed" error when not using server managed fds (e.g. using a different login manager then gdm) - Fix duplicate binaries in -devel / intel-gpu-tools subpackages (rhbz#1323641)
(In reply to Oleg Drokin from comment #1) > I think this was just fixed by xorg-x11-drv-intel update, at least lightdm > works for me now. > > There's this bit in the changelog: > * Thu May 12 2016 Hans de Goede <hdegoede> - 2.99.917-23.20160512 > - Update to 20160512 snapshot > - This fixes laptops with switchable graphics hanging after a dpms off of > the lcd screen (rhbz#1334581) > - Fix fd-leak when falling back to mode-setting on skylake, this fixes > Xorg exiting with a "drmSetMaster failed" error when not using server > managed fds (e.g. using a different login manager then gdm) > - Fix duplicate binaries in -devel / intel-gpu-tools subpackages > (rhbz#1323641) Yes, fixes things here, too. The nightly composes don't seem to have caught up yet, but I'm sure they will.
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.