On Sun, May 4, 2014 at 12:58 PM, Philipp Kern <[email protected]> wrote: > Package: gummiboot > Version: 44-1 > Severity: normal > > I previously installed gummiboot manually. > > pkern@spike /boot/efi % sudo apt-get install gummiboot > Reading package lists... Done > Building dependency tree > Reading state information... Done > The following NEW packages will be installed: > gummiboot > 0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded. > Need to get 44.3 kB of archives. > After this operation, 121 kB of additional disk space will be used. > Get:1 http://http.debian.net/debian/ sid/main gummiboot amd64 44-1 [44.3 kB] > Fetched 44.3 kB in 0s (95.6 kB/s) > Selecting previously unselected package gummiboot. > (Reading database ... 199892 files and directories currently installed.) > Preparing to unpack .../gummiboot_44-1_amd64.deb ... > Unpacking gummiboot (44-1) ... > Processing triggers for man-db (2.6.7.1-1) ... > Setting up gummiboot (44-1) ... > Install 3.12-1-amd64 to ESP > Install 3.13-1-amd64 to ESP > Copied /usr/lib/gummiboot/gummibootx64.efi to > /boot/efi/EFI/gummiboot/gummibootx64.efi. > Failed to create EFI Boot variable entry: No such file or directory > > pkern@spike /tmp/gummiboot-44 % sudo efibootmgr -v > [sudo] password for pkern: > BootCurrent: 001A > Timeout: 0 seconds > BootOrder: > 0019,001A,001B,000C,0006,0007,0008,0009,000A,000B,000D,000E,000F,0010,0011,0012,0013 > Boot0000 Setup > Boot0001 Boot Menu > Boot0002 Diagnostic Splash Screen > Boot0003 Startup Interrupt Menu > Boot0004 ME Configuration Menu > Boot0005 Rescue and Recovery > Boot0006* USB CD > 030a2400d23878bc820f604d8316c068ee79d25b86701296aa5a7848b66cd49dd3ba6a55 > Boot0007* USB FDD > 030a2400d23878bc820f604d8316c068ee79d25b6ff015a28830b543a8b8641009461e49 > Boot0008* ATAPI CD0 > 030a2500d23878bc820f604d8316c068ee79d25baea2090adfde214e8b3a5e471856a35401 > Boot0009* ATA HDD2 > 030a2500d23878bc820f604d8316c068ee79d25b91af625956449f41a7b91f4f892ab0f602 > Boot000A* ATA HDD0 > 030a2500d23878bc820f604d8316c068ee79d25b91af625956449f41a7b91f4f892ab0f600 > Boot000B* ATA HDD1 > 030a2500d23878bc820f604d8316c068ee79d25b91af625956449f41a7b91f4f892ab0f601 > Boot000C* USB HDD > 030a2400d23878bc820f604d8316c068ee79d25b33e821aaaf33bc4789bd419f88c50803 > Boot000D* PCI LAN > 030a2400d23878bc820f604d8316c068ee79d25b78a84aaf2b2afc4ea79cf5cc8f3d3803 > Boot000E* ATAPI CD1 > 030a2500d23878bc820f604d8316c068ee79d25baea2090adfde214e8b3a5e471856a35403 > Boot000F* ATAPI CD2 > 030a2500d23878bc820f604d8316c068ee79d25baea2090adfde214e8b3a5e471856a35404 > Boot0010 Other CD > 030a2500d23878bc820f604d8316c068ee79d25baea2090adfde214e8b3a5e471856a35406 > Boot0011* ATA HDD3 > 030a2500d23878bc820f604d8316c068ee79d25b91af625956449f41a7b91f4f892ab0f603 > Boot0012* ATA HDD4 > 030a2500d23878bc820f604d8316c068ee79d25b91af625956449f41a7b91f4f892ab0f604 > Boot0013 Other HDD > 030a2500d23878bc820f604d8316c068ee79d25b91af625956449f41a7b91f4f892ab0f606 > Boot0014* IDER BOOT CDROM ACPI(a0341d0,0)PCI(16,2)ATAPI(0,1,0) > Boot0015* IDER BOOT Floppy ACPI(a0341d0,0)PCI(16,2)ATAPI(0,0,0) > Boot0016* ATA HDD > 030a2400d23878bc820f604d8316c068ee79d25b91af625956449f41a7b91f4f892ab0f6 > Boot0017* ATAPI CD: > 030a2400d23878bc820f604d8316c068ee79d25baea2090adfde214e8b3a5e471856a354 > Boot0018* PCI LAN > 030a2400d23878bc820f604d8316c068ee79d25b78a84aaf2b2afc4ea79cf5cc8f3d3803 > Boot0019* Linux > HD(1,800,f3a41,0cc0bda1-7887-4d53-9ebf-1c2febe91e60)File(\elilo.efi) > Boot001A* Linux Boot Manager > HD(1,800,64000,0cc0bda1-7887-4d53-9ebf-1c2febe91e60)File(\EFI\gummiboot\gummibootx64.efi) > Boot001B* UEFI Shell > HD(1,800,f3a41,0cc0bda1-7887-4d53-9ebf-1c2febe91e60)File(\EFI\shell\shellx64.efi) > > A bit of instrumentation says: > > pkern@spike /tmp/gummiboot-44 % sudo ./gummiboot update --path=/boot/efi > Copied /usr/lib/gummiboot/gummibootx64.efi to > /boot/efi/EFI/gummiboot/gummibootx64.efi. > /sys/firmware/efi/efivars/Boot0000-8be4df61-93ca-11d2-aa0d-00e098032b8c > Failed to create EFI Boot variable entry: No such file or directory > > pkern@spike /tmp/gummiboot-44 % ls -al > /sys/firmware/efi/efivars/Boot0000-8be4df61-93ca-11d2-aa0d-00e098032b8c > ls: cannot access > /sys/firmware/efi/efivars/Boot0000-8be4df61-93ca-11d2-aa0d-00e098032b8c: No > such file or directory > > pkern@spike /tmp/gummiboot-44 % ls -al /sys/firmware/efi/efivars > total 0 > drwxr-xr-x 2 root root 0 May 4 12:48 . > drwxr-xr-x 4 root root 0 May 2 17:16 .. > > pkern@spike /tmp/gummiboot-44 % uname -a > Linux spike.0x539.de 3.13-1-amd64 #1 SMP Debian 3.13.7-1 (2014-03-25) x86_64 > GNU/Linux > > So there are a lot of variables in /sys/firmware/efi/vars: > > root@spike:~# ls -al > /sys/firmware/efi/vars/Boot0000-8be4df61-93ca-11d2-aa0d-00e098032b8c > total 0 > drwxr-xr-x 2 root root 0 May 4 12:48 . > drwxr-xr-x 130 root root 0 May 4 12:48 .. > -r-------- 1 root root 4096 May 4 12:58 attributes > -r-------- 1 root root 4096 May 4 12:58 data > -r-------- 1 root root 4096 May 4 12:58 guid > -rw------- 1 root root 4096 May 4 12:48 raw_var > -r-------- 1 root root 4096 May 4 12:58 size > > The source says: > > fprintf(stderr, "Failed to access EFI variables, " > "efivarfs needs to be available at /sys/firmware/efi/efivars/.\n"); > > And lo' and behold: > > root@spike:~# mount -t efivarfs none /sys/firmware/efi/efivars > root@spike:~# gummiboot update --path=/boot/efi > Copied /usr/lib/gummiboot/gummibootx64.efi to > /boot/efi/EFI/gummiboot/gummibootx64.efi. > > pkern@spike /tmp/gummiboot-44 % ls -al > /sys/firmware/efi/efivars/Boot0000-8be4df61-93ca-11d2-aa0d-00e098032b8c > -rw-r--r-- 1 root root 46 May 4 12:56 > /sys/firmware/efi/efivars/Boot0000-8be4df61-93ca-11d2-aa0d-00e098032b8c > > I'm not sure what should set up efivarfs, but it is not happening for me on > jessie.
Nobody currently. It's supposed to be done by systemd, but EFI support is currently disabled in the package (I submitted a patch for that, and for enabling kernel-install to replace the scripts I currently ship for kernel installations; but have not heard back yet). The problem is that efibootmgr still uses efivars instead of efivarfs and is used by default, so it's problematic, because it is not recommended to use efivars and efivarfs at the same time. I have blacklist efi_pstore blacklist efivars and then loaded efivarfs in /etc/modules. It's currently seems to be auto mounting here, I'm not sure why. -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
