This is apparently a kernel bug. It should be introduced after bug 703574. In an attempt to protect more Samsungs from bricking, kernel prevented you from using more than 50% firmware storage with efi variables. Somehow the algorithm of determining 50% gets overzealous with different firmware, and on your machine it decides it's always over 50% and stops you from doing anything no matter how. This is why you can't create new boot entries.
kernels affected: After upstream 68d929862e29a8b52a7f2f2f86a0600423b093cd Stable 3.2.41 - 3.2.y 3.8.3 - 3.8.y kernels "fixed": After upstream 31ff2f20d9003e74991d135f56e503fe776c127c (and patches around) 3.9 - 3.9.y Upstream 8c58bf3eec3b8fc8162fe557e9361891c20758f2 provides a workaround of booting with kernel parameter efi_no_storage_paranoia, which is also only available in 3.9+. I just ran into this bug when updating kernel from 3.8.5~experimental. Unfortunately all these fix and workaround aren't available in debian kernels (3.2; 3.8, which is EOL upstream). I'll try to send a backport of these sometime to [email protected] if I get the time. The "fix" is a bit weird that it got merged despite two reports of it not fixing the bug. Anyway, any further fix has to be based on it so never mind... Lingzhu Xiang -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
