Displaying 3 results from an estimated 3 matches for "elf_mod_sys".
2015 Aug 05
1
EFI: HP + syslinux = crash
...messages end up nowhere. This may explain
> why I never saw anything beyond a certain point, even with debugging
> turned on.
> <<<
>
> isn't it redirected at all??
No. If, for example, I change:
dprintf("Starting %s elf module subsystem...\n", ELF_MOD_SYS);
into regular printf(), I don't see the result in my ipmi-logs nor on my
screen. If I change it to Aprint() (and %s into %a) then I do see the
message.
To make sure it isn't overwritten before I see it, I put a while(1) in
front, so it will end in an endless loop printing this message...
2015 Oct 07
2
Hyper-V Gen 2 waiting for ldlinux.e64
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
2015 Aug 04
8
EFI: HP + syslinux = crash
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