search for: _bios_

Hello all, We're having the following issue: when in UEFI mode, any output/errors from a lua script is invisible! This occurs even just running 'lua -v'. It runs and returns to a (visible) 'boot:' prompt, but there is simply no output visible from lua! (It does do a linefeed, but no visible text appears.) Has anyone encountered this? And/or know of a solution? For

...utput visible > from lua! (It does do a linefeed, but no visible text appears.) Yes, the report can be confirmed. FWIW, the invisible output is not just a linefeed; rather, the "same" output that would be expected is not seen. To replicate, from a boot prompt using 6.04-pre1 in _BIOS_ mode: _ the output of 'lua.c32 -v' (in lower-case) is correctly shown, in one line/row; _ the output of 'lua.c32 -V' (in upper-case) is correctly shown, spanning several lines/rows. Repeating the above 2 commands in UEFI mode (with the corresponding _UEFI_ binaries) shows the...

> There's 0 need to build MBRs for > EFI At least gptmbr.bin might come to mind (after all, GPT is part of the UEFI specs). Isohybrid with UEFI options perhaps too? > and I'm looking at why utils/ depends on mbr/ isohybrid(.pl) and mkdiskimage come to mind here? I'm not saying for certain these are the reasons for such dependencies, but they might (and perhaps

.../geneC/syslinux/blob/master/mbr/gptmbr.S > > "Active" partitn would be the one which has bit 2 set in the Attributes > field (byte offset 48 to 55) of its GPT entry: "Legacy BIOS Bootable". That's the main goal of gptmbr.bin: to be able to boot a GPT scheme in _BIOS_ mode. > So indeed, EFI on hard disk does not need more of an MBR than the magic > number at bytes 510, 511 and an MBR partition entry of type 0xEE or > 0xEF. Well, for booting in UEFI mode, the (0xEE and/or 0xEF and/or any other) "legacy" partition(s) in the so-called &quo...