Hi, Arbol One wrote: > > With the memory stick containing the Debian installation files > > plugged, I proceeded to reboot the computer. The booting process > > then tells me something I've never seen before, something along the > > lines of > > > > Something went terribly wrong. Security Policy Violation, ... , > > SBAT self check failed,
David Christensen wrote: > It would help if you provided the following information: > ... various valid questions ... We should add that SBAT is the protocol by which "shim", the early boot stage of GRUB with EFI Secure Boot, revokes the signatures for older versions of GRUB in which security flaws have been found. See "What the fuck is an SBAT and why does everyone suddenly care" https://mjg59.dreamwidth.org/70348.html So it seems that some software has installed a new SBAT demand for a "security generation" which the boot loader on the memory stick does not fulfill. The usual workaround is to disable Secure Boot in order to boot via GRUB and to then update GRUB in the hope to get a new acceptable set of GRUB binaries in the boot process. See for example https://askubuntu.com/questions/1523438/verifying-shim-sbat-data-failed-security-policy-violation Whether this has anything to do with the keyboard not working is beyong my technical scope. This mail is just to explain why an older Debian GNU/Linux might fail with an EFI firmware which has seen newer MS-Windows or GRUB or GNU/Linux. (Dunno whether GRUB and GNU/Linux change the SBAT demand. In any case they could do.) Have a nice day :) Thomas
