From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1csUNw-0005Jy-3g for mharc-grub-devel@gnu.org; Mon, 27 Mar 2017 09:08:36 -0400 Received: from eggs.gnu.org ([2001:4830:134:3::10]:55711) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1csUNs-0005II-Vl for grub-devel@gnu.org; Mon, 27 Mar 2017 09:08:34 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1csUNr-0006oO-AY for grub-devel@gnu.org; Mon, 27 Mar 2017 09:08:32 -0400 Received: from mail-qt0-x243.google.com ([2607:f8b0:400d:c0d::243]:35970) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1csUNr-0006o7-5w for grub-devel@gnu.org; Mon, 27 Mar 2017 09:08:31 -0400 Received: by mail-qt0-x243.google.com with SMTP id n37so7431569qtb.3 for ; Mon, 27 Mar 2017 06:08:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=8GgQrGgG3xe3pHTxq/04ek69yqx49r3i0QccZYZZJLg=; b=SpW3nxgT7mH/GlSI9aIa40HaKPfuJuMh1+9fyGH0u5OjfxGpN0NVc1xyRYCL1hFRlw HYKNCRUiTWZ0JvTQ0Vq/YXcCSgBWqUrO9yeePB4cYTVrrCMKuN24apQ3PhKq/qsYKNOd 2DNPKNEfFGmLvwaQ0SiGDamgLEiJ0T8xIvIYXzu8+99+vRbb4lkN7uuNGduwPo7c1PUC zEDOkrUxrVnHFuAhV9VoEGytLJNhVhSEN7U+e+KyCF5Mp/lg99/62GAzoquK78GvH7uH rlW80NgkM5cacGH9MDIsnsgjd2JeE4J1KXKSJSEURXJlCZH19aGycXNsKPYbAI+0+Uq2 9YCw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=8GgQrGgG3xe3pHTxq/04ek69yqx49r3i0QccZYZZJLg=; b=qKzUBCcI1Pn+O6n4TAB2BO74j5BoOOaqEuVzTv1rrFP9EzS8U3koAUIeEAnKZbSRYv 8DMefJ4eAJLngx9SiAmLI2wrZam3md19l8vi3B1N3IKmIeQCqB5k0hE3IBbHJuN05vgT l0x6RpCUwu955X4V8Eo95+fAc5QfZPqlX+7jp41ScCp9UAG+0nzLzrQXVhzBeAB1kWKY ZM1kk6ncCNSBLMkj7gv7dNwDAUFCInFiwtREEJwq00kbliXPrTMPsF/qIrTSqoGYp1rr bPpKMOhMwSEazlKZpZG4UBsQcDe29WVemIVQh8ZpSJyIrCWOOooKvZJqpjFVWh0er9Fw Wgcg== X-Gm-Message-State: AFeK/H2xvBmWNj6i5CIe9fUSnZfQzlBe4En8oEuphSv1ciD0ge+h/MDRtEDR7SUwu5oaBiC2A8Q6u3LP1rOc1Q== X-Received: by 10.200.44.100 with SMTP id e33mr6582691qta.192.1490620110486; Mon, 27 Mar 2017 06:08:30 -0700 (PDT) MIME-Version: 1.0 Received: by 10.200.41.131 with HTTP; Mon, 27 Mar 2017 06:08:30 -0700 (PDT) In-Reply-To: <20170327124133.GG9002@riva.ucam.org> References: <20170327124133.GG9002@riva.ucam.org> From: Andrei Borzenkov Date: Mon, 27 Mar 2017 16:08:30 +0300 Message-ID: Subject: Re: [weasel@debian.org: Bug#858832: calls efibootmgr with invalid options] To: The development of GNU GRUB Cc: Peter Palfrader , 858832-forwarded@bugs.debian.org Content-Type: text/plain; charset=UTF-8 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2607:f8b0:400d:c0d::243 X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: The development of GNU GRUB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Mar 2017 13:08:34 -0000 Link to the bug report would be helpful. I assume it contains actual invocation with arguments, I do not see them in this mail. On Mon, Mar 27, 2017 at 3:41 PM, Colin Watson wrote: > I guess that the attached bug happens because grub_install_register_efi > is called on non-biosdisk-ish systems but uses > grub_util_biosdisk_get_osdev to get an OS device name for > efidir_grub_dev->disk, which isn't going to work so well. I'm a bit > rusty here - would anyone care to venture a guess at suitable > replacement code that would work on devices other than biosdisk? > > Thanks, > > -- > Colin Watson [cjwatson@debian.org] > > > ---------- Forwarded message ---------- > From: Peter Palfrader > To: Debian Bug Tracking System > Cc: > Bcc: > Date: Mon, 27 Mar 2017 12:24:16 +0000 > Subject: Bug#858832: calls efibootmgr with invalid options > Package: grub-efi-arm64 > Version: 2.02~beta3-5 > Severity: serious > User: debian-admin@lists.debian.org > Usertags: needed-by-DSA-Team > > On upgrading from jessie to stretch on our arm64 box acker.debian.org I > noticed this issue with grub-efi-arm64: > > > acker:~# apt-get install --reinstall grub-efi-arm64 > Reading package lists... Done > Building dependency tree > Reading state information... Done > 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 1 not upgraded. > Need to get 73.0 kB of archives. > After this operation, 0 B of additional disk space will be used. > Get:1 http://mirror.netcologne.de/debian stretch/main arm64 grub-efi-arm64 arm64 2.02~beta3-5 [73.0 kB] > Fetched 73.0 kB in 0s (603 kB/s) > Preconfiguring packages ... > (Reading database ... 62883 files and directories currently installed.) > Preparing to unpack .../grub-efi-arm64_2.02~beta3-5_arm64.deb ... > Unpacking grub-efi-arm64 (2.02~beta3-5) over (2.02~beta3-5) ... > Setting up grub-efi-arm64 (2.02~beta3-5) ... > Installing for arm64-efi platform. > efibootmgr: option requires an argument -- 'd' > efibootmgr version 14 > usage: efibootmgr [options] > -a | --active sets bootnum active > -A | --inactive sets bootnum inactive > -b | --bootnum XXXX modify BootXXXX (hex) > -B | --delete-bootnum delete bootnum > -c | --create create new variable bootnum and add to bootorder > -C | --create-only create new variable bootnum and do not add to bootorder > -D | --remove-dups remove duplicate values from BootOrder > -d | --disk disk (defaults to /dev/sda) containing loader > -r | --driver Operate on Driver variables, not Boot Variables. > -e | --edd [1|3|-1] force EDD 1.0 or 3.0 creation variables, or guess > -E | --device num EDD 1.0 device number (defaults to 0x80) > -g | --gpt force disk with invalid PMBR to be treated as GPT > -i | --iface name create a netboot entry for the named interface > -l | --loader name (defaults to \EFI\redhat\grub.efi) > -L | --label label Boot manager display label (defaults to "Linux") > -m | --mirror-below-4G t|f mirror memory below 4GB > -M | --mirror-above-4G X percentage memory to mirror above 4GB > -n | --bootnext XXXX set BootNext to XXXX (hex) > -N | --delete-bootnext delete BootNext > -o | --bootorder XXXX,YYYY,ZZZZ,... explicitly set BootOrder (hex) > -O | --delete-bootorder delete BootOrder > -p | --part part (defaults to 1) containing loader > -q | --quiet be quiet > -t | --timeout seconds set boot manager timeout waiting for user input. > -T | --delete-timeout delete Timeout. > -u | --unicode | --UCS-2 pass extra args as UCS-2 (default is ASCII) > -v | --verbose print additional information > -V | --version return version and exit > -w | --write-signature write unique sig to MBR if needed > -y | --sysprep Operate on SysPrep variables, not Boot Variables. > -@ | --append-binary-args file append extra args from file (use "-" for stdin) > -h | --help show help/usage > grub-install: error: efibootmgr failed to register the boot entry: Operation not permitted. > Failed: grub-install --target=arm64-efi > WARNING: Bootloader is not properly installed, system may not be bootable > Generating grub configuration file ... > Found linux image: /boot/vmlinuz-4.9.0-2-arm64 > Found initrd image: /boot/initrd.img-4.9.0-2-arm64 > Found linux image: /boot/vmlinuz-4.9.0-0.bpo.2-arm64 > Found initrd image: /boot/initrd.img-4.9.0-0.bpo.2-arm64 > Found linux image: /boot/vmlinuz-4.8.0-0.bpo.2-arm64 > Found initrd image: /boot/initrd.img-4.8.0-0.bpo.2-arm64 > Adding boot menu entry for EFI firmware configuration > done > acker:~# > > Cheers, > -- > | .''`. ** Debian ** > Peter Palfrader | : :' : The universal > https://www.palfrader.org/ | `. `' Operating System > | `- https://www.debian.org/ > > > > > _______________________________________________ > Grub-devel mailing list > Grub-devel@gnu.org > https://lists.gnu.org/mailman/listinfo/grub-devel >