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.
I've had more time to work on this, and have a few more things to report. This problem initially happened after I installed the latest updates in Windows 11, and then attempted to restart into Tumbleweed. In the middle of some troubleshooting, the Bios updated on it's own, without my selecting an update. But that didn't change anything regarding the booting, as I still can't boot normally. Subsequently, I tried reinstalling Win 11, but that didn't help. I've found that now the computer won't recognize uefi formatted usb sticks that I have made with Rufus on Win10. The only way that it recognizes them to boot from them (such as g-parted, supergrub2, or Tumbleweed installation iso) is to disable secureboot in the bios. This never was an issue before the booting problem. 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. I have to go into the bios boot selection list to boot the windows bootloader for a successful boot to Windows. When I try to select Tumbleweed in the bios boot menu, I get this message again: Verifying shim SBAT data failed. Security Policy Violation. Something has gone seriously wrong: SBAT Self-check failed: Security Policy Violation. If I deselect Secureboot in the Bios, the grub operating selection screen presents, and I can select the operating systems as I normally would. But booting doesn't occur normally. 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. 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