# Unable to boot after upgrading to kernel 4.6.3

I just reinstalled F24 on a ThinkPad T-460s (the only thing about the laptop which is a bit non-standard is that I have a NVMe-PCIe disk). The image I installed from has kernel 4.5.5. After the install, I ran dnf upgrade which brought me up to kernel 4.6.3. I installed some other things and did some superficial tweaking before rebooting.

When I rebooted and selected 4.6.3 from the GRUB menu, my machine just hung immediately after. (To see if I was just being impatient, I also let it sit for an hour or so while I went out to dinner; it was still hung after I got back.)

Since I had just reinstalled, I decided to reinstall again. This time I just upgraded the kernel (dnf upgrade kernel) and immediately rebooted. It still hangs immediately after selecting the kernel from the GRUB menu.

I can fall back to kernel 4.5.5 and everything works just fine.

I'm honestly not really sure how to start troubleshooting this one and I welcome any suggestions.

edit retag close merge delete

Sort by » oldest newest most voted

I finally got around to playing with this a bit more.

I got rid of the rhgb and quiet parameters hoping to see something useful, but it still hung immediately. I also tried getting rid of rd.lvm.lv=xxx parameters (per @jorti), but nothing.

So, I did another clean install. This time I updated the kernel (dnf upgrade kernel) and ran grub2-mkconfig. I rebooted and it started up just fine.

So, I'm inclined to believe that something went awry with the grub.cfg before, but I just have this poor circumstantial evidence to go on.

However, I'm now successfully running F24 on kernel 4.6.3-300.fc24.x86_64.

more

I'm also have problems booting, but I'm not sure if it is the same thing, as I see a few systemd lines and error messages. My problem seems related to the initrd being unable to load the lvm volumes.

I've workarounded it by editing the kernel grub line and removing all the "rd.lvm.lv=xxx"

Just give it a try to see if you have luck.

more

Sounds like your system is getting farther than mine.

I'll try your workaround this evening.

( 2016-07-05 09:59:12 -0500 )edit