Jump to content
fantomas

[pre-release] macOS High Sierra

3,845 posts in this topic

Recommended Posts

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. 

Share this post


Link to post
Share on other sites
Advertisement

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

Ok.Thank you.I'll try to do the complete procedure that is more complicated and you will report

regards

Share this post


Link to post
Share on other sites

 

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

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

interesting hot plug works for me beta 9

Share this post


Link to post
Share on other sites

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$ 

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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. 

Share this post


Link to post
Share on other sites

 

i saw. also i calculated each parts. what she said is right.

crsactiveconfig is as users prefer. some users want to disable all flags, other users don't want to disable all flags.

 

at least crsactiveconfig 0x67 or over, no problem. i now used 0x67. In my case, do not need to disable all flags.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

 

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?

Share this post


Link to post
Share on other sites

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. 

Share this post


Link to post
Share on other sites

 

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

Share this post


Link to post
Share on other sites

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

 

 

 

Share this post


Link to post
Share on other sites

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

 

 

 

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

 

 

 

  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>

attachicon.gifTrim with Clover Kexts to Patch.png

 

 

 

Thanks @Fusion71au

 

Wait and see the final release.  :)

Share this post


Link to post
Share on other sites

iOS11 Beta10 comeout

 

I think osx 10.13 beta10 will comeout later.

 

从我的 iPhone 发送,使用 Tapatalk

Yeah, I think so too. Small update though, only 37,8mb for me

Share this post


Link to post
Share on other sites

Can someone help me please with an External Icon Fix for the NVMe Drive?

 

test

IONVMeFamily 4885c074 07808b20  4885c066 90808b20 NVMe drive internal

Share this post


Link to post
Share on other sites

@PMheart

DP9 seems unstable for my unsupported CPU (some random reboots)

Have you checked if something is changed in dp9 kernel for unsupported cpu?

Thank you for your precious help

:-)

Share this post


Link to post
Share on other sites

@PMheart

DP9 seems unstable for my unsupported CPU (some random reboots)

Have you checked if something is changed in dp9 kernel for unsupported cpu?

Thank you for your precious help

:-)

Hi, nice to meet you again.

I checked the kernel of DP9 just now. Unfortunately I didn't see any change related to XCPM.

Well, technically all patches are critical, you can't even boot while lacking of anyone. As for the instability, I'm not sure why. Which patches are you currently using?

 

(To avoid bothering others, let's go on in private, I've sent a PM to you.)

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

  • Recently Browsing   0 members

    No registered users viewing this page.

Announcements

  • Similar Content

    • By poisson-myfish
      So I have some less powerful hardware, that's why I'm installing High Sierra in 2020. Anyway, I'm trying to boot from the USB and I get the following errors:
      00:000 00:000 OCB: Missing DMG signature, aborting 00:585 00:585 OCB: LoadImage failed - Unsupported That's it. The logs begin and end there. The rest of the file is zeroes.
       
      Bootloader: OpenCore 0.5.9 Release
      Drivers:
      HfsPlus.efi
      OpenRuntime.efi
       
      Kexts:
      AppleALC.kext
      Lilu.kext
      RealtekRTL8111.kext
      SMCBatteryManager.kext
      SMCLightSensor.kext
      SMCProcessor.kext
      SMCSuperIO.kext
      VirtualSMC.kext
      WhateverGreen.kext
       
      ACPI:
      SSDT-EC.aml
      SSDT-HPET.aml
      SSDT-PLUG.aml
      Note: I used SSDTTime to make the DSDT dumps for this exact computer
       
      Hardware:
      Intel Core i3 (Haswell)
      An Intel VGA-Compatible Haswell iGPU
      An nVidia Geforce 920m GPU (part of the reason for installing High Sierra)
      USB: Intel 8 Series USB xHCI HC
      SATA: Intel 8 series SATA Controller
       
      If you need more details, here's my laptop https://www.asus.com/Laptops/X540LJ/ . I have the 512GB version with 4GB of RAM
       
      I found a lot of forum posts about people having the same error, except nothing solved mine. Also, I haven't found anything online about the error with the Missing DMG Signature.
       
      EDIT: If anybody needs my config.plist, feel free to ask for it and I'll happily post it
    • By PropoFlexWX4
      After hearing that OpenCore is so much better than Clover, and that it will probably be able to boot Big Sur before Clover does, I decided to take the jump.
       
      Running Catalina 10.15.5 18F101 with OC 0.5.9.
       
      So far I like the result. The OS feels faster, boots faster.
      And absolutely everything works (sleep, network, etc...)
       
      So, that's it? Is there anything else I have to do?
    • By fantomas
      macOS Big Sur beta (20A4299v)
    • By gengik84
      First beta is coming... and as always...
       

       
       
      Useful information:
      macOSDeveloperBetaAccessUtility.dmg.zip
×