I could have solved this problem two weeks ago had I just read the paper manual a bit more closely (and not just to the point where I realised I lost the missing plug)

ok so I was able to fix it and it was ultimately my fault but also this experience wasn't normal

... also apparently I'm now using Debian live media to troubleshoot my Arch system since archboot no longer boots on this system (:

like at this point I'm not even 100% sure if the original boot issue is even Secure Boot ("invalid parameter")

I think this would be somewhat smooth sailing with a more recent device, a bit better firmware, and access to the Secure Boot setup mode... but alas

like I did install the firmware update for that afaict but in uefi I can only the see old keys... which would explain why old but not new archboot works (but not why new Debían does, and old archboot randomly stopped working)

like especially with the shim revocation and the new Microsoft keys, and the entire thing being SO difficult to debug.... I still haven't been able to reliably figure out if the new keys are installed in this machine or not

skalierungsproblem, weil sobald du zu Mens-N kommst weiß man nimmer ob die alle Mensen oder die Mens-N meinst ! weil es sich gleich anhört - leider daher TECHNISCH nicht möglich

like at this point I know but still that's the first thought every time

the energy, the absurdity, the community in the comments - it still exists