similar to: [bug] 6.00: No linux boot function

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. > >

Am 24.06.2013 11:25, schrieb Matt Fleming: > 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" >>>

On Tue, 25 Jun, at 01:09:47PM, H. Peter Anvin wrote: > Not really... let's just document "make bios". There's preliminary documentation in doc/building.txt. -- Matt Fleming, Intel Open Source Technology Center

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

I'm planning on releasing 6.01 next week. The list of changes (so far) are appended below. This is going to be a quick bug fix release, mainly because of the rather embarrassing bug in the 6.00 that prevents booting a Linux kernel on BIOS. The idea is to get a fixed release into everyone's hands ASAP. Thanks to everyone who has helped with debugging. --- Matt Fleming (9): efi:

On 07/05/2013 01:02 PM, Gerardo Exequiel Pozzi wrote: > > 5.00 [pxelinux.0] OK 5.01 [pxelinux.0] OK 5.02-pre1 > [pxelinux.0] OK 5.02-pre2 [pxelinux.0] OK 5.02-pre3 [pxelinux.0] > BAD (freeze, no error messages, 100% CPU used) > > 5.10-pre1 [pxelinux.0] BAD (freeze, no error messages, 100% CPU > used) 5.10-pre2 [pxelinux.0] BAD (Failed to load: ldlinux.c32,

On Thu, 27 Jun, at 11:02:51PM, Thomas B?chler wrote: > Am 27.06.2013 22:08, schrieb Matt Fleming: > > I'm planning on releasing 6.01 next week. The list of changes (so far) > > are appended below. This is going to be a quick bug fix release, mainly > > because of the rather embarrassing bug in the 6.00 that prevents booting > > a Linux kernel on BIOS. The idea is to

On Thu, 27 Jun, at 11:02:51PM, Thomas B?chler wrote: > Am 27.06.2013 22:08, schrieb Matt Fleming: > > I'm planning on releasing 6.01 next week. The list of changes (so far) > > are appended below. This is going to be a quick bug fix release, mainly > > because of the rather embarrassing bug in the 6.00 that prevents booting > > a Linux kernel on BIOS. The idea is to

Hello With 4.06 this works fine all times. But with versions 5.1x-preX and 6.0x-preX, 6.01) does not work, random errors or nothing shows (netconn_write error -5), random behaviour. Only few times works (1/50...). Note that retriving files via TFTP works perfect in all cases. This happens using pre-compiled files in tarball and building for source. # dnsmasq --port=0 \

On Mon, 24 Jun 2013, Matt Fleming wrote: > On Mon, 24 Jun, at 10:27:52AM, Thomas B?chler wrote: > >> 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

On Wed, 26 Jun, at 02:17:00PM, Helmut Hullen wrote: > Running "pxelinux": more problems than with 5.10. > > 5.00-pre6: all worked fine > > 5.10: the start menu (GUI) wasn't shown; "tab" showed the labels, and > the textual menus. Invoking the labels worked. > > 6.00: no GUI start menu. "tab" showed the textual menus. Invoking them

Am 06.06.2013 07:00, schrieb Gene Cumm: > iPXE details. My testing was with an Intel PXE OROM in a VMware > hosted platform with 0 issues. > >> 1370470692 192.168.0.90 "GET /arch/boot/syslinux/pxelinux.0" 200 26813 >> "" "iPXE/1.0.0+ (09c5)" This is the iPXE version that comes bundled with qemu as the default qemu boot rom. -------------- next

Finally, the Syslinux 6.00 release is out. This release includes support for booting from EFI, both from disk-based media and over the network via PXE. Thanks to everyone who has been testing this out. There are some EFI bugs that I'm aware of, * booting Linux kernels without CONFIG_RELOCATABLE doesn't work * 64-bit syslinux.efi cannot boot 32-bit kernels and vice versa *

Hello friends! HAXM is a hardware-assisted virtualization engine (hypervisor) that uses Intel Virtualization Technology to speed up IA (x86/ x86_64) emulation on a host machine running Windows or macOS. Latest Isolinux 6.03 hangs under VM after "Main image LBA =...". Please, help us investigate the root of the problem. Bug on github: https://github.com/intel/haxm/issues/15 Thank you!

> Hallo, Matt, > > Du meintest am 25.06.13: > > >> Not really... let's just document "make bios". > > > There's preliminary documentation in doc/building.txt. > > (sent to you and to the mailing list; some robot blocks the list ...) > > Additionally: > > Compiling (with "make bios") worked. > > Running

Hi, I have the same problem as Helmut with INCLUDE keyword and extlinux 5.10 an later. The following configuration has been tested and worked with extlinux 4.05, 4.06, 5.01 Contents of "boot_label" file DEFAULT 1 --------------------------------------- Contents of "extlinux.conf" file # Enable menu.c32 UI menu.c32 # Disable the boot: prompt PROMPT 0 # 5 sec TIMEOUT 50 #

Hallo, I wrote am 26.06.13: > Running "pxelinux": more problems than with 5.10. > 5.00-pre6: all worked fine > 5.10: the start menu (GUI) wasn't shown; "tab" showed the labels, and > the textual menus. Invoking the labels worked. > 6.00: no GUI start menu. "tab" showed the textual menus. Invoking > them seems to do nothing (after some

On Fri, 30 Aug 2013 05:43:42 -0400 Gene Cumm <gene.cumm at gmail.com> wrote: > On Aug 30, 2013 4:51 AM, "YuGiOhJCJ Mailing-List" < > yugiohjcj-mailinglist at laposte.net> wrote: > > > > Hello, > > > > If I do: > > $ tar xvf syslinux-6.01.tar.xz > > $ cd syslinux-6.01 > > $ make clean > > > > Then I get: > >

> Have you tried 5.10 in your environment on a BIOS machine to see whether > that works and which port numbers it uses? > > -- > Matt Fleming, Intel Open Source Technology Center Hi Matt, I have now tested the gpxelinux.0 from syslinux-6.00. This work. The ldlinux.c32 download is from the same port as it was requested from the client. My problem is with EFI boot, not BIOS.

On Wed, Jun 5, 2013 at 9:58 PM, upen <upendra.gandhi at gmail.com> wrote: > I copied pxelinux.cfg/default to pxelinux.cfg/<IP to HEX> and it looks this > step resolved the earlier error. Next I get failed to load com32 file > vesamenu.c32 while that file exists in /tftplinux/linux-install. Is vesamenu.c32 from 5.10? -- -Gene