From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1eh063-00021g-QW for mharc-grub-devel@gnu.org; Wed, 31 Jan 2018 16:39:11 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:51648) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eh062-00021S-3v for grub-devel@gnu.org; Wed, 31 Jan 2018 16:39:11 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eh05x-00068I-7c for grub-devel@gnu.org; Wed, 31 Jan 2018 16:39:10 -0500 Received: from mout.gmx.net ([212.227.17.20]:63505) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eh05w-00067o-Ty for grub-devel@gnu.org; Wed, 31 Jan 2018 16:39:05 -0500 Received: from scdbackup.webframe.org ([79.222.38.208]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MarAM-1eR7uB3sIk-00KPf6; Wed, 31 Jan 2018 22:39:02 +0100 Date: Wed, 31 Jan 2018 22:37:59 +0100 From: "Thomas Schmitt" To: grub-devel@gnu.org Subject: Re: A thread on grub-bug could need attention Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Cc: michel@bouissou.net References: <1655785697419791611@scdbackup.webframe.org> In-Reply-To: <1655785697419791611@scdbackup.webframe.org> Message-Id: <30153785849355277707@scdbackup.webframe.org> X-Provags-ID: V03:K0:GpgHUziFyXr1LmOi8Iu1XsvpJu3+8bWojHQQcoWS/VZpf0Vnu86 PUihsAHOF3UMM5xBEQsv7/Knwouv+LcezzGs3hPNvGXv4GdYWOiMMiImhRbBoc0sNK/F5Tj UWWD3WYa5LXlgVAef4VW11UiLCEsDhmxj2TyTJhH+6TOurWT+ip2XCfXvPEFT2Fn/jWC0cv /1RPmsu/FVNwDE/jv3lTA== X-UI-Out-Filterresults: notjunk:1;V01:K0:GWmDfwxMhkk=:kiO/x/3a2qG5KOrwWkwhcq IGzjRMjONYjOOcTwrBrum4v5PPrxZF8GcCAzl5yY8KzE/tHUsRjaGiIozbA3wQjPwSjiPudYQ /I4CLPOgjHsMRwDZ2myY5nN3GkAddhiuKeOb7FzQ9W+0Rk0qSnVIwLTmOp+yxehi1W69Z3Kix B5QEbpZYBt/VgTj3eu2GAOZ6M4766sD7wPwaPhI6TdFj33lhP3nmLbGIBFqnkFVqQi2ngqZyQ zcMXcCl+bxt3el+45C2Y+GkJ6r/5h8hnbuuEg5wBRNnhFM+EJC0NzG3bkznHJF55ORoen7mfX yUEW90bb4MSkqUl2YfESz4GGrptw/x78UiCRiVkhQC42eu2xlIxOIYefnrn172O5xbBNaDHS3 AbxUQOctDuwS09VDNq0kRTQwv91Z5NVqXwJVKCx2250zMfIElssdywOI2KjKkck2meYP1dmaj LISfEB1a5IWuprR4Yn+AkibfalGcbQMNXhNMsbY4lfrqWQZ6uW/s3GhSxK0TgkyS9KG8Nj+qk Ks7+Rm96PWsWPk1iqbgmKcdvKdIMGQPoEXMeDOFZFOmE9Z11jpPk3Nit6uSOFM/TOSfpK5B23 VKV0IiBDX4vXGi47riS6xGu6L1rUoJjnjxDdx25v1o4q4MSXsAS7/B2MbSiSPWlKP5l/dPfNT 2dmTEYAqQY1uzruyK5uFA5refWjirv9+C5edczy+7jwe/g7hrvreIXTw7+Cj8Uwf9KIdoQBsW +xrU42SVIj+kBrPmZlHwNhwvZUDfLTVhMFghUIZbnJJp63+vgPTvv5Qb6O8LuNwlpza6yXqrd /akBiFI8Mw5GRREp1Ww7kP5/Yoqgpn3b3hzrVEwrYfElietnu4= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 212.227.17.20 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: Wed, 31 Jan 2018 21:39:11 -0000 Hi, it comes to me that possibly Michel's grub-mkrescue run was BIOS-only. So Michel, take much care to come back in good shape. We have experiments to do. :)) ----------------------------------------------------------------------- At least on Debian the boot equipment prepared by grub-mkrescue depends on which grub-* Debian packages are installed. "grub-pc" enables BIOS equipment. In the case of an USB stick, it's the MBR x86 boot code which comes into effect. It knows the block address of the El Torito boot image. So i assume it loads and executes that binary. "grub-efi-amd64" causes grub-mkrescue to prepare an EFI System Partition with binary /efi/boot/bootx64.efi . "grub-efi-ia32" causes an EFI System Partition with binary /efi/boot/bootia32.efi . All three can be combined. So after a vanilla run with grub-mkrescue, it is essential to inspect the partition tables and El Torito boot equipment by xorriso -indev output.iso \ -report_el_torito plain -report_system_area plain If no lines like GPT disk GUID : 04a5adf35d1adb4382bf8300bebe08a1 ... GPT start and size : 4 34132 600 are reported, then the ISO has no EFI System Partition. In this case a run with grub-mkrescue-sed.sh will not make much sense. First one will have to configure GRUB to enable at least one of the EFI variants. I dimly remember that the machine was 64 bit, i.e. should run bootx64.efi. Have a nice day :) Thomas