Clover General discussion

[bronxteck]

mick do you think its safe now to update the edk version to 23831 in your script seeming as your default edk 23704 is causing issues with boot on some machines?

[Micky1979]

The fact is that I don't know what revision is reccomended by Slice. However the script can be edited for now.

[Micky1979]

Take into account that we don't know where the kernel is loaded. It is Chameleon who knows.

I'll test it soon, the idea (ATM is only that) is that there's no need for the kernel itself, but for its segments and relative load commands.

[bs0d]

Take into account that we don't know where the kernel is loaded. It is Chameleon who knows.

 

At ExitBootServices once you found the boot args struct.

 

KernelData = (VOID *)(UINTN)(BA2->kernelSlide + 0x00200000);

 

now you know too

[Slice]

At ExitBootServices once you found the boot args struct.

 

KernelData = (VOID *)(UINTN)(BA2->kernelSlide + 0x00200000);

 

now you know too

It's a pity I saw faults with this algo. I need double check with some signature.

The fault is not influence on kernel patches because in this case we just search all memory, long delay but works.

Rare users have full faults without ability to start system. This can be one of the reason. 

[mhaeuser]

AptioFix vs AptioFix2? The text section was always at that address and kernelSlide is always set correctly (otherwise the kernel itself wouldn't know where stuff is... could need fixing if u relocate, idk), this algo cannot be flawed...

[erice]

In new 10.12.4 beta Radeon HD 5570 shows flicker.

I restored the kext graphics of 12.3 but the situation is the same: hd works but bad for exactly the same way.

No idea where the problem may reside for a card whose id is still present in AMDLegacySupport.kext?

 

Sorry for the English and thank you.

[r2tincan]

Clover will not go past "Scanning Entries..." if I have SoftRAID drives. This is using the newest release version. My previous version did not have this issue. Please fix!

[Dajjal]

Tried r3994 on my X58 system but it killed Audio.Nothing showed up in system prefs but was present system report/audio.Tried rebuilding caches etc but had to roll back to 3974...

[liujianwei]

 

In new 10.12.4 beta Radeon HD 5570 shows flicker.

I restored the kext graphics of 12.3 but the situation is the same: hd works but bad for exactly the same way.

No idea where the problem may reside for a card whose id is still present in AMDLegacySupport.kext?

 

Sorry for the English and thank you.

 

same here

[erice]

In new 10.12.4 beta Radeon HD 5570 shows flicker.

 

Corrections of the personalities of the Ati card, different energy management to the graphics card, different id?   Clover can possibly help?

 

Thanks.

[Laavuska]

For me the latest version(3994) kept giving CMOS error after I restarted my computer so I had to revert to 3974. Sierra 10.12.3 and a legacy system here. 

[bronxteck]

what edk version did you build 3994 with.

[Slice]

In new 10.12.4 beta Radeon HD 5570 shows flicker.

 

Corrections of the personalities of the Ati card, different energy management to the graphics card, different id?   Clover can possibly help?

 

Thanks.

Same with 6670.

[Sherlocks]

Tried r3994 on my X58 system but it killed Audio.Nothing showed up in system prefs but was present system report/audio.Tried rebuilding caches etc but had to roll back to 3974...

 

try this. and please report

 

thank you

r3994 fix.zip

[pkdesign]

Same here, v3994 killed my audio using the following patches with a realtekALC kext:

 

            <dict>
                <key>Comment</key>
                <string>t1-110.9-10.11-AppleHDA/Realtek ALC885 (Optional)</string>
                <key>Disabled</key>
                <false/>
                <key>Find</key>
                <data>ixnUEQ==</data>
                <key>Name</key>
                <string>AppleHDA</string>
                <key>Replace</key>
                <data>hQjsEA==</data>
            </dict>
            <dict>
                <key>Comment</key>
                <string>t1-AppleHDA/Resources/xml>zml</string>
                <key>Disabled</key>
                <false/>
                <key>Find</key>
                <data>eG1sLnps</data>
                <key>Name</key>
                <string>AppleHDA</string>
                <key>Replace</key>
                <data>em1sLnps</data>
            </dict>

 

When I reverted back to v3974 all was okay.

[mhaeuser]

I just saw this in the latest AptioFix src in Lib.c:

if ((Desc->PhysicalStart < 0xa0000) && (PhysicalEnd >= 0x9e000))

What is this supposed to do? Want to check for a Memory region that is fit in 0x9e000 - 0xa0000? If so, wouldn't it rather need to be this?

if ((Desc->PhysicalStart >= 0x9e000) && (PhysicalEnd <= 0xa0000))

[nekonoko]

For me the latest version(3994) kept giving CMOS error after I restarted my computer so I had to revert to 3974. Sierra 10.12.3 and a legacy system here. 

 

Yep, I'm having the same issue with 10.12.3 and legacy system.

[Sherlocks]

Yep, I'm having the same issue with 10.12.3 and legacy system.

http://www.insanelymac.com/forum/index.php?/topic/284656-Clover-General-discussion&do=findComment&comment=2359605

 

Please test.

 

나의 LG-F410S 의 Tapatalk에서 보냄

Same here, v3994 killed my audio using the following patches with a realtekALC kext:

 

<dict>

<key>Comment</key>

<string>t1-110.9-10.11-AppleHDA/Realtek ALC885 (Optional)</string>

<key>Disabled</key>

<false/>

<key>Find</key>

<data>ixnUEQ==</data>

<key>Name</key>

<string>AppleHDA</string>

<key>Replace</key>

<data>hQjsEA==</data>

</dict>

<dict>

<key>Comment</key>

<string>t1-AppleHDA/Resources/xml>zml</string>

<key>Disabled</key>

<false/>

<key>Find</key>

<data>eG1sLnps</data>

<key>Name</key>

<string>AppleHDA</string>

<key>Replace</key>

<data>em1sLnps</data>

</dict>

 

When I reverted back to v3974 all was okay.

http://www.insanelymac.com/forum/index.php?/topic/284656-Clover-General-discussion&do=findComment&comment=2359605

 

Test please.

 

Now, some patches are not working(KextToPatch). I already reported before. Still not resolve issue.

 

If you give us report, we can solve

 

Thank you

 

나의 LG-F410S 의 Tapatalk에서 보냄

[Slice]

 

I just saw this in the latest AptioFix src in Lib.c:

if ((Desc->PhysicalStart < 0xa0000) && (PhysicalEnd >= 0x9e000))

What is this supposed to do? Want to check for a Memory region that is fit in 0x9e000 - 0xa0000? If so, wouldn't it rather need to be this?

if ((Desc->PhysicalStart >= 0x9e000) && (PhysicalEnd <= 0xa0000))

No.

Range [0x80000, 0x9f000] satisfies first condition but not second.

[kosakgroove]

So will there be any new feature regarding Clover 4000 ?

[Mirone]

Anyone here have problems with reboot? with the latest version r3994 this problem for me became frequent.

simply does not restart, stays in a black screen with the led 
HDD blinking, and after that just only pressing the button 
power to turn off.

[Sherlocks]

Anyone here have problems with reboot? with the latest version r3994 this problem for me became frequent.

simply does not restart, stays in a black screen with the led

HDD blinking, and after that just only pressing the button

power to turn off.

http://www.insanelymac.com/forum/index.php?/topic/284656-Clover-General-discussion&do=findComment&comment=2359605

 

Please test this, and report

 

Thank you

 

나의 LG-F410S 의 Tapatalk에서 보냄

[PMheart]

Hi. I came up with a new idea to find the patch code for KernelPm dynamically instead of now-using static data.

But... Cannot test and too lazy to write code. 

Here it is: (Patch kernel_patcher.c)

 

1. Introduce "UINT32" variable 'i'

2. Call SearchAndCount() to find '00 00 00 00 00 00 00 00 0F 04 00 00 00 00 00 00' and check how many sets we can found.

3. Introduce "int" variable 'k'

4. for (k=0; k < SearchAndCount('00 00 00 00 00 00 00 00 0F 04 00 00 00 00 00 00'); k++) {

      // introduce "int" variable 'j'

      for (j=8; j>0; j--)

        bytes[i-j] == 0x00 // the actual patch for KernelPm 10.10+

}

 

Could someone write the code based on the idea above? Thanks in advance. 

[bs0d]

Hi. I came up with a new idea to find the patch code for KernelPm dynamically instead of now-using static data.

But... Cannot test and too lazy to write code. 

Here it is: (Patch kernel_patcher.c)

 

1. Introduce "UINT32" variable 'i'

2. Call SearchAndCount() to find '00 00 00 00 00 00 00 00 0F 04 00 00 00 00 00 00' and check how many sets we can found.

3. Introduce "int" variable 'k'

4. for (k=0; k < SearchAndCount('00 00 00 00 00 00 00 00 0F 04 00 00 00 00 00 00'); k++) {

      // introduce "int" variable 'j'

      for (j=8; j>0; j--)

        bytes[i-j] == 0x00 // the actual patch for KernelPm 10.10+

}

 

Could someone write the code based on the idea above? Thanks in advance. 

Or just port the symbol based patcher that meklort did umm 4 years ago for chameleon.