Hi folks,
Returning to an old bug that's still affecting some people...
I can see that lots of you are reporting problems with efibootmgr
failing to write/update UEFI boot entries, complaining about lack of
space.
In #852513, Norbert *may* have found the cause - lots of data being left
in
Hi,
I'm facing the same problem caused most probably by the latest grub update.
Any issue how to fix or hack to have bootable laptop?
Here are some of my logs:
# efibootmgr -c -l "\\EFI\\debian\\grubx64.efi" -L "Debian"
efibootmgr: Could not set variable Boot: No space left on device
The problem was that the nvram entry wasn't properly created under sid.
I managed to login in a stable distribution I have on the same system to
create it.
Am Montag, den 24.08.2015, 10:28 +0200 schrieb Giorgio Valocchi:
The problem was that the nvram entry wasn't properly created under
sid.
I managed to login in a stable distribution I have on the same system
to
create it.
In that case it would be a bug either in efibootmgr or the Linux
On Sun, 16 Aug 2015 08:42:48 +0200 Felix Zielcke fziel...@z-51.de wrote:
Am Mittwoch, den 21.01.2015, 00:58 + schrieb Steve McIntyre:
On Wed, Jan 21, 2015 at 06:55:05AM +0900, Mike Hommey wrote:
On Tue, Jan 20, 2015 at 01:44:37PM +, Steve McIntyre wrote:
The automatic setup
Am Mittwoch, den 21.01.2015, 00:58 + schrieb Steve McIntyre:
On Wed, Jan 21, 2015 at 06:55:05AM +0900, Mike Hommey wrote:
On Tue, Jan 20, 2015 at 01:44:37PM +, Steve McIntyre wrote:
The automatic setup of grub-install calling efibootmgr won't be
touching the grub entry at all
On Mon, Jan 19, 2015 at 07:42:37AM +0900, Mike Hommey wrote:
On Sun, Jan 18, 2015 at 11:37:28AM +, Steve McIntyre wrote:
The ENOSPC handling has been bad in the past, but it's not clear that
was the cause of your original bug. :-/ *Now* it's a very bad state to
be in, and may cause other
On Tue, Jan 20, 2015 at 01:44:37PM +, Steve McIntyre wrote:
On Mon, Jan 19, 2015 at 07:42:37AM +0900, Mike Hommey wrote:
On Sun, Jan 18, 2015 at 11:37:28AM +, Steve McIntyre wrote:
The ENOSPC handling has been bad in the past, but it's not clear that
was the cause of your original
On Wed, Jan 21, 2015 at 06:55:05AM +0900, Mike Hommey wrote:
On Tue, Jan 20, 2015 at 01:44:37PM +, Steve McIntyre wrote:
The automatic setup of grub-install calling efibootmgr won't be
touching the grub entry at all - it's set up to only play with
debian entries. So that should be safe.
On Sun, Jan 18, 2015 at 08:16:51AM +0900, Mike Hommey wrote:
On Sat, Jan 17, 2015 at 05:22:52PM +, Steve McIntyre wrote:
On Sat, Jan 17, 2015 at 04:16:56PM +0900, Mike Hommey wrote:
On Fri, Jan 16, 2015 at 10:28:51PM +, Steve McIntyre wrote:
Hi Mike,
Have you seen this again
On Sun, Jan 18, 2015 at 08:22:13AM +0900, Mike Hommey wrote:
With the attachment this time
...
9167 close(3) = 0
9167
access(/sys/firmware/efi/vars/Boot0001-8be4df61-93ca-11d2-aa0d-00e098032b8c/data,
F_OK) = -1 ENOENT (No such file or directory)
9167
On Sun, Jan 18, 2015 at 11:37:28AM +, Steve McIntyre wrote:
The ENOSPC handling has been bad in the past, but it's not clear that
was the cause of your original bug. :-/ *Now* it's a very bad state to
be in, and may cause other problems too. On the Dell machine you have,
I'm not personally
On Sat, Jan 17, 2015 at 05:22:52PM +, Steve McIntyre wrote:
On Sat, Jan 17, 2015 at 04:16:56PM +0900, Mike Hommey wrote:
On Fri, Jan 16, 2015 at 10:28:51PM +, Steve McIntyre wrote:
Hi Mike,
Have you seen this again recently? Is it still happening for you?
As a matter of fact,
On Sat, Jan 17, 2015 at 04:16:56PM +0900, Mike Hommey wrote:
On Fri, Jan 16, 2015 at 10:28:51PM +, Steve McIntyre wrote:
Hi Mike,
Have you seen this again recently? Is it still happening for you?
As a matter of fact, it hasn't happened recently. That being said, I'm
not upgrading grub
On Wed, Oct 29, 2014 at 09:19:26PM -0300, Ibirisol wrote:
Hi there,
I have the same problem here. I'm using rEFInd to boot.
Sorry, but I think you're seeing a slightly different bug here.
# efibootmgr -c -l \\EFI\\debian\\grubx64.efi -L Debian -v
Alternate GPT is invalid, using primary GPT.
[ Hoping to help investigate this... ]
On Fri, Oct 24, 2014 at 07:30:26PM +0900, Mike Hommey wrote:
On Mon, Oct 13, 2014 at 03:45:31PM +0100, Colin Watson wrote:
On Mon, Jul 28, 2014 at 09:26:22AM +0900, Mike Hommey wrote:
After the upgrade from 2.02~beta2-10 to 2.02~beta2-11, a reboot just
On Fri, Jan 16, 2015 at 10:28:51PM +, Steve McIntyre wrote:
Hi Mike,
Have you seen this again recently? Is it still happening for you?
As a matter of fact, it hasn't happened recently. That being said, I'm
not upgrading grub that often, but I happen to have upgraded it today,
and a reboot
Hi there,
I have the same problem here. I'm using rEFInd to boot.
---
# dpkg -l efibootmgr
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Nome
On Mon, Oct 13, 2014 at 03:45:31PM +0100, Colin Watson wrote:
On Mon, Jul 28, 2014 at 09:26:22AM +0900, Mike Hommey wrote:
After the upgrade from 2.02~beta2-10 to 2.02~beta2-11, a reboot just got
me under Windows. The EFI boot menu had two entries for Windows (I don't
think it had two in
On Mon, Jul 28, 2014 at 09:26:22AM +0900, Mike Hommey wrote:
After the upgrade from 2.02~beta2-10 to 2.02~beta2-11, a reboot just got
me under Windows. The EFI boot menu had two entries for Windows (I don't
think it had two in the past, but maybe it did, and that's not related),
and one for
Package: grub-efi-amd64
Version: 2.02~beta2-11
Severity: critical
After the upgrade from 2.02~beta2-10 to 2.02~beta2-11, a reboot just got
me under Windows. The EFI boot menu had two entries for Windows (I don't
think it had two in the past, but maybe it did, and that's not related),
and one for
21 matches
Mail list logo
