Jump to content

[pre-release] macOS High Sierra

fantomas

By fantomas,
in New Releases and Updates

 Share
3,737 posts in this topic

Recommended Posts

Badruzeus
Badruzeus
Posted
Posted

All good here minus Nvidia drivers on my Skylake system.

attachicon.gifScreen Shot 2017-06-30 at 10.27.03 am.png

 

 

GTX960? I'm not sure why native GeForce* won't loaded on some GPUs under 10.13, many changes on SMBios since 10.12. But I read this on @Pike's blog:

The OSBundleLibraries in AppleSMC.kext has changed. This one is new:

<key>com.apple.iokit.IOPCIFamily</key>
<string>1.8</string>

IDK how 10.13 sees PCIe GPU on hackintosh (or only some of them), is it become Internal or external (eGPU). I noticed on Beta 1 my GF119 always crashes while logging out with "No GPU found" logs, but my friend somewhere has no problem with HDMI. Then it solved on Beta 2 with disabling AutoLogin. Still waiting for Web Driver (if not Appl* bugs)

 

Link to comment
Share on other sites
Wppley2
Wppley2
Posted
Posted

Or stay with Sierra, isn't old yet..

And maybe in the next betas or final release will work for us too.

 

Sent from my HTC One M9 using Tapatalk

Beta installed. I did not need to put video kexts again. There was no modification of these kexts. Everything worked normally.

Link to comment
Share on other sites
SavageAUS
SavageAUS
Posted
Posted

should update biosdata before update public beta?

I'm unsure what you mean? But I am already using updated bios information.

 

Sent from my SM-G930F using Tapatalk

GTX960? I'm not sure why native GeForce* won't loaded on some GPUs under 10.13, many changes on SMBios since 10.12. But I read this on @Pike's blog:

The OSBundleLibraries in AppleSMC.kext has changed. This one is new:

<key>com.apple.iokit.IOPCIFamily</key>
<string>1.8</string>
IDK how 10.13 sees PCIe GPU on hackintosh (or only some of them), is it become Internal or external (eGPU). I noticed on Beta 1 my GF119 always crashes while logging out with "No GPU found" logs, but my friend somewhere has no problem with HDMI. Then it solved on Beta 2 with disabling AutoLogin. Still waiting for Web Driver (if not Appl* bugs)

 

https://www.youtube.com/watch?v=NlN7XCwDKnw

Yeah I have no idea. You would think by now Apple would support more cards out of the box to reduce the need for Nvidia drivers.

 

Sent from my SM-G930F using Tapatalk

Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted

For your platformdata update @Sherlocks:

 

 

 

EFIPayloads:

 - IM101.88Z.00CD.B01.1706261549
 - IM111.88Z.0035.B01.1706261406
 - IM112.88Z.0058.B01.1706261628
 - IM121.88Z.004A.B01.1706261231
 - IM131.88Z.010C.B01.1706261419
 - IM141.88Z.0119.B01.1706261354
 - IM142.88Z.0119.B01.1706261827
 - IM143.88Z.0119.B01.1706261217
 - IM144.88Z.0180.B01.1706261218
 - IM151.88Z.0208.B01.1706261354
 - MB61.88Z.00C9.B01.1706261518
 - MB71.88Z.003A.B01.1706261443
 - MBA31.88Z.0064.B01.1706261714
 - MBA41.88Z.0078.B01.1706261217
 - MBA51.88Z.00F1.B01.1706261433
 - MBA61.88Z.0100.B01.1706261827
 - MBP101.88Z.00EF.B01.1706261418
 - MBP102.88Z.0107.B01.1706261827
 - MBP111.88Z.0139.B01.1706261010
 - MBP112.88Z.0139.B01.1706261355
 - MBP61.88Z.0058.B01.1706261104
 - MBP71.88Z.003A.B01.1706261020
 - MBP81.88Z.0049.B01.1706261922
 - MBP91.88Z.00D4.B01.1706261216
 - MM41.88Z.0043.B01.1706261836
 - MM51.88Z.0078.B01.1706261437
 - MM61.88Z.0107.B01.1706261217
 - MM71.88Z.0221.B02.1706261516
 - MP61.88Z.0117.B01.1706261354
 - IM161.88Z.0209.B02.1706261516
 - IM162.88Z.0209.B02.1706261516
 - IM171.88Z.0106.B01.1706260138
 - IM181.88Z.0147.B01.1706251744
 - IM183.88Z.0147.B01.1706251744
 - MB101.88Z.0150.B01.1706260154
 - MB81.88Z.0165.B01.1706261516
 - MB91.88Z.0155.B01.1706260138
 - MBA71.88Z.0167.B01.1706261032
 - MBP114.88Z.0173.B01.1706261516
 - MBP121.88Z.0168.B01.1706261516
 - MBP131.88Z.0206.B01.1706260154
 - MBP132.88Z.0227.B01.1706260154
 - MBP133.88Z.0227.B01.1706260154
 - MBP141.88Z.0161.B01.1706251744
 - MBP142.88Z.0161.B01.1706251744
 - MBP143.88Z.0161.B01.1706252330


SMCJSONs:

 - Mac-031B6874CF7F642A: 2.14f24
 - Mac-189A3D4F975D5FFC: 2.16f68
 - Mac-27ADBB7B4CEE8E61: 2.15f7
 - Mac-2BD1B31983FE1663: 2.19f12
 - Mac-35C1E88140C3E6CF: 2.12f143
 - Mac-35C5E08120C7EEAF: 2.24f32
 - Mac-3CBD00234E554E41: 2.18f15
 - Mac-42FD25EABCABB274: 2.22f16
 - Mac-473D31EABEB93F9B: 2.36f97
 - Mac-65CE76090165799A: 2.33f10
 - Mac-66E35819EE2D0D05: 2.37f20
 - Mac-77EB7D7DAF985301: 2.17f7
 - Mac-7DF21CB3ED6977E5: 2.13f15
 - Mac-81E3E92DD6088272: 2.21f92
 - Mac-937CB26E2E02BB01: 2.27f2
 - Mac-9AE82516C7C6B903: 2.35f105
 - Mac-9F18E312C5C2BF0B: 2.26f2
 - Mac-A369DDC4E67F1C45: 2.31f36
 - Mac-A5C67F76ED83108C: 2.38f7
 - Mac-B809C3757DA9BB8D: 2.34f2
 - Mac-BE0E8AC46FE800CC: 2.25f87
 - Mac-DB15BD556843C820: 2.33f10
 - Mac-E43C1C25D4880AD6: 2.28f7
 - Mac-F60DEB81FF30ACF6: 2.20f18
 - Mac-FA842E06C61E91C5: 2.23f11
 - Mac-FFE5EF870D7BA81A: 2.32f20


FirmwareFeatures(Mask):

 - IM131.88Z.010C.B01.1706261419: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xe005e137
 - IM141.88Z.0119.B01.1706261354: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xe007e137
 - IM142.88Z.0119.B01.1706261827: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xe007e137
 - IM143.88Z.0119.B01.1706261217: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xe007e137
 - IM144.88Z.0180.B01.1706261218: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xf007e137
 - IM151.88Z.0208.B01.1706261354: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xf807e137
 - MBA41.88Z.0078.B01.1706261217: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xd005e137
 - MBA51.88Z.00F1.B01.1706261433: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xe005e137
 - MBA61.88Z.0100.B01.1706261827: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xe007e137
 - MBP101.88Z.00EF.B01.1706261418: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xe005e137
 - MBP102.88Z.0107.B01.1706261827: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xe005e137
 - MBP111.88Z.0139.B01.1706261010: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xe807e137
 - MBP112.88Z.0139.B01.1706261355: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xe807e137
 - MBP91.88Z.00D4.B01.1706261216: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xc005e137
 - MM51.88Z.0078.B01.1706261437: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xd005e137
 - MM61.88Z.0107.B01.1706261217: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xe005e137
 - MP61.88Z.0117.B01.1706261354: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xe807e136
 - IM171.88Z.0106.B01.1706260138: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc07e136
 - IM181.88Z.0147.B01.1706251744: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc07e136
 - IM183.88Z.0147.B01.1706251744: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc07e136
 - MB101.88Z.0150.B01.1706260154: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc07e13e
 - MB91.88Z.0155.B01.1706260138: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc07e13e
 - MBP131.88Z.0206.B01.1706260154: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc07e136
 - MBP132.88Z.0227.B01.1706260154: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc07e136
 - MBP133.88Z.0227.B01.1706260154: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc07e13e
 - MBP141.88Z.0161.B01.1706251744: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc07e136
 - MBP142.88Z.0161.B01.1706251744: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc07e136
 - MBP143.88Z.0161.B01.1706252330: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc07e13e

 

 

 

thank you for great info

 

I think it's better waiting for Clover devs. updating it's Platform Datas within bootloader..

 

can you test fresh install high sierra? if you can, test and report please

 

clover now support native value. but need to surely check work or not.

 

post-980913-0-68646000-1498795675_thumb.png

 

my screentshot. not yet update bios version and date in config.plist. FirmwareFeatures and FirmwareFeaturesMask is nop

 

thanks

platform.zip

Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted

Those EFIPayloads are they bios revision to us? Do we need to modify smbios again?

 

Sent from my SM-G930F using Tapatalk

Only have to change bios boo rom and date from EFI firmware in config.plist.

 

Clover support FF and FFM native value above my test1 file.

 

Before commit, need to surely check work or not. Until someone check, i never commit and also not report it to Slice.

 

Kylon' CCE will follow clover platformdata.not yet commit.

If dont have BIOS info, will follow it.

 

 

나의 LG-F800S 의 Tapatalk에서 보냄

Link to comment
Share on other sites
SavageAUS
SavageAUS
Posted
Posted

Only have to change bios version and date from EFI firmware in config.plist.

 

Clover support FF and FFM native value above my test1 file.

 

Before commit, need to surely check work or not. Until someone check, i never commit and also not report it to Slice

 

나의 LG-F800S 의 Tapatalk에서 보냄

Just to confirm this is MacBook Pro 11,1?

MBP111.88Z.0139.B01.1706261010

And the date we set in smbios is

26/06/2017

And thats all we need to change? Along with your test1?

Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted

Just to confirm this is MacBook Pro 11,1?

MBP111.88Z.0139.B01.1706261010

And the date we set in smbios is

26/06/2017

And thats all we need to change? Along with your test1?

Sorry my english

 

-No need FF and FFM in config.plist(support native value according each model)-ofc you can use own value(keep) in config.plist or GUI(temp(once))

 

-Clover include latest BIOS ROM and bios date information. But normarlly users have own any data(BIOS ROM, bios date)

 

So you have to change BIOS ROM and Date from cecekpawon's info according your model in config.plist.

 

Then if you can, please test fresh install high sierra.

 

 

나의 LG-F800S 의 Tapatalk에서 보냄

Link to comment
Share on other sites
Badruzeus
Badruzeus
Posted
Posted

can you test fresh install high sierra? if you can, test and report please

 

clover now support native value. but need to surely check work or not.

...

 

Really need a cleaned install mach? Perhaps someone else  :)

on my case, $ sudo nvram -c && uuidgen with new (fake) SN w/o "Firmware Features" value, but use:

BiosVersion=MBP101.88Z.00EF.B01.1706261418
BiosReleaseDate=06/26/17

And below is what I get. Thanks..

#Edit: DMI Tables output from DarwinDumper v3.0.3.

post-826765-0-22927600-1498803361_thumb.png

SMBIOS_A43SJ_r4099_test.txt

Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted

Really need a cleaned install mach? Perhaps someone else :)

on my case, $ sudo nvram -c && uuidgen with new (fake) SN w/o "Firmware Features" value, but use:

BiosVersion=MBP101.88Z.00EF.B01.1706261418
BiosReleaseDate=06/26/17
And below is what I get. Thanks..

#Edit: DMI Tables output from DarwinDumper v3.0.3.

Just want to clear problem. Previous some users reported osinstall.pkg issue. Does it resolved all now? I don't know exactly.

 

 

 

나의 LG-F800S 의 Tapatalk에서 보냄

Link to comment
Share on other sites
Badruzeus
Badruzeus
Posted
Posted

Just want to clear problem. Previous some users reported osinstall.pkg issue. Does it resolved all now? I don't know exactly.

 

Nah, that was also happened with my USB Install method while on Beta 1  :lol:

I think just booting the installer with those new Platform Data & Clover test version above, we'll know what appears there.

Oops.. but I don't have new Installer yet.. (my Beta 1 Installer removed by mistake).

 

Question:

Bios Release Date pattern is American, isn't it?

I mean: 06/26/17 (MM/DD/YY) and not 26/06/17 or am I wrong.. hmmb.

Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted

DMI dump

 

good status. thank you

 

Nah, that was also happened with my USB Install method while on Beta 1  :lol:

I think just booting the installer with those new Platform Data & Clover test version above, we'll know what appears there.

Oops.. but I don't have new Installer yet.. (my Beta 1 Installer removed by mistake).

 

Question:

Bios Release Date pattern is American, isn't it?

I mean: 06/26/17 (MM/DD/YY) and not 26/06/17 or am I wrong.. hmmb.

 

(MM/DD/YY)

 

BIOS Information

Vendor: Apple Inc.
Version: IM171.88Z.0105.B05.1511031741
Release Date: 11/03/2015
ROM Size: 8192 kB
 
as result, clover's platform data is right.
Link to comment
Share on other sites
SavageAUS
SavageAUS
Posted
Posted

Nah, that was also happened with my USB Install method while on Beta 1  :lol:

I think just booting the installer with those new Platform Data & Clover test version above, we'll know what appears there.

Oops.. but I don't have new Installer yet.. (my Beta 1 Installer removed by mistake).

 

Question:

Bios Release Date pattern is American, isn't it?

I mean: 06/26/17 (MM/DD/YY) and not 26/06/17 or am I wrong.. hmmb.

Yes i believe i did it wrong, it should be, i think 06/26/2017

New USB created, with test1 files and updated smbios details.

Attempting fresh install now.

Link to comment
Share on other sites
Badruzeus
Badruzeus
Posted
Posted

 

good status. thank you

 

 

(MM/DD/YY)

 

BIOS Information

Vendor: Apple Inc.
Version: IM171.88Z.0105.B05.1511031741
Release Date: 11/03/2015
ROM Size: 8192 kB
 
as result, clover's platform data is right.

 

Thank u for confirming...

 

Yes i believe i did it wrong, it should be, i think 06/26/2017

New USB created, with test1 files and updated smbios details.

Attempting fresh install now.

 

Well done  :thumbsup_anim:

Link to comment
Share on other sites
wern apfel
wern apfel
Posted
Posted (edited)

It seems that the new AppleGFXHDAController.kext was built to work with external PCIe cards. The IOPCITunnelCompatible entry is already there, it works without the HDA kexts and probably also for external PCIe sound cards. Bad news for the nVidia users there are only Intel and AMD entries.

 

I have not exactly searched, the nVidia device-IDs are there.

 

post-448675-0-01825100-1498806527_thumb.png

Edited by wern apfel
  • Like 1
Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted

OSInstall.mpkg error.

 

Sent from my SM-G930F using Tapatalk

 

how did you install high sierra before?

 

use clover default FF and FFM?

 

add. if you install beta1

 

use default FF and FFM in test1.

 

only use previous BIOS ROM and date.

MBP111.88Z.0138.B38.1705011614

05/01/2017

 

then try

 

if not work above

FF - 0xE907F537

FFM - 0xFFFFFFFF

BIOS ROM - MBP111.88Z.0138.B38.1705011614

BIOS DATE - 05/01/2017

Link to comment
Share on other sites
SavageAUS
SavageAUS
Posted
Posted

how did you install high sierra before?

 

use clover default FF and FFM?

By running the downloaded beta.app from Sierra then after first reboot boot from USB.

I just wanted to test USB boot but now I'll do it the other way.

 

Sent from my SM-G930F using Tapatalk

Link to comment
Share on other sites
Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...