On 12/28/2014 06:38 PM, Ludwig Nussel wrote: I've skipped the quoting. I am seeing two serious problems with the 20141225 update. I have not yet filed any bug report. Problem 1: I am unable to boot the 3.18 kernel. My Tumbleweed system uses an encrypted LVM, and the kernel is not reading the keyboard. So there is no way that I can enter the encryption key. I am still able to boot the 3.17.4 kernel. Problem 2: Secure-boot seems to be broken. I get an immediate message about "invalid signature." I would like any comments on this. My hardware does not recognize "shim" with two signatures, so I have to follow the recommended procedure for removing one of the signatures. I did an "md5sum" check and the new "shim.efi" looks to be identical to the old "shim.efi". So I simply copied my previous version with the second signature stripped that had worked with Tumbleweed prior to this update. Using that, I still get an immediate "invalid signature" message. If I set my hardware to boot from "\EFI\Boot", then secure-boot works and I get to the kernel selection stage of the grub menu. That directory has the old efi boot stuff, with "shim.efi" (stripped to a single signature) renamed to "bootx64.efi". It looks to me as if shim.efi is objecting to the signature on "grub.efi" (or whatever it is checking at that stage, before it loads a menu). If I disable secure-boot, then I get to a grub menu where I can select a kernel that boots (the 3.17.4 kernel). -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org