I think #define REFIT_DEBUG (1) just adds some debug text to the screen (requires text mode?). I haven't tried this so I don't know what it looks like. There's only a handful of message that may appear.
It can show device paths of scanned volumes. Change (1) to (2) to also include a hex dump of the path which you can check with gfxutil in macOS.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
@Startergo , when you asked about this a while ago and I pointed you to these flags, i was just telling you within the context of the amended version I was working on that you wanted to build.
In reality, @joevt is correct that the REFIT_DEBUG natively simply outputs some text to screen as Refind does not have debug build flags (you can't build DEBUG) mode and does not do debug logging natively.
BTW, REFIT_DEBUG actually has three settings in the native implementation: 0, 1 & 2 as pointed outbu joevt.
In the amended version by Jief_Machak leveraging stuff from Clover, this flag was used as part of the MemLog patch using with 0 & 1 (actually anything over 0) as a "on/off" switch to create debug logs. Basically, he found a way to create a Quasi Debug Version.
DearthnVader on MacRumours built the v0.10.3 variant that showed Bootscreen on CMP 3,1 running Custom GPUs based on Jief Machak's work and I have taken it further in Refind-GOPFix and significantly expanded the logging as part of introducing the enhancements in that variant to provide bootscreen on other units running Custom GPUs. I also added a script to automate creating the quasi debug version.
In summary, if you build the native released version and change the flag, you will not get any debug log. It only works in this way on the amended versions that build on Jief's work.
Last edit: dakanji 2020-08-03
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm new to rEFind and I'm trying to figure out how the DebugModes work.
I found some meantion of DebugModes 0/1/2 in the Bootlog.c, but I'm not sure how to enable each mode, is that something I can set in the refind.conf?
I think you've got the wrong project; there is no Bootlog.c source file in rEFInd, nor is there a DebugModes variable or constant.
Debug switch is in the source code in RefindPkg/refind/globals.h
define REFIT_DEBUG (0)
define REFIT_DEBUG (1)
(1) Enables debug logging
You will have to compile from the source code.
Last edit: Startergo 2020-08-02
I think
#define REFIT_DEBUG (1)
just adds some debug text to the screen (requires text mode?). I haven't tried this so I don't know what it looks like. There's only a handful of message that may appear.It can show device paths of scanned volumes. Change
(1)
to(2)
to also include a hex dump of the path which you can check withgfxutil
in macOS.@Startergo , when you asked about this a while ago and I pointed you to these flags, i was just telling you within the context of the amended version I was working on that you wanted to build.
In reality, @joevt is correct that the REFIT_DEBUG natively simply outputs some text to screen as Refind does not have debug build flags (you can't build DEBUG) mode and does not do debug logging natively.
BTW, REFIT_DEBUG actually has three settings in the native implementation: 0, 1 & 2 as pointed outbu joevt.
In the amended version by Jief_Machak leveraging stuff from Clover, this flag was used as part of the MemLog patch using with 0 & 1 (actually anything over 0) as a "on/off" switch to create debug logs. Basically, he found a way to create a Quasi Debug Version.
DearthnVader on MacRumours built the v0.10.3 variant that showed Bootscreen on CMP 3,1 running Custom GPUs based on Jief Machak's work and I have taken it further in Refind-GOPFix and significantly expanded the logging as part of introducing the enhancements in that variant to provide bootscreen on other units running Custom GPUs. I also added a script to automate creating the quasi debug version.
In summary, if you build the native released version and change the flag, you will not get any debug log. It only works in this way on the amended versions that build on Jief's work.
Last edit: dakanji 2020-08-03