Anyone having issues with the 4.6.3 kernel in F24?

So upgraded my desktop, and the new 4.6.3 kernel absolutely WILL NOT boot, doesn't even seem to START booting, as it never even launches the splash screen, just black after grub. The prior 4.5.7 works perfectly still, so something odd with how 4.6.3 sees my hardware. I've already removed 4.6.3 so no chance to get logs, but I know early in the 4.6 testing it seemed to have issues with AMD processors and would do this exact issue. Just basically seeing if anyone on here has the same issue with the newer 4.6.3 kernel.

Kernel 4.6.3-300.fc24.x86_64 is working well for me running XFCE.

If I had to guess kernel 4.5.7 has a module/driver or something else that 4.6.3 may not have. The change logs would most likely reveal that.
(kernel regression maybe)

Do you have a AMD CPU?

Yup. My laptop (intel) running 4.6.3 with no issues. Desktop (AMD) fails almost immediately after grub.

I just install Fedora 24 on my quad core AMD desktop and it boots fine.

Sounds like the newer kernel doesn't want to play nice with the hardware on your desktop.
Is it an older desktop?

If the black screen is related to your GPU than you should be able to pass a parameter to the kernel line and that might stop the black screen boot up.

Support for older AMD processors may have been dropped recently.

It's older but still produced. FX8320 w/ 970 chipset. Not just graphics, entirely stops booting.

Did it boot before the fresh install of Fedora 24?

<OR> did it just start after the new FC installation?

Hi All.

I Have the same problem on a Xeon based machine.
All drives (except /boot and /boot/efi of course) are LUKS-encrypted.
No logs are created.

Have tried a reinstall to see if it was an upgrade glitch.
I wasn't... So now I'm stuck on Kernel 4.5.5 insted of 4.5.7.

Kind regards, Rumpole

Originally Posted by Ztcoracat Did it boot before the fresh install of Fedora 24? <OR> did it just start after the new FC installation?

This was an existing install, started out as F23, and all kernels from 4.2.3 up to 4.5.7 have no issues (still have 4.5.7 and 4.5.6 before it), only 4.6.3 has issues. If I choose to boot 4.5.7-300 it boots and works perfectly. If I choose to boot 4.6.3, as soon as grub passes over management, it stops booting.

Originally Posted by Rumpole Hi All. I Have the same problem on a Xeon based machine. All drives (except /boot and /boot/efi of course) are LUKS-encrypted. No logs are created. Have tried a reinstall to see if it was an upgrade glitch. I wasn't... So now I'm stuck on Kernel 4.5.5 insted of 4.5.7. Kind regards, Rumpole

Probably very similar problem, however 4.5.7 boot perfectly in mine and the following kernel caused mine to stop. Somewhat odd that you'd have the issue on xeon, I hadn't heard of anyone having this problem on Intel hardware before. Does it get ANYWHERE booting? Or just fail immediately after grub?

Sorry, I wasn't specifik enough.
Both 4.5.5 and 4.5.7 works perfectly on my Xeon based Z620.
It's only the 4.6.3 Kernel that wonøt boot.

First I upgraded from 23 (4.5.7) to 24 (4.5.7) and Fedora 24 worked like a charm.
Updating F24 (4.5.7) to F24 (4.6.3) caused the system to not boot - could still boot in 4.5.7 though.
Tried a fresh install of F24 (Kernel 4.5.5) and that worked.
Updating to 4.6.3 from the fresh install caused the problem again.

Have upgraded 4.5.5 to 4.5.7 now through Koji-rpms and that still works.

But I can't boot in Kernel 4.6.3.

Kind regards, Rumpole

OK, yeah, exactly the same as mine.

Glad to hear that kernel 4.5.7-300 works for you.

Sounds like kernel 4.6.3 lacks the support you need.

Give the men that make patches to the kernel time. That may change over the next several weeks.

My problem was the combination of graphics card, Geforce GT 630, and the Nouveau driver!

Tried to install a fresh copy in basic graphics mode and from there - after updating to Kernel 4.6.3-300 - installing the Nvidia proprietary driver for the Geforce GT 630.
Rebooting thereafter worked and all is well.
The problem was thus not related to LUKS.

Still somewhat annoyed about the issue in general though but now annoyed in from of a working Fedora 24 4.6.3 :-)