#4437 BFO does not work from GRUB2
Closed: Insufficient data 2 years ago Opened 6 years ago by vondruch.

This question stays unanswered:

https://ask.fedoraproject.org/en/question/23832/have-others-had-success-with-bfo-grub2-on-fedora-18/

I have tried today without success.


Can you re-test this now?

We are using the latest ipxe now...

Can you reopen if there's still a problem here?

No luck here :/

When I followed the instructions exactly, I got the "can't find command linux" error. So I tried to use "linuxefi" instead, since this is UEFI system. This gave me file '/bfo.lkrn' not found.

So I modified the /etc/grub2-efi.cfg (basically copying the other entries):

{{{
menuentry 'Boot BFO' --class gnu-linux --class gnu --class os {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 7ce53d1d-66d2-4193-9c60-04da20b15168
else
search --no-floppy --fs-uuid --set=root 7ce53d1d-66d2-4193-9c60-04da20b15168
fi
linuxefi /bfo.lkrn
}
}}}

This gave me "kernel too old" message.

It seems that the IPXE kernel reports rather old version :/

{{{
$ file /boot/bfo.lkrn
/boot/bfo.lkrn: Linux kernel x86 boot executable bzImage, version 1.0.0+ (a937), RO-rootFS,

$ file /boot/vmlinuz-3.18.7-200.fc21.x86_64
/boot/vmlinuz-3.18.7-200.fc21.x86_64: Linux kernel x86 boot executable bzImage, version 3.18.7-200.fc21.x86_64 (mockbuild@bkernel02.phx2.fedoraproject., RO-rootFS, swap_dev 0x5, Normal VGA
}}}

Faking the version to be 3.6+ might help.

Since this seems to be caused by Grub's naive version checks, I reported this issue here:

https://bugzilla.redhat.com/show_bug.cgi?id=1215693

Finally I got somewhere. For UEFI, I can't load the .lkrn image, but I need to have something like bfo.efi. This was pointed out in this thread [1]. Nevertheless, such image is not available at BFO, so the question is now how to create/get it?

[1] http://lists.ipxe.org/pipermail/ipxe-devel/2015-September/004413.html

So I did "make everything EMBED=script0.ipxe". This gave me bin-x86_64-efi/ipxe.efi I used to boot and I succeeded. But didn't get far enough. It downloads the fedora configuration and tries to execute the "chain http://dl.fedoraproject.org/pub/alt/bfo/pxelinux.0" and fails with

Could not boot: Exec format error (http://ipxe.org/err/2e0080)

This page says that for EFI, there should not be loaded the pxelinux.0, but iPXE menuing capabilities can be used.

[1] http://ipxe.org/cmd/choose

Can you test against the latest images now? I don't know that it's fixed, but I did update ipxe at f27beta.

Metadata Update from @kevin:
- Issue priority set to: Waiting on Reporter

3 years ago

Metadata Update from @kevin:
- Issue priority set to: Next Meeting (was: Waiting on Reporter)

2 years ago

Metadata Update from @smooge:
- Issue assigned to smooge

2 years ago

So I talked with the former upstream for bfo, and they have not been running it for a long time due to lots of little issues. I would like to get an idea if this is something we should continue or if the bfo can be EOL.

Metadata Update from @smooge:
- Issue priority set to: Waiting on Reporter (was: Next Meeting)

2 years ago

This service was never really promoted. But I'd love to use it, since it should be supposedly the easiest way to get Fedora, because if I understand it correctly, this should allow me to boot Fedora without any media, just using iPXE. But it did not worked with UEFI and so far I had no chance to experiment with the new images. However, I am building new computer right now, so soon I might get chance to test the new images.

Thanks. We currently see 1 to 2 ip addresses a day use the service but do not get much/any feedback other than this ticket.

The problem is due to various factors outside of Fedoraprojects's control
* Lack of UEFI testing
* boot upstream is dead
* slow upstream support to ipxe

We will continue keeping the service going but it should be considered deprecated for what can be fixed/improved.

Metadata Update from @smooge:
- Issue close_status updated to: Insufficient data

2 years ago

Login to comment on this ticket.

Metadata