Re: TPM Error on Warm Boot From F38

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


On 30/8/23 01:54, stan via users wrote:
On Tue, 29 Aug 2023 18:08:59 +1000
Stephen Morris <samorris@xxxxxxxxxxxxxxx> wrote:

Having done a warm boot and gotten the tpm error, I opened the grub
console and issued the ls subcommand which showed that what the
system sees as hd2 on a normal boot, when the tpm error occurs
"grub/system" is seeing that same drive as hd0.
Hence it sees (hd0,gpt1) through (hd0,gp9) and for hd1 through hd4 it
only sees gpt1, which matches the ssd drive and the four hard disks
which only 1 partition each.
What I don't understand is when the error occurs, why grub is seeing
                                                             ^ not?
the physical drives in the order that I would expect them go be given
the way they are physically plugged into the motherboard. And more
importantly, what component update is causing this issue?
Was grub updated?
The one thing I haven't tried yet is for a normal boot, booting off
an older kernel to see if it gets the issue, and if not, the issue is
potentially the current kernel?
Yes that would be a good test.  There have been a lot of changes to the
fedora kernel SPEC file to clean it up, and streamline it.  It isn't
impossible that you are seeing a corner case side effect of that,
though unlikely.


To answer Stan's question from earlier, I've had lots of warm start
reboots since updating the bios and adding in the keys for the
nvidia drivers.
Trying to identify which package may be causing the issue might be
problematic, as I was on holidays for 6 weeks and did an update
when I got back, which updated around 350 packages.
I'll check the grub console when I reboot my system.
One other thing I forgot to mention, there is also an entry in the
menu to boot into a UEFI shell, and when I try to boot into that it
also gets the tpm errors.

Just as an off-topic question, hd2 is my solid state drive
containing windows drive C, the UEFI partitions for Windows, F38
and Ubuntu, and the F38 and Ubuntu /boot partitions. That drive is
plugged into the first physical port on the motherboard, so why
does F38 not see it as hd0? The two drives it sees as hd0 and hd1
are plugged into ports 3 - 6 (I've got 4 3 TB hard drives).
I don't have an answer, but I wonder if there is an obscure setting in
the bios that is responsible.  What is the boot order set to?
The bios is set to boot off my ssd drive, which is the first drive plugged into the motherboard, which is the device that Fedora sees as hd2.

I did a system update yesterday, which upgraded the kernel to 6.4.12 and also updated grub, and then updated the grub menus via grub2-mkconfig as I always do, and that has not made any difference to the issue. I have grub configured to build sub-menus for all the kernel entries as well as showing the latest kernel in the main menu, so that I have all the Fedora kernels and Ubuntu kernels in sub-menus. What I have now found is that if I open up a sub-menu, that is when the tpm error occurs, and since the grub update it is now producing an extra error telling me to load a kernel first (what I don't understand is that message seems to be coming from an I386 sub-folder but my environment is 64 bit, or does that mean that somehow or other grub has reverted to 32 bit?). I've also mentioned in another thread, that if when I get the tpm errors I edit the grub menu entry and change all occurrences of hd2 to hd0, even though it continues to display the tpm errors it successfully boots into F38. It seems as though at the moment it boots normally if I select a main menu entry to boot from, but only if the tpm error hasn't already occurred. If the tpm error has occurred none of the menu entries will boot, which includes the Chainloader entry for Windows.

Having started my machine from a cold start, when the grub menu's were displayed, I went to the grub command line and issued the LS command to list all devices, that showed my boot device as hd0 (hd0,gpt1 - hd0,gpt9), and then when I exited from the command line, and selected the menu entry for the latest Fedora kernel, which specified to boot from hd2,gpt7 (this is the fedora UEFI partition), it successfully booted into Fedora. How is this possible when the grub command line is indicating that grub is seeing the devices differently? What I might add to this is that the way the grub command line is showing the devices is the way I would expect them to be shown given the way the devices are physically connected to the motherboard.


users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct:
List Guidelines:
List Archives:
Do not reply to spam, report it:

Attachment: OpenPGP_0x594338B1DE179AB2.asc
Description: OpenPGP public key

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct:
List Guidelines:
List Archives:
Do not reply to spam, report it:
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux