[ipxe-devel] where to begin debugging

Geert Stappers stappers at stappers.nl
Sun Jan 11 21:03:44 UTC 2026


On Fri, Jan 09, 2026 at 11:04:40PM +0000, Geert Stappers wrote:
> 
> Hello,
> 
> 
> Being a bootloader, that iPXE is, implies starting with nothing.
> Having nothing means having no debugprintroutines.
> 
> What is the first console output that iPXE produces?
> 
> 
> Which DEBUG=   to use to follow the program flow?
> As in:  Which .c file contains main()?
> 
> 
> ( https://ipxe.org/download#debug_builds doesn't tell )
> 
 
I'm asking for my future self. Would be cool if My future self
will find the "where to begin debugging" on the iPXE website
or here in the mailinglist archive.

It is not only me who does benefit from that knowledge.
And it is not my future self that my current self is asking.
This was on the iPXE channel on IRC:


|21:44 < person> Is there a way how to enable debug for all facilities?
|Day changed to 09 jan 2026
|04:21 < stappers> enable debug on all facilities results in being flooded
|                  by debug messages
|06:05 < person> stappers: ok ... so what facility do I need to begin with?
|06:07 < person> stappers: I need the debug flood just to identify the
|                facility responsible for the freeze and therefore I
|                probably don't care it floods the output since I need
|                just the last messages


Groeten
Geert Stappers
-- 
Silence is hard to parse


More information about the ipxe-devel mailing list