Contribute
Register

Intel DH67CF with HD4000 using Clover

Status
Not open for further replies.
Hello @RehabMan,

I tried the following values without success:
0x01620005 - strange graphics
0x01620006 - crash & reboot
0x01620007 - crash & reboot
0x01660000 - strange graphics
0x01660001 - strange graphics
0x01660002 - progress bar stuck
0x01660003 - strange graphics
0x01660004 - progress bar stuck
0x01660008 - progress bar stuck
0x01660009 - progress bar stuck
0x0166000a - strange graphics
0x0166000b - strange graphics


Is there any other parameter I should change in config.plist file ? I can't find anything else related to prealloc video memory size in BIOS

Thanks
 
Hello @RehabMan,

I tried the following values without success:
0x01620005 - strange graphics
0x01620006 - crash & reboot
0x01620007 - crash & reboot
0x01660000 - strange graphics
0x01660001 - strange graphics
0x01660002 - progress bar stuck
0x01660003 - strange graphics
0x01660004 - progress bar stuck
0x01660008 - progress bar stuck
0x01660009 - progress bar stuck
0x0166000a - strange graphics
0x0166000b - strange graphics


Is there any other parameter I should change in config.plist file ? I can't find anything else related to prealloc video memory size in BIOS

Thanks

Did you try with IntelGraphicsFixup.kext + Lilu.kext?
AptioMemoryFix.efi instead of OsxAptioFix*.efi?
 
I added IntelGraphicsFixup.kext + Lilu.kext but can't see any graphics improvements :(
Switching to AptioMemoryFix.efi instead of OsxAptioFix*.efi stops the boot after few seconds with ''does printf work ??" message
 

Attachments

  • IMG_20180430_125530.jpg
    IMG_20180430_125530.jpg
    2.6 MB · Views: 85
I added IntelGraphicsFixup.kext + Lilu.kext but can't see any graphics improvements :(
Switching to AptioMemoryFix.efi instead of OsxAptioFix*.efi stops the boot after few seconds with ''does printf work ??" message

Did you remove any slide= kernel flag specification?
 
Correct, I was still having slide=0 in my boot args
But my graphics are not better :/ (only color change)
 

Attachments

  • IMG_20180430_144323.jpg
    IMG_20180430_144323.jpg
    4.9 MB · Views: 69
Right, he is my last EFI/Clover folder with AptioMemoryFix.efi

Thanks
 

Attachments

  • efi:clover.zip
    4.1 MB · Views: 98
Right, he is my last EFI/Clover folder with AptioMemoryFix.efi

Thanks

Try with OsxAptioFixDrv-64.efi instead of AptioMemoryFix.efi.
AptioMemoryFix.efi might also work if you spend some time calculating the correct slide value (refer to the AptioMemoryFix thread on insanelymac.com).

Note: Have you tried different monitors?

Why are you using MacBookPro SMBIOS with your desktop?
 
Hi @RehabMan

Sorry for the late reply I wasn't able to try last days...

I switched to OsxAptioFixDrv-64.efi, updated my SMBIOS to Macmini5,1 and try with a different monitor/TV but sadly with the same graphic result :(

Do you have any other clue ?

Thank you
 

Attachments

  • 20180511_EFI_CLOVER.zip
    4.1 MB · Views: 98
Hi @RehabMan

Sorry for the late reply I wasn't able to try last days...

I switched to OsxAptioFixDrv-64.efi, updated my SMBIOS to Macmini5,1 and try with a different monitor/TV but sadly with the same graphic result :(

Do you have any other clue ?

Thank you

You could patch the framebuffer connectors so they match your physical connectors, but you'll have to look at ioreg to determine which connectors are used. You can use remote desktop to look at ioreg when the graphics are loading.

Or you could try different ig-platform-id values.

Also, make sure you have fast boot disabled, legacy/CSM boot enabled.

Also, I don't know if you already installed FakeSMC to the system volume. Keep in mind that if you did, the kexts in EFI/Clover/kexts/Other *will not* be injected. If you want/need them, they would need to be installed along with FakeSMC.kext.
 
Status
Not open for further replies.
Back
Top