Contribute
Register

Sierra on Lenovo T470 laptop

Status
Not open for further replies.
Joined
Sep 7, 2017
Messages
5
Motherboard
Lenovo T470
CPU
Intel Core i7-7600U
Graphics
Intel HD620
Hi All
I've been working on a Hackintosh build for a Lenovo T470.

Thanks to the excellent information and guides on these forums, I now have Sierra is up and running. The main initial challenges were with installation - NMVe drive and Intel HD620 gfx mainly.

What's working currently:
- Intel HD620 graphics working (via Clover's config.plist settings, FakePCIID_Intel_HD_Graphics.kext, IntelGraphicsFixup.kext)
- PS2 keyboard/trackpad (Synaptics) working with VoodooPS2Controller
- audio (working via VoodooHDA)
- WiFi (working via edimax/USB, and have ordered a Broadcom BCM94352Z)
- brightness slider (with AppleBacklightInjector.kext)

What's not working:
- battery indicator (this Laptop has 2 batteries)
- shutdown/restart issues
- function keys
- sleep/wake

For the last x days or so I've been trying to resolve my remaining issues by making a DSDT for this laptop. This has been a steep learning curve(!) and I'm now at such a point that I have got a bit stuck and don't know how to proceed further.

I have been following the excellent and detailed guide by Rehabman here: https://www.tonymacx86.com/threads/guide-patching-laptop-dsdt-ssdts.152573/

So far I have:
- Extracted and disassembled my native BIOS ACPI to .dsl files using iasl
- Applied common patches to DSDT file using MaciASL
- Fixed the field sizes in embedded controller device (as per RehabMan's guide - https://www.tonymacx86.com/threads/guide-how-to-patch-dsdt-for-working-battery-status.116102/)
- Tested that it compiles correctly
- Saved the file in MaciASL as a binary .aml file and placed in CLOVER/ACPI/patched

When I try and boot with this config, the machine pauses for about 2 minutes after displaying:
Code:
ACPI: Executed x blocks of module-level executable AML code
View media item 189379
It then continues and boots up. (NOTE - I should say that without the DSDT file, the laptop doesn't suffer this pause and boots very quickly).

Q. Does anyone have any ideas on why this pause occurs, and how I may go about resolving it?


Having booted up, I haven't yet been able to make any improvement to the issues above, and in fact some things have got worse! Is it now a case of identifying the methods used for the problem ACPI events (e.g. sleep/wake, startup/restart) and patching them up?
I would appreciate any pointers on how to proceed from here (and not afraid of learning more of the language syntax if this is required).

I know that there are several battery patches out there for laptops with 2 batteries, and I'm hoping to write a patch myself by studying these. With my DSDT loaded, the output from "sudo dmesg" currently returns the following ACPI errors which I'm guessing is because OS X doesn't know what to do with the second battery:

Code:
ACPI Error: ACPI Error: Method parse/execution failed Method parse/execution failed [\134_SB_.PCI0.LPCB.EC__.GBIX] (Node ffffff804022d2d0)[\134_SB_.PCI0.LPCB.EC__.GBIX] (Node ffffff804022d2d0), AE_BAD_PARAMETER, AE_BAD_PARAMETER (20140828/psparse-270)
(20140828/psparse-270)
ACPI Error: ACPI Error: Method parse/execution failed Method parse/execution failed [\134_SB_.PCI0.LPCB.EC__.BAT0._BIX] (Node ffffff804022ddd0)[\134_SB_.PCI0.LPCB.EC__.BAT0._BIX] (Node ffffff804022ddd0), AE_BAD_PARAMETER, AE_BAD_PARAMETER (20140828/psparse-270)
(20140828/psparse-270)
ACPI Exception: AE_BAD_PARAMETER, ACPI Exception: AE_BAD_PARAMETER, Returned by Handler for [EmbeddedControl]Returned by Handler for [EmbeddedControl] (20140828/evregion-170)
(20140828/evregion-170)
ACPI Error: ACPI Error: Method parse/execution failed Method parse/execution failed [\134_SB_.PCI0.LPCB.EC__.GBST] (Node ffffff804022d250)[\134_SB_.PCI0.LPCB.EC__.GBST] (Node ffffff804022d250), AE_BAD_PARAMETER, AE_BAD_PARAMETER (20140828/psparse-270)
(20140828/psparse-270)
ACPI Error: ACPI Error: Method parse/execution failed Method parse/execution failed [\134_SB_.PCI0.LPCB.EC__.BAT0._BST] (Node ffffff804022de10)[\134_SB_.PCI0.LPCB.EC__.BAT0._BST] (Node ffffff804022de10), AE_BAD_PARAMETER, AE_BAD_PARAMETER (20140828/psparse-270)
(20140828/psparse-270)
ACPI Exception: AE_BAD_PARAMETER, ACPI Exception: AE_BAD_PARAMETER, Returned by Handler for [EmbeddedControl]Returned by Handler for [EmbeddedControl] (20140828/evregion-170)
(20140828/evregion-170)
ACPI Error: ACPI Error: Method parse/execution failed Method parse/execution failed [\134_SB_.PCI0.LPCB.EC__.GBIX] (Node ffffff804022d2d0)[\134_SB_.PCI0.LPCB.EC__.GBIX] (Node ffffff804022d2d0), AE_BAD_PARAMETER, AE_BAD_PARAMETER (20140828/psparse-270)
(20140828/psparse-270)
ACPI Error: ACPI Error: Method parse/execution failed Method parse/execution failed [\134_SB_.PCI0.LPCB.EC__.BAT1._BIX] (Node ffffff804022e790)[\134_SB_.PCI0.LPCB.EC__.BAT1._BIX] (Node ffffff804022e790), AE_BAD_PARAMETER, AE_BAD_PARAMETER (20140828/psparse-270)
(20140828/psparse-270)
ACPI Exception: AE_BAD_PARAMETER, ACPI Exception: AE_BAD_PARAMETER, Returned by Handler for [EmbeddedControl]Returned by Handler for [EmbeddedControl] (20140828/evregion-170)
(20140828/evregion-170)
ACPI Error: ACPI Error: Method parse/execution failed Method parse/execution failed [\134_SB_.PCI0.LPCB.EC__.GBST] (Node ffffff804022d250)[\134_SB_.PCI0.LPCB.EC__.GBST] (Node ffffff804022d250), AE_BAD_PARAMETER, AE_BAD_PARAMETER (20140828/psparse-270)
(20140828/psparse-270)
ACPI Error: ACPI Error: Method parse/execution failed Method parse/execution failed [\134_SB_.PCI0.LPCB.EC__.BAT1._BST] (Node ffffff804022e850)[\134_SB_.PCI0.LPCB.EC__.BAT1._BST] (Node ffffff804022e850), AE_BAD_PARAMETER, AE_BAD_PARAMETER (20140828/psparse-270)


Thanks
 

Attachments

  • Original Disassemble .zip
    68.7 KB · Views: 144
  • DSDT - WIP3.dsl
    924.9 KB · Views: 412

RehabMan

Moderator
Joined
May 3, 2012
Messages
186,702
Motherboard
Intel DH67BL
CPU
i7-2600K
Graphics
HD 3000
Mac
  1. MacBook Air
Mobile Phone
  1. iOS
Hi All
I've been working on a Hackintosh build for a Lenovo T470.

Thanks to the excellent information and guides on these forums, I now have Sierra is up and running. The main initial challenges were with installation - NMVe drive and Intel HD620 gfx mainly.

What's working currently:
- Intel HD620 graphics working (via Clover's config.plist settings, FakePCIID_Intel_HD_Graphics.kext, IntelGraphicsFixup.kext)
- PS2 keyboard/trackpad (Synaptics) working with VoodooPS2Controller
- audio (working via VoodooHDA)
- WiFi (working via edimax/USB, and have ordered a Broadcom BCM94352Z)
- brightness slider (with AppleBacklightInjector.kext)

What's not working:
- battery indicator (this Laptop has 2 batteries)
- shutdown/restart issues
- function keys
- sleep/wake

For the last x days or so I've been trying to resolve my remaining issues by making a DSDT for this laptop. This has been a steep learning curve(!) and I'm now at such a point that I have got a bit stuck and don't know how to proceed further.

I have been following the excellent and detailed guide by Rehabman here: https://www.tonymacx86.com/threads/guide-patching-laptop-dsdt-ssdts.152573/

So far I have:
- Extracted and disassembled my native BIOS ACPI to .dsl files using iasl
- Applied common patches to DSDT file using MaciASL
- Fixed the field sizes in embedded controller device (as per RehabMan's guide - https://www.tonymacx86.com/threads/guide-how-to-patch-dsdt-for-working-battery-status.116102/)
- Tested that it compiles correctly
- Saved the file in MaciASL as a binary .aml file and placed in CLOVER/ACPI/patched

When I try and boot with this config, the machine pauses for about 2 minutes after displaying:
Code:
ACPI: Executed x blocks of module-level executable AML code
View media item 189379
It then continues and boots up. (NOTE - I should say that without the DSDT file, the laptop doesn't suffer this pause and boots very quickly).

Q. Does anyone have any ideas on why this pause occurs, and how I may go about resolving it?


Having booted up, I haven't yet been able to make any improvement to the issues above, and in fact some things have got worse! Is it now a case of identifying the methods used for the problem ACPI events (e.g. sleep/wake, startup/restart) and patching them up?
I would appreciate any pointers on how to proceed from here (and not afraid of learning more of the language syntax if this is required).

I know that there are several battery patches out there for laptops with 2 batteries, and I'm hoping to write a patch myself by studying these. With my DSDT loaded, the output from "sudo dmesg" currently returns the following ACPI errors which I'm guessing is because OS X doesn't know what to do with the second battery:

Code:
ACPI Error: ACPI Error: Method parse/execution failed Method parse/execution failed [\134_SB_.PCI0.LPCB.EC__.GBIX] (Node ffffff804022d2d0)[\134_SB_.PCI0.LPCB.EC__.GBIX] (Node ffffff804022d2d0), AE_BAD_PARAMETER, AE_BAD_PARAMETER (20140828/psparse-270)
(20140828/psparse-270)
ACPI Error: ACPI Error: Method parse/execution failed Method parse/execution failed [\134_SB_.PCI0.LPCB.EC__.BAT0._BIX] (Node ffffff804022ddd0)[\134_SB_.PCI0.LPCB.EC__.BAT0._BIX] (Node ffffff804022ddd0), AE_BAD_PARAMETER, AE_BAD_PARAMETER (20140828/psparse-270)
(20140828/psparse-270)
ACPI Exception: AE_BAD_PARAMETER, ACPI Exception: AE_BAD_PARAMETER, Returned by Handler for [EmbeddedControl]Returned by Handler for [EmbeddedControl] (20140828/evregion-170)
(20140828/evregion-170)
ACPI Error: ACPI Error: Method parse/execution failed Method parse/execution failed [\134_SB_.PCI0.LPCB.EC__.GBST] (Node ffffff804022d250)[\134_SB_.PCI0.LPCB.EC__.GBST] (Node ffffff804022d250), AE_BAD_PARAMETER, AE_BAD_PARAMETER (20140828/psparse-270)
(20140828/psparse-270)
ACPI Error: ACPI Error: Method parse/execution failed Method parse/execution failed [\134_SB_.PCI0.LPCB.EC__.BAT0._BST] (Node ffffff804022de10)[\134_SB_.PCI0.LPCB.EC__.BAT0._BST] (Node ffffff804022de10), AE_BAD_PARAMETER, AE_BAD_PARAMETER (20140828/psparse-270)
(20140828/psparse-270)
ACPI Exception: AE_BAD_PARAMETER, ACPI Exception: AE_BAD_PARAMETER, Returned by Handler for [EmbeddedControl]Returned by Handler for [EmbeddedControl] (20140828/evregion-170)
(20140828/evregion-170)
ACPI Error: ACPI Error: Method parse/execution failed Method parse/execution failed [\134_SB_.PCI0.LPCB.EC__.GBIX] (Node ffffff804022d2d0)[\134_SB_.PCI0.LPCB.EC__.GBIX] (Node ffffff804022d2d0), AE_BAD_PARAMETER, AE_BAD_PARAMETER (20140828/psparse-270)
(20140828/psparse-270)
ACPI Error: ACPI Error: Method parse/execution failed Method parse/execution failed [\134_SB_.PCI0.LPCB.EC__.BAT1._BIX] (Node ffffff804022e790)[\134_SB_.PCI0.LPCB.EC__.BAT1._BIX] (Node ffffff804022e790), AE_BAD_PARAMETER, AE_BAD_PARAMETER (20140828/psparse-270)
(20140828/psparse-270)
ACPI Exception: AE_BAD_PARAMETER, ACPI Exception: AE_BAD_PARAMETER, Returned by Handler for [EmbeddedControl]Returned by Handler for [EmbeddedControl] (20140828/evregion-170)
(20140828/evregion-170)
ACPI Error: ACPI Error: Method parse/execution failed Method parse/execution failed [\134_SB_.PCI0.LPCB.EC__.GBST] (Node ffffff804022d250)[\134_SB_.PCI0.LPCB.EC__.GBST] (Node ffffff804022d250), AE_BAD_PARAMETER, AE_BAD_PARAMETER (20140828/psparse-270)
(20140828/psparse-270)
ACPI Error: ACPI Error: Method parse/execution failed Method parse/execution failed [\134_SB_.PCI0.LPCB.EC__.BAT1._BST] (Node ffffff804022e850)[\134_SB_.PCI0.LPCB.EC__.BAT1._BST] (Node ffffff804022e850), AE_BAD_PARAMETER, AE_BAD_PARAMETER (20140828/psparse-270)


Thanks

There is probably an existing patch for battery already in my repo.
See guide:
https://www.tonymacx86.com/threads/guide-how-to-patch-dsdt-for-working-battery-status.116102/

It has some clues (early in the text) about how to find an existing patch that might match.
 
Joined
Sep 7, 2017
Messages
5
Motherboard
Lenovo T470
CPU
Intel Core i7-7600U
Graphics
Intel HD620
Thank you! I should have looked harder before.

I've now managed to get a working battery status on my T470.

After trying a number of patches I ended up getting success with the Lenovo X220 patch.

To do this, I did the following:
- Started with vanilla DSDT
- Applied "[syn] Rename _DSM methods to XDSM" (not sure why but this seemed to help)
- Applied "[bat] Lenovo X220"
- Applied "[sys] OS Check Fix (Windows 7)" (also not sure why, but it helped)
- Merged in "BATC" Device code to DSDT (taken from SSDT-BATC)
- Added patches to Config.plist to replace "Notify BAT0/1" with "BATC"
- Added ACPIBatteryManager.kext

Very pleased with this and have learnt lots about ACPI/DSDT editing! One amateur mistake that threw me for ages was that the scope in the T470 DSDT is "LPCB", whereas most of the patches and other code snippets out there are "LPC". I couldn't understand why they wouldn't work...

I'll now continue working on the other issues I have.

One last thing that is really bugging me, do you have any thoughts on why I get a very long delay when booting (2 minutes) after this msg in the boot process:
ACPI: Executed 28 blocks of module-level executable AML code
(Screenshot attached)

Thanks again
 

Attachments

  • IMG_5115.JPG
    IMG_5115.JPG
    139.7 KB · Views: 643

RehabMan

Moderator
Joined
May 3, 2012
Messages
186,702
Motherboard
Intel DH67BL
CPU
i7-2600K
Graphics
HD 3000
Mac
  1. MacBook Air
Mobile Phone
  1. iOS
Thank you! I should have looked harder before.

I've now managed to get a working battery status on my T470.

After trying a number of patches I ended up getting success with the Lenovo X220 patch.

To do this, I did the following:
- Started with vanilla DSDT
- Applied "[syn] Rename _DSM methods to XDSM" (not sure why but this seemed to help)
- Applied "[bat] Lenovo X220"
- Applied "[sys] OS Check Fix (Windows 7)" (also not sure why, but it helped)

Very typical.

- Merged in "BATC" Device code to DSDT (taken from SSDT-BATC)

You could just add SSDT-BATC.aml to ACPI/patched.

- Added patches to Config.plist to replace "Notify BAT0/1" with "BATC"

Since you have patched DSDT, you could also edit the Notify in DSDT directly.

One last thing that is really bugging me, do you have any thoughts on why I get a very long delay when booting (2 minutes) after this msg in the boot process:

No "Problem Reporting" files attached.
Read FAQ, "Problem Reporting" again. Carefully. Attach all requested files/output.
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/
 
Joined
Sep 7, 2017
Messages
5
Motherboard
Lenovo T470
CPU
Intel Core i7-7600U
Graphics
Intel HD620

Attachments

  • Problem Reporting.zip
    1.7 MB · Views: 146

RehabMan

Moderator
Joined
May 3, 2012
Messages
186,702
Motherboard
Intel DH67BL
CPU
i7-2600K
Graphics
HD 3000
Mac
  1. MacBook Air
Mobile Phone
  1. iOS
Thanks again. I've attached a zip containing all the requested files/output.

Your SystemMemory addresses are out of sync.
Look carefully:
Code:
SPEEDY-NUC-2:origin rehabman$ diff ../origin/ ../patched/ |grep SystemMemory
<     OperationRegion (GNVS, SystemMemory, 0x8FF1D000, 0x072C)
>     OperationRegion (GNVS, SystemMemory, 0x8FF4E000, 0x072C)
<         OperationRegion (PWMR, SystemMemory, \PWRM, 0x0800)
>         OperationRegion (PWMR, SystemMemory, PWRM, 0x0800)
<             OperationRegion (XHCP, SystemMemory, Add (\_SB.PCI0.GPCB (), 0x000A0000), 0x0100)
>             OperationRegion (XHCP, SystemMemory, Add (GPCB (), 0x000A0000), 0x0100)
<                 OperationRegion (MC11, SystemMemory, \XWMB, 0x9000)
>                 OperationRegion (MC11, SystemMemory, XWMB, 0x9000)
<                 OperationRegion (MC11, SystemMemory, \XWMB, 0x9000)
>                 OperationRegion (MC11, SystemMemory, XWMB, 0x9000)
<                 OperationRegion (RPAL, SystemMemory, Add (\_SB.PCI0.GPCB (), Add (Add (0x000B8000, 0x0100), Arg1)), 0x04)
>                 OperationRegion (RPAL, SystemMemory, Add (GPCB (), Add (0x000B8100, Arg1)), 0x04)
<                 OperationRegion (EPAC, SystemMemory, Add (\_SB.PCI0.GPCB (), Add (0x000B8000, 0x0308)), 0x08)
>                 OperationRegion (EPAC, SystemMemory, Add (GPCB (), 0x000B8308), 0x08)
<                 OperationRegion (NCRG, SystemMemory, Add (\_SB.PCI0.GPCB (), Add (0x000B8000, 0x0FC0)), 0x04)
>                 OperationRegion (NCRG, SystemMemory, Add (GPCB (), 0x000B8FC0), 0x04)
<                         OperationRegion (MCRC, SystemMemory, Add (\_SB.PCI0.GPCB (), Add (0x000B8000, 0x033C)), 0x04)
>                         OperationRegion (MCRC, SystemMemory, Add (GPCB (), 0x000B833C), 0x04)
<                         OperationRegion (MCRC, SystemMemory, Add (\_SB.PCI0.GPCB (), Add (0x000B8000, 0x033C)), 0x04)
>                         OperationRegion (MCRC, SystemMemory, Add (GPCB (), 0x000B833C), 0x04)
<                         OperationRegion (MCRC, SystemMemory, Add (\_SB.PCI0.GPCB (), Add (0x000B8000, 0x033C)), 0x04)
>                         OperationRegion (MCRC, SystemMemory, Add (GPCB (), 0x000B833C), 0x04)
<                         OperationRegion (MCRC, SystemMemory, Add (\_SB.PCI0.GPCB (), Add (0x000B8000, 0x033C)), 0x04)
>                         OperationRegion (MCRC, SystemMemory, Add (GPCB (), 0x000B833C), 0x04)
<                         OperationRegion (MCRC, SystemMemory, Add (\_SB.PCI0.GPCB (), Add (0x000B8000, 0x033C)), 0x04)
>                         OperationRegion (MCRC, SystemMemory, Add (GPCB (), 0x000B833C), 0x04)
<                         OperationRegion (MCRC, SystemMemory, Add (\_SB.PCI0.GPCB (), Add (0x000B8000, 0x033C)), 0x04)
>                         OperationRegion (MCRC, SystemMemory, Add (GPCB (), 0x000B833C), 0x04)
<             OperationRegion (MEM0, SystemMemory, Local7, 0x01)
>             OperationRegion (MEM0, SystemMemory, Local7, One)
<             OperationRegion (MEM0, SystemMemory, Local7, 0x01)
>             OperationRegion (MEM0, SystemMemory, Local7, One)
<             OperationRegion (PCI0, SystemMemory, Local7, 0x01)
>             OperationRegion (PCI0, SystemMemory, Local7, One)
<             OperationRegion (PCI0, SystemMemory, Local7, 0x01)
>             OperationRegion (PCI0, SystemMemory, Local7, One)
<     OperationRegion (MNVS, SystemMemory, 0x8FF2F018, 0x1000)
>     OperationRegion (MNVS, SystemMemory, 0x8FF60018, 0x1000)
 
Joined
Sep 7, 2017
Messages
5
Motherboard
Lenovo T470
CPU
Intel Core i7-7600U
Graphics
Intel HD620
Your SystemMemory addresses are out of sync.
Look carefully:
Code:
SPEEDY-NUC-2:origin rehabman$ diff ../origin/ ../patched/ |grep SystemMemory
<     OperationRegion (GNVS, SystemMemory, 0x8FF1D000, 0x072C)
>     OperationRegion (GNVS, SystemMemory, 0x8FF4E000, 0x072C)
<         OperationRegion (PWMR, SystemMemory, \PWRM, 0x0800)
>         OperationRegion (PWMR, SystemMemory, PWRM, 0x0800)
<             OperationRegion (XHCP, SystemMemory, Add (\_SB.PCI0.GPCB (), 0x000A0000), 0x0100)
>             OperationRegion (XHCP, SystemMemory, Add (GPCB (), 0x000A0000), 0x0100)
<                 OperationRegion (MC11, SystemMemory, \XWMB, 0x9000)
>                 OperationRegion (MC11, SystemMemory, XWMB, 0x9000)
<                 OperationRegion (MC11, SystemMemory, \XWMB, 0x9000)
>                 OperationRegion (MC11, SystemMemory, XWMB, 0x9000)
<                 OperationRegion (RPAL, SystemMemory, Add (\_SB.PCI0.GPCB (), Add (Add (0x000B8000, 0x0100), Arg1)), 0x04)
>                 OperationRegion (RPAL, SystemMemory, Add (GPCB (), Add (0x000B8100, Arg1)), 0x04)
<                 OperationRegion (EPAC, SystemMemory, Add (\_SB.PCI0.GPCB (), Add (0x000B8000, 0x0308)), 0x08)
>                 OperationRegion (EPAC, SystemMemory, Add (GPCB (), 0x000B8308), 0x08)
<                 OperationRegion (NCRG, SystemMemory, Add (\_SB.PCI0.GPCB (), Add (0x000B8000, 0x0FC0)), 0x04)
>                 OperationRegion (NCRG, SystemMemory, Add (GPCB (), 0x000B8FC0), 0x04)
<                         OperationRegion (MCRC, SystemMemory, Add (\_SB.PCI0.GPCB (), Add (0x000B8000, 0x033C)), 0x04)
>                         OperationRegion (MCRC, SystemMemory, Add (GPCB (), 0x000B833C), 0x04)
<                         OperationRegion (MCRC, SystemMemory, Add (\_SB.PCI0.GPCB (), Add (0x000B8000, 0x033C)), 0x04)
>                         OperationRegion (MCRC, SystemMemory, Add (GPCB (), 0x000B833C), 0x04)
<                         OperationRegion (MCRC, SystemMemory, Add (\_SB.PCI0.GPCB (), Add (0x000B8000, 0x033C)), 0x04)
>                         OperationRegion (MCRC, SystemMemory, Add (GPCB (), 0x000B833C), 0x04)
<                         OperationRegion (MCRC, SystemMemory, Add (\_SB.PCI0.GPCB (), Add (0x000B8000, 0x033C)), 0x04)
>                         OperationRegion (MCRC, SystemMemory, Add (GPCB (), 0x000B833C), 0x04)
<                         OperationRegion (MCRC, SystemMemory, Add (\_SB.PCI0.GPCB (), Add (0x000B8000, 0x033C)), 0x04)
>                         OperationRegion (MCRC, SystemMemory, Add (GPCB (), 0x000B833C), 0x04)
<                         OperationRegion (MCRC, SystemMemory, Add (\_SB.PCI0.GPCB (), Add (0x000B8000, 0x033C)), 0x04)
>                         OperationRegion (MCRC, SystemMemory, Add (GPCB (), 0x000B833C), 0x04)
<             OperationRegion (MEM0, SystemMemory, Local7, 0x01)
>             OperationRegion (MEM0, SystemMemory, Local7, One)
<             OperationRegion (MEM0, SystemMemory, Local7, 0x01)
>             OperationRegion (MEM0, SystemMemory, Local7, One)
<             OperationRegion (PCI0, SystemMemory, Local7, 0x01)
>             OperationRegion (PCI0, SystemMemory, Local7, One)
<             OperationRegion (PCI0, SystemMemory, Local7, 0x01)
>             OperationRegion (PCI0, SystemMemory, Local7, One)
<     OperationRegion (MNVS, SystemMemory, 0x8FF2F018, 0x1000)
>     OperationRegion (MNVS, SystemMemory, 0x8FF60018, 0x1000)

Thanks for spotting that, and I got the hint!

Enabling Clover's FixRegions_10000000 option has fixed the problem :). It now boots up instantly.
In addition, sleep/wake, startup and shutdown are also now working.

Thanks for your help RehabMan.
 

RehabMan

Moderator
Joined
May 3, 2012
Messages
186,702
Motherboard
Intel DH67BL
CPU
i7-2600K
Graphics
HD 3000
Mac
  1. MacBook Air
Mobile Phone
  1. iOS
Thanks for spotting that, and I got the hint!

Enabling Clover's FixRegions_10000000 option has fixed the problem :). It now boots up instantly.
In addition, sleep/wake, startup and shutdown are also now working.

Thanks for your help RehabMan.

FixRegions is known to have serious bugs.
Do not use it.
Re-extract/re-patch ACPI files instead.
 
Joined
Sep 7, 2017
Messages
5
Motherboard
Lenovo T470
CPU
Intel Core i7-7600U
Graphics
Intel HD620
Hi - just wanted to update you on my Hackintosh on Lenovo T470.
As suggested, I turned off FixRegions in Clover - having read up on this it looks like there are issues, so definitely not a good idea to use it.

I then (cold) booted up 10 times and extracted ACPI by pressing F4 in Clover, then grep'ed the output files for SystemMemory and put the results into a spreadsheet to compare and check I'd got the right addresses. Once that was done, I repatched DSDT and it booted up fine.

Having got this far, I decided to wipe the entire HD (which was a dual boot with Windows 10) and just put Sierra on exclusively. Having done the hard work to get a bootable USB config, this was then easy and the reinstall went smoothly.

However, after installing a few apps and using the system for a few hours it became unstable, and I started getting the following drive errors in the log:

Example of errors:
Code:
/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression_kexts/AppleFSCompression-88.50.3/Common/ChunkCompression.cpp:188:
/System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib:
VNOP_GETXATTR: errno 5
hfs_swap_BTNode: invalid forward link (0xeafcc337 >= 0x00005480)
hfs: node=10586 fileID=4 volume=Mac HD device=/dev/disk1
hfs_mark_inconsistent: Runtime corruption detected on Mac HD, fsck will
be forced on next mount.
/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression_kexts/AppleFSCompression-88.50.3/Common/ChunkCompression.cpp:188:
/System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib:
VNOP_GETXATTR: errno 5
hfs_swap_BTNode: invalid forward link (0xeafcc337 >= 0x00005480)
hfs: node=10586 fileID=4 volume=Mac HD device=/dev/disk1
hfs_mark_inconsistent: Runtime corruption detected on Mac HD, fsck will
be forced on next mount.

After this the drive wouldn't boot due to corruption.

I believe this will be something to do with my NCMe drive (either that or my USB WIFI perhaps?).

Unfortunately I was pressed for time and needed a working system, so have had to put Win 10 for this wk :( so I can get some work done and pay the bills... But I will try again soon. At least I have a good config on USB now so can reinstall OSX pretty quickly.

Thanks
 

RehabMan

Moderator
Joined
May 3, 2012
Messages
186,702
Motherboard
Intel DH67BL
CPU
i7-2600K
Graphics
HD 3000
Mac
  1. MacBook Air
Mobile Phone
  1. iOS
Hi - just wanted to update you on my Hackintosh on Lenovo T470.
As suggested, I turned off FixRegions in Clover - having read up on this it looks like there are issues, so definitely not a good idea to use it.

I then (cold) booted up 10 times and extracted ACPI by pressing F4 in Clover, then grep'ed the output files for SystemMemory and put the results into a spreadsheet to compare and check I'd got the right addresses. Once that was done, I repatched DSDT and it booted up fine.

Having got this far, I decided to wipe the entire HD (which was a dual boot with Windows 10) and just put Sierra on exclusively. Having done the hard work to get a bootable USB config, this was then easy and the reinstall went smoothly.

However, after installing a few apps and using the system for a few hours it became unstable, and I started getting the following drive errors in the log:

Example of errors:
Code:
/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression_kexts/AppleFSCompression-88.50.3/Common/ChunkCompression.cpp:188:
/System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib:
VNOP_GETXATTR: errno 5
hfs_swap_BTNode: invalid forward link (0xeafcc337 >= 0x00005480)
hfs: node=10586 fileID=4 volume=Mac HD device=/dev/disk1
hfs_mark_inconsistent: Runtime corruption detected on Mac HD, fsck will
be forced on next mount.
/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression_kexts/AppleFSCompression-88.50.3/Common/ChunkCompression.cpp:188:
/System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib:
VNOP_GETXATTR: errno 5
hfs_swap_BTNode: invalid forward link (0xeafcc337 >= 0x00005480)
hfs: node=10586 fileID=4 volume=Mac HD device=/dev/disk1
hfs_mark_inconsistent: Runtime corruption detected on Mac HD, fsck will
be forced on next mount.

After this the drive wouldn't boot due to corruption.

I believe this will be something to do with my NCMe drive (either that or my USB WIFI perhaps?).

Unfortunately I was pressed for time and needed a working system, so have had to put Win 10 for this wk :( so I can get some work done and pay the bills... But I will try again soon. At least I have a good config on USB now so can reinstall OSX pretty quickly.

Thanks

You say "NCMe". Assume you mean NVMe.
You didn't mention how you implemented NVMe, nor what kind of NVMe SSD you have.
See guide for best practice:
https://www.tonymacx86.com/threads/...h-ionvmefamily-using-class-code-spoof.210316/
 
Status
Not open for further replies.
Top