Hello Matt, > On Tue, 28 May, at 08:40:32PM, Felix Braun wrote: > > When I try to write something to the efi boot variables, I get an kernel > > error > > > > # efibootmgr > > BootCurrent: 0000 > > Timeout: 1 seconds > > BootOrder: 0000,0002,0003 > > Boot0000* Linux > > Boot0002* Hard Drive > > Boot0003* CD/DVD Drive > > # efibootmgr -n2 > > # tail /var/log/messages > > [Firmware Bug]: Broken EFI implementation is returning > > MaxVariableSize=0 > It sounds like your machine isn't initiating garbage collection. Try > adding the efi_no_storage_paranoia kernel parameter to your kernel > cmdline. That seems to have worked. With that parameter added, things work again. Thank you! How can I prevent the efi storage from filling up? Is there a way to initiate garbage collection manually? > > On boot up, I get a number of the following error messages: > > > > e820: too many entries; ignoring [mem 0x01d8a000-0x01d8ffff] > > e820: too many entries; ignoring [mem 0x01d90000-0x01d91fff] > > ... > I doubt that's related but it's certainly not good. Could you paste your > full dmesg? What boot loader are you using? It does seem to be related as these error messages go away with efi_no_storage_paranoia. I'm using EFISTUB to boot linux directly from the EFI shell. I'm attaching gzipped dmesg output (with efi_no_storage_paranoia). Thanks again! Regards Felix
Attachment:
dmesg.gz
Description: application/gzip
