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

[MarkClerk]

Hello
i can not send you message even with private message.
i add them as attachment here : https://bugzilla.redhat.com/show_bug.cgi?id=1384238
If you want send me a email adress as private message.
I will not use it except for sending you these images

regards

[MarkClerk]

Hello
i also try to add this boot parameters : kernel.panic=1
I have the same problem

regards

[myopic]

This downgrade may have been some help:


[root@AI one]# dnf history info 139
Transaction ID : 139
Begin time : Sun Oct 16 15:13:17 2016
Begin rpmdb : 2086:3d4d44541f88b91b683f11b73b05489c83b043da
End time : 15:13:34 2016 (17 seconds)
End rpmdb : 2086:fda28d741dc428b3b3f124651e271ef517483d05
User : one <one>
Return-Code : Success
Command Line : downgrade ModemManager ModemManager-glib c-ares ca-certificates efibootmgr mokutil --allowerasing
Transaction performed with:
Installed dnf-1.1.10-1.fc24.noarch @updates
Installed rpm-4.13.0-0.rc1.27.fc24.x86_64 @koji-override-0
Packages Altered:
Downgrade ModemManager-1.6-0.3.rc3.fc24.x86_64 @fedora
Downgraded 1.6.2-1.fc24.x86_64 @updates
Downgrade ModemManager-glib-1.6-0.3.rc3.fc24.x86_64 @fedora
Downgraded 1.6.2-1.fc24.x86_64 @updates
Downgrade c-ares-1.11.0-1.fc24.x86_64 @fedora
Downgraded 1.12.0-1.fc24.x86_64 @updates
Downgraded ca-certificates-2016.2.10-1.0.fc24.noarch @updates
Downgrade ca-certificates-2016.2.7-1.0.fc24.noarch @fedora
Downgrade efibootmgr-0.12-3.fc24.x86_64 @fedora
Downgraded 14-3.fc24.x86_64 @updates
Downgrade efivar-libs-0.23-1.fc24.x86_64 @fedora
Downgraded 30-3.fc24.x86_64 @updates
Downgrade mokutil-1:0.2.0-4.fc24.x86_64 @fedora
Downgraded 1:0.3.0-2.fc24.x86_64 @updates

[myopic]

journal.txt

Downgrade-list.txt

MarkClerk,

Have attached full downgrade list, and journal of kernel-4.7.7 boot.

I don't suggest you downgrade all, but possibly anything connected to efi might have some effect.
The journal gives all my boot parameters near the start.
Good Luck.

[MarkClerk]

Hello Myopic,
thanks for your return

samoht0 gives us information :

Considering your downgrade list from
http://forums.fedoraforum.org/showth...=311784&page=3
all packages of this efi-stuff update (which was pushed stable recently)
https://bodhi.fedoraproject.org/upda...016-c6141386ba
look suspicious to me.
So you may try to upgrade the system leaving this packages out (if installed):

efibootmgr-14-3.fc24
pesign-0.112-4.fc24
dbxtool-7-2.fc24
fwupd-0.7.2-4.fc24
mokutil-0.3.0-2.fc24
fwupdate-8-2.fc24
efivar-30-3.fc24

i will try to downgrade those one
Do you know what is the exact command : something like this : 'dnf downgrade efibootmgr-14-3.fc24' ?
do you need to rebuild initramd for kernel 4.7.7-200.fc24.x86_64 after that like this : 'dracut -f --kver 4.7.7-200.fc24.x86_64'

by the way shame on me i just realised that i can join image directly....
i give you the result of a boot with this parameter : efi=noruntime

quietparameterboot.jpg
noQuietparameterBoot.jpg

regards

[myopic]

Have just finished upgrading.

Everything worked so I upgraded efibootmgr, efivar-libs, and mokutil ( none of others present )

I then rebooted into kernel-4.7.5 and deleted kernel 4.7.7

I rebooted for good measure then installed kernel-4.7.7 on upgraded efi packages.

Then rebooted into new kernel-4.7.7 .... which I could only do using

efi=noruntime

So now I'm a bit stumped on your situation.


To downgrade:

dnf downgrade efibootmgr no need for version number do

Use --allowerasing if there are dependencies

If you do erase a kernel make sure you do enter version number .. or you could erase your running kernel.

[myopic]

If you uninstall efibootmgr
efivar
mokutil
and any of the others that are on your system

To check if they are installed use:

rpm -qa pesign*
rpm -qa fwupd*

Then uninstall kernel-4.7.7

dnf remove kernel-core-4.7.7-200.fc24.x86_64

That should remove kernel with dependencies and remove old initramfs from /boot

Then install kernel on downgraded efi packages:

dnf install kernel ( there should only be one available )

This should create a new initramfs in boot.

Then try and boot new kernel adding

efi=noruntime

in boot parameters

---------- Post added at 01:08 PM ---------- Previous post was at 01:05 PM ----------

downgrade not uninstall efi packages

---------- Post added at 01:09 PM ---------- Previous post was at 01:08 PM ----------

downgrade not uninstall efi packages

[MarkClerk]

thanks
i'm gone a try that
you suggest me to uninstall efibootmgr efivar mokutil ...before uninstalling kernel ? if i just uninstall kernel, are they not uninstalled to ?

Should i do the same for kernel 4.7.6 ?

regards

[myopic]

Sorry I meant downgrade efibootmgr, efivar-libs, mokutil, etc

Then remove kernel-4.7.7

Reboot to make sure kernel-4.7.7 has been removed.

Then install kernel-4.7.7

Then try to boot kernel-4.7.7 with extra parameter.

[MarkClerk]

Hello
so :
1 i downgraded efibootmgr, efivar-libs, mokutil with dnf downgrade .....
2 fwup version was already the oldest one
3 pesign, dbxtool fwupdate were not downgraded because they were not installed
4 remove kernel-4.7.6
5 remove kernel-4.7.7
6 close pc
7 reboot on 4.7.5
8 install kernel-4.7.7
7 reboot on 4.7.7 with efi=noruntime in boot parameters
--> i still have the problem (cf images previously provided) with 'end kernel panic not syncing attempted to kill init'

i do not know what to do....please do not tell me to find another OS...i am so kind of fedora

regards

[myopic]

I'm afraid all I can suggest is to downgrade microcode_ctl as well and then reinstall kernel-4.7.7.

Meanwhile have you tried adding

earlyprint=efi

to get a full readout of error messages, to send to bugzilla? Hopefully they will be able to work out what has upset UEFI and suggest a fix.

A couple of other parameters that you could throw in:

efi=old_map
efi=nochunk
efi=debug

[MarkClerk]

thank you
does earlyprint=efi will print information on journalctl, or just on the screen ?

i'm will try that

regards

[myopic]

All I can offer is what it says in kernel-parameters.txt

earlyprintk is useful when the kernel crashes before
the normal console is initialized. It is not enabled by
default because it has some cosmetic problems.

Append ",keep" to not disable it when the real console
takes over.

---------- Post added at 04:01 PM ---------- Previous post was at 03:58 PM ----------

earlyprintk

I missed off the k at the end.

---------- Post added at 04:02 PM ---------- Previous post was at 04:01 PM ----------

So you need to use

earlyprintk=efi

[MarkClerk]

ok thank you so much for helping me !
and how can i print it on a text file ? from journalctl ?
regards

[myopic]

journalctl --since 2016-10-17 >> journal-log

will dump it in your /home dir ( depending who you are logged on as )