similar to: [PATCH] Improve EFI console logging

Hello, While debugging #1103692 on Debian [0], I came across an issue where error messages generated early in the syslinux boot process through writestr() didn't end up appearing on-screen. Instead, it appeared that only the cursor moved. I discovered that it's because the early code passes a video attribute of 0 to the efi_write_char() function, which is black-on-black, and produces

On Thu, Oct 08, 2015 at 01:24:26AM +0200, Geert Stappers via Syslinux wrote: > On Wed, Oct 07, 2015 at 05:58:51PM -0500, Clements, James wrote: > > > Correct me if I am wrong but if I understand correctly, syslinux.efi is > > what drives the request for ldlinux.e64. Is there a way we can enable > > some debug somehow to see why the request for ldlinux.e64 includes >

On Wed, Oct 07, 2015 at 05:58:51PM -0500, Clements, James wrote: > James Clement > > Geert Stappers > > > On Wed, Oct 07, 2015 at 05:06:41PM -0500, Clements, James wrote: > > > > The screen displays the following: > > > > > > > > PXE Network Boot using IPv4 > > > > .... > > > > Station IP address is 192.168.205.50

> Hello James, > > > ----- Forwarded message from Geert Stappers via Syslinux > <syslinux at zytor.com> ----- > > Date: Thu, 8 Oct 2015 01:24:26 +0200 > From: Geert Stappers via Syslinux <syslinux at zytor.com> > To: "Clements, James" <James.Clements at affiliate.oliverwyman.com> > Cc: "syslinux at zytor.com" <syslinux at

On 13.07.2015 12:08, Gene Cumm wrote: > systemd Mailing List <systemd-devel at lists.freedesktop.org> would be > the wrong address. > > On Mon, Jul 13, 2015 at 5:33 AM, poma <pomidorabelisima at gmail.com> wrote: >> On 03.07.2015 21:35, Gene Cumm wrote: >>> On Jul 3, 2015 1:34 PM, "poma" <pomidorabelisima at gmail.com> wrote: >>>

This patch adds to Com32 modules the capabilities of accessing the EFI environment The idea is simple, the EFI parameters "image" and "table" received by syslinux.efi's efi_main() are stored in the "firmware" structure, next they are retrieved from the Com32 module which is linked against the gnu-efi static library. The Com32 module can use the EFI

On Tue Mar 24 03:57:51 PDT 2020, Thomas Petazzoni wrote: > Building syslinux against gnu-efi 3.0.10 currently fails with: > > syslinux/efi/main.c:33:8: error: unknown type name ?jmp_buf? >??? 33 | static jmp_buf load_error_buf; >?????? |??????? ^~~~~~~ > syslinux/efi/main.c: In function ?local_boot?: > syslinux/efi/main.c:189:5: warning: implicit declaration of

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 *

EFI booting may hang indefinitely when no keyboard is present on a machine (or when UEFI has chosen to not init USB due to fast boot). Reproducible at least with "EFI v2.31 by American Megatrends" on an Asrock H81M-ITX board. Reason is the input draining loop near the end in efi/main.c; it calls ReadKeyStroke() as long as EFI_NOT_READY is not returned. On machines without keyboard,

From: Matt Fleming <matt.fleming at intel.com> The location of __file_info[] and ansicon_counter are split between the core and ldlinux.c32. We can end up calling __ansicon_close (from fp->oop->close) in the process of reloading ldlinux.c32, and while ansicon_counter is set to its initialised data value of 0 when reloading ldlinux.c32, the core is never reloaded, and so __file_info[]

Hi, I just pushed out changes that fix pretty much all the compiler build warnings on the elflink branch. Also, I've added "auto extension" support so that if the user doesn't type the file name extension it will automatically be looked up, e.g. now typing "ls" will execute "ls.c32". The following changes since commit

Hi Peter, The main part of this pull request includes commits that try to replace as many __intcall() invocations as possible. Some remain, but not many (and eventually they'll be gone too). There's also a patch to make better use of ld's --as-needed option and various other bug fixes/cleanups. The following changes since commit ff7334a2ce536b7f4b1f6d6f93ff4e285a3bd45a: Only

Hello, On Debian, I've hit a bit of an issue with the 32-bit EFI support where the ELF loader failed to load the ldlinux.e32 file. The issue occurs in com32/lib/sys/module/i386/elf_module.c in the load_segments() function, particularly when iterating through the module's program headers and loading the PT_LOAD ones. The code hits a program section which has a zero on-disk size, the

From: Gene Cumm <gene.cumm at gmail.com> CORE/writedec: Fix overflow and redeclaration; If EDX is greater than or equal to 10, div can cause an overflow. Comment out declaration of writechr. Signed-off-by: Gene Cumm <gene.cumm at gmail.com> --- Against current head. hpa: If there's a preferred way to do what this function provides, let me know. Was the writechr in there on

Greetings, I'm having a slight error with a certain program in wine. I'm using RPG Maker XP to make an rpg game. It utilizes a modified version of ruby called RGSS. I am using a script that opens a debug output console, it works fine in M$ Windows, but I get the following error in wine: > Microsoft Visual C++ Runtime Library > Runtime Error! > > Program:

From: Sylvain Gault <sylvain.gault at gmail.com> The behavior when running a "CONFIG" command line is to reload ldlinux.c32 with the new file as argument. This call never return. In order to avoid stacking up the calls to start_ldlinux, this patch introduce a setjmp/longjmp to return to the first call to start_ldlinux, thus freeing all the stack space. Signed-off-by: Sylvain

On Fri, 27 Oct 2023, Roger Marsh wrote: This is missing a lot of context, and I had to go to the misc@ archives to find out the actual command that is running slow for you. AFAIK, it's ssh -Y opendev xterm -title roger at opendev Please get a debug trace from the ssh connection, e.g. "ssh -vvv -Y ..." and annotate where the delay happens. Without this, we're not in a position

Hi, Matt Fleming wrote: > 'make efi64' will build just for x86-64. Likewise, 'make efi32' will > build just for i386. You can combine these, so to build BIOS and efi64 > you'd do, > > make bios efi64 'make efi64' failed with: ld -T /tmp/syslinux/efi/x86_64/syslinux.ld -Bsymbolic -pie -nostdlib -znocombreloc -L/usr/lib64 --hash-style=gnu -m elf_x86_64

Hi all, i am learning cucumber and when i am trying to run rake cucumber:ok resulting in following error: C:/Ruby187/bin/ruby -S bundle exec cucumber --profile default *** WARNING: You must use ANSICON 1.31 or higher ( http://adoxa.110mb.com/ansicon ) to get coloured output on Windows Using the default profile... Feature: Creating projects In order to have projects to assign

On 04-08-15 14:42, Patrick Masotta wrote: > I think we solved a bug but we found a new one. > AFAIK you were not able to retrieve anything after loading syslinux.efi > Now you retrieve ldlinux.e32, libcom32.c32, etc but it crashes when loading a png. > If this is the case then the multi-nic issue is solved; the new code is able to > find the NIC that booted syslinux.efi and then