Lenovo G51-70; i3-5005U and HD5500

[RehabMan]

AppleIntelBDWGraphics.kext removed to achieve files.

Huh?
"Problem Reporting" attachments must represent the problem scenario.
As per FAQ, need image of verbose boot and EFI/Clover that produces it.

 

[RehabMan]

I found out z51-70 use diffrent LCDs. I think i have eDP. Maybe thats the problem?

Read post #14.

 

[fivos1996]

Huh?
"Problem Reporting" attachments must represent the problem scenario.
As per FAQ, need image of verbose boot and EFI/Clover that produces it.

Here they are. Note that "kernel extensions in backtrace" mentions random kexts like hfs.kext as in post #1.

 

[RehabMan]

Here they are. Note that "kernel extensions in backtrace" mentions random kexts like hfs.kext as in post #1.

Does it always crash? You attached an ioreg, which implies you can boot (so... confusion when you also provide a KP image which implies you cannot boot).

Your issue is likely a memory configuration problem.
The Clover bootlog shows only one RAM stick (I extracted Clover bootlog from ioreg).
Therefore you probably need to enter memory details in config.plist/SMBIOS/Memory. Or at least need to use config.plist/SMBIOS/Trust=true.

Also could be an ACPI patching issue. But you forgot to press F4, so impossible to compare ACPI/patched/DSDT.aml against ACPI/origin as ACPI/origin files are too old (from Jun 13).

 

[fivos1996]

Does it always crash? You attached an ioreg, which implies you can boot (so... confusion when you also provide a KP image which implies you cannot boot).

Your issue is likely a memory configuration problem.
The Clover bootlog shows only one RAM stick (I extracted Clover bootlog from ioreg).
Therefore you probably need to enter memory details in config.plist/SMBIOS/Memory. Or at least need to use config.plist/SMBIOS/Trust=true.

Also could be an ACPI patching issue. But you forgot to press F4, so impossible to compare ACPI/patched/DSDT.aml against ACPI/origin as ACPI/origin files are too old (from Jun 13).

As I said in another post, if I remove the kext that provides graphics acceleration (AppleIntelBDWGraphics.kext, NOT AppleIntelBDWGraphicsFramebuffer.kext), it boots with correct display detection and video outputs plus brightness. Native ACPI files from Clover F4 are in CLOVER/ACPI/origin. I have filled my memory details in SMBIOS. Also my DVMT is set to 96MB. So no patching required.

 

[RehabMan]

Native ACPI files from Clover F4 are in CLOVER/ACPI/origin.

They are too old. Read "Problem Reporting" again. Carefully.

I have filled my memory details in SMBIOS.

Your settings there are likely incorrect.
My understanding: With SlotCount=2, you must have two entries in Modules.
And you should verify the number of slots with physical inspection.
If you actually have two slots, it is probably worthwhile swapping the location of the single RAM stick.
Or installing two sticks for dual-channel support.

Also my DVMT is set to 96MB. So no patching required.

You should try DVMT-prealloc 64mb. And keep in mind each time you change DVMT-prealloc (or any other BIOS option), you *must* re-extract/re-patch ACPI.

Also, try OsxAptioFixDrv-64.efi instead of OsxAptioFix2Drv-64.efi.

Also, InjectKexts should be "Detect". You have InjectKexts=true, but no kexts in Clover/kexts, which is a bit of nonsense. InjectKexts=Detect and placing "essential" kexts in Clover/kexts/Other will enable you do boot the installer and recovery partitions, but will not inject when booting your main install (as FakeSMC.kext is installed there).

Other:
- IGPU PM not implemented
- USB not implemented correctly
- USB WiFi not recommended
- best to remove unneeded software such as VirtualBox

Finally, you didn't answer my question in post #24... "Does it always crash?"

 

[fivos1996]

Finally, you didn't answer my question in post #24... "Does it always crash?"

Yes. I haven't seen QE/CI working on this laptop since I bought it last September. Always the same problem. I re-extracted ACPI.

 

[RehabMan]

Yes. I haven't seen QE/CI working on this laptop since I bought it last September.

Actually, your ioreg shows CI working, but not QE (due to removal of the QE kext).

Always the same problem.

I would focus on memory issues.
Also, you might try FakePCIID_Intel_HD_Graphics.kext (or without).

I re-extracted ACPI.

SystemMemory addresses match, but DSDT.aml is not patched correctly.

 

[fivos1996]

I would focus on memory issues.
Also, you might try FakePCIID_Intel_HD_Graphics.kext (or without). SystemMemory addresses match, but DSDT.aml is not patched correctly.

I have already tried that kext. I tried booting with maxmem=4096 to limit the RAM to 4 gigs but nothing helped. Of course I played with the RAM slots to see if there's any difference. Again, nothing. Would you suggest replacing the memory with a Kingston 8GB SODIMM? Or even use it along with the existing one as dual channel 16GB? I popped in a 2GB DDR3 1066MHz stick but the laptop didn't post. As expected.

 

[RehabMan]

I have already tried that kext. I tried booting with maxmem=4096 to limit the RAM to 4 gigs but nothing helped. Of course I played with the RAM slots to see if there's any difference. Again, nothing. Would you suggest replacing the memory with a Kingston 8GB SODIMM? Or even use it along with the existing one as dual channel 16GB? I popped in a 2GB DDR3 1066MHz stick but the laptop didn't post. As expected.

It seems to me you forgot to rename HECI->IMEI.
I don't know if that is the cause of the issue, but it is something you should fix, along with GFX0->IGPU rename.
If you have two memory slots, install two matched/compatible RAM sticks.