similar to: [PATCH 0/1] dprintf: add debug console support

On Sun, Feb 08, 2015 at 09:13:02AM -0700, Jonathan Boeing via Syslinux wrote: > This patch adds support for printing messages through a debug console. QEMU, > for example, supports this through the debugcon facility. The benefit is that > it's *much* faster than printing over a serial port. > > To print to I/O port 0x402 (the default used by SeaBIOS and OVMF), > add

On 05-08-15 15:28, Gene Cumm wrote: >>> 0x2f8 is a BIOSism. > >> Is this a problem? The example in the comments said 0x3f8 which is COM1. > > It means that a BIOS IO port for a UART won't work for EFI. No value > for DEBUG_PORT will do anything unless someone's got some translation > "glue" to take the attempts to open the UART and use an EFI handle

On 05-08-15 12:05, Gene Cumm wrote: > > I recompiled with this in mk/devel.mk <http://devel.mk>: > > GCCWARN += -DDEBUG_PORT=0x2f8 -DCORE_DEBUG=1 > > 0x2f8 is a BIOSism. Is this a problem? The example in the comments said 0x3f8 which is COM1.

On Sun, 8 Feb 2015 17:41:58 +0100 Geert Stappers via Syslinux <syslinux at zytor.com> wrote: > On Sun, Feb 08, 2015 at 09:13:02AM -0700, Jonathan Boeing via > Syslinux wrote: > > This patch adds support for printing messages through a debug > > console. QEMU, for example, supports this through the debugcon > > facility. The benefit is that it's *much* faster

On Tue, Oct 27, 2015 at 10:15 PM, Bruno Cornec via Syslinux <syslinux at zytor.com> wrote: > Bruno Cornec via Syslinux said on Wed, Oct 28, 2015 at 01:45:22AM +0100: >> >> Is there a way to increase the debug level of syslinux.efi in order to >> check what it tries to do and diagnose more precisely what happens ? > > > Ok, I tried to modify mk/devel.mk to put:

I noticed several issues when diagnosing why pxechn.c32 didn't work in 5.01-pre3. 1) pxechn.c32, prdhcp.c32 and other modules crash Syslinux and force a reboot by executing an unresolved symbols. unload_pxe(), dns_resolv() and pxe_call() are the three. "Error: An undefined symbol was referenced" 2) In past versions, I built a debug build by having "CFLAGS += -DDEBUG=1"

On 04-08-15 17:38, Oscar Roozen wrote: > Okay, the code in efi/ uses Print() from gnu_efi, but generic code from > core/ like core/elflink/load_env32.c prints their messages and debugging > stuff using printf(). These messages end up nowhere. This may explain > why I never saw anything beyond a certain point, even with debugging > turned on. I was busy adding some code to dprintf.h

As per Ian comment on previous commit 7123d9834d58287d43514d7799ed1a7b34eea243 Signed-off-by: Julian Pidancet <julian.pidancet@gmail.com> --- src/Kconfig | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/src/Kconfig b/src/Kconfig index cf0bff0..cee0005 100644 --- a/src/Kconfig +++ b/src/Kconfig @@ -361,6 +361,7 @@ menu "Debugging" config DEBUG_IO_PORT

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

On 6/6/19 8:16 AM, Ady Ady via Syslinux wrote: > >> the PXELINUX log line is >> printed (PXELINUX 6.04 lwIP 6.04-pre3 Copyright (C) 1994-2015 H. Peter >> Anvin et al), > > (snip) > > FWIW, the official binaries from 6.04-pre2 and 6.04-pre3 are not good > for troubleshooting. > > Is the same behavior present when testing with other versions? I would

Thanks VERY MUCH for all the info and help! Apologies for the extreme delay. I got distracted by other threads that forced out this work to later date. Also some frustration as well. ;) I completely missed this update. Apologies and thanks Will be diving back into this shortly! On Thu, Mar 24, 2016 at 3:57 PM, Laszlo Ersek <lersek@redhat.com> wrote: > On 03/21/16 19:53, jsl6uy js16uy

Fixes some typos and missing newlines Jonathan Boeing (2): fix a few typos add missing '\n' to dprintf com32/include/sys/module.h | 2 +- com32/lib/sys/module/exec.c | 4 ++-- core/fs/fs.c | 2 +- core/lwip/src/netif/undiif.c | 2 +- 4 files changed, 5 insertions(+), 5 deletions(-) -- 2.3.0

The following changes since commit 89794a3d0b8659e2a143faeffc77877b45754c52: Matt Fleming (1): Merge branch 'dynamic-debug' into elflink are available in the git repository at: git://github.com/geneC/syslinux.git elflink-undi-debug-for-mfleming Gene Cumm (5): lwip: undiif: Fix debug options to unique *_DEBUG macros lwip: Allow LWIP_PLATFORM_* output to use

On Tue, Jun 30, 2015 at 4:29 PM, poma <pomidorabelisima at gmail.com> wrote: > "A real serial port that can reliably operate at 115200 8n1 may be > necessary." > > Gene, is there something special in "A real serial port" usage, compared to emulated? I should restate: A serial port that responds on BIOS IO port 3F8h that can reliably operate at 115200 8n1 may

I have reason to believe that an odd box that is having boot trouble has three instances of "!PXE" in the chunk of memory that "Method D" should look at. I thought I would try to find out how pxelinux copes with this, by trying to insert printfs in pxe_init, but nothing gets printed. I can spew lots of output if I set DEBUGOPT = -DDEBUG=1 -DDEBUG_STDIO -DCORE_DEBUG=1 but

The following changes since commit 6438fbcb6cb7e0cd40e4bb3681ada047fe77ffdd: Gene Cumm (1): Allow for UNDIIF_ID_DEBUG in 1 mk line are available in the git repository at: git://github.com/geneC/syslinux.git elflink-pxe-fixes-for-mfleming https://github.com/geneC/syslinux/tree/elflink-pxe-fixes-for-mfleming Gene Cumm (12): core/lwip/undi: Improve UNDIIF_ID_DEBUG messages

On Mon, Jul 22, 2013 at 11:43 AM, Matt Fleming <matt at console-pimps.org> wrote: > On Sat, 20 Jul, at 09:33:53AM, Gene Cumm wrote: >> The following changes since commit 89794a3d0b8659e2a143faeffc77877b45754c52: >> Matt Fleming (1): >> Merge branch 'dynamic-debug' into elflink >> >> are available in the git repository at: >> >>

Hello Thomas, Thomas Schmitt via Syslinux said on Sun, Oct 25, 2015 at 04:35:57PM +0100: >I assume you can boot Fedora Live CD on the same (virtual) hardware. Not sure for Fedora, but the system is installed with either RHEL6, RHEL7 or Ubuntu 14.04 depending on the Lab I'm making on it without issue. >Just to make sure that the firmware works so far. Globally they do ;-) >

>>> > On 05-08-15 12:05, Gene Cumm wrote: >> >>? > I recompiled with this in mk/devel.mk <http://devel.mk>: >>? >? GCCWARN += -DDEBUG_PORT=0x2f8 -DCORE_DEBUG=1 >> >> 0x2f8 is a BIOSism. > Is this a problem? The example in the comments said 0x3f8 which is COM1. It means that a BIOS IO port for a UART won't work for EFI.? No

BTRFS file systems will be corrupted on 6.02 (mainstream) and some previous versions. DYNAMIC_DEBUG makes the core larger than the allowed. Even before its introduction, building Syslinux with DEBUG_PORT enabled would probably corrupt BTRFS images (IIRC) *if* ldlinux.sys surpasses the maximum allowed size. Besides, the installer isn't safe at all... The check could be easily made there to