Contribute
Register

Gahhh! Stuck at ' No native mechanism to verify * ' :(

Status
Not open for further replies.
Joined
Aug 3, 2018
Messages
18
Motherboard
Lenovo Ideapad 110 17IKB 80VK [Clover]
CPU
i5-7200U
Graphics
HD 620 - 1600X900
Mac
  1. iMac
  2. MacBook Pro
Mobile Phone
  1. Android
Hey guys,

So I finally decided to make a hackeytosh for school, mostly cuz I spilled a half-glass of Finlandia and Cranberry in my real MBP, quickly doing some surgery to it and ..well, in the end it was ok, except the keyboard was kack, had to use a bluetooth one instead.

anyhooo, the screen started acting bananas about a year later, and NOW its gon' bye bye - yup - finally the Truly-Canadian Igloo fell on it, and i'm not paying $950 bukaroos to fix it! [ actually i was wrestling in the snow and it slid out of my book bag, aaaaand sat there for a while, half in dirty water, BUT I did mAD snowjob my friend who was askin' fer it ] ..Apple took a bite out of me in the end.

We've been lurking in the shadows for months on and off, my little brother too, reading and taking notes, actually personally i was going to do this last year, but, yea had to make some money this summer, so I grabbed 2 cheaper laptops, and i'm gonna do them both, then give the other one to my best friend for her birthday. /back story

Right, so I've read all of Mr. Rehabman's guides; wOAO, this is easily the most complicated computer'majig thing i've done yet! but i grew up in a house full of techies, and i'm actually quite the HackNinja. Plus i've read about 50 threads on fixes for various things pertaining to this 7200U and 620.

I'm well into doing this, and i've made about 20 researched attempts, searching up fixes, and getting a little further each time, guhh, just getting the installer to show up was about 2 weeks of reading, then getting it to not freeze when i push Go, blahh, anyway, i cant even remember all the combinations of drivers and kexts and oh..hang on my twisty bread is ready .....

so i've gone back to basics, and it's kinda burning me out, i'm thinking if there was a way i could just jump right into patching my DsDT and SSDT, the system would just behave, likewise, i'm feeling whats got me stuck just now / with the super basic combo in the clover below, iiiiiis probably something kinda simple, but blahhh, i was hoping i could do it all my self, then make a guide for others.....i've recorded everything along the way so i could make one ..... anyway please help :/

There is a pic of the log from the installer attached - ummm, dont mind my friend lela's art, she's a strange one ...i knew she was up to something...

the installer hangs with an arbitrary 2 mins left - osinstallersetupd [577] - *

I found the furthest i could get with the installer was with the SATA-200-series-unsupported.kext - as you'll see in my profile i have the 9Cwhatever 'unsupported' controller, but i'm a little confused about the right one to use...

- Lenovo ideapad 110 17IKB 80vk - 1TB - win10 oem
intel i5 7200U kaby lake - HD 620 graphics ~ Ven ID 0x8086 (0x17AA) MODEL ID 0x5916 (0x39E8) Rev. 0x2
8gb ddr4, MB: Nano 7c1 - (0x00000257 - 0x00F46EA8)
1600X900 - realtek network, realtek audio, Elan on PS2, keyboard on PS2 Crispy fresh Clover
High sierra from app store using macbookpro4,1

I hope ur eyes aren't swollen from reading all that ....

Sketch001.jpg
 

Attachments

  • CLOVER.zip
    1.8 MB · Views: 165
Hey guys,

So I finally decided to make a hackeytosh for school, mostly cuz I spilled a half-glass of Finlandia and Cranberry in my real MBP, quickly doing some surgery to it and ..well, in the end it was ok, except the keyboard was kack, had to use a bluetooth one instead.

anyhooo, the screen started acting bananas about a year later, and NOW its gon' bye bye - yup - finally the Truly-Canadian Igloo fell on it, and i'm not paying $950 bukaroos to fix it! [ actually i was wrestling in the snow and it slid out of my book bag, aaaaand sat there for a while, half in dirty water, BUT I did mAD snowjob my friend who was askin' fer it ] ..Apple took a bite out of me in the end.

We've been lurking in the shadows for months on and off, my little brother too, reading and taking notes, actually personally i was going to do this last year, but, yea had to make some money this summer, so I grabbed 2 cheaper laptops, and i'm gonna do them both, then give the other one to my best friend for her birthday. /back story

Right, so I've read all of Mr. Rehabman's guides; wOAO, this is easily the most complicated computer'majig thing i've done yet! but i grew up in a house full of techies, and i'm actually quite the HackNinja. Plus i've read about 50 threads on fixes for various things pertaining to this 7200U and 620.

I'm well into doing this, and i've made about 20 researched attempts, searching up fixes, and getting a little further each time, guhh, just getting the installer to show up was about 2 weeks of reading, then getting it to not freeze when i push Go, blahh, anyway, i cant even remember all the combinations of drivers and kexts and oh..hang on my twisty bread is ready .....

so i've gone back to basics, and it's kinda burning me out, i'm thinking if there was a way i could just jump right into patching my DsDT and SSDT, the system would just behave, likewise, i'm feeling whats got me stuck just now / with the super basic combo in the clover below, iiiiiis probably something kinda simple, but blahhh, i was hoping i could do it all my self, then make a guide for others.....i've recorded everything along the way so i could make one ..... anyway please help :/

There is a pic of the log from the installer attached - ummm, dont mind my friend lela's art, she's a strange one ...i knew she was up to something...

the installer hangs with an arbitrary 2 mins left - osinstallersetupd [577] - *

I found the furthest i could get with the installer was with the SATA-200-series-unsupported.kext - as you'll see in my profile i have the 9Cwhatever 'unsupported' controller, but i'm a little confused about the right one to use...

- Lenovo ideapad 110 17IKB 80vk - 1TB - win10 oem
intel i5 7200U kaby lake - HD 620 graphics ~ Ven ID 0x8086 (0x17AA) MODEL ID 0x5916 (0x39E8) Rev. 0x2
8gb ddr4, MB: Nano 7c1 - (0x00000257 - 0x00F46EA8)
1600X900 - realtek network, realtek audio, Elan on PS2, keyboard on PS2 Crispy fresh Clover
High sierra from app store using macbookpro4,1

I hope ur eyes aren't swollen from reading all that ....

View attachment 347854

See guide:
https://www.tonymacx86.com/threads/guide-booting-the-os-x-installer-on-laptops-with-clover.148093/
 
Pardon me.
Let me try this again.

Greetings.

This will be my thread to troubleshoot/configure what is necessary for a complete install.

Correct procedure for the installation/post installation of High Sierra.

Lenovo Ideapad 110-171KB-80VK - Nano 7C1 ( With Clover)

CPU: Intel Core i5 7200U
Graphics: Intel HD 620 Graphics
Resolution: 1600x900

Using: https://www.tonymacx86.com/threads/guide-booting-the-os-x-installer-on-laptops-with-clover.148093/
https://www.tonymacx86.com/threads/laptop-compatibility.106791/
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/

Other resources:
https://www.tonymacx86.com/forums/high-sierra-laptop-support.192/


Many of the questions here are because sufficient clarification is not present in the guide(s) OR
more likely my inferior understanding of the specifics involved in OS re-seating.
Careful time was put into the questions asked, please consider answering in a clear way, thank you.

Lets begin:

Configuring the general elements needed



SATA Controller - [PCI\VEN_8086&DEV_9D03&SUBSYS_382F17AA&REV_21]
*NOTES: - "Some **Skylake SATA controller** device-ids are not in the AppleAHCIPort.kext
Info.plist **(yet)** If you have an unsupported SATA controller
(8086:a103, ***8086:9d03***), use SATA-100-series-unsupported.kext."

## The corresponding device ID matches. I will include this.

USB 3.0 XHC - [PCI\VEN_8086&DEV_9D2F&REV_21]
*NOTES: - "XHC, 100-series chipset (**8086:9d2f**): 10-USB2 ports HS01-HS10, 6-USB3
ports SS01-SS06, plus USR1/USR2)"

## This is made perfectly obvious. I will include it.

Elan PS2 Track Pad - [ACPI\VEN_ETD&DEV_0675 - system device -PCI\VEN_8086&DEV_9D23&SUBSYS_383117AA&REV_21]
*NOTES: - Not the i2c type.

## As I understand there is only one closed-source provider to obtain this Kext elsewhere.

*** - Q: This has no relation to the 'Synaptics' kext, or any additional requirements to make it work?

Realtek Network - [PCI\VEN_10EC&DEV_8136&SUBSYS_383317AA&REV_07]
*NOTES: - in the 'example image' - 'typical EFI/Clover/kexts' what is displayed shows both:
'RealtekRTL8100.kext' *AND*
'IntelMausiEthernet.kext' --> *** Q: Is this erroneous?
(As I understand i do not have an intel nic, it is realtek)

## I will assume 8136 is of the 8100 series. I will include this.

Config.plist
Res. 1600x900
*NOTES: - [Main board indicates 'Nano 7c1' is '7' series] - Is there another way this should be checked?
- [Included with i5 7200U is Intel HD 620 Graphics] - I don't believe it is "mixed".
--> "download the entire ZIP to get all files" - Done.
- Therefore I choose the 'config_HD615_620_630_640_650_spoof.plist'.

!! ## EDIT: Wrong, Using the 'spoof' config is for installing prior to 10.12.6 Sierra.
When i downloaded 'the entire zip' a couple weeks ago to obtain the
config.plist - the only .plist in the zip labeled with '620' WAS the
'spoof' one - so obviously using it was incorrect. Re-downloading the ZIP
just now again reveals the correct ' config_HD615_620_630_640_650.plist '
## This file was not in the zip, or something
happened when downloading from the repo the first time.

- Rename to 'config.plist' and overwrite -config.plist- in the clover folder at "/EFI/Clover/config.plist."
--> in the EFI - on the hidden USB partition. -Done.

*NOTES: - "In any case you may need to change the ig-platform-id that is used at * /Graphics/ig-platform-id."
* WITHIN THE '.plist' FILE USING A .plist EDITOR.

## " Common ig-platform-ids: " Section examples do not include information for HD 620 Graphics.
## A link to information on achieving (hopefully) full functionality would be excellent.

*NOTES: - "In case you cannot boot with a valid ig-platform-id -- use an invalid ig-platform-id (0x12345678)"

## It is my understanding this should be avoided, if the proper ig-platform-id CAN be used.

*** - Q: Are there any other additional requirements to include along with
the applied 'config_HD615_620_630_640_650.plist' in the clover folder?
*** - Q: Is there any additional changes which must be made to the config.plist outside
of the '/Graphics/ig-platform-id.' section - within the .plist?
(using an editor or otherwise)

DVMT-prealloc
For Kaby Lake - ---->
*NOTES: - "The graphics kexts provided by Apple require DVMT-prealloc to be set 64mb or larger.
Many laptops set it by default to 32mb, which is not large enough and will cause a KP (kernel panic)."
[your main system RAM is shared with the video chip, and intitially it doesn't ask for enough]
- "all the plists linked by this guide have a patch for 32MB DVMT-prealloc, enabled by default."

Helpful hint: ## kaby lake - minStolenSize patch not necessary.
- FakePCIID_Intel_HD_Graphics.kext has NO facilities for KabyLake graphics.

- "There is no need to use the minStolenSize patch or change DVMT-prealloc...
Instead, you can patch the framebuffer to match your BIOS configuration
for DVMT-prealloc" - Okay....

- or you can use 'IntelGraphicsDVMTFixup.kext', which implements the
32MB DVMT-prealloc patch. - Alright...

## Noted the distinction now between potentially using a 'fake ID' and 'ig-platform-id'
(0x12345678) as they are in separate sections.

*** - Q: What is the correct method to assess what my Bios sets the DVMT-preallocation to?
*** - Q: Is there a list to know what applies to my machine? or a matrix to understand the
corresponding requirements?
*** - Q: Is this recommended for initial installation? -->
[ "guide-booting-the-os-x-installer-on-laptops" ]
or should this indeed be done before booting the installer? to avoid doing it later?

*** - Q: Is the patch which is enabled by default in the provided .plist adiquate? or should
I also include IntelGraphicsDVMTFixup.kext? -or- proceed to 'patch the fame buffer'?

## From --> https://github.com/BarbaraPalvin/IntelGraphicsDVMTFixup <--
"IntelGraphicsDVMTFixup is now part of WhateverGreen, please use it instead."
Please update the Guide to reflect this.

## Obviously whatever produces the best final result should be done,
but forgive my confusion about what Should/Can be done.
Best procedure is to install with '0x12345678' then correct after?

Create Installer - Used 'Create install media' method - with copy of high sierra from app store using
a macbook pro running El Capitan.

BIOS Settings - BIOS settings:
- "VT-d" - off
- "secure boot" - off
- "legacy boot" - off
- "fast boot" - off
- "boot from USB" - on



---------------------------------------------------------- End of Preparation Section.


Useful information collected from this thread:
https://www.tonymacx86.com/threads/laptop-compatibility.106791/
Use the link to read more in depth information.


Note on Kaby Lake - HD 620 Graphics
*NOTES: - Early testing of Kaby Lake CPUs and Intel HD620 graphics reveals good
compatibility with the kexts for Skylake. Kaby Lake CPU requires using
the FakeCPUID (Clover option) with the appropriate CPUID for similar
Skylake CPU. And graphics can be made to work with FakeID/IntelGFX and
FakePCIID kexts. Read the laptop FAQ.
http://www.tonymacx86.com/yosemite-...faq-read-first-laptop-frequent-questions.html

*** - Q: What is the appropriate CPUID for similar Skylake CPU?

*** - Q: EDIT: Is this a correct procedure?

[i5 7200U and HD 620 Graphics]

IntelGFX = 0x59168086, ig-platform-id 0x59160000

com.apple.driver.AppleIntelKBLGraphicsFramebuffer

Find:
01030303 00002002 00000000
Replace:
01030303 00003001 00009000

## The needed information about many parts can be much more organized.
Many general scenarios can be absolved by adding a link to a thread
which contains common configurations. This will reduce the necessity
of both randomly searching threads, and the bother of repetitive
questions being asked about the same hardware over and over.


Working Audio - Finding or creating a patched AppleHDA
*NOTES: - Getting audio to work generally depends on finding or creating a patched
AppleHDA (for best results and stability, don't use VoodooHDA except as
a last resort). Although patching AppleHDA for any audio codec is possible.

Battery status - AppleSmartBatteryManager.kext
*NOTES: - Possible to make work by using an ACPI compliant AppleSmartBatteryManager.kext.
I generally recommend my own kext: (RehabMan)
https://github.com/RehabMan/OS-X-ACPI-Battery-Driver.
Most DSDTs will need patching to work correctly.
More on this later..

DSDT & SSDT - [This is its own whole section]
*NOTES: - DSDT: Most laptops will require ACPI edits to get various laptop features
working. You should be prepared to learn about DSDT patches, MaciASL, how
to install your ACPI files such that the bootloader (eg. Clover) can load them.
More on this later..

## I have become familliar with the procedure to complete this, but first I
Must get it to install.

Dual Booting with
Windows already
preinstalled - ["OS X doesn't like the MSR partition, so you have to remove it"]
*NOTES: - Info on this thread:
http://www.tonymacx86.com/multi-booting/133940-mavericks-windows-8-same-drive-without-erasing.html

- "Installing with MSR is possible, but you must create a placeholder partition
in diskmgmt.msc then reformat it in Disk Utility (Disk Utility cannot create
partitions on a disk that contains an MSR partition)."

- "Windows does not require it. You are unlikely to use the features in Windows
that require it (storage spaces, or perhaps certain software raid configurations)."

- If your EFI partition is not big enough ( 200mb+ ) you will need to make it larger.
there are a few ways to accomplish it, read the thread above.

Helpful Hint: - Recommend Rehabmans suggestion - "backup your EFI partition, remove both EFI and
MSR, create new (larger) EFI (in the space formerly occupied by MSR+EFI),
and restore the original EFI contents."
- Beware of apparent comedy: If you 'clean' a disk, the entire disk is wiped out. (all partitions).


- If your EFI is already large enough (most are now) then continue.
- Make a full backup-image of your system (all partitions), I use the integrated
' sdclt ' command in windows (undocumented), search how to do this -
works perfect, and its free, you'll need a drive big enough for everything.

Made a quick guide....

Removing MSR - [I must say be CAREFUL what you do here, you can whack everything, if you
are unsure what you are doing, read the above thread first]
I triple checked everything on ******, and 2 other sites first!

First open an elevated command prompt.
- Go to search and type 'cmd' - right click on it and select run as admin.
- Enter 'diskpart'
- Enter 'list disk'
- Enter 'select disk 0'
- Enter 'list partition'
- On this machine it looks ike this:
----------------------------------------------------------
Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 1 System 260 MB 1024 KB
Partition 2 Reserved 16 MB 261 MB
Partition 3 Primary 334 GB 277 MB
Partition 4 Unknown 307 GB 334 GB
Partition 5 Unknown 7629 MB 642 GB
Partition 6 Unknown 18 GB 649 GB
Partition 7 Unknown 74 GB 668 GB
Partition 8 Primary 25 GB 892 GB
Partition 9 Recovery 1000 MB 917 GB
Partition 10 Recovery 12 GB 918 GB
Partition 11 OEM 1000 MB 930 GB
----------------------------------------------------------
- First one is EFI - more than enough.
- The first primary is Win10
- The first Unknown you see is the space where MacOS is going HFS+
- The other 3 Unknown ones are Linux mint 19 - Scratch, /Root, /Home.
- [Here is 150gbs of unallocated space to make a 'share' partition between them]
- The 25gb primary is the 'D' drive made by lenovo which comes with 1gb of drivers.
- The 12gb near the end is the win10 oem installer, and the last one is
the '1 key recovery' from lenovo.


- now the one we're interested in is the '16mb' 'Reserved' 2nd partition.
yours may be a different size, apparently up to 128mb or more.
- Also be careful as some drives are set up differently, with a recovery
partition first, or whatever, MAKE SURE YOU KNOW WHAT YOU ARE DOING!

....In the case of this Lenovo ideapad.....
- Enter 'select partition 2' - MAKE SURE YOU'RE ON THE RIGHT PARTITION!
- Enter 'detail partition'
- You should get this:
-----------------------------------------------------------
Partition 2
Type : e3c9e316-0b5c-4db8-817d-f92df00215ae
Hidden : Yes
Required: No
Attrib : 0000000000000000
Offset in Bytes: 273678336

There is no volume associated with this partition.
-----------------------------------------------------------
- This is my MSR partition... useless, meek, annoying..
(btw, doing some poking around, i'm getting the feeling its an N$A/gov
reserved place to plant spy code, and hackers are mOre than aware of it, and
exploit it for hiding malware .... aside from it's 'official' use. 8| )

- Enter 'delete partition override' and tighten your butt!
(You have to use the override part otherwise it will say you cant do it)

BAM-O
- Enter 'list partition'
- You will now see the (in my case) 2nd partition is gone, the list goes
from partition 1 to 3 and forward.

- Opening disk management now shows 16mb unallocated space between the first
partition EFI - and the beginning of the 300gb windows10 install.
- Success! NOW Iee THE HACKER.
- With your right hand, reach over to the back of your left shoulder and
give yourself a pat, you deserve it.
- Enter 'exit' ...'exit'.
- Contribute 5 bucks to this site.

--------------------------------------------------------------
To be continued ...





Can you please give me a hint at what i'm doing wrong?
at least what you think it may be, so i can find answers myself.

I have made changes to clover and attached it.
Please excuse if there is a superfluous driver or something,
I may have added something while making attempts out of frustration.

I deleted the MSR, i legit missed that part, didn't know anything about it before arriving here.
Added the proper plist file.
I'm still getting the same response from the installer log
which leads me to believe it has something to do with either:

-Something not being recognized, like sata, or the USB - then it can't verify the contents.
-perhaps i need to do something more to this MSR thing than just delete the partition to unused space
-this is a 1tb spinner, so the APFS thing shouldn't be even in error, humm

I'll admit i'm mediocre at this particular stuff, but a good hint would be nice.
Thank you.
 

Attachments

  • CLOVER.zip
    1.6 MB · Views: 193
*** - Q: This has no relation to the 'Synaptics' kext, or any additional requirements to make it work?

No idea what you mean by "this" or "the 'Synaptics' kext", or 'it"...

Realtek Network - [PCI\VEN_10EC&DEV_8136&SUBSYS_383317AA&REV_07]
*NOTES: - in the 'example image' - 'typical EFI/Clover/kexts' what is displayed shows both:
'RealtekRTL8100.kext' *AND*
'IntelMausiEthernet.kext' --> *** Q: Is this erroneous?
(As I understand i do not have an intel nic, it is realtek)

## I will assume 8136 is of the 8100 series. I will include this.

It does not matter if you include kexts which don't apply to your hardware (they simply will not load/will not start).

Config.plist
Res. 1600x900
*NOTES: - [Main board indicates 'Nano 7c1' is '7' series] - Is there another way this should be checked?

The hardware in your profile is not 7-series. It is likely 100-series chipset.

- Therefore I choose the 'config_HD615_620_630_640_650_spoof.plist'.

Best to use Skylake spoof with KabyLake hardware only if necessary.
eg. Start with non-spoof plist.

## " Common ig-platform-ids: " Section examples do not include information for HD 620 Graphics.

The provided plist has the most common ig-platform-id.

## A link to information on achieving (hopefully) full functionality would be excellent.

Use search.

## It is my understanding this should be avoided, if the proper ig-platform-id CAN be used.

Yes, of course.

*** - Q: Are there any other additional requirements to include along with
the applied 'config_HD615_620_630_640_650.plist' in the clover folder?

Read the guide. All aspects of EFI/Clover are important.

*** - Q: Is there any additional changes which must be made to the config.plist outside
of the '/Graphics/ig-platform-id.' section - within the .plist?
(using an editor or otherwise)

Depends on the problem you're attempting to solve.

Helpful hint: ## kaby lake - minStolenSize patch not necessary.

Hardware dependent. For some, it is the only way to make things work (Microsoft Surface for example).

- FakePCIID_Intel_HD_Graphics.kext has NO facilities for KabyLake graphics.

Wrong.

*** - Q: What is the correct method to assess what my Bios sets the DVMT-preallocation to?

Without the setting directly in BIOS UI, no direct way.

You will know it is 32mb if you KP in the graphics kexts without a 32mb patch and valid ig-platform-id.

Otherwise, requires IFR extract from BIOS and inspection of the setting via setup_var or setup_var2 in special UEFI shell.

*** - Q: Is there a list to know what applies to my machine? or a matrix to understand the
corresponding requirements?

List of what?

*** - Q: Is this recommended for initial installation? -->
[ "guide-booting-the-os-x-installer-on-laptops" ]
or should this indeed be done before booting the installer? to avoid doing it later?

What do you mean by 'this'?

*** - Q: Is the patch which is enabled by default in the provided .plist adiquate? or should
I also include IntelGraphicsDVMTFixup.kext? -or- proceed to 'patch the fame buffer'?

IntelGraphicsDVMTFixup.kext does the same thing as the patch.

## From --> https://github.com/BarbaraPalvin/IntelGraphicsDVMTFixup <--
"IntelGraphicsDVMTFixup is now part of WhateverGreen, please use it instead."
Please update the Guide to reflect this.

I will not be changing the recommendation for WhateverGreen.kext until Mojave is released and WhateverGreen.kext is fully debugged.

## Obviously whatever produces the best final result should be done,
but forgive my confusion about what Should/Can be done.
Best procedure is to install with '0x12345678' then correct after?

Your call.

*** - Q: What is the appropriate CPUID for similar Skylake CPU?

FakeCPUID not needed in High Sierra as there is native support.
Also native support in 10.12.6.
You're reading stuff that applied to early versions of macOS before native KBL support arrived.

*** - Q: EDIT: Is this a correct procedure?

[i5 7200U and HD 620 Graphics]

IntelGFX = 0x59168086, ig-platform-id 0x59160000

com.apple.driver.AppleIntelKBLGraphicsFramebuffer

Find:
01030303 00002002 00000000
Replace:
01030303 00003001 00009000

The patch is already present in the guide plist.

Can you please give me a hint at what i'm doing wrong?

Your drivers64UEFI is wrong. EmuVariableUefi-64.efi is not used with AptioMemoryFix.efi.

-Something not being recognized, like sata, or the USB - then it can't verify the contents.
-perhaps i need to do something more to this MSR thing than just delete the partition to unused space
-this is a 1tb spinner, so the APFS thing shouldn't be even in error, humm

Best to repartition the entire disk with Disk Utility (wiping Windows and everything else), leaving a standard GPT setup with single macOS target partition. Install Windows later.
 
No idea what you mean by "this" or "the 'Synaptics' kext", or 'it"...

Forgive me, i could have been clearer, i wrote much of this during some really tired nights. This is likely irrelevant at this point because i haven't yet had a chance to even check if the Elan track pad works within macOS - so i will test this on my own.
I would like to mention, for what its worth, some of this' is notes for me/internal thoughts, i should have omitted some of this.
sorry.

It does not matter if you include kexts which don't apply to your hardware (they simply will not load/will not start).

I didn't know this, i thought it could cause issues, thank you for clarifying.

The hardware in your profile is not 7-series. It is likely 100-series chipset.

Yes, this is ultimately what i was thinking, what i was referring to was that it is my belief that the cpu and the chipset are of the same 'series' together, not mixed er whatever... more personal 'notes' ..i apologize

Best to use Skylake spoof with KabyLake hardware only if necessary.
eg. Start with non-spoof plist.

indeed, i changed to using the non-spoof 620 plist. i had some confusion there.

The provided plist has the most common ig-platform-id.

I see now, it is included already. i apologize for many of these quite basic misunderstandings.

Read the guide. All aspects of EFI/Clover are important.

I will read it through again.

Hardware dependent. For some, it is the only way to make things work (Microsoft Surface for example).
ref - ## kaby lake - minStolenSize patch not necessary.

I see, some of the confusion on my part is i'm attempting to search for answers among other threads, and although i am trying to pay attention to the dates, as some information may become updated or nullified. I did come across a thread of you mentioning that to someone, it is a quote, however I do reserve that it may have been specific to that persons situation, or may have changed at this point.

ref. - FakePCIID_Intel_HD_Graphics.kext has NO facilities for KabyLake graphics.

Again, same as the above situation, that is a quote from you, but i understand that must have been specific, or now incorrect.

Without the setting directly in BIOS UI, no direct way.

You will know it is 32mb if you KP in the graphics kexts without a 32mb patch and valid ig-platform-id.

Otherwise, requires IFR extract from BIOS and inspection of the setting via setup_var or setup_var2 in special UEFI shell.

Interesting, i can see this is more involved than i thought, that is probably why i couldn't easily find information of how to check this value, only direction that 'windows is not a valid way to check'. And no, this low-end laptop doesn't have any good settings for this.
Seeing as though i believe your patch is sufficient, i will attempt to achieve full functionality before further inquiry.

List of what?
ref. - DVMT-prealloc For Kaby Lake

One of the important aspects of my interest in doing this is to have fully working graphics, hopefully, as i am attending school for design related courses. [..I understand there may be complications. I'll make my best attempt. ]
What i was referring to was a place/thread where common configurations can be obtained, so i could input what is needed. but i suppose mOre than just the preallocation aspect, perhaps a thread of such information can be formed, to focus on graphics for newer set-ups at least. I will attempt to assemble / start this list if you think it's worth it. Of course after fixing my issues first.

What do you mean by 'this'?
ref. - Q: Is this recommended for initial installation? --> DVMT-prealloc

I was asking if you think the graphics should be set up entirely before the initial installation, or rather ultimately, CAN they be set up properly from the starting gate - to avoid any complications later?. To clarify, would you say it is your recommendation to just use the fake ig-platform-id, then dig into getting full functionality after installing?.
Forgive my focus on the graphics aspect, perhaps i'm ahead of myself here.

IntelGraphicsDVMTFixup.kext does the same thing as the patch.

Okay.

I will not be changing the recommendation for WhateverGreen.kext until Mojave is released and WhateverGreen.kext is fully debugged.

I see, i wasn't aware of the kext being potentially buggy, I suppose I assumed it was essentially just a name change.

FakeCPUID not needed in High Sierra as there is native support.
Also native support in 10.12.6.
You're reading stuff that applied to early versions of macOS before native KBL support arrived.

A-HA! thank you. I was looking for conformation that there was 'native' support for kaby lake in HS
That was the last thing i was searching for last night - search " kaby lake native support " - i found a few sparse things, but not satisfactory. good. That changes my focus a little.

The patch is already present in the guide plist.

I understand now, thank you.

Your drivers64UEFI is wrong. EmuVariableUefi-64.efi is not used with AptioMemoryFix.efi.

Allright, ...... i believe i may have tried without EmuVariableUefi-64 - simply. But maybe i didn't .. ..ok, I will experiment and read more, thank you for looking.

Best to repartition the entire disk with Disk Utility (wiping Windows and everything else), leaving a standard GPT setup with single macOS target partition. Install Windows later.

Guhhhh... you know, i was hoping you wouldn't say this ..lol ... buuuuut ... well, i was gifted with good intuition .. i had a feeling this would be a way to eliminate my issue, please let me tell you why.

I'm not afraid to do anything necessary, moving things around, whatever. no problem.
but like i'm sure anyone attempting to do this with an oem copy of windows, and myriad programs installed.
To the best of your knowledge, do you think it would be possible to just make an image of the installed

current win10 partition
win recovery partition
OEM win10 installer partition
lenovo 1 key partition thing
+ copy everything out of the EFI

without there being sOme sort of issue when poping it back in, after a clean wipe?

I ask this, because could there be some issue with windows complaining that it's written to a different part of the drive?
or the other OEM parts complaining? or maybe the 'partition types' not identifying properly afterward?

Although i don't see why that could be the case, i have run into strange issues before with obscure program issues.
I understand this is all on me, but do you think it will be ok if i just:

- image everything* (i use sdclt built in win-image, a better way?)
- Wipe the drive with disk utility
- Patition a little more than half the drive to empty space
- install as normal, HS to the HFS+ partition (first half)
- then dump the win+oem images into the sufficient left over space (i guess i would have to find a way to format it NTFS first)
---maybe using the Windows recovery image Disc i made - open command and format the empty space first?

I understand this is maybe out of the scope of what you are prepared to help with.
i guess, you're opinion/experience on it would be nice.

Thank you kindly for spending so much time answering my giant post, i wasn't expecting such an audience.
It is well appreciated. :)
 
ref. - Q: Is this recommended for initial installation? --> DVMT-prealloc

I was asking if you think the graphics should be set up entirely before the initial installation, or rather ultimately, CAN they be set up properly from the starting gate - to avoid any complications later?. To clarify, would you say it is your recommendation to just use the fake ig-platform-id, then dig into getting full functionality after installing?.
Forgive my focus on the graphics aspect, perhaps i'm ahead of myself here.

It is really quite simple: Use invalid ig-platform-id if necessary, then deal with it later (if necessary).


I see, i wasn't aware of the kext being potentially buggy, I suppose I assumed it was essentially just a name change.

Not just a name change. It is a major change with the way we deal with framebuffer patching, and other related graphics patching.

I will be transitioning all my guides to it soon... but it is a bit of work to convert all KextsToPatch entries to the WhateverGreen mechanism. And a lot of testing...

Guhhhh... you know, i was hoping you wouldn't say this ..lol ... buuuuut ... well, i was gifted with good intuition .. i had a feeling this would be a way to eliminate my issue, please let me tell you why.

I'm not afraid to do anything necessary, moving things around, whatever. no problem.
but like i'm sure anyone attempting to do this with an oem copy of windows, and myriad programs installed.
To the best of your knowledge, do you think it would be possible to just make an image of the installed

current win10 partition
win recovery partition
OEM win10 installer partition
lenovo 1 key partition thing
+ copy everything out of the EFI

without there being sOme sort of issue when poping it back in, after a clean wipe?

I have been able to do exactly that (with my Lenovo u430), but there are a lot of details/tricks involved. You need to really know what you're doing with diskpart.exe and various other software (gparted, gdisk, etc) to accomplish a complete restore by cloning individual partitions (for example, recovery partitions have special partition GUIDs that must be saved, then restored).

And it is really not worth it at all... OEMs install all kinds of unnecessary junk that is better left out.

I ask this, because could there be some issue with windows complaining that it's written to a different part of the drive?
or the other OEM parts complaining? or maybe the 'partition types' not identifying properly afterward?

And, as mentioned above, special partition GUIDs that are not documented...

It is not worth it... just plan on a Windows re-install... you'll end up with a better Windows install than provided by the OEM anyway.
 
Last edited:
Not just a name change. It is a major change with the way we deal with framebuffer patching, and other related graphics patching.

I will be transitioning all my guides to it soon... but it is a bit of work to convert all KextsToPatch entries to the WhateverGreen mechanism. And a lot of testing...

I see. You know, from all the poking around here, and reading on other sites where your name pops up, I Reaaally don't think people here realize just hOW much you know, and how much time you put into all the intricate bits and pieces to make this stuff work, i'm totally not just pumping you up .lol.. i don't think you're the type to care for that. I really mean it though, i am completely humbled by the utterly hUGe amount of stuff you can do, and i just don't think i'll ever get to that point in this life.
We all need more people like you, and if i can make a swift suggestion, Don't let peoples stupidness get to you, don't let it make you cynical, you are a valuable person to good slice of people around here... and i'm sure elsewhere.

But i digress, you can make like i didn't even say that :)

I have been able to do exactly that (with my Lenovo u430), but there are a lot of details/tricks involved. You need to really know what you're doing with diskutil and various other software to accomplish a complete restore by cloning individual partitions (for example, recovery partitions have special partition GUIDs that must be saved, then restored).

And it is really not worth it at all... OEMs install all kinds of unnecessary junk that is better left out.

Ok, i figured ..
I had that intuition thing dingin' again. Yeahh i'm not that interested in wrestling that beast down.. seems like more work than just starting from scratch.


And, as mentioned above, special partition GUIDs that are not documented...

It is not worth it... just plan on a Windows re-install... you'll end up with a better Windows install than provided by the OEM anyway.

Yup, Agreed.
I just finished making a complete image of the state its in now anyway, so nothing to worry about ultimately.
Well, i say that because it's just kinda sad to waist a perfectly good windows key, if you don't have to, heh.
I'm bi-OS-ual, i like both mac and windows, they're both good at what they do.

Okay thank you for you're help, i'm gonna wipe this suckker out right now!
I'll have to use my older mac to get online while i'm setting this one up.

Meg-out.
 
I see. You know, from all the poking around here, and reading on other sites where your name pops up, I Reaaally don't think people here realize just hOW much you know, and how much time you put into all the intricate bits and pieces to make this stuff work, i'm totally not just pumping you up .lol.. i don't think you're the type to care for that. I really mean it though, i am completely humbled by the utterly hUGe amount of stuff you can do, and i just don't think i'll ever get to that point in this life.
We all need more people like you, and if i can make a swift suggestion, Don't let peoples stupidness get to you, don't let it make you cynical, you are a valuable person to good slice of people around here... and i'm sure elsewhere.

But i digress, you can make like i didn't even say that :)

Thanks. I have a lot going on lately outside of hackintosh, so actually haven't been able to invest time into new things like WhateverGreen.kext/Mojave (only cursory looks, a few fixes).

Ok, i figured ..
I had that intuition thing dingin' again. Yeahh i'm not that interested in wrestling that beast down.. seems like more work than just starting from scratch.




Yup, Agreed.
I just finished making a complete image of the state its in now anyway, so nothing to worry about ultimately.
Well, i say that because it's just kinda sad to waist a perfectly good windows key, if you don't have to, heh.
I'm bi-OS-ual, i like both mac and windows, they're both good at what they do.

Okay thank you for you're help, i'm gonna wipe this suckker out right now!
I'll have to use my older mac to get online while i'm setting this one up.

Meg-out.

Enjoy...
 
hey, i'm back

yeahhh nope, ......Zhe GoGGLEs ZHEY DO NOZTHING!

The complete formatting didn't work, i tried sOOO many things .. i honestly cant believe that i'm the only person on the internet with these problems, each different issue i get has - little - to no - info, like as if no one has these issues what so ever ....... i'm still getting the same basic message. except, well, now i don't remember, i think the 'failed to get physical whole disk' may have disappeared. i'll start it up again to check.... that would make sense

I tried about 25 times to get it to go, with aNYthing. I don't even remember all the messed up stuff saw, like a war zone on the screen.. at one point i was seeing serialATAPI errors, and the only stuff i could find about that was from 2010.. and that was without fakeSMC kext, so wow, i don't know what dark corners of hackville i was in. I thought it could be the TPM thing in the bios, turned that off .. tried resetting default values/re-configuring it .... guhhh ... i tried with a blank drive, and i tried creating an EFI in linux - 300mb with boot flags 'boot,efi'
then i wiped that out, i thought i saw at one point that diskutil was formatting sda2..only ..maybe ..when i was going for the 18th time or so... so do you think it's not actually wiping the old efi partition? could that be related?.. in linux it shows it gone.. but i dunno' i wasn't watching every time... i spent like 20 hours on it .. and i'm SO confused now.

I re-downloaded high sierra TWOOOhh more times! Recreated the USB installer F I V EEEE more times (i know ...i know) ... i changed out the kexts in different orders, trying random stuff, reading different possible things it could be... same with the drivers ..... yea i guess i didn't need to .. but i just want to get it done already ....i haven't even started with all the issues once it goes in ... unless it just ..wont

I attached some of the verbose from before the installer shows up if there maybe something in there ... one of the /later attempts...
but basically its the same - no native mechanism stuff .. could not find board id, chip id, ecid .. or whatever .. same as the first pic basically.

.... if there was info on what i'm experiencing, i'm sure i could figure it out ... but alas.. i feel bad asking...
i read through the guide again .... and .... anyway ...whAT am i missing???

maybe you have some idea what it could be? ..should i just toss it in the fire pit in the backyard? ..
Log22_.jpg log23_.jpg
 
Last edited:
hey, i'm back

yeahhh nope, ......Zhe GoGGLEs ZHEY DO NOZTHING!

The complete formatting didn't work, i tried sOOO many things .. i honestly cant believe that i'm the only person on the internet with these problems, each different issue i get has - little - to no - info, like as if no one has these issues what so ever ....... i'm still getting the same basic message. except, well, now i don't remember, i think the 'failed to get physical whole disk' may have disappeared. i'll start it up again to check.... that would make sense

I tried about 25 times to get it to go, with aNYthing. I don't even remember all the messed up stuff saw, like a war zone on the screen.. at one point i was seeing serialATAPI errors, and the only stuff i could find about that was from 2010.. and that was without fakeSMC kext, so wow, i don't know what dark corners of hackville i was in. I thought it could be the TPM thing in the bios, turned that off .. tried resetting default values/re-configuring it .... guhhh ... i tried with a blank drive, and i tried creating an EFI in linux - 300mb with boot flags 'boot,efi'
then i wiped that out, i thought i saw at one point that diskutil was formatting sda2..only ..maybe ..when i was going for the 18th time or so... so do you think it's not actually wiping the old efi partition? could that be related?.. in linux it shows it gone.. but i dunno' i wasn't watching every time... i spent like 20 hours on it .. and i'm SO confused now.

I re-downloaded high sierra TWOOOhh more times! Recreated the USB installer F I V EEEE more times (i know ...i know) ... i changed out the kexts in different orders, trying random stuff, reading different possible things it could be... same with the drivers ..... yea i guess i didn't need to .. but i just want to get it done already ....i haven't even started with all the issues once it goes in ... unless it just ..wont

I attached some of the verbose from before the installer shows up if there maybe something in there ... one of the /later attempts...
but basically its the same - no native mechanism stuff .. could not find board id, chip id, ecid .. or whatever .. same as the first pic basically.

.... if there was info on what i'm experiencing, i'm sure i could figure it out ... but alas.. i feel bad asking...
i read through the guide again .... and .... anyway ...whAT am i missing???

maybe you have some idea what it could be? ..should i just toss it in the fire pit in the backyard? ..
View attachment 350310 View attachment 350311

"Problem Reporting" files are incomplete.
Read FAQ, "Problem Reporting" again. Carefully. Attach all requested files/output.
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/
 
Status
Not open for further replies.
Back
Top