[opensuse] How to generate grubx64.efi
Hello everybody, On my desktopcomputer i have a standalone boot partition a real orphan,no kernel and no operating system looks for it. It is a stable and customized, al my opensuse flavours boots are adressed via this partition no problems at all. But i added win10 and that doesn't work. I have to generate a new grubx64.efi ! Which program or procedure in leap42.1 does the job ? Is there any documentation on generating a uefi environment ? Thanks, Hans -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
31.01.2016 18:31, Hans de Faber пишет:
Hello everybody,
On my desktopcomputer i have a standalone boot partition a real orphan,no kernel and no operating system looks for it. It is a stable and customized, al my opensuse flavours boots are adressed via this partition no problems at all. But i added win10 and that doesn't work. I have to generate a new grubx64.efi !
I miss relationship between these two statements. How is grub related to Windows 10? May be if you start with telling what you try to achieve (instead of how you want to do it) it will be easier to give correct advice.
Which program or procedure in leap42.1 does the job ?
This happens automatically if you install on UEFI based system.
Is there any documentation on generating a uefi environment ?
I do not understand what "generating a uefi environment" means.
Thanks, Hans
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
31.01.2016 18:31, Hans de Faber пишет:
Hello everybody,
On my desktopcomputer i have a standalone boot partition a real orphan,no kernel and no operating system looks for it. It is a stable and customized, al my opensuse flavours boots are adressed via this partition no problems at all. But i added win10 and that doesn't work. I have to generate a new grubx64.efi ! note: Every boot is a non secure boot, so no shim load. I miss relationship between these two statements. How is grub related to Windows 10? May be if you start with telling what you try to achieve (instead of how you want to do it) it will be easier to give correct advice. Every *.efi has a PHYSICAL connection (device partition directory) in binary to the item it boots (grub) . So i can not copy a working one. A *.efi file has also some match with the booting os. Booting opensuse flavors works, on windows i get the error "symbol 'grub_efi_find_last_device_path' not found". There is some mismatch with the .efi file. The versions of grub are identical
Which program or procedure in leap42.1 does the job ? This happens automatically if you install on UEFI based system. Of course but not for a standalone grub environment The .efi file is generated somewhere in the bootconfig proces. There is a easy but timeconsuming workaround, Install another opensuse and use a separate bootpartition, throw away the os and keep the bootpartition. But I want to learn something about the uefi boot and the goal is this time "How to generate grubx64.efi
Is there any documentation on generating a uefi environment ? I do not understand what "generating a uefi environment" means. Everthing that should be done to boot a kernel from uefi. A good starting point to read is http://www.rodsbooks.com/efi-bootloaders/. But for now is there any opensuse document what describes programs and
Op 31-01-16 17:14, Andrei Borzenkov schreef: parameters in the efi part of make-grub-config ??
Thanks, Hans
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
31.01.2016 21:01, Hans de Faber пишет:
Op 31-01-16 17:14, Andrei Borzenkov schreef:
31.01.2016 18:31, Hans de Faber пишет:
Hello everybody,
On my desktopcomputer i have a standalone boot partition a real orphan,no kernel and no operating system looks for it. It is a stable and customized, al my opensuse flavours boots are adressed via this partition no problems at all. But i added win10 and that doesn't work. I have to generate a new grubx64.efi ! note: Every boot is a non secure boot, so no shim load. I miss relationship between these two statements. How is grub related to Windows 10? May be if you start with telling what you try to achieve (instead of how you want to do it) it will be easier to give correct advice. Every *.efi has a PHYSICAL connection (device partition directory) in binary to the item it boots (grub) . So i can not copy a working one. A *.efi file has also some match with the booting os. Booting opensuse flavors works, on windows i get the error "symbol 'grub_efi_find_last_device_path' not found". There is some mismatch with the .efi file. The versions of grub are identical
I re-read it five times and still cannot make head nor tail of it. You apparently did something (but you did not describe what) and you expected result different from what you got (but you describe neither what you expected not what you got).
Which program or procedure in leap42.1 does the job ? This happens automatically if you install on UEFI based system.
Of course but not for a standalone grub environment The .efi file is generated somewhere in the bootconfig proces. There is a easy but timeconsuming workaround, Install another opensuse and use a separate bootpartition, throw away the os and keep the bootpartition. But I want to learn something about the uefi boot and the goal is this time "How to generate grubx64.efi
I have hard time to believe this is goal ... rather means to achieve something. To install grub2 you use grub2-install. That is true for every supported platform including EFI. On 64 bit EFI it will generate grubx64.efi among other things.
Is there any documentation on generating a uefi environment ?
I do not understand what "generating a uefi environment" means. Everthing that should be done to boot a kernel from uefi. A good starting point to read is http://www.rodsbooks.com/efi-bootloaders/. But for now is there any opensuse document what describes programs and parameters in the efi part of make-grub-config ??
Sorry, what is "make-grub-config"? This is the first time I hear about it.
Thanks, Hans
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 31/01/2016 19:36, Andrei Borzenkov a écrit :
To install grub2 you use grub2-install. That is true for every supported platform including EFI. On 64 bit EFI it will generate grubx64.efi among other things.
may be the need is only to mount the efi partition under /boot/EFI, update with yast and umount jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
In general: Please answer only if have knowledge of the subject. 1. There is only one efi partition and is always mounted, operating systems are differentiated by directory name 2. on the efi partition only the directory that belongs to the running os is updated. 3. the updated grubx64.efi points directly to the grub of the running os. My standalone grubpartition has its own grubx64.efi and has no kernels onboard and can not be updated in the normal way. For that reason i have to do it by hand. Grub-install is collection of procedures and programs and i want to known which part (program) creates the grubx64.efi and is there any documentation. Op 31-01-16 20:09, jdd schreef:
Le 31/01/2016 19:36, Andrei Borzenkov a écrit :
To install grub2 you use grub2-install. That is true for every supported platform including EFI. On 64 bit EFI it will generate grubx64.efi among other things.
may be the need is only to mount the efi partition under /boot/EFI, update with yast and umount
jdd
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
31.01.2016 23:07, Hans de Faber пишет:
In general: Please answer only if have knowledge of the subject.
1. There is only one efi partition and is always mounted, operating systems are differentiated by directory name 2. on the efi partition only the directory that belongs to the running os is updated. 3. the updated grubx64.efi points directly to the grub of the running os.
That's misunderstanding. First stage grub2 image (which grubx64.efi effectively is) has no idea about "running os" whatsoever. What it needs to know is where its binaries (loadable modules) are located and where to read configuration script (grub.cfg) from. That information is indeed embedded in this image.
My standalone grubpartition has its own grubx64.efi and has no kernels onboard and can not be updated in the normal way.
grub2-install *is* the normal way to update grub2 installation and it absolutely does not depend on having any (Linux) kernel on partition where grub2 is installed.
For that reason i have to do it by hand.
Grub-install is collection of procedures and programs and i want to known which part (program) creates the grubx64.efi and is there any documentation.
grub2-install on current versions of openSUSE (13.2, Leap and TW) is single binary. You need to tell it a) where GRUB binaries will be installed (--boot-directory) b) where ESP is mounted (--efi-directory) c) how subdirectory on ESP will be named (--bootloader-id) d) whether you want it to update EFI boot menu entry (--no-nvram). There is man page and some description in grub2 info documentation. Whether openSUSE includes something else I simply do not know.
Op 31-01-16 20:09, jdd schreef:
Le 31/01/2016 19:36, Andrei Borzenkov a écrit :
To install grub2 you use grub2-install. That is true for every supported platform including EFI. On 64 bit EFI it will generate grubx64.efi among other things.
may be the need is only to mount the efi partition under /boot/EFI, update with yast and umount
jdd
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
I appriciate that everybody tries to help me. There is no grub problem everything boots fine . I read your message, some wrong things but the good thing was grub-install is a single binary. Conclusion: there is no separate program that generates the *.efi. Thanks, Hans Op 01-02-16 04:46, Andrei Borzenkov schreef:
31.01.2016 23:07, Hans de Faber пишет:
In general: Please answer only if have knowledge of the subject.
1. There is only one efi partition and is always mounted, operating systems are differentiated by directory name 2. on the efi partition only the directory that belongs to the running os is updated. 3. the updated grubx64.efi points directly to the grub of the running os. That's misunderstanding. First stage grub2 image (which grubx64.efi effectively is) has no idea about "running os" whatsoever. What it needs to know is where its binaries (loadable modules) are located and where to read configuration script (grub.cfg) from. That information is indeed embedded in this image. grubx64.efi is not a part of grub(2) but from the efi bootstructure it is specific and should NOT be copied My standalone grubpartition has its own grubx64.efi and has no kernels onboard and can not be updated in the normal way. grub2-install *is* the normal way to update grub2 installation and it absolutely does not depend on having any (Linux) kernel on partition where grub2 is installed.
For that reason i have to do it by hand.
Grub-install is collection of procedures and programs and i want to known which part (program) creates the grubx64.efi and is there any documentation.
grub2-install on current versions of openSUSE (13.2, Leap and TW) is single binary. You need to tell it
a) where GRUB binaries will be installed (--boot-directory) b) where ESP is mounted (--efi-directory) c) how subdirectory on ESP will be named (--bootloader-id) d) whether you want it to update EFI boot menu entry (--no-nvram).
There is man page and some description in grub2 info documentation. Whether openSUSE includes something else I simply do not know.
Op 31-01-16 20:09, jdd schreef:
Le 31/01/2016 19:36, Andrei Borzenkov a écrit :
To install grub2 you use grub2-install. That is true for every supported platform including EFI. On 64 bit EFI it will generate grubx64.efi among other things.
may be the need is only to mount the efi partition under /boot/EFI, update with yast and umount
jdd
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/31/2016 09:31 AM, Hans de Faber wrote:
Hello everybody,
On my desktopcomputer i have a standalone boot partition a real orphan,no kernel and no operating system looks for it. It is a stable and customized, al my opensuse flavours boots are adressed via this partition no problems at all. But i added win10 and that doesn't work. I have to generate a new grubx64.efi ! Which program or procedure in leap42.1 does the job ? Is there any documentation on generating a uefi environment ?
Thanks, Hans
I think that happens if you forget to mount the EFI partition at "/boot/efi" during the install. The only way that I know to generate the file, is "grub2-install". The file "grubx64.efi" should actually be identical to "/boot/grub2/x86_64-efi/core.efi", so if you have that file, you can probably just copy it. If you don't have that file, then maybe there's a whole bunch of other files that you don't have (in "/boot/grub2/x86_64_efi"). The "grub2-install" should take care of that. If your system is not bootable, then you would need to boot the installer in rescue mode, and repair from there. Make sure that you use UEFI booting (not legacy booting) to boot the rescue system. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Andrei Borzenkov -
Hans de Faber -
jdd -
Neil Rickert