macOS High Sierra Public Beta 5 is Now Available

[el_charlie]

nv_disable=1 boot flag fails to force my Nvidia discrete cards to boot into VESA mode; window server fails to start on beta 5 using nv_disable=1. This is a problem when doing updates on a 17,1 system that generates a black screen using vanilla video kexts.

Any one: Besides using Lilu+Nvfix-up kexts is there a way to get around the blaxk screen issue on a 17,1 profile? Historically, I'd just do nv_disable=1, boot, run agdpfix and reboot no problem.

Change your board-id to an iMac14,2 iMac13,2 or MacPro6,1. You can even do that in the Clover boot screen. I used Lilu + NvidiaGraphicsFixUp before, but now I'm using this method. I don't know if placebo, but my geekbench scores increased like 200 points. My original SMBIOS is iMac11,3.

There's no need to change anything else from your SMBIOS, just the board-id.

The list of board ids is here: https://gist.github.com/rtrouton/e6cf0f4064aea52fac2e5116c4b05f2e

MacBook9,1: 'Mac-9AE82516C7C6B903'
iMac14,1: 'Mac-031B6874CF7F642A'
iMac10,1: 'Mac-F2268DC8'
MacBookPro8,1: 'Mac-50619A408DB004DA'
MacBook6,1: 'Mac-F22C8AC8'
MacBookPro10,2: 'Mac-AFD8A9D944EA4843'
iMac12,2: 'Mac-942B59F58194171B'
iMac14,2: 'Mac-27ADBB7B4CEE8E61'
MacBook8,2: 'Mac-F305150B0C7DEEEF'
MacBookAir6,1: 'Mac-35C1E88140C3E6CF'
iMac14,3: 'Mac-77EB7D7DAF985301'
MacBookAir5,2: 'Mac-2E6FAB96566FE58C'
Macmini5,3: 'Mac-7BA5B2794B2CDB12'
MacBook8,1: 'Mac-BE0E8AC46FE800CC'
iMac13,1: 'Mac-00BE6ED71E35EB86'
MacBookPro9,1: 'Mac-4B7AC7E43945597E'
MacBook7,1: 'Mac-F22C89C8'
MacBookAir7,2: 'Mac-937CB26E2E02BB01'
MacBookPro8,3: 'Mac-942459F5819B171B'
iMac16,2: 'Mac-FFE5EF870D7BA81A'
MacBookPro7,1: 'Mac-F222BEC8'
Macmini5,2: 'Mac-4BC72D62AD45599E'
MacMini4,1: 'Mac-F2208EC8'
MacBookAir5,1: 'Mac-66F35F19FE2A0D05'
MacBookPro11,1: 'Mac-189A3D4F975D5FFC'
MacBookAir4,1: 'Mac-C08A6BB70A942AC2'
Macmini5,1: 'Mac-8ED6AF5B48C039E1'
iMac15,2: 'Mac-FA842E06C61E91C5'
iMac13,2: 'Mac-FC02E91DDD3FA6A4'
MacBookPro11,4: 'Mac-06F11FD93F0323C5'
MacBookPro11,5: 'Mac-06F11F11946D27C5'
MacBookPro9,2: 'Mac-6F01561E16C75D06'
MacPro6,1: 'Mac-F60DEB81FF30ACF6'
iMac14,4: 'Mac-81E3E92DD6088272'
MacBookPro11,2: 'Mac-3CBD00234E554E41'
MacBookPro6,2: 'Mac-F22586C8'
MacPro5,1: 'Mac-F221BEC8'
MacBookAir3,2: 'Mac-942C5DF58193131B'
iMac11,3: 'Mac-F2238BAE'
MacBookAir7,1: 'Mac-9F18E312C5C2BF0B'
MacBookPro10,1: 'Mac-C3EC7CD22292981F'
iMac10,1: 'Mac-F221DCC8'
MacBookAir4,2: 'Mac-742912EFDBEE19B3'
iMac17,1: 'Mac-B809C3757DA9BB8D'
Macmini6,2: 'Mac-F65AE981FFA204ED'
Macmini6,1: 'Mac-031AEE4D24BFF0B1'
iMac17,1: 'Mac-DB15BD556843C820'
MacBookPro6,1: 'Mac-F22589C8'
iMac11,2: 'Mac-F2238AC8'
MacBookAir3,1: 'Mac-942452F5819B1C1B'
iMac17,1: 'Mac-65CE76090165799A'
Macmini7,1: 'Mac-35C5E08120C7EEAF'
MacBookPro8,1: 'Mac-94245B3640C91C81'
iMac15,1: 'Mac-42FD25EABCABB274'
iMac13,3: 'Mac-7DF2A3B5E5D671ED'
iMac11,1: 'Mac-F2268DAE'
MacBookPro11,3: 'Mac-2BD1B31983FE1663'
MacBookAir6,2: 'Mac-7DF21CB3ED6977E5'
iMac16,1: 'Mac-A369DDC4E67F1C45'
iMac10,1: 'Mac-F2268CC8'
MacBookPro8,2: 'Mac-94245A3940C91C80'
MacBookPro12,1: 'Mac-E43C1C25D4880AD6'
iMac12,1: 'Mac-942B5BF58194151B'

The reason for this is that the AppleGraphicsDevicePolicy.kext checks the board-id and not the whole SMBIOS to manage the graphics and in some cases it disables the video signal. That's what NvidiaGraphicsFixup does, it spoofs the MacPro6,1 board id and therefore the AGDP is not loaded and you get video signal.

Sorry for the long post.

Cheers!

 

[Gigamaxx]

Right or wrong already took it back. Got Asus from Amazon and may not get until next week because back ordered. There is a shortage right now, tried Newegg and out of stock and even Fry's only a couple and not what I wanted.

BTW Gigamaxx I did try it booting my Sierra 12.6 with the RX 560 and the ID was in the info.plist already. Must have been from last update however did not work for me in Sierra, similar problems.

I suspect we will see a lot more successful builds with AMD Video. My first couple of CustoMacs had Radeon cards.

I tried hacking the NVidia Web Drivers with some success but more to see if it would work

Thanks again...

For the Graphics cards AMD there are usually 2 kexts the xxxxControllerKext, and the xxxxKext. For that card the 4100Kext needs to have it as well as the 9510ControllerKext. Its usually missing from the ControllerKext.

 

[Justcurious1]

Can anyone with a Vega GPU run a BruceX test in FCPX? Thanks.

 

[helob]

Update to Beta 5 from Beta 4 with OTA.
Encountered KP with Prohibited error.
Verbose show following:
OsxAptionFix2Drv:Starting overrides for \System\Library\CoreServices\boot.efi
Using reloc........
_fs get inode with hint:7825:failed to load inode 328436 ret22
_fs get inode with hint: 7825:failed to load inode 328436 ret22
Error loading kernel cache (0xe)
Boot failed, sleeping for 10 sec before exiting

I have updated to Clover Bootloader ver4173 from 4097 before Beta5 update.
Also try ver 4152 but same result.
Also try -x -f and UsekernelCache=No but same result.
Any inputs on correcting boot will be much appreciated.
Thank You

 

[Lundli]

I updated to Clover 4173 and can install now without firmware error, using 6,1 in smbios, there is a newer firmware in 4173 that works.

Hmm.. still getting the firmware error even with Clover 4173

 

[Gigamaxx]

When you updated clover did you add or check for FakeSMCkext in clover kext folder 10.12 or other.

 

[johnnyx86]

I just upgraded my intel nuc i3 6th gen from 10.12.6 to 10.13b5. First installation got KP then retry the 2nd time went ok but upon booting the macOS drive is missing from the clover boot menu, only has the windows boot drive. Any idea how to get back the macOS boot drive in the clover boot menu?

I had updated to the latest clover prior to starting the beta update within 10.12.6. I did not create bootable USB for 10.13b5.

Thanks

 

[Gigamaxx]

I just upgraded my intel nuc i3 6th gen from 10.12.6 to 10.13b5. First installation got KP then retry the 2nd time went ok but upon booting the macOS drive is missing from the clover boot menu, only has the windows boot drive. Any idea how to get back the macOS boot drive in the clover boot menu?

I had updated to the latest clover prior to starting the beta update within 10.12.6. I did not create bootable USB for 10.13b5.

Thanks

Did you upgrade to APFS? I think you need to uncheck the upgrade to use the HFS file system. I think you may have to add a file in clover folder for it to see it.

 

[helob]

When you updated clover did you add or check for FakeSMCkext in clover kext folder 10.12 or other.

I checked and confirmed that FakesSMC.kext is in Clover>Kext>other folder.
When I upgrade Clover 4173, the updated EFI was in the root partition and not in EFI partition.
I have to copy the EFI folder from root partition to replace that in EFI partition.
What do I have to configure in Clover to ensure the update is written to the EFI partition instead of the root?
Thank You

 

[johnnyx86]

Did you upgrade to APFS? I think you need to uncheck the upgrade to use the HFS file system. I think you may have to add a file in clover folder for it to see it.

Actually I started the installer when I was in 10.12.6 and there was no option given to upgrade to APFS. Basically the installer restarted and start installing, no option given to select anything.