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

Sherlocks
Sherlocks
Posted
Posted

in here

 

thank you for info

but 0x3ff is no luck like 0x3e7

 

Sherlocksui-MacBook-Pro:~ sherlocks$ csrutil status

System Integrity Protection status: enabled (Custom Configuration).

 

Configuration:

Apple Internal: disabled

Kext Signing: disabled

Filesystem Protections: disabled

Debugging Restrictions: disabled

DTrace Restrictions: disabled

NVRAM Protections: disabled

BaseSystem Verification: disabled

 

This is an unsupported configuration, likely to break in the future and leave your machine in an unknown state.

Sherlocksui-MacBook-Pro:~ sherlocks$ 

 

  • Like 1
Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted

thank you for info

but 0x3ff is no luck like 0x3e7

 

In find cecekpawon'post http://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page-691?do=findComment&comment=2467180 And try this tool: csrstat. Give me your opinion on the results for csrutil status?

 

Under Sierra with 0x3e7

 

 

post-1110743-0-14698200-1504502020_thumb.png

  • Like 1
Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted

In find cecekpawon'post http://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page-691?do=findComment&comment=2467180 And try this tool: csrstat. Give me your opinion on the results for csrutil status?

 

Under Sierra with 0x3e7

 

okay. good script. i don't know crsutil detail. i just checked system profiler's difference on each crsutil value.

i will check more

0x67 result

 

Sherlocksui-MacBook-Pro:~ sherlocks$ /Users/sherlocks/Downloads/csrstat 

System Integrity Protection status: disabled.

 

Configuration: (0x00000067)

Apple Internal...........: disabled

Kext Signing Restrictions: disabled

Task for PID Restrictions: disabled

Filesystem Protections...: disabled

Debugging Restrictions...: disabled

DTrace Restrictions......: disabled

NVRAM Protections........: disabled

Device Configuration.....: enabled

BaseSystem Verification..: enabled

Sherlocksui-MacBook-Pro:~ sherlocks$ 

  • Like 1
Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted

okay. good script. i don't know crsutil detail. i just checked system profiler's difference on each crsutil value.

i will check more

0x67 result

Strange: with this tool, crsutil detail show "Configuration: (0x000001e7) " with crs 0x3e7. While with 0x67 result "Configuration: (0x00000067)"

  • Like 1
Link to comment
Share on other sites
wellcome
wellcome
Posted
Posted

thanks sandro I was hoping I wouldn't have to fix dsdt and ssdts.  I did disable gpu with DSDT reg fix but don't think thats enough.will have another go later cheers!

Please, niknod could teach me how to disable the Nvidia card through SSDT. You could send me your patched SSDT. As you know I had the same problem as you with MacOS High Sierra update beta 8 (WindowServer)
 
Thank you
 
P.D.:
 
I extend my request to any other member who can help me
 
 
 
Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted

Strange: with this tool, crsutil detail show "Configuration: (0x000001e7) " with crs 0x3e7. While with 0x67 result "Configuration: (0x00000067)"

 

i tested all. in script, some parts shown wrong info that you mentioned
0x3FF
all flags are disabled. just shown System Integrity Protection status: enabled on system profile, actually disabled all csr flags, script also shown enabled with "Custom Configuration"
 
0x3e7
except CSR_ALLOW_KERNEL_DEBUGGER, CSR_ALLOW_APPLE_INTERNAL, all flags are disabled.
 
i don't exactly know role of each flags. just if 0x67 crsactive config, system profiler recoginzed "SIP: disabled".
At high Sierra, the value 0x67 does not seem to be a big problem. because The 0x67 value contains the flags we need most.
as result, i think that useful values is 0x3FF to avoid any situation in future
  • Like 2
Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted

 

i tested all. in script, some parts shown wrong info that you mentioned
0x3FF
all flags are disabled. just shown System Integrity Protection status: enabled on system profile, actually disabled all csr flags, script also shown enabled with "Custom Configuration"
 
0x3e7
except CSR_ALLOW_KERNEL_DEBUGGER, CSR_ALLOW_APPLE_INTERNAL, all flags are disabled.
 
i don't exactly know role of each flags. just if 0x67 crsactive config, system profiler recoginzed "SIP: disabled".
At high Sierra, the value 0x67 does not seem to be a big problem. because The 0x67 value contains the flags we need most.
as result, i think that useful values is 0x3FF to avoid any situation in future

 

ThanKs. I will follow your advice

Link to comment
Share on other sites
niknod
niknod
Posted
Posted

 

Please, niknod could teach me how to disable the Nvidia card through SSDT. You could send me your patched SSDT. As you know I had the same problem as you with MacOS High Sierra update beta 8 (WindowServer)
 
Thank you
 
P.D.:
 
I extend my request to any other member who can help me
 
 
 

 

ok Wellcome here my 3 ssdts that did the trick.but don't think they will for you as different laptop good luck!

Wellcome.zip

Link to comment
Share on other sites
tj5
tj5
Posted
Posted

Anyone noticing slow boot speeds? My Computer has Sierra on a ssd and High Sierra on a Samsung 960 NVMe m.2 and booting the Sierra drive I get to the login in about 8 seconds. The High Sierra boot process takes almost 30 seconds to get to the login screen. I thought by now that High Sierra  (using DP9) that my boot time would be at least equal to or faster than the Sierra ssd. I get reads of 3000mb/s on the High Sierra drive vs 460mb/s on Sierra drive. 

  • Like 2
Link to comment
Share on other sites
LockDown
LockDown
Posted
Posted

 

i tested all. in script, some parts shown wrong info that you mentioned
0x3FF
all flags are disabled. just shown System Integrity Protection status: enabled on system profile, actually disabled all csr flags, script also shown enabled with "Custom Configuration"
 
0x3e7
except CSR_ALLOW_KERNEL_DEBUGGER, CSR_ALLOW_APPLE_INTERNAL, all flags are disabled.
 
i don't exactly know role of each flags. just if 0x67 crsactive config, system profiler recoginzed "SIP: disabled".
At high Sierra, the value 0x67 does not seem to be a big problem. because The 0x67 value contains the flags we need most.
as result, i think that useful values is 0x3FF to avoid any situation in future

 

from PMheart reply

Link to comment
Share on other sites
erice
erice
Posted
Posted

Anyone noticing slow boot speeds? My Computer has Sierra on a ssd and High Sierra on a Samsung 960 NVMe m.2 and booting the Sierra drive I get to the login in about 8 seconds. The High Sierra boot process takes almost 30 seconds to get to the login screen. I thought by now that High Sierra  (using DP9) that my boot time would be at least equal to or faster than the Sierra ssd. I get reads of 3000mb/s on the High Sierra drive vs 460mb/s on Sierra drive. 

 

 

Update DP9 succeed  :)  As Beta 7, Beta 8, Beta 9 not allowed Hot-swap (Hot-Plug) internal hard drive on my system.

Nobody has an answer, a tip, a suggestion for these problems, which are also my problems?

Thanks in advance.

  • Like 1
Link to comment
Share on other sites
SavageAUS
SavageAUS
Posted
Posted

okay. good script. i don't know crsutil detail. i just checked system profiler's difference on each crsutil value.

i will check more

0x67 result

Shanes-iMac:~ shane$ /Users/shane/Downloads/csrstat 
System Integrity Protection status: disabled.
 
Configuration: (0x00000067)
Apple Internal...........: disabled
Kext Signing Restrictions: disabled
Task for PID Restrictions: disabled
Filesystem Protections...: disabled
Debugging Restrictions...: enabled
DTrace Restrictions......: disabled
NVRAM Protections........: disabled
Device Configuration.....: enabled
BaseSystem Verification..: enabled
Shanes-iMac:~ shane$ 
  • Like 1
Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted

Nobody has an answer, a tip, a suggestion for these problems, which are also my problems?

Thanks in advance.

 

I found no solutions for this problem. Despite search and search on several forum.

 

Sorry for my bad english

interesting hot plug works for me beta 9

 

Can you share your EFI folder, Bios settings? I see you have an Ozmosis Bios patched, mine is not.

 

Thanks

 

Sorry for my bad english

Link to comment
Share on other sites
prud28
prud28
Posted
Posted (edited)

Wellcome

 NVOP   5b810e50 43415003 0040084c 43544c10141f5f49 4e490070 005c2f05 5f53425f50434930 52503035 50585358 5f41445214400d ----> 5b810e50 43415003 0040084c 43544c1014235f49 4e490070 005c2f05 5f53425f50434930 52503035 50585358 5f4144525f4f4646 14400d

Disable nvidia
I do not speak English
Edited by Allan
Translated
  • Like 2
Link to comment
Share on other sites
stehor
stehor
Posted
Posted

Matgen84 there is no ozmosis support on this mobo as its a 100 series board. x99/100/200 have no support so i am using clover on this rig. i have hot plug enabled on my sata 4 port in bios for hot plug

  • Like 1
Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted

Matgen84 there is no ozmosis support on this mobo as its a 100 series board. x99/100/200 have no support so i am using clover on this rig. i have hot plug enabled on my sata 4 port in bios for hot plug

 

Sorry for my mistake: I've read Osmozis in your "interest" under your avatar. Like you, I have hot plug enabled on my 6 sata port in Bios. Hot Plug work like a charm under Sierra and under High Sierra up to Developer Beta 6. Since Beta 7, don't work as I say before. 

Link to comment
Share on other sites
fusion71au
fusion71au
Posted
Posted

fusion71au, on 30 Aug 2017 - 12:51 AM, said:

snapback.png

 

Thank. I try but don't work...

 

Edit: Asmedia1061-Asmedia1062 with with AHCIPortInjector.kext. Since beta 7 and of course with Beta 8, I can no longer use the hot-plugging of internal hard drives. I can't insert HDD when High Sierra is running. Does anyone even have same problem? Hot-pluggging HDD work like a charm under Sierra.

 

 

According to kextstat, the kexts loading on my system related to AHCI are

fusion71aus-iMac:~ fusion71au$ kextstat | grep AHCI
   64    3 0xffffff7f81f3f000 0x1a000    0x1a000    com.apple.iokit.IOAHCIFamily (288) F3AC999A-975D-3D01-82D4-8ACCB4A885B1 <5 4 3 1>
   65    0 0xffffff7f82b6b000 0x14000    0x14000    com.apple.driver.AppleAHCIPort (328) 440D7F9B-DE37-375D-AFE0-EABC372B001E <64 12 5 4 3 1>
   78    0 0xffffff7f81f69000 0x27000    0x27000    com.apple.iokit.IOAHCIBlockStorage (301.1.2) 81611BFF-AE58-3937-A337-1731E734B3C2 <64 27 6 5 4 3 1>
   85    0 0xffffff7f81f5c000 0xd000     0xd000     com.apple.iokit.IOAHCISerialATAPI (267) BA23AC56-7AB4-3898-A468-B18B1550E039 <64 28 5 4 3 1>
 
Maybe try downgrading both AppleAHCIPort and IOAHCIFamily kexts to versions before DB7 (after making backups of current kexts).  Attached are AHCI kexts from High Sierra PB1_17A291m.  Note IOAHCIBlockStorage and IOAHCISerialATAPI are Plugin kexts inside IOAHCIFamily.kext.  
 
Don't forget to set correct kext permissions and rebuild caches (sudo touch /System/Library/Extensions && sudo kextcache -u /).  Can check kexts are loadable with kextutil -tn command eg
fusion71aus-iMac:~ fusion71au$ sudo kextutil -tn /System/Library/Extensions/AppleAHCIPort.kext
Password:
/System/Library/Extensions/AppleAHCIPort.kext appears to be loadable (including linkage for on-disk libraries).
 
Good Luck!

AHCI kexts from PB1_17A291m.zip

  • Like 2
Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted

 

According to kextstat, the kexts loading on my system related to AHCI are

fusion71aus-iMac:~ fusion71au$ kextstat | grep AHCI
   64    3 0xffffff7f81f3f000 0x1a000    0x1a000    com.apple.iokit.IOAHCIFamily (288) F3AC999A-975D-3D01-82D4-8ACCB4A885B1 <5 4 3 1>
   65    0 0xffffff7f82b6b000 0x14000    0x14000    com.apple.driver.AppleAHCIPort (328) 440D7F9B-DE37-375D-AFE0-EABC372B001E <64 12 5 4 3 1>
   78    0 0xffffff7f81f69000 0x27000    0x27000    com.apple.iokit.IOAHCIBlockStorage (301.1.2) 81611BFF-AE58-3937-A337-1731E734B3C2 <64 27 6 5 4 3 1>
   85    0 0xffffff7f81f5c000 0xd000     0xd000     com.apple.iokit.IOAHCISerialATAPI (267) BA23AC56-7AB4-3898-A468-B18B1550E039 <64 28 5 4 3 1>
 
Maybe try downgrading both AppleAHCIPort and IOAHCIFamily kexts to versions before DB7 (after making backups of current kexts).  Attached are AHCI kexts from High Sierra PB1_17A291m.  Note IOAHCIBlockStorage and IOAHCISerialATAPI are Plugin kexts inside IOAHCIFamily.kext.  
 
Don't forget to set correct kext permissions and rebuild caches (sudo touch /System/Library/Extensions && sudo kextcache -u /).  Can check kexts are loadable with kextutil -tn command eg
fusion71aus-iMac:~ fusion71au$ sudo kextutil -tn /System/Library/Extensions/AppleAHCIPort.kext
Password:
/System/Library/Extensions/AppleAHCIPort.kext appears to be loadable (including linkage for on-disk libraries).
 
Good Luck!

 

 

Thanks. I try this.

 

I've forgotten:  I use under Sierra and High Sierra, AHCIPortInjector.kext (Fabio version 2016) in EFI/CLOVER/KEXT and I can Hot-Plugging. It does the job now only in Sierra.

 

 

Update: with only AppleAHCIPort version 328 instead of version 329 in S/L/E and AHCIPortInjector.kext (Fabio version 2016) in EFI/CLOVER/KEXT Hot-Plug work again under High Sierra.

 

I don't know why? these two versions, both of which date back to 2016, appear to be identical. Should I do the same manipulation for the release?

  • Like 1
Link to comment
Share on other sites
macinsane
macinsane
Posted
Posted

Just an experience: I reverted back to HFS+ because Clover lost track of my APFS partion for two times now: once boot error, the other time the drive simply didn't show up. Both times out of nowhere, just after a regular shutdown. I had to reinstall DP9-update each time to get Clover recognize the drive again, using different apfs.efi's didn't make any difference. So I stay on HFS+ until the new file system proves itself reliable within the next months. 

Link to comment
Share on other sites
erice
erice
Posted
Posted

 

According to kextstat, the kexts loading on my system related to AHCI are

fusion71aus-iMac:~ fusion71au$ kextstat | grep AHCI
   64    3 0xffffff7f81f3f000 0x1a000    0x1a000    com.apple.iokit.IOAHCIFamily (288) F3AC999A-975D-3D01-82D4-8ACCB4A885B1 <5 4 3 1>
   65    0 0xffffff7f82b6b000 0x14000    0x14000    com.apple.driver.AppleAHCIPort (328) 440D7F9B-DE37-375D-AFE0-EABC372B001E <64 12 5 4 3 1>
   78    0 0xffffff7f81f69000 0x27000    0x27000    com.apple.iokit.IOAHCIBlockStorage (301.1.2) 81611BFF-AE58-3937-A337-1731E734B3C2 <64 27 6 5 4 3 1>
   85    0 0xffffff7f81f5c000 0xd000     0xd000     com.apple.iokit.IOAHCISerialATAPI (267) BA23AC56-7AB4-3898-A468-B18B1550E039 <64 28 5 4 3 1>
 
Maybe try downgrading both AppleAHCIPort and IOAHCIFamily kexts to versions before DB7 (after making backups of current kexts).  Attached are AHCI kexts from High Sierra PB1_17A291m.  Note IOAHCIBlockStorage and IOAHCISerialATAPI are Plugin kexts inside IOAHCIFamily.kext.  
 
Don't forget to set correct kext permissions and rebuild caches (sudo touch /System/Library/Extensions && sudo kextcache -u /).  Can check kexts are loadable with kextutil -tn command eg
fusion71aus-iMac:~ fusion71au$ sudo kextutil -tn /System/Library/Extensions/AppleAHCIPort.kext
Password:
/System/Library/Extensions/AppleAHCIPort.kext appears to be loadable (including linkage for on-disk libraries).
 
Good Luck!

 

 

Thanks first of all to the suggestion.
The hot plug now works; but trim activation no longer works.
???

 

Thanks first of all to the suggestion.
The hot plug now works; but trim activation no longer works.
???

 

 

AppleDataSetManagement.kext

  Dependency Resolution Failures:

  Kexts already loaded for these libraries have no OSBundleCompatibleVersion: com.apple.iokit.IOAHCIBlockStorage

  • Like 1
Link to comment
Share on other sites
fusion71au
fusion71au
Posted
Posted

Update: with only AppleAHCIPort version 328 instead of version 329 in S/L/E and AHCIPortInjector.kext (Fabio version 2016) in EFI/CLOVER/KEXT Hot-Plug work again under High Sierra.

 

I don't know why? these two versions, both of which date back to 2016, appear to be identical. Should I do the same manipulation for the release?

 

When you compare the MD5 values of the binaries inside AppleAHCIPort kexts v328 vs v329, you will find that they are different...

 

post-846696-0-67621900-1504646291_thumb.png

 

 

We will have to wait for the final release before knowing if regressing the kext still works  :).  It seems v329 is still buggy on quite a few older hardwares eg

 

 

Thanks first of all to the suggestion.
The hot plug now works; but trim activation no longer works.

 

 

  1. Downgrade only AppleAHCIPort v329 to v328 (restore original IOAHCIFamily with IOAHCIBlockStorage kext in /S/L/E, repair permissions & rebuild kext cache etc)
  2. Enable Trim with Clover KextsToPatch....

 

 

 

		<key>KextsToPatch</key>
		<array>
			<dict>
				<key>Comment</key>
				<string>TRIM Enabler</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				AEFQUExFIFNTRAA=
				</data>
				<key>Name</key>
				<string>IOAHCIBlockStorage</string>
				<key>Replace</key>
				<data>
				AAAAAAAAAAAAAAA=
				</data>
			</dict>

post-846696-0-69216800-1504647204_thumb.png

 

 

 

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