unable to boot after updating from fedora 24 4.7.5-200 to fedora 24 4.7.6-200

[myopic]

I am encountering the same problem in a fully upgraded system.

Unable to boot into kernel-4.7.6 and now unable to boot into kernel-4.7.7.

All of your reported symptoms appear the same and unfortunately this includes no log information via journalctl while attempting to boot into kernel-4.7.6 or kernel-4.7.7

I can still boot into kernel-4.7.5-200.fc.x86_64 ( Graphics are not 100% stable, some flickering especially when resizing windows and sluggish response ) This makes me think that the problem is likely to be associated with AMD / Updated graphics stack.

Have tried downgrading the efibootmgr which was upgraded with kernel-4.7.6.. but that had no effect.

If I downgrade xorg to 1.17 and install AMD proprietary driver ( with patch ) on kernel-4.7.5, graphics are stable. ( Obviously this has no effect on booting issue but proves graphics card is O.K. )

I am running F24 on an Acer Aspire 725-C7Xkk
AMD C-70 APU with RADEON HD7290 GRAPHICS

[MarkClerk]

Hello Myopic
thank you for this feed back.
It seems that i'm not the only one in trouble
i have reported your comment to the redhat bugzilla here : https://bugzilla.redhat.com/show_bug.cgi?id=1384238

Did you try to debug dracut like this

Could you tell me how you install kernel 4.7.7 (gnome software ? Terminal ?)

The thing is that we can not run on 4.7.5 forever. Even if 4.7.6 and 4.7.7 do not seem to bring security updates (if anybody can confirm me ) we will soon run too old kernel if nothing is done...

Right now i did every tests i can do (thanks for the other user's help), spend a lot to solve this issu.

I would like to do something but i do not know what to do.....

regards

[srakitnican]

That suggest that initramd is not being loaded at all. Found the previous thread: http://forums.fedoraforum.org/showthread.php?t=310467

So the next step would be to downgrade microcode_ctl and to rebuild initramd for newest kernel and seeing if that fixes the issue. https://bugzilla.redhat.com/show_bug.cgi?id=1353103#c19

Before that you could try with kernel option "dis_ucode_ldr".

[MarkClerk]

Hello
thank you semirocket.
If it is easy for, you could you provide me the terminal commands to downgrade microcode_ctl and to rebuild initramd ?
And to think it still usefuu to push test about dragut like you suggest yesterday ?

Regards

[srakitnican]

Hello,

I don't think dracut page is relevant since you are not getting to that stage. You can just add "dis_ucode_ldr" to kernel command line for a start to see if that helps - On boot menu (grub) choose your new kernel and press 'e'. Next use arrow keys to find a line that starts with linux, append that option to the end of the line and press Ctrl+X to boot.
https://docs.fedoraproject.org/en-US...B-runtime.html

microcode_ctl is a dnf package, to downgrade it you can use:

$ sudo dnf downgrade microcode_ctl

To rebuild initramd for kernel 4.7.6-200.fc24.x86_64 you would enter:

$ sudo dracut -f --kver 4.7.6-200.fc24.x86_64

[myopic]

I used terminal to upgrade to kernel 4.7.7 .

Have tried downgrading microcode_ctl
dnf downgrade microcode*

This took it down to v.2.1-11 from v.2.1-13

Then cd into /boot and ran
dracut initramfs-4.7.7-200.fc24.x86_64.img 4.7.7-200.fc24.x86_64

Then rebooted... Same problem no boot.

I have also tried adding dis_ucode_ldr ... still no boot

[MarkClerk]

Hello
1 i tried to add "dis_ucode_ldr" --> still have the problem

2 i have also upgraded to kernel 4.7.7 (terminal)
then
dnf downgrade microcode_ctl in commandline
then
dracut -f --kver 4.7.7-200.fc24.x86_64 in commandline
--> still have the problem
3 if i use a light distribution (lxde) instead of gnome, does it change anything ? I guess not because the boot crashes before the graphical destkop is loaded

What do you suggest me to do now ?

regards to everyone

[myopic]

I am going to uninstall both non-working kernels.
Then downgrade all packages since last working kernel ( 4.7.5 ) was installed using:

dnf history list
dnf history info 1,2,3,etc
dnf downgrade x,y,z,etc

Then try reinstalling kernel-4.7.6

This could take some time so don't expect update for a quite a while.

[antikythera]

10/10 for effort there myopic. good luck with that

[MarkClerk]

Hello Myopic,
thank you for being so involved in this matter.
By the way the kernel-4.7.7 is now available with classic dnf upgrade.
by the way again, samoht0 updated the 1384238 bugzilla redhat ticket : he is thinking about a UEFI related issue

Let you know if your method solved the problem.

Good luck

keep in touch

Regards

[srakitnican]

If you are feeling adventurous, you could also try to regenerate initramfs for a working kernel with current packages. If it doesn't boot with a previous working kernel then that could possibly tell something.

Before you do that you can archive currently working /boot/initramfs-<kernel-version> file so that you can restore it later if needed.

For example:

$ sudo cp -a /boot/initramfs-4.7.5-200.fc24.x86_64.img{,.orig}
$ dracut -f --kver 4.7.5-200.fc24.x86_64

If you are unable to boot you can edit grub line that starts with "initrd" to point to archived file:

initrd /initramfs-4.7.5-200.fc24.x86_64.img.orig

[MarkClerk]

Hello semiRocket,
that becomes hard for me. Since i am not an expert with this kind of manipulation, i'm afraid to definitely make my 4.7.5-200 unbootable definitively...
Once you edit grub line withe initrd like this : 'initrd /initramfs-4.7.5-200.fc24.x86_64.img.orig'
How do you make it bootable again ?
I guess asking this question is a prove that my level is not very high !

myopic seems to be more expert than me ! I hope the tests he is currently doing will give us more clues.

Thank you to everybody for the contribution for solving this problem

Regards

[myopic]

Well have had fun afternoon downgrading, dnf now informs me I have 178 packages to upgrade.
I have installed kernel-4.7.7 on top of this downgraded install, but it still refuses to boot.
Unless anyone has any suggestions regarding working with this downgraded install, I will upgrade to current status and have a play with semiRocket's initramfs idea.
I wouldnt be surprised if it was a UEFI issue.

[myopic]

MarkClerk good news.

Thanks to samoht0 at bugzilla.redhat for the link to kernel-parameters, and suggestion.

I found that if you add kernel option:

efi=noruntime
kernel-4.7.7 boots.

This is currently on my downgraded system. I will wait to hear if it works for you before upgrading.

[MarkClerk]

Hello
unfortunately i can not boot even with efi=noruntime.
But with efi=noruntime i can now see messages.
The journalctl parameters do not show this

i'm gone a send you this image since i can not add it here
regards