Description of problem: Linux 4.6.3-300.fc24 does not boot. If I select 4.5.5-300.fc24 I can boot (and report this bug). Version-Release number of selected component (if applicable): 4.6.3-300.fc24
It might be some kind of grub problem. When I try to look at the boot records from that boot I get nothing.
There is not enough information for us to even begin here. Do you see anything on the screen when you boot? If so, please take a picture of the failure state if you don't have logs.
All I get is a blank black screen.
I have the same problem. Unfortunately i can't provide more information. Because the Screen goes immediately to power saving mode. The HDD Led is not blinking so i don't think it is booting without a picture. Booting 4.5.7-300 still works.
I tried updating both with "dnf update" and Gnome software. Same results from both (I manually removed the kernel in between).
There is more info here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-1c409313f4 I also have a ASUS Zenbook UX305CA
Please remove 'rhgb' from your kernel command line and see if that helps. Please attach the output of dmesg from a fresh boot of a working kernel.
Created attachment 1176277 [details] dmesg from 4.5.5
No difference when removing rhgb quiet from boot menu.
Please try adding 'nomodeset' and see if that gets you anything. Also, please attach your grub.cfg file.
nomodeset does work for me. don't know if this is an aftereffect but xorg failes to set the correct resolution with this setting. i have an nvidia gtx 970 gpu and everything worked with the 4.5 kernel i attached my grub.cfg
Created attachment 1176549 [details] grub.cfg
(In reply to Syed Amer Gilani from comment #12) > nomodeset does work for me. don't know if this is an aftereffect but xorg > failes to set the correct resolution with this setting. > i have an nvidia gtx 970 gpu and everything worked with the 4.5 kernel > i attached my grub.cfg Please don't clear the needinfo for other reporters. Also, please file a separate bug for your issue unless you have exactly the same hardware as the original reporter.
Where can I find the grub.cfg file? I can't see it in the boot/grub2 directory.
(In reply to Andreas Tunek from comment #15) > Where can I find the grub.cfg file? I can't see it in the boot/grub2 > directory. It is in either: /boot/grub/grub.cfg or /boot/efi/EFI/fedora/grub.cfg
Created attachment 1176896 [details] grub.cfg from Andreas Tunek
(In reply to Andreas Tunek from comment #17) > Created attachment 1176896 [details] > grub.cfg from Andreas Tunek This doesn't even list the 4.6.3 kernel. Have you removed it?
Can you also tell me which version of microcode_ctl you have installed?
After more investigation, this may be a duplicate of bug 1353103. Can you try booting the 4.6.3 kernel with 'dis_ucode_ldr' on the kernel command line?
Created attachment 1177001 [details] grub.cfg from Andreas Tunek Using dnf update
(In reply to Josh Boyer from comment #19) > Can you also tell me which version of microcode_ctl you have installed? How do I do that?
(In reply to Josh Boyer from comment #11) > Please try adding 'nomodeset' and see if that gets you anything. > I can boot with nomodeset, but it has the wrong resolution and it does not start gdm.
(In reply to Josh Boyer from comment #20) > After more investigation, this may be a duplicate of bug 1353103. > > Can you try booting the 4.6.3 kernel with 'dis_ucode_ldr' on the kernel > command line? I can boot and type this using that code.
I can also replicate this bug with a Lenovo ThinkPad T460 (model number is 20FN003LRI if that is helpful for anyone). However, removing the 'rhgb quiet' option and using 'nomodeset' instead did not help. The behaviour is that the screen goes black and the cursor, which is not blinking, appears. It's similar to the behaviour I see when booting the 4.5.5 kernel but using that kernel the textbox for the full-disk encryption password appears while with 4.6.3 it does not. I do not know how to gather more information as I can't boot using that kernel but I'll gladly follow any instructions.
*** This bug has been marked as a duplicate of bug 1353103 ***