Ask Your Question

Bootlog flashing after updates, unsure whether to update again

asked 2017-10-16 13:58:27 -0600

I myself am not too good with Linux, but I had a friend over who works on servers and such and he couldn't figure it out either. Kernel 4.12.9-300.fc26.x8664 is the last one which still boots on my system, and fortunately Fedora by default saves the last 3 kernels in case something like this happens. After updating to kernel 4.12.13-300.fc26.x8664, the system would "boot" I suppose, but partway through all the text that comes up when booting, upon arriving at starting gnome, the screen would start flashing, and do so indefinitely. I just figured it was an issue a lot of people would have that would get fixed fairly quickly next update. So then another update comes (4.12.14), and I'm thinking yay, I can use a current system again, but then the same thing happens again. Fedora only rolls back 3 kernels, and there's another update. At this point I'm pretty sure the problem has to do with my system in particular, so I don't want to update again, and wanted to ask if there's anything that I can do to address this issue that hasn't been done. What I've done so far: updated BIOS, tried booting through the grub of a different Linux installation, tried booting with only one monitor connected, added nomodeset kernel options on boot (fixed my other Linux install, but Fedora seems to have it by default already).

edit retag flag offensive close merge delete


Thanks for the help backing that up, I ran the above (with sudo, wouldn't let me otherwise), so hopefully that's saved. Does it keep it in grub too? also, here's the output:

peaceblaster gravatar imagepeaceblaster ( 2017-10-16 17:19:16 -0600 )edit

and from the update -- refresh thing, I got: Last metadata expiration check: 0:00:00 ago on Mon 16 Oct 2017 06:21:49 PM EDT. Error: Problem: package kernel-4.12.13-300.fc26.x8664 requires kernel-core-uname-r = 4.12.13-300.fc26.x8664, but none of the providers can be installed - conflicting requests - problem with installed package kernel-4.12.13-300.fc26.x86_64

peaceblaster gravatar imagepeaceblaster ( 2017-10-16 17:22:29 -0600 )edit

2 Answers

Sort by ยป oldest newest most voted

answered 2017-10-16 15:44:24 -0600

jmt gravatar image

With kernel problems on one of my machines I've usually removed the offending new kernel and excluded it in my dnf.conf file. This way I don't have to worry about losing the working kernel. You'll know when your excludedirective is written correctly whe dnf update will no longer try to install that kernel version.

The manual page of dnf.conf also mentions protecting packages, which is done by adding a file to the /etc/donf/protected.d directory with the protected package name in it. The documentation is not clear about whether you can protect a certain kernel version this way, but the running kernel is always protected from deletion.

edit flag offensive delete link more


IIRC I used something like exclude=kernel*-4.13.5-* but this was in the days when Fedora still used yum.

jmt gravatar imagejmt ( 2017-10-16 15:48:07 -0600 )edit

answered 2017-10-16 16:27:32 -0600

ozeszty gravatar image

updated 2017-10-17 03:25:57 -0600

Firstly use versionlock to keep for now last known good kernel (this will keep it from removing from system and grub):

dnf install python3-dnf-plugins-extras-versionlock
dnf versionlock add kernel-4.12.9-300.fc26

Post your hardware details inxi -SMGsxxz and apply all available system updates dnf update --refresh, after that we'll see what to do next.


If you configured your user to be an administrator, you can prepend sudo to run those commands. Another option is to use su to login as root and run many commands sequentially without using sudo.

Use dnf remove kernel*-4.12.13-300.fc26 to resolve your update problem - this kernel didn't work anyway.

You'll also have to update your GPU driver, or remove it (how to do that depends on how you installed it) and install one that will be updated with the rest of your system updates:

If all those updates help, then you'll have to unlock old kernel with dnf versionlock delete kernel-4.12.9-300.fc26.

edit flag offensive delete link more


when running "dnf remove kernel*-4.12.13-300" is kept saying package not found... I went to /boot to maek sure it didn't disappear somehow, and there's still config-4.12.13-300.fc26.x86-64, with the same for 4.12.14, and 4.12.9. I'll look into updating the graphics drivers now + Looks like graphics drivers are up to date

peaceblaster gravatar imagepeaceblaster ( 2017-10-16 19:00:22 -0600 )edit

384.90 are the latest stable drivers, to install them now from RPMFusion you have to append --enablerepo=rpmfusion-nonfree-updates-testing to dnf command.

dnf remove kernel*-4.12.13-300.fc26 will remove the kernel, my mistake...

ozeszty gravatar imageozeszty ( 2017-10-17 03:24:28 -0600 )edit

Something's weird here, because it still thinks it has those drivers, and still says "Problem: package kernel-4.12.13-300.fc26.x8664 requires kernel-core-uname-r = 4.12.13-300.fc26.x8664, but none of the providers can be installed" when I try to remove the non-functioning kernel

peaceblaster gravatar imagepeaceblaster ( 2017-10-17 12:35:33 -0600 )edit

Try removing with -v parameter and post here full output using

ozeszty gravatar imageozeszty ( 2017-10-17 14:56:34 -0600 )edit

Question Tools

1 follower


Asked: 2017-10-16 13:58:27 -0600

Seen: 106 times

Last updated: Oct 17 '17