Jump to content
953 posts in this topic

Recommended Posts

@Slice ,How to solve the addressing error of dual network card in ASUS z87-deluxe? When using OC boot, there will be no problem. When using clover boot, from the start log, we can see that there is a problem in clover days. 0:100 0:000 PCI (00|07:00.00) : 10EC 8168 class=020000。 The address of rtl8111 network card is under Intel. Normally, under Realtek, 0:100 0:000 PCI (00| 09:00.00): 14e4 43b1 class = 028000 will be driven. 

 

preboot.log

Edited by jinbingmao
4 hours ago, kevpatts said:

Any chance of supporting the 5120x1440 native resolution of the Samsung CRG9? It shows in low res when I tried this. Highest 32:9 res I can get working is 3840x1080.

Are you talking about using 5120x1440 in the Clover EFI menu or in macOS?

 

I don't think I've ever seen EFI use anything wider than 3840.

 

SwitchResX can fix macOS - just set the "Scaled resolution base" to 5120x1440. The HDMI and DisplayPort ports may have different EDIDs. HDMI might not have a 5120x1440 timing. If the EDID is missing the 5120x1440 timing then you can create it in SwitchResX. The manual seems to indicate that the HDMI port of the display has the 5120x1440 timing, so this shouldn't be a problem. The display may have different modes that affect the EDID. The display may have different EDIDs between DisplayPort and HDMI ports.

 

You can use my script at https://gist.github.com/joevt/32e5efffe3459958759fb702579b9529 to check and compare all the EDIDs. Use AGDCDiagnose for all the modes and ports (HDMI 1.4/HDMI 2.0, 60Hz, 100Hz, 120Hz, FreeSync Standard Engine, FreeSync Ultimate Engine, FreeSync Disabled, DisplayPort 1.2, DisplayPort 1.4).

 

 

/System/Library/Extensions/AppleGraphicsControl.kext/Contents/MacOS/AGDCDiagnose -a > AGDCDiagnoseXXX.txt 2>&1

 

(replace XXX in the file name with a description of the connected port and mode).

Then use loadagdcfile to load all the files you created - it combines duplicates so that only unique EDIDs are listed by the listedids commands. Then use 

edidbinall
dumpedidall
decodeall

to save all the EDIDs as binaries, dump, and decode them all. Then you can compare them. See if any are missing the 5120x1440 timing.


 

  • Like 1

 

Quote

Are you talking about using 5120x1440 in the Clover EFI menu or in macOS?

Yes, in the Clover EFI.

 

Quote

SwitchResX can fix macOS - just set the "Scaled resolution base" to 5120x1440. The HDMI and DisplayPort ports may have different EDIDs. HDMI might not have a 5120x1440 timing. If the EDID is missing the 5120x1440 timing then you can create it in SwitchResX. The manual seems to indicate that the HDMI port of the display has the 5120x1440 timing, so this shouldn't be a problem. The display may have different modes that affect the EDID. The display may have different EDIDs between DisplayPort and HDMI ports.

I'm using SwitchResX but it doesn't correct the res until a few seconds after you log in, so the login prompts all show at the low res.

 

Quote

You can use my script at https://gist.github.com/joevt/32e5efffe3459958759fb702579b9529 to check and compare all the EDIDs. Use AGDCDiagnose for all the modes and ports (HDMI 1.4/HDMI 2.0, 60Hz, 100Hz, 120Hz, FreeSync Standard Engine, FreeSync Ultimate Engine, FreeSync Disabled, DisplayPort 1.2, DisplayPort 1.4).

 


/System/Library/Extensions/AppleGraphicsControl.kext/Contents/MacOS/AGDCDiagnose -a > AGDCDiagnoseXXX.txt 2>&1

 

(replace XXX in the file name with a description of the connected port and mode).

Then use loadagdcfile to load all the files you created - it combines duplicates so that only unique EDIDs are listed by the listedids commands. Then use 


edidbinall
dumpedidall
decodeall

to save all the EDIDs as binaries, dump, and decode them all. Then you can compare them. See if any are missing the 5120x1440 timing.

I did this at the bottom but the final command just gives me:

Quote

decode:3: command not found: edid-decode

decode:3: command not found: edid-decode

 

12 hours ago, kevpatts said:

 

Yes, in the Clover EFI.

 

I'm using SwitchResX but it doesn't correct the res until a few seconds after you log in, so the login prompts all show at the low res.

 

I did this at the bottom but the final command just gives me:

 

Install edid-decode for the decode and decodeall command to work.

https://git.linuxtv.org/edid-decode.git/about/

 

As for getting 5120x1440 in EFI, that would be an interesting project. I've not looked at EFI video drivers much. One thing it will need to do is to be able to read timings from the DisplayID extension blocks of the EDID since the other blocks do not support resolutions wider than 4096. I don't think EFI supports DisplayID blocks. I don't even think it supports CTA blocks.

 

All the code to parse all parts of EDID is in edid-decode. Most of the specs it uses are publicly available. I'm not sure where or how you would apply it to EFI though. I guess Clover would need to override or patch some drivers...

  • 1 month later...
On 12/25/2019 at 1:16 AM, XLNC said:

@Slice
thanks for implementing the mask patching to clover .
i am trying to use the mask kernel patches from opencore to clover.
but it doesnt seem to work.

can you confirm that this is correct way of mask patching in clover ? 


       FIND: 833D0000 00000074 008B5DBC
    REPLACE: 00000000 00000100 00000000
   MASKFIND: FFFF0000 00FFFFFF 00FFFFFF
MASKREPLACE: 00000000 00000F00 00000000

 

I tested and somehow changed the possibility to patch kernel with masks.

The above syntax is good and the patching works.

The debug message said success

Снимок экрана 2020-03-16 в 7.24.34.png

 

And I see the result of changing kernel

Снимок экрана 2020-03-16 в 7.25.11.png

I changed the kernel message.

 

Test today commit 4618b74d1a9818a6fb5581b84957d7b6b5faa899

On 2/9/2020 at 9:44 PM, jinbingmao said:

@Slice ,How to solve the addressing error of dual network card in ASUS z87-deluxe? When using OC boot, there will be no problem. When using clover boot, from the start log, we can see that there is a problem in clover days. 0:100 0:000 PCI (00|07:00.00) : 10EC 8168 class=020000。 The address of rtl8111 network card is under Intel. Normally, under Realtek, 0:100 0:000 PCI (00| 09:00.00): 14e4 43b1 class = 028000 will be driven. 

 

preboot.log

No, all is right there.

  • Like 1

Hi @Slice

 

Yesterday, I update r5105 48b175 to r5105 5ed385d, without reboot. This morning, I have no Clover GUI only black screen.

 

Do you think is a Clover problem or macOS issue? I rebuild several time kernel cache from a working USB stick (5104), don't works. There is a message Error Kernel cache 0x09.

 

Needs help! Please. 

1 hour ago, Slice said:

I am not sure what is the problem you encountered.

 

Sorry for my bad english. I posted some other details in Clover general topic.

 

This morning:

  • r5105 5ed385d: black screen at start without Clover GUI.
  • r5105 48b175: all works fine.

 

Maybe a macOS Mojave issue?.

 

 

Edited by Matgen84
On 3/16/2020 at 10:03 AM, Slice said:

I tested and somehow changed the possibility to patch kernel with masks.

The above syntax is good and the patching works.

The debug message said success

Снимок экрана 2020-03-16 в 7.24.34.png

 

And I see the result of changing kernel

Снимок экрана 2020-03-16 в 7.25.11.png

I changed the kernel message.

 

Test today commit 4618b74d1a9818a6fb5581b84957d7b6b5faa899


thanks for looking into it .
i will test it out and let you know the result : )
thanks !

13 hours ago, Matgen84 said:

 

Sorry for my bad english. I posted some other details in Clover general topic.

 

This morning:

  • r5105 5ed385d: black screen at start without Clover GUI.
  • r5105 48b175: all works fine.

 

Maybe a macOS Mojave issue?.

 

 

But 5ed385d is not working commit. Test please more recent sources.

  • Thanks 1
3 hours ago, Slice said:

But 5ed385d is not working commit. Test please more recent sources.

 

Same issue with r5105 ce86d7f: no Clover GUI, only Black screen at start. I've to rollback again to working previous version r5105 48b175.

 

I don't understand why.

1 hour ago, Matgen84 said:

 

Same issue with r5105 ce86d7f: no Clover GUI, only Black screen at start. I've to rollback again to working previous version r5105 48b175.

 

I don't understand why.

Is it possible to see debug.log?

46 minutes ago, Slice said:

Is it possible to see debug.log?

 

I try and report.

 

EDIT: @Slice

Despite <key>Log</key> to <true/>, all debug key to true in config.plist, I can't generate debug.log. Maybe because I build release r5105 ce86d7f

Edited by Matgen84
1 hour ago, Matgen84 said:

 

I try and report.

 

EDIT: @Slice

Despite <key>Log</key> to <true/>, all debug key to true in config.plist, I can't generate debug.log. Maybe because I build release r5105 ce86d7f

There is no key "Log", there is key "Debug".

	<key>Boot</key>
	<dict>
		<key>Arguments</key>
		<string>-v arch=x86_64 slide=0</string>
		<key>DefaultVolume</key>
		<string>LastBootedVolume</string>
		<key>DefaultLoader</key>
		<string>boot.efi</string>
		<key>Debug</key>
		<true/>
		<key>Timeout</key>
		<integer>15</integer>

 

  • Like 1
17 minutes ago, Slice said:

There is no key "Log", there is key "Debug".


	<key>Boot</key>
	<dict>
		<key>Arguments</key>
		<string>-v arch=x86_64 slide=0</string>
		<key>DefaultVolume</key>
		<string>LastBootedVolume</string>
		<key>DefaultLoader</key>
		<string>boot.efi</string>
		<key>Debug</key>
		<true/>
		<key>Timeout</key>
		<integer>15</integer>

 

 

 

Debug.log in attachment

 

 

debug.log

3 hours ago, XLNC said:

can anyone provide me the latest clover pkg with recent commit. 
i cant seem to build it on my mac.

- thanks !

This is not a release but latest Clover to test. The installer is restricted. Clover_r5105.zip

 

6 hours ago, Matgen84 said:

@Slice

 

If I exclude  Kernelpatches section (all keys), I've Clover GUI. And of course, I can't boot on macOS Mojave.

May I look this kernelpatches section to reproduce your issue?

 

  • Like 1
5 hours ago, Slice said:

This is not a release but latest Clover to test. The installer is restricted. Clover_r5105.zip

 

May I look this kernelpatches section to reproduce your issue?

 

Thanks for the clover pkg. Tested it but still didnt work unfortunately.

Enabled debug and this time it showed Error for all the patches in the list. :/

  • Sad 1
×
×
  • Create New...