[opensuse] building a 32 bits efi file for leap
Hello, I have no way to test this right now (hardware unavailable for some days), so this post. is it possible to build a working bootia32.efi 32 bits file for Leap using the instructions here: https://github.com/jfwells/linux-asus-t100ta/tree/master/boot I see nothing in this related to the running system (and it says "on any computer"), but I'm not that good on the subject :-( I try to make a bootable dvd for 32 bits uefi/64 bits processor systems thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, Feb 24, 2016 at 11:16 AM, jdd <jdd@dodin.org> wrote:
Hello,
I have no way to test this right now (hardware unavailable for some days), so this post.
is it possible to build a working bootia32.efi 32 bits file for Leap using the instructions here:
https://github.com/jfwells/linux-asus-t100ta/tree/master/boot
I see nothing in this related to the running system (and it says "on any computer"), but I'm not that good on the subject :-(
I try to make a bootable dvd for 32 bits uefi/64 bits processor systems
Install DVD is using pre-built image from grub2 RPM; just take it from grub2-i386-efi package (/usr/lib/efi/grub.efi) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 24/02/2016 09:40, Andrei Borzenkov a écrit :
Install DVD is using pre-built image from grub2 RPM; just take it from grub2-i386-efi package (/usr/lib/efi/grub.efi)
install fails for Leap -I only find a beta version on obs and none in yast: https://software.opensuse.org/package/grub2-i386-efi?search_term=grub2-i386-... I'm downloading the rpm now, but what vI have is only 1.1ko large, not to be a rpm. I don't have this repo on Leap reason why I wanted to know is this file is specific to an install or general :-( jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 24/02/2016 10:00, jdd a écrit :
reason why I wanted to know is this file is specific to an install or general :-(
I have the one from 13.2 (my present computer is not uefi, may be it's the reason why I can't install this grub version?) jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, Feb 24, 2016 at 12:00 PM, jdd <jdd@dodin.org> wrote:
Le 24/02/2016 09:40, Andrei Borzenkov a écrit :
Install DVD is using pre-built image from grub2 RPM; just take it from grub2-i386-efi package (/usr/lib/efi/grub.efi)
install fails for Leap -I only find a beta version on obs and none in yast:
https://software.opensuse.org/package/grub2-i386-efi?search_term=grub2-i386-...
I'm downloading the rpm now, but what vI have is only 1.1ko large, not to be a rpm. I don't have this repo on Leap
reason why I wanted to know is this file is specific to an install or general :-(
Oh, so it appears that package built on x86_64 does not include pre-built grub.efi. And there are no (published) 32 bit packages for Leap. How weird ... Well, if you want to use exactly the same version as in Leap, you could install grub2-i386-efi on Leap (yes, it *is* available there in standard repository) and build grub.efi yourself following grub2.spec: FS_MODULES="ext2 btrfs ext2 xfs jfs reiserfs" CD_MODULES=" all_video boot cat chain configfile echo \ efinet font gfxmenu gfxterm gzio halt iso9660 \ jpeg minicmd normal part_apple part_msdos part_gpt \ password_pbkdf2 png reboot search search_fs_uuid \ search_fs_file search_label sleep test video fat loadenv" PXE_MODULES="efinet tftp" CRYPTO_MODULES="luks gcry_rijndael gcry_sha1" CD_MODULES="${CD_MODULES} linux linuxefi" GRUB_MODULES="${CD_MODULES} ${FS_MODULES} ${PXE_MODULES} ${CRYPTO_MODULES} mdraid09 mdraid1x lvm" ./grub-mkimage -O i386-efi -o grub.efi --prefix= ${GRUB_MODULES} You get (almost) the same binary as is on installation DVD. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, Feb 24, 2016 at 12:15 PM, Andrei Borzenkov <arvidjaar@gmail.com> wrote:
Well, if you want to use exactly the same version as in Leap, you could install grub2-i386-efi on Leap (yes, it *is* available there in standard repository)
Scratch it. It is not, I mixed something up. Well, this is one of problems I told you about from the very beginning - supporting 32 bit EFI on 64 bit OS is far more involved than just providing installation DVD image. So you should be able to 32 bit packages from OBS using osc. Otherwise you can get *any* package, e.g. from Tumbleweed - at the end it does not matter, you need single file /usr/lib/grub2/i386-efi/grub.efi. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 24/02/2016 10:20, Andrei Borzenkov a écrit :
Scratch it. It is not, I mixed something up. Well, this is one of problems I told you about from the very beginning - supporting 32 bit EFI on 64 bit OS is far more involved than just providing installation DVD image.
right now, it's only openSUSE don't supporting it
So you should be able to 32 bit packages from OBS using osc. Otherwise you can get *any* package, e.g. from Tumbleweed - at the end it does not matter, you need single file /usr/lib/grub2/i386-efi/grub.efi.
no, there is no uefi 32 bits Tumbleweed AFAIK did you get a look at the link https://github.com/jfwells/linux-asus-t100ta/tree/master/boot it's not a big deal to compile is if there is no distro-specific option in this page thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, Feb 24, 2016 at 12:20:33PM +0300, Andrei Borzenkov wrote:
On Wed, Feb 24, 2016 at 12:15 PM, Andrei Borzenkov <arvidjaar@gmail.com> wrote:
Well, if you want to use exactly the same version as in Leap, you could install grub2-i386-efi on Leap (yes, it *is* available there in standard repository)
Scratch it. It is not, I mixed something up. Well, this is one of problems I told you about from the very beginning - supporting 32 bit EFI on 64 bit OS is far more involved than just providing installation DVD image.
I think we had created an openFATE in the past to support 32-bit UEFI booting and installation, but so far I just can't find it out. And yes, it is collective work on more than just grub2. The YaST and kiwi needs to work together to support it. Thanks, Michael -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 24/02/2016 10:15, Andrei Borzenkov a écrit :
Oh, so it appears that package built on x86_64 does not include pre-built grub.efi.
yes there is one, but I presume it's a 64 bits one And there are no (published) 32 bit packages for
Leap. How weird ...
Leap was said to be only 64 bits, so it's not surprising. I just try to make it bootable from 32 bits uefi, to be installed then as 64 bits (works for debian)
Well, if you want to use exactly the same version as in Leap,
I just want to install Leap :-) you
could install grub2-i386-efi on Leap (yes, it *is* available there in standard repository)
binary don't install, I guess you speak of source?
You get (almost) the same binary as is on installation DVD.
I don't find it on the dvd thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, Feb 24, 2016 at 12:15:57PM +0300, Andrei Borzenkov wrote:
On Wed, Feb 24, 2016 at 12:00 PM, jdd <jdd@dodin.org> wrote:
Le 24/02/2016 09:40, Andrei Borzenkov a écrit :
Install DVD is using pre-built image from grub2 RPM; just take it from grub2-i386-efi package (/usr/lib/efi/grub.efi)
install fails for Leap -I only find a beta version on obs and none in yast:
https://software.opensuse.org/package/grub2-i386-efi?search_term=grub2-i386-...
I'm downloading the rpm now, but what vI have is only 1.1ko large, not to be a rpm. I don't have this repo on Leap
reason why I wanted to know is this file is specific to an install or general :-(
Oh, so it appears that package built on x86_64 does not include pre-built grub.efi. And there are no (published) 32 bit packages for Leap. How weird ...
From what I know, we dropped support booting from 32 bit architecture on UEFI. That's the reason why 32 bit grub.efi wasn't provided because it's not needed in 32 bit installation media and also don't require signed image for secure boot, which apparently also don't support on 32 bit.
Thanks, Michael -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, Feb 24, 2016 at 1:14 PM, Michael Chang <mchang@suse.com> wrote:
From what I know, we dropped support booting from 32 bit architecture on UEFI.
Well, there are apparently more and more systems with 32 bit firmware emerging. So you probably need to reconsider it (see bug report mentioned somewhere in this thread). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 24/02/2016 11:33, Andrei Borzenkov a écrit :
On Wed, Feb 24, 2016 at 1:14 PM, Michael Chang <mchang@suse.com> wrote:
From what I know, we dropped support booting from 32 bit architecture on UEFI.
Well, there are apparently more and more systems with 32 bit firmware emerging. So you probably need to reconsider it (see bug report mentioned somewhere in this thread).
and only *boot* support is needed, install can follow as 64 bits. my IT WORKS TW891 is only 129€ for 1280x800 screen, 32Gb ssd and 2Gb ram. of course, supporting a tablet is not that easy, not all works natively, but I don't ask for full support, not even to have it on mainstream Leap, but If I could build a Leap network install on Studio to support these machines, it could be a significant step on. Main stream support is probably not that important, because as price drop and memory get bigger, the need for 32 bits should hopefully vanish :-) jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, Feb 24, 2016 at 11:40:56AM +0100, jdd wrote:
Le 24/02/2016 11:33, Andrei Borzenkov a écrit :
On Wed, Feb 24, 2016 at 1:14 PM, Michael Chang <mchang@suse.com> wrote:
From what I know, we dropped support booting from 32 bit architecture on UEFI.
Well, there are apparently more and more systems with 32 bit firmware emerging. So you probably need to reconsider it (see bug report mentioned somewhere in this thread).
and only *boot* support is needed, install can follow as 64 bits.
I think system would break if you updated the grub2 package, without change the LOADER_TYPE to 'none', it will reinstall bootloader which defaults to x86_64.
my IT WORKS TW891 is only 129€ for 1280x800 screen, 32Gb ssd and 2Gb ram.
of course, supporting a tablet is not that easy, not all works natively, but I don't ask for full support, not even to have it on mainstream Leap, but If I could build a Leap network install on Studio to support these machines, it could be a significant step on. Main stream support is probably not that important, because as price drop and memory get bigger, the need for 32 bits should hopefully vanish :-)
Ok. thanks, but I still think full support because the system has to be useful for update and TW did that quite oftenly. Mind to open a fate? then we can sum up more things there, bug may not be ideal for people evalutes efforts. Thanks, Michael
jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 24/02/2016 12:06, Michael Chang a écrit :
I think system would break if you updated the grub2 package, without change the LOADER_TYPE to 'none', it will reinstall bootloader which defaults to x86_64.
not with uefi. uefi bootloader is choosen by the firmware, not by the OS. If you choose to boot from, say "my32bits.efi" the computer will always boot this. of course this "uefi boot" is only a priority in nvram, but yast/gru should not change this - add an entry, yes, but not change the default
Ok. thanks, but I still think full support because the system has to be useful for update and TW did that quite oftenly.
I was not thinking of TW, but the more the better, if this do not delay the result excessively :-)
Mind to open a fate? then we can sum up more things there, bug may not be ideal for people evalutes efforts.
I often wonder what is the real use of openfate there is already one https://features.opensuse.org/318252 opened more than one year ago... jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, Feb 24, 2016 at 12:35:32PM +0100, jdd wrote:
Le 24/02/2016 12:06, Michael Chang a écrit :
I think system would break if you updated the grub2 package, without change the LOADER_TYPE to 'none', it will reinstall bootloader which defaults to x86_64.
not with uefi. uefi bootloader is choosen by the firmware, not by the OS. If you choose to boot from, say "my32bits.efi" the computer will always boot this.
of course this "uefi boot" is only a priority in nvram, but yast/gru should not change this - add an entry, yes, but not change the default
It won't change the default or the boot order, the potential problem here is that grub2-install will try to cleanup boot entries created by the same distributor with new one. That is you still have to fiddle with distributor manually in YaST or grub settings to get around the problem.
Ok. thanks, but I still think full support because the system has to be useful for update and TW did that quite oftenly.
I was not thinking of TW, but the more the better, if this do not delay the result excessively :-)
Mind to open a fate? then we can sum up more things there, bug may not be ideal for people evalutes efforts.
I often wonder what is the real use of openfate
there is already one
https://features.opensuse.org/318252
opened more than one year ago...
Sorry, I lose tracking of that one. I will try to sum up and put my work toward it. Thanks, Michael
jdd
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 24/02/2016 11:14, Michael Chang a écrit :
From what I know, we dropped support booting from 32 bit architecture on UEFI.
two years ago it seemed sensible (and I don't remember of any 32 bits uefi support on openSUSE), but now we see lot of tablets that are more powerfull than some computers, atom based, with 'who knows why, probably to same some ram) but with 32 bits uefi and windows 10. I can install debian on them and would like to have openSUSE That's the reason why 32 bit grub.efi wasn't provided because it's
not needed in 32 bit installation media and also don't require signed image for secure boot, which apparently also don't support on 32 bit.
windows 10 boots on 32 bits uefi with secureboot, but secureboot could be removed on all the tablets I had in hand, Debian do not manage secureboot. jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, Feb 24, 2016 at 10:00:19AM +0100, jdd wrote:
Le 24/02/2016 09:40, Andrei Borzenkov a écrit :
Install DVD is using pre-built image from grub2 RPM; just take it from grub2-i386-efi package (/usr/lib/efi/grub.efi)
install fails for Leap -I only find a beta version on obs and none in yast:
https://software.opensuse.org/package/grub2-i386-efi?search_term=grub2-i386-...
I'm downloading the rpm now, but what vI have is only 1.1ko large, not to be a rpm. I don't have this repo on Leap
I have bad news for you that the rpm install must have failed, because the system is 64bit and you're trying to install i586 package on it. Admitted this is a problem, as those grub2 module should be packaged as noarch ... Thanks, Michael -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, Feb 24, 2016 at 1:32 PM, Michael Chang <mchang@suse.com> wrote:
On Wed, Feb 24, 2016 at 10:00:19AM +0100, jdd wrote:
Le 24/02/2016 09:40, Andrei Borzenkov a écrit :
Install DVD is using pre-built image from grub2 RPM; just take it from grub2-i386-efi package (/usr/lib/efi/grub.efi)
install fails for Leap -I only find a beta version on obs and none in yast:
https://software.opensuse.org/package/grub2-i386-efi?search_term=grub2-i386-...
I'm downloading the rpm now, but what vI have is only 1.1ko large, not to be a rpm. I don't have this repo on Leap
I have bad news for you that the rpm install must have failed, because the system is 64bit and you're trying to install i586 package on it. Admitted this is a problem, as those grub2 module should be packaged as noarch ...
Well, I tried to draw attention and discuss it couple of years ago, but RPM won't allow ELF executable in noarch package and everyone continued to tell me that they cannot go into noarch because they are ELF executable ... @jdd - you do not need to install them, just run rpm2cpio grub2-i386-pc-XXX.rpm | cpio -imduv and it will unpack RPM into current directory, just pick usr/lib/grub2/i386-elf/grub.efi (notice lack of leading slash). Which does not change the fact that openSUSE should fully support installation of 64 bit user space on 32 bit EFI firmware. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, Feb 24, 2016 at 01:48:02PM +0300, Andrei Borzenkov wrote:
On Wed, Feb 24, 2016 at 1:32 PM, Michael Chang <mchang@suse.com> wrote:
On Wed, Feb 24, 2016 at 10:00:19AM +0100, jdd wrote:
Le 24/02/2016 09:40, Andrei Borzenkov a écrit :
Install DVD is using pre-built image from grub2 RPM; just take it from grub2-i386-efi package (/usr/lib/efi/grub.efi)
install fails for Leap -I only find a beta version on obs and none in yast:
https://software.opensuse.org/package/grub2-i386-efi?search_term=grub2-i386-...
I'm downloading the rpm now, but what vI have is only 1.1ko large, not to be a rpm. I don't have this repo on Leap
I have bad news for you that the rpm install must have failed, because the system is 64bit and you're trying to install i586 package on it. Admitted this is a problem, as those grub2 module should be packaged as noarch ...
Well, I tried to draw attention and discuss it couple of years ago, but RPM won't allow ELF executable in noarch package and everyone continued to tell me that they cannot go into noarch because they are ELF executable ...
I was involved in those discussions, but now I tend to agree you are right. Thanks, Michael -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 24/02/2016 11:48, Andrei Borzenkov a écrit :
@jdd - you do not need to install them, just run
rpm2cpio grub2-i386-pc-XXX.rpm | cpio -imduv
of course, you can even open it with ark or engrampa, but there is no grub-i386 rpm for Leap - but I could find one elsewhere. I will get a new IT Works this afternoon, and may be able to continue tesing :-) jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
jdd said:
I will get a new IT Works this afternoon, and may be able to continue testing :-)
some details here: https://bugzilla.opensuse.org/show_bug.cgi?id=963496 in summary, I succeed to boot with openSUSE Leap using Tumbleweed 32 bits grub-efi rpm. I have to build myself a EFI 32 bits usb stick, Debian one do not read btrfs (and I installed Leap all as defaults) and my computer is picky: needs the EFI partition to be the first one of the stick, when the standard do not ask for this. I had successfully installed Leap with the help of Debian, using two usb stick (one Debian, the other Leap). Then I could boot with my own usb stick 32 bits EFI TW, that done, from Leap, I could add the 32 bits grub.efi and boot without usb stick. However I was obliged to go to windows and use easyefi to register to go on. Not sure it was really mandatory, but it like this I could do. I still have to write somewhere a grub.cfg to automate the process. jdd NB: Leap works, but is not fully functional, more later -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Отправлено с iPhone
I still have to write somewhere a grub.cfg to automate the process.
Well, grub2-mkconfig is still there and will produce exactly the same configuration. But you will also need to manually run grub2-install --target i386-efi if grub2 is updated. Btw, it should also take care of NVRAM entries, at least if Leap has efibootmgr.-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 28/02/2016 10:20, Andrei Borzenkov a écrit :
Отправлено с iPhone
I still have to write somewhere a grub.cfg to automate the process.
Well, grub2-mkconfig is still there and will produce exactly the same configuration.
certainly not. It's Leap, that don't even know than grub-i386-efi exists. May be sometime in the future, but not now (default kde install)
But you will also need to manually run grub2-install --target i386-efi if grub2 is updated. Btw, it should also take care of NVRAM entries, at least if Leap has efibootmgr.
this may the future I speak of :-). But for now I only tried to boot an unbootable system... and finally it works. efi boot partition have an EFI folder. In it you can have any folder you want (and the partition size accommodate). For example "windows", "opensuse" (the official openSUSE folder), and, for me, "32". in these folders are the "efi" binaries that do the actual boot, for me grub.efi. You can also add a grub.cfg file with the necessary config right there, alongside with grub.efi and this is the file that will be used. Of course, for openSUSE it's an alien OS, so untouched. To boot, you have to register this on nvram, but there is a default nvram entry for usb device that should but don't on my stick, I have to understand why. and Leap crashed, apparently when trying to hibernate... (I can't allow 4Go for swap on such small ssd) jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Отправлено с iPhone
28 февр. 2016 г., в 14:39, jdd <jdd@dodin.org> написал(а):
Le 28/02/2016 10:20, Andrei Borzenkov a écrit :
Отправлено с iPhone
I still have to write somewhere a grub.cfg to automate the process.
Well, grub2-mkconfig is still there and will produce exactly the same configuration.
certainly not.
Not what?
It's Leap, that don't even know than grub-i386-efi exists.
Grub-mkconfig creates configuration that is platform agnostic (with notable exception of secure boot).
May be sometime in the future, but not now (default kde install)
But you will also need to manually run grub2-install --target i386-efi if grub2 is updated. Btw, it should also take care of NVRAM entries, at least if Leap has efibootmgr.
this may the future I speak of :-). But for now I only tried to boot an unbootable system...
and finally it works.
efi boot partition have an EFI folder. In it you can have any folder you want (and the partition size accommodate). For example "windows", "opensuse" (the official openSUSE folder), and, for me, "32".
in these folders are the "efi" binaries that do the actual boot, for me grub.efi. You can also add a grub.cfg file with the necessary config right there, alongside with grub.efi and this is the file that will be used. Of course, for openSUSE it's an alien OS, so untouched.
To boot, you have to register this on nvram, but there is a default nvram entry for usb device that should but don't on my stick, I have to understand why.
and Leap crashed, apparently when trying to hibernate... (I can't allow 4Go for swap on such small ssd)
jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 28/02/2016 15:46, Andrei Borzenkov a écrit :
Well, grub2-mkconfig is still there and will produce exactly the same configuration.
certainly not.
Not what?
It's Leap, that don't even know than grub-i386-efi exists.
Grub-mkconfig creates configuration that is platform agnostic (with notable exception of secure boot).
of course not. I just reread the man page, grub2-mkconfig do not ask for the grub version to use. so it gives only one file, the one used by Leap to boot and this one do not boot with 32 bits grub.efi (tested). the grub.cfg next to the efi binay in opensuse folder simply link to grub.cfg in /boot. as far as I know, one can't have two config files in "opensuse". to boot my itworks, I had to wrote the 32bits grub.efi in an other folder (I named it "32"), and add a grub.cfg with essentially ........ set btrfs_relative_path="yes" search --fs-uuid --set=root 28efb6d2-1287-4f29-b38b-b383b89d6568 set timeout=10 menuentry "Jean-Daniel's openSUSE Leap 42.1 nomodeset" { linux /boot/vmlinuz nomodeset initrd /boot/initrd } .............. (plus several entries for various tests) The first line come from the official openSUSE grub.cfg (partition UID) copying the official grub.cfg in the same place as mine gives unbootable result (the computer skip ti and boots windows). several hours of tests :-( jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
28.02.2016 19:14, jdd пишет:
Le 28/02/2016 15:46, Andrei Borzenkov a écrit :
Well, grub2-mkconfig is still there and will produce exactly the same configuration.
certainly not.
Not what?
It's Leap, that don't even know than grub-i386-efi exists.
Grub-mkconfig creates configuration that is platform agnostic (with notable exception of secure boot).
of course not. I just reread the man page, grub2-mkconfig do not ask for the grub version to use.
It should generate configuration that runs with any GRUB version; if not this is a bug.
so it gives only one file, the one used by Leap to boot and this one do not boot with 32 bits grub.efi (tested).
Where exactly it fails - could you please quote part that does not work?
the grub.cfg next to the efi binay in opensuse folder simply link to grub.cfg in /boot.
as far as I know, one can't have two config files in "opensuse".
to boot my itworks, I had to wrote the 32bits grub.efi in an other folder (I named it "32"), and add a grub.cfg with essentially
........ set btrfs_relative_path="yes" search --fs-uuid --set=root 28efb6d2-1287-4f29-b38b-b383b89d6568 set timeout=10
menuentry "Jean-Daniel's openSUSE Leap 42.1 nomodeset" {
linux /boot/vmlinuz nomodeset initrd /boot/initrd } ..............
(plus several entries for various tests) The first line come from the official openSUSE grub.cfg (partition UID)
copying the official grub.cfg in the same place as mine gives unbootable result (the computer skip ti and boots windows).
several hours of tests :-(
jdd
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 28/02/2016 18:10, Andrei Borzenkov a écrit :
Where exactly it fails - could you please quote part that does not work?
no idea, grub fails and I happen booting windows, it's what I have for any error at this step :-( without any grub.cfg, I have the grub prompt and can continue (by hand), with my grub.cfg all is fine, I boot (right now init 3, as I only can have the correct screen with this). And it's specially tedious to test, May be I could copy a second folder (32-2), with different grub.cfg. only thing I notice on this file is that "linux" command is "linuxefi", and I don't know how it's expected to work jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
28.02.2016 20:34, jdd пишет:
Le 28/02/2016 18:10, Andrei Borzenkov a écrit :
Where exactly it fails - could you please quote part that does not work?
no idea, grub fails and I happen booting windows, it's what I have for any error at this step :-(
without any grub.cfg, I have the grub prompt and can continue (by hand), with my grub.cfg all is fine, I boot (right now init 3, as I only can have the correct screen with this).
And it's specially tedious to test, May be I could copy a second folder (32-2), with different grub.cfg.
only thing I notice on this file is that "linux" command is "linuxefi", and I don't know how it's expected to work
It should work exactly the same as long as secure boot is not enabled, but of course it has never been actually tested on i386 so who knows. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 28/02/2016 18:43, Andrei Borzenkov a écrit :
It should work exactly the same as long as secure boot is not enabled,
it's not
but of course it has never been actually tested on i386 so who knows.
now we can :-) thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
28.02.2016 20:54, jdd пишет:
Le 28/02/2016 18:43, Andrei Borzenkov a écrit :
It should work exactly the same as long as secure boot is not enabled,
it's not
but of course it has never been actually tested on i386 so who knows.
now we can :-)
No, we cannot. We still do not have any information what fails and where. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 28/02/2016 18:57, Andrei Borzenkov a écrit :
No, we cannot. We still do not have any information what fails and where.
I have a system with which I can make tests. Still we have to find a process I don't find any "linuxefi" command in my usable grub, may be it's the problem? I have an other computer with 64 bits uefi, but it's not active right now :-( jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
28.02.2016 21:01, jdd пишет:
Le 28/02/2016 18:57, Andrei Borzenkov a écrit :
No, we cannot. We still do not have any information what fails and where.
I have a system with which I can make tests. Still we have to find a process
I don't find any "linuxefi" command in my usable grub, may be it's the problem?
If you are using grub.efi image from RPM - yes; for some reasons it is not included on 32 bit version. It is present in module list, and if you actually used grub2-install to install it it would be present. Put RPM content under /usr/lib/grub2/i386-efi. Then use grub2-install --target i386-efi to setup grub2 on your system. *Then* we can discuss whether it works or not :) BTW I just submitted SR for update to 2.02~beta3 that should make explicit --target unnecessary, by auto-detecting firmware word size.
I have an other computer with 64 bits uefi, but it's not active right now :-(
jdd
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 28/02/2016 19:08, Andrei Borzenkov a écrit :
If you are using grub.efi image from RPM - yes; for some reasons it is not included on 32 bit version. It is present in module list, and if you actually used grub2-install to install it it would be present.
Put RPM content under /usr/lib/grub2/i386-efi. Then use
that mean simply "zypper in grub...", I guess
grub2-install --target i386-efi
ok
to setup grub2 on your system. *Then* we can discuss whether it works or not :)
what I said is that grub.efi works alone, if correctly configured. I had many problem to build an usb stick, because Leap /efi partition is pretty small, too small for all modules...
BTW I just submitted SR for update to 2.02~beta3 that should make explicit --target unnecessary, by auto-detecting firmware word size.
if yast can install this at install time, very nice. May be we could have it also on the install dvd (ready to boot :-) thanks jdd NB: My usb network card don't works well, so I don't have network on this machine right now :-( -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
28.02.2016 21:40, jdd пишет:
Le 28/02/2016 19:08, Andrei Borzenkov a écrit :
If you are using grub.efi image from RPM - yes; for some reasons it is not included on 32 bit version. It is present in module list, and if you actually used grub2-install to install it it would be present.
Put RPM content under /usr/lib/grub2/i386-efi. Then use
that mean simply "zypper in grub...", I guess
I do not know if RPM will allow installation of 32 bit RPM on 64 bit system. Try.
grub2-install --target i386-efi
ok
to setup grub2 on your system. *Then* we can discuss whether it works or not :)
what I said is that grub.efi works alone, if correctly configured. I had many problem to build an usb stick, because Leap /efi partition is pretty small, too small for all modules...
Once again - you use grub2-install *after* you have running system.
BTW I just submitted SR for update to 2.02~beta3 that should make explicit --target unnecessary, by auto-detecting firmware word size.
if yast can install this at install time, very nice. May be we could have it also on the install dvd (ready to boot :-)
No, it won't change anything in overall support for 32 bit EFI in (open)SUSE. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 28/02/2016 19:46, Andrei Borzenkov a écrit :
Once again - you use grub2-install *after* you have running system.
of course, no other way :-)
No, it won't change anything in overall support for 32 bit EFI in (open)SUSE.
:-( jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 28/02/2016 19:08, Andrei Borzenkov a écrit : I used a rpm found I don't remember where :-( (grub2-i386-efi-2.02~beta2-20.14.2.i586.rpm), because the leap one I found on obs is a fake (1.1ko only)
Put RPM content under /usr/lib/grub2/i386-efi. Then use
yes, couldn't use zypper, because with no network I couldn't solve some dependencies, but I extracted the folder myself and copied it where you said
grub2-install --target i386-efi
to setup grub2 on your system. *Then* we can discuss whether it works or not :)
yes, this works. Seems to use my edited grub.cfg (in /boot) may be simply don't care
BTW I just submitted SR for update to 2.02~beta3 that should make explicit --target unnecessary, by auto-detecting firmware word size.
always better. well. I have to summarize all this (get a working net and a working i915 video card :-(), but it's better. I still have to find a way to make this easier, that is not needing a debian stick on first time :-) thanks for your patience jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
28.02.2016 22:27, jdd пишет:
grub2-install --target i386-efi
to setup grub2 on your system. *Then* we can discuss whether it works or not :)
yes, this works. Seems to use my edited grub.cfg (in /boot) may be simply don't care
it is simply using /boot/grub2.grub.cfg. Whether this file was edited by you or not is irrelevant. But now I expect that it should work with file created by grub2-mkconfig. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 28/02/2016 20:31, Andrei Borzenkov a écrit :
it is simply using /boot/grub2.grub.cfg. Whether this file was edited by you or not is irrelevant. But now I expect that it should work with file created by grub2-mkconfig.
right now, I still need nomodeset. When I will have solved my network problem, I will come back to i915 setup :-) thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
I wrote the result of my experience(s) here: http://dodin.info/wiki/pmwiki.php?n=Doc.UEFIBoot any comment / proofread... welcome :-) thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
Andrei Borzenkov -
jdd -
Michael Chang