In trying Syslinux-6.00 bios/core/pxelinux.0 with a 3.0.21 kernel, I got" "No linux boot function registered for firmware Booting kernel failed: Bad file number" Using Syslinux-5.10, the same kernel/initrd succeeds. Screenshot, kernel and initrd available but I'm figuring this is an issue in the BIOS loader not handling things as it should. -- -Gene
Am 24.06.2013 04:10, schrieb Gene Cumm:> In trying Syslinux-6.00 bios/core/pxelinux.0 with a 3.0.21 kernel, I got" > > "No linux boot function registered for firmware > Booting kernel failed: Bad file number" > > Using Syslinux-5.10, the same kernel/initrd succeeds. > > Screenshot, kernel and initrd available but I'm figuring this is an > issue in the BIOS loader not handling things as it should.As far as I can see, this is an issue of the BIOS firmware not handling things at all - there is not even a code path to the function that boots Linux via BIOS. I can only guess that this is a result of a failed merge followed by not testing 6.00 on BIOS before releasing it. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 901 bytes Desc: OpenPGP digital signature URL: <http://www.zytor.com/pipermail/syslinux/attachments/20130624/f1c96b09/attachment.sig>
On Mon, 24 Jun, at 10:27:52AM, Thomas B?chler wrote:> Am 24.06.2013 04:10, schrieb Gene Cumm: > > In trying Syslinux-6.00 bios/core/pxelinux.0 with a 3.0.21 kernel, I got" > > > > "No linux boot function registered for firmware > > Booting kernel failed: Bad file number" > > > > Using Syslinux-5.10, the same kernel/initrd succeeds. > > > > Screenshot, kernel and initrd available but I'm figuring this is an > > issue in the BIOS loader not handling things as it should. > > As far as I can see, this is an issue of the BIOS firmware not handling > things at all - there is not even a code path to the function that boots > Linux via BIOS. I can only guess that this is a result of a failed merge > followed by not testing 6.00 on BIOS before releasing it.Urk, sorry about that. This is fixed in 6.01-pre1, which I just released. This isn't the result of a failed merge, but I did (clearly) fail to remember to test booting a kernel under BIOS before releasing 6.00. Apologies. -- Matt Fleming, Intel Open Source Technology Center