28.03.2017 09:34, Peter Palfrader пишет:
> } /dev/md2953M 176K 953M 1% /boot/efi
Sorry, that's not going to work. Even assuming that grub can map from
Linux MD to underlying physical device + partition (as that is what
efibootmgr needs, we cannot simply pass /dev/md2 to it), this will
On Mon, 27 Mar 2017, Andrei Borzenkov wrote:
> 27.03.2017 15:41, Colin Watson пишет:
> > 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->dis
On Mon, 27 Mar 2017, Andrei Borzenkov wrote:
> Link to the bug report would be helpful. I assume it contains actual
> invocation with arguments, I do not see them in this mail.
see https://bugs.debian.org/858832
--
| .''`. ** Debian **
Peter Palfrader
On Mon, 27 Mar 2017, Steve McIntyre wrote:
> >efibootmgr: option requires an argument -- 'd'
> >efibootmgr version 14
As a potential (side-) effect, acker no longer auto-boots but puts me in
an efi prompt, where selecting the device and then launching grub
manually works.
> OK, that's odd. Can y
Hi!
On Mon, Mar 27, 2017 at 12:24:16PM +, Peter Palfrader wrote:
>Package: grub-efi-arm64
>Version: 2.02~beta3-5
>Severity: serious
>User: debian-ad...@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
Package: grub-efi-arm64
Version: 2.02~beta3-5
Severity: serious
User: debian-ad...@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
Rea
6 matches
Mail list logo
