On 29.04.2023 16:49, Mark Misulich wrote:
On Fri, 2023-04-21 at 15:34 +0300, Andrei Borzenkov wrote:
On Fri, Apr 21, 2023 at 3:12 PM lxmark <munguanaweza@gmail.com> wrote:
Full output of
journalctl -b --no-pager --full
This needs to be run as root, not user.
Sorry, I got distracted, so missed you reply and now I cannot download log. But recently I noticed grub2 changelog that fixes filesystem type detection on disks with 4K sectors. What sector size your disk has? ...
I can't boot either Windows 11 or Tumbleweed from Grub, with secure boot activated in the bios. When I try to boot the computer in expectation of seeing the grub operating system selection menu, the grub screen never appears and I get a message:
Verifying shim SBAT data failed. Security Policy Violation. Something has gone seriously wrong: SBAT Self-check failed: Security Policy Violation.
This means you booted very moder shim at least once. See https://bugzilla.suse.com/show_bug.cgi?id=1209985 ...
Selecting Tumbleweed boots to a screen saying:
[ 0.052339][ T1]: [Firmware Bug]: TPM interrupt not working, polling instead You are in emergency mode. After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" or "exit" to boot into default mode.
The only reason to go into emergency mode is failed mount. Check your /etc/fstab, check which devices are available. It could also be resume=... kernel option referring to a missing device.
Give root password for maintenance (or press Control-D to continue): [ 9.168832][ T1048] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
I can no longer boot into Tumbleweed at all, either with secureboot enabled or disabled in the bios.
If I select Windows in the grub selection screen while booting with secureboot disabled, I get a blue Bitlocker screen asking for my harddrive passcode to enable boot.
I had been using this laptop computer as a multiboot with Win 11 and openSUSE for a few years now without a problem. This booting problem has only just presented itself since I first posted about it on the mailing list. It seems as if the computer no longer recognizes Tumbleweed as being secureboot capable, and won't allow it to operate.
Mark