On Tue, 2014-12-30 at 21:32 +0100, Axel Angel wrote:
@@ -7511,7 +7511,6 @@
grub-install: info: executing efibootmgr --version /dev/null /dev/null.
grub-install: info: executing modprobe -q efivars.
grub-install: info: executing efibootmgr -c -d /dev/sda -p 1 -w -L debian -l
Was this in the state where things crashed or the working state (but
with the second issue you mentioned occurring)?
This is the diff between -18 and -19 when nothing crash in both case.
This shows there is a visible change for efibootmgr.
I think there is a pretty good chance that this is
On Wed, 2014-12-31 at 12:08 +0100, Axel Angel wrote:
You might find that adding noexec=off to your kernel command line
worksaround this issue.
I can give it a try. Question: isn't it dangerous to enable this flag in
normal use? I guess so.
It's not really dangerous as such, there would
Package: grub-efi-amd64
Version: 2.02~beta2-19
Severity: important
Dear Maintainer,
* What led up to the situation?
Usual daily upgrade. Including grub-efi-amd64:
2.02~beta2-18 - 2.02~beta2-19~i
* What exactly did you do (or not do) that was effective (or
ineffective)?
On Mon, 2014-12-29 at 11:30 +0100, Axel wrote:
Package: grub-efi-amd64
Version: 2.02~beta2-19
Severity: important
Dear Maintainer,
* What led up to the situation?
Usual daily upgrade. Including grub-efi-amd64:
2.02~beta2-18 - 2.02~beta2-19~i
(is ~i a typo here?)
The
5 matches
Mail list logo
