What is -cdfon boot argument used in clover.plist?

[Mikael25]

What is -cdfon boot argument used in config.plist?

I searched but no results anywhere. I am curious because this flag causes my hack to keep waiting with some harddisk activity ongoing and a never finishing loading bar.

Tried with verbose but somewhere the screen just goes blank and stays like that.

 

[RehabMan]

What is -cdfon boot argument used in config.plist?

Read the WhateverGreen documentation on github.

Hint: It enables 'CoreDisplayFixup' related code/patching in WhateverGreen.kext.

 

[Mikael25]

I tried to understand how it works but very little knowledge about that on Whatevergreen Github so I tried digging a bit on the original page here.

Unfortunately the developer hasn't released CoreDisplay patches for 10.14
I still tried patching for tests, and surprisingly, it patched the CoreDisplay.framework

-----------------------------------------------------------------------------------------
Mac:~ Mac$ ~/Documents/CoreDisplay-patcher.command
SIP might or might not be disabled
the script might or might not be working
check "$ csrutil status"
more info: Google 'SIP'
Do you want to continue? [Y/n] y

Unknown version of CoreDisplay found..
---- BEGINNING MD5 HASH SUMS ---- version: 10.14.1 build:18B75


otool CoreDisplay: 6c76846ea2b77e2a5f933c260ae95471
otool CoreDisplay.bak: NO FILE (this is okay)
CoreDisplay: 7a46a80605f6d794e9e60612964ee5bf
CoreDisplay.bak: NO FILE (this is okay)

---- ENDING MD5 HASH SUMS -------
-----------------------------------------------------------------------------------------

I am assuming that WhateverGreen has it's own way of adopting these patches even though the original patches are not for 10.14..

Also, -cdfon only worked after the above patch process and disabling SIP (0x67).
From what I could analyse, I assume this boot argument may cause issue for people using HiDPI resolutions (I used RDM for this).

When trying to unpatch the CoreDisplay, it returned this;

Mac:~ Mac$ ~/Documents/CoreDisplay-patcher.command unpatch
There is no backup file, we can not undo the patch. the patch might not even been done.
Closing..

 

[RehabMan]

I tried to understand how it works but very little knowledge about that on Whatevergreen Github so I tried digging a bit on the original page here.

Unfortunately the developer hasn't released CoreDisplay patches for 10.14
I still tried patching for tests, and surprisingly, it patched the CoreDisplay.framework

-----------------------------------------------------------------------------------------
Mac:~ Mac$ ~/Documents/CoreDisplay-patcher.command
SIP might or might not be disabled
the script might or might not be working
check "$ csrutil status"
more info: Google 'SIP'
Do you want to continue? [Y/n] y

Unknown version of CoreDisplay found..
---- BEGINNING MD5 HASH SUMS ---- version: 10.14.1 build:18B75


otool CoreDisplay: 6c76846ea2b77e2a5f933c260ae95471
otool CoreDisplay.bak: NO FILE (this is okay)
CoreDisplay: 7a46a80605f6d794e9e60612964ee5bf
CoreDisplay.bak: NO FILE (this is okay)

---- ENDING MD5 HASH SUMS -------
-----------------------------------------------------------------------------------------

I am assuming that WhateverGreen has it's own way of adopting these patches even though the original patches are not for 10.14..

Also, -cdfon only worked after the above patch process and disabling SIP (0x67).
From what I could analyse, I assume this boot argument may cause issue for people using HiDPI resolutions (I used RDM for this).

When trying to unpatch the CoreDisplay, it returned this;

Mac:~ Mac$ ~/Documents/CoreDisplay-patcher.command unpatch
There is no backup file, we can not undo the patch. the patch might not even been done.
Closing..

No need to patch CoreDisplay manually.
You can simply use WhateverGreen.kext+Lilu.kext+ kernel flag -cdfon.