Hello, Trying to test fedora 24 beta on my laptop. With normal boot, machine freezes before going into graphic mode. With safe graphics mode boot, screen stays on TTY and gnome doesn't launch, the following stays on screen: [ OK ] Starting Location Lookup Service...[ OK ] Started Location Lookup Service.[ OK ] Started session c6 of user gdm. (These messages are shown 6 times, for user c1 to c6). When going to TTY2, dmesg gives: 20.196734 do_trap: 12 callbacks suppressed 20.197634 traps: gnome-shell[1887] trap invalid opcode ip:7f78d1a2608f sp:7ffd180df8c0 error:0 Another 10 of these traps messages are present. I have tried nomodeset, rd.driver.blacklist=nouveau (and nouveau.blacklist=1) as boot arguments. I have disabled CSTATES in bios to outrule skylake errors (because I had trouble with previous kernels in F23). Using a skylake i7 6700HQ with nvidia GT960M and of course integrated graphics laptop. Regards, Ozy.
Same with F24 Final, cannot use install media. Text anaconda is not useful for me because ofpartitionning limitations. Any clues what I could try ?
journalctl -b output: https://gist.github.com/deajan/cbc505eaa68de35745e94de2878146ed
Finally got it sorted out, it was the Nvidia GM107M (GT960M) that made gnome-shell fail. Adding "rd.blacklist.nouveau=0" to the kernel boot cmdline does not blacklist nouveau anymore (lsmod still shows the driver loaded). Had to use "nouveau.modeset=0" in order to get things sorted out. Has the blacklist command changed or is it a bug ?
Same for me. It's nVidia 970 that caused this.
I have encountered this problem while booting the Live CD in a Windows 10 Hyper-V VM (gen 2). nouveau.modeset=0 did not resolve the problem, nor did nomodeset. I have an Intel 6700k, and an AMD HD 7850.
*** Bug 1396017 has been marked as a duplicate of this bug. ***
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.