SavageAUS Posted July 15, 2017 Share Posted July 15, 2017 My resolution is Full HD. Yeah. Still have B.I issue. Badruzeus mentioned this http://www.insanelymac.com/forum/index.php?/topic/324194-[pre-release]-macOS-High-Sierra#entry2462366 B.I issue seems as HS bug. 나의 LG-F800S 의 Tapatalk에서 보냄 Yes i seen that but i thought i might have found something but i didn't lol. I have only a 1366 x 768 screen so i installed switchresx and after reboot on HS my BI appeared. But it broke sleep. Link to comment Share on other sites More sharing options...
Badruzeus Posted July 15, 2017 Share Posted July 15, 2017 I have only a 1366 x 768 screen so i installed switchresx and after reboot on HS my BI appeared. But it broke sleep. My native disp reso is also 1366x768 and I use overrides method generated by FixEDID v2.3.0, but for battery issue is still same. So I think we need to wait till (maybe) next Monday for DP4 release but I'm not sure.. 1 Link to comment Share on other sites More sharing options...
SavageAUS Posted July 15, 2017 Share Posted July 15, 2017 My native disp reso is also 1366x768 and I use overrides method generated by FixEDID v2.3.3, but for battery issue is still same. So I think we need to wait till (maybe) next Monday for DP4 release but I'm not sure.. Do you have a guide for overriding the display resolution? Link to comment Share on other sites More sharing options...
Badruzeus Posted July 15, 2017 Share Posted July 15, 2017 Do you have a guide for overriding the display resolution? a little bit OOT here... I'm sure this one is still works well, on my case I have no issue with disp reso.. but only "glitch (a not smooth color transition)" if not using "MBA Display Data". I also need it for including "Display Name, Color Profile, Gamma, etc" right from DisplayOverride file, so mine looks a "Real" Mac Display.. :LoL Link to comment Share on other sites More sharing options...
crazybirdy Posted July 15, 2017 Share Posted July 15, 2017 If is anyone interested I installed with Core.pkg method and replaced AppleAHCIPort.kext from S/L/E with the one from Sierra 10.12.6 DB6. But isn't a really fix because can't be installed with the installer. 10.13.pb1 works fine here, but the db3 original installer is dead here too. I have the same problem of Still waiting for root device as yours, and need to replace AppleAHCIPort.kext from S/L/E with 10.13.pb1. I use clover + pk to install 13.db3 to MBR hdd fine, here is howto rebuild pk. 1. restore BaseSystem.dmg to a partition. 2. copy /System/Library/Kernels/kernel from Core.pkg 3. replace all SLE from Core.pkg. 4. replace AppleAHCIPort.kext with 10.13.pb1 5. sudo kextcache -u /Volumes/1013db3 (works fine under 10.11.6.) Then, you get new prelinkedkernel to boot the installer now. Just replace to be the new prelinkedkernel as you needed. 2 Link to comment Share on other sites More sharing options...
Matgen84 Posted July 15, 2017 Share Posted July 15, 2017 Oh, I'm sorry, I have 2 dsdt, one with Langur that I use with the patch in config and working fine on Sierra and this DSDT2 that I use with Uakari(only dvi working) to test high sierra. I get DB3 working on my pc, but I still can't use it as daily because sleep isn't working, don't know why sleep isn't working for me on HS, also not working on HDX 16... If is anyone interested I installed with Core.pkg method and replaced AppleAHCIPort.kext from S/L/E with the one from Sierra 10.12.6 DB6. But isn't a really fix because can't be installed with the installer. Also I need to remove AppleGFXHDA and replace graphics kexts to get it working, probably my hack will never run HS properly. Also I don't know why sleep isn't working on my HDX, I don't need to do anything special to make it working, in Yosemite, El Capitan and Sierra the sleep is working fine, but with HS it enters sleep and when I try to wake I get reboot. Did you try this method call "newCore" for unsupported macs from macrumors site. You can't create flash drive. See here: https://forums.macrumors.com/threads/macos-high-sierra-10-13-unsupported-macs-thread.2048478/page-4#post-24671216 Link to comment Share on other sites More sharing options...
KGP-iMacPro Posted July 15, 2017 Share Posted July 15, 2017 Hi. Sure. Here you are: First of all. Both Haswell-E and Ivy Bridge don't need to patch _cpuid_set_info(). # Haswell-E # _xcpm_bootstrap 89 d8 04 c4 3c 22 77 22 -> 89 d8 04 c1 3c 22 77 22 # Ivy Bridge # _xcpm_bootstrap 89 d8 04 c4 3c 22 77 22 -> 89 d8 04 c6 3c 22 77 22 And also, don't forget to add necessary instant reboot fix patches! Absolutely gorgeous, man! Many, many thanks indeed! May I ask one last question? What about Skylake-X and X299? Any FakeCPUID, KextToPatch and XCPM KernelToPatch entries yet for 10.13? Cheers, KGP 2 Link to comment Share on other sites More sharing options...
PMheart Posted July 16, 2017 Share Posted July 16, 2017 Absolutely gorgeous, man! Many, many thanks indeed! May I ask one last question? What about Skylake-X and X299? Any FakeCPUID, KextToPatch and XCPM KernelToPatch entries yet for 10.13? Cheers, KGP As for SKL-X. Here you are: // KernelToPatch # _cpuid_set_info 75 00 04 72 3c d0 77 50 0f b6 c0 -> 75 00 04 7b 3c d0 77 50 0f b6 c0 # _xcpm_bootstrap 89 d8 04 c4 3c 22 77 22 -> 89 d8 04 cd 3c 22 77 22 And check instant reboot fix patches on http://www.insanelymac.com/forum/topic/324194-pre-release-macos-high-sierra/page-3?do=findComment&comment=2435885 Or. You could also try FakeCPUID = 0x506e3 with reboot fix patches. But I don't recommend this. 2 Link to comment Share on other sites More sharing options...
KGP-iMacPro Posted July 16, 2017 Share Posted July 16, 2017 As for SKL-X. Here you are: // KernelToPatch # _cpuid_set_info 75 00 04 72 3c d0 77 50 0f b6 c0 -> 75 00 04 7b 3c d0 77 50 0f b6 c0 # _xcpm_bootstrap 89 d8 04 c4 3c 22 77 22 -> 89 d8 04 cd 3c 22 77 22 And check instant reboot fix patches on http://www.insanelymac.com/forum/topic/324194-pre-release-macos-high-sierra/page-3?do=findComment&comment=2435885 Or. You could also try FakeCPUID = 0x506e3 with reboot fix patches. But I don't recommend this. Excellent, man! Thanks a lot again... you definitely saved my day! Great work! 2 Link to comment Share on other sites More sharing options...
chris1111 Posted July 16, 2017 Share Posted July 16, 2017 I would not be surprised if apple want to completely eliminate HFS + J in the macOS High Sierra He could do it quickly APFS is better to get used to it quickly Link to comment Share on other sites More sharing options...
KGP-iMacPro Posted July 16, 2017 Share Posted July 16, 2017 As for SKL-X. Here you are: // KernelToPatch # _cpuid_set_info 75 00 04 72 3c d0 77 50 0f b6 c0 -> 75 00 04 7b 3c d0 77 50 0f b6 c0 # _xcpm_bootstrap 89 d8 04 c4 3c 22 77 22 -> 89 d8 04 cd 3c 22 77 22 And check instant reboot fix patches on http://www.insanelymac.com/forum/topic/324194-pre-release-macos-high-sierra/page-3?do=findComment&comment=2435885 Or. You could also try FakeCPUID = 0x506e3 with reboot fix patches. But I don't recommend this. Another last question Can you please explain the function of your last patch and what would be the right comment entry?: BE 0B 00 00 00 5D E9 08 00 00 00 0F 1F 84 00 00 00 00 00 55 48 89 E5 41 57 -> BE 0B 00 00 00 5D E9 08 00 00 00 0F 1F 84 00 00 00 00 00 C3 48 89 E5 41 57 I mean, you do have already the xcpm_SMT_scope_msrs patch be0b0000 005de908 000000 -> be0b0000 005dc390 909090 with a different replacement. Thus this last part still appears confusing to me. Thanks for clarification, man! Cheers, KGP Link to comment Share on other sites More sharing options...
PMheart Posted July 16, 2017 Share Posted July 16, 2017 Another last question Can you please explain the function of your last patch and what would be the right comment entry?: BE 0B 00 00 00 5D E9 08 00 00 00 0F 1F 84 00 00 00 00 00 55 48 89 E5 41 57 -> BE 0B 00 00 00 5D E9 08 00 00 00 0F 1F 84 00 00 00 00 00 C3 48 89 E5 41 57 I mean, you do have already the xcpm_SMT_scope_msrs patch be0b0000 005de908 000000 -> be0b0000 005dc390 909090 with a different replacement. Thus this last part still appears confusing to me. Thanks for clarification, man! Cheers, KGP Hi. Sure. BE 0B 00 00 00 5D E9 08 00 00 00 0F 1F 84 00 00 00 00 00 55 48 89 E5 41 57 -> BE 0B 00 00 00 5D E9 08 00 00 00 0F 1F 84 00 00 00 00 00 C3 48 89 E5 41 57 Like I wrote. This will disable the call entirely. Look. All calls and jumps (_xcpm_SMT_scope_msrs _xcpm_core_scope_msrs _xcpm_pkg_scope_msrs) are going to 0xffffff80003d0d20, which is a push. So simply replacing it with a ret(urn) instruction will make all these calls/jumps nonsense. And also. "e9 08 00 00 00" jumps to 0xffffff80003d0d20 as well, which ignores that nop. (0f 1f 84 00 00 00 00 00) If you just want to disable this MSR only, then you can replacing with a single retq and filling the rest bytes with nop. (Like I did, "e9 08 00 00 00 -> c3 90 90 90 90") Link to comment Share on other sites More sharing options...
Orion's Sword Posted July 16, 2017 Share Posted July 16, 2017 As for SKL-X. Here you are: // KernelToPatch # _cpuid_set_info 75 00 04 72 3c d0 77 50 0f b6 c0 -> 75 00 04 7b 3c d0 77 50 0f b6 c0 # _xcpm_bootstrap 89 d8 04 c4 3c 22 77 22 -> 89 d8 04 cd 3c 22 77 22 And check instant reboot fix patches on http://www.insanelymac.com/forum/topic/324194-pre-release-macos-high-sierra/page-3?do=findComment&comment=2435885 Or. You could also try FakeCPUID = 0x506e3 with reboot fix patches. But I don't recommend this. What about KBL? Link to comment Share on other sites More sharing options...
PMheart Posted July 16, 2017 Share Posted July 16, 2017 What about KBL? KBL is supported natively. No need to patch anything. Link to comment Share on other sites More sharing options...
Orion's Sword Posted July 16, 2017 Share Posted July 16, 2017 KBL is supported natively. No need to patch anything. I keep getting this on my KBL laptop: Do yo have any idea why? Here's the link to my current config.plist and preboot.log Link to comment Share on other sites More sharing options...
PMheart Posted July 16, 2017 Share Posted July 16, 2017 I keep getting this on my KBL laptop: Do yo have any idea why? Here's the link to my current config.plist and preboot.log Looks like a kernel error, but sorry I have no idea why this occurs. Link to comment Share on other sites More sharing options...
azlvda Posted July 16, 2017 Share Posted July 16, 2017 I keep getting this on my KBL laptop: Do yo have any idea why? Here's the link to my current config.plist and preboot.log hi, try to drop BGRT table <key>DropTables</key> <array> <dict> <key>Signature</key> <string>BGRT</string> </dict> </array> 2 Link to comment Share on other sites More sharing options...
Orion's Sword Posted July 16, 2017 Share Posted July 16, 2017 hi, try to drop BGRT table <key>DropTables</key> <array> <dict> <key>Signature</key> <string>BGRT</string> </dict> </array> Thanks, it worked! 2 Link to comment Share on other sites More sharing options...
kosakgroove Posted July 16, 2017 Share Posted July 16, 2017 Hi guys, I am using developer beta 3 successfully and all is working, the only thing being random issues entering sleep mode , but most the time sleep is perfect. I have noticed something funny, I am using a GUID scheme with a Triple boot and APFS , with Recovery HD Last login: Sun Jul 16 13:24:12 on console MacBook-Pro-de-Joe:~ joe$ sudo diskutil list Password: /dev/disk0 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *1.0 TB disk0 1: EFI EFI 209.7 MB disk0s1 2: Apple_APFS Container disk1 528.9 GB disk0s2 3: Apple_KernelCoreDump 655.4 MB disk0s3 4: Microsoft Reserved 16.8 MB disk0s4 5: Microsoft Basic Data Windows 344.6 GB disk0s5 6: Linux Filesystem 125.8 GB disk0s6 /dev/disk1 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +528.9 GB disk1 Physical Store disk0s2 1: APFS Volume Macintosh HD 371.5 GB disk1s1 2: APFS Volume VM 6.4 GB disk1s2 3: APFS Volume Preboot 28.5 MB disk1s3 4: APFS Volume Recovery 506.7 MB disk1s4 MacBook-Pro-de-Joe:~ joe$ I have noticed a funny entry in my Clover GUI, I was prompted to enable FileVault but I didn't since I know it may cause problems. I am able to boot from all entries in the pic (???????) My question is, can I enable FileVault since I am in APFS??? This is an Asus X550LDV SMBIOS MacbookPro11,2 Thanks for your hard work guys Link to comment Share on other sites More sharing options...
arsradu Posted July 16, 2017 Share Posted July 16, 2017 Hi guys, I am using developer beta 3 successfully and all is working, the only thing being random issues entering sleep mode , but most the time sleep is perfect. I have noticed something funny, I am using a GUID scheme with a Triple boot and APFS , with Recovery HD Screen Shot 2017-07-16 at 13.31.04.png Last login: Sun Jul 16 13:24:12 on console MacBook-Pro-de-Joe:~ joe$ sudo diskutil list Password: /dev/disk0 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *1.0 TB disk0 1: EFI EFI 209.7 MB disk0s1 2: Apple_APFS Container disk1 528.9 GB disk0s2 3: Apple_KernelCoreDump 655.4 MB disk0s3 4: Microsoft Reserved 16.8 MB disk0s4 5: Microsoft Basic Data Windows 344.6 GB disk0s5 6: Linux Filesystem 125.8 GB disk0s6 /dev/disk1 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +528.9 GB disk1 Physical Store disk0s2 1: APFS Volume Macintosh HD 371.5 GB disk1s1 2: APFS Volume VM 6.4 GB disk1s2 3: APFS Volume Preboot 28.5 MB disk1s3 4: APFS Volume Recovery 506.7 MB disk1s4 MacBook-Pro-de-Joe:~ joe$ I have noticed a funny entry in my Clover GUI, I was prompted to enable FileVault but I didn't since I know it may cause problems. I am able to boot from all entries in the pic (???????) screenshot1.png screenshot2.png My question is, can I enable FileVault since I am in APFS??? This is an Asus X550LDV SMBIOS MacbookPro11,2 Thanks for your hard work guys FileVault works with APFS, as well. So, I see no reason why not. Just make sure you have all the files you need for FileVault in the first place. Keyboard driver in particular. Check this out for more info: http://www.insanelymac.com/forum/topic/317290-filevault-2/ 1 Link to comment Share on other sites More sharing options...
cecekpawon Posted July 16, 2017 Share Posted July 16, 2017 Thanks, it worked! Would you please share your untouched BGRT? Thanks Link to comment Share on other sites More sharing options...
pinarek Posted July 16, 2017 Share Posted July 16, 2017 Does it actually with you from iTunes and filmtrailer? Despite bootargs -alcbeta -lilubeta -shikibeta the hackintosh hangs up immediately when one A filmtrailer wants to play. I also installed the IntelGraphicsDVMTFixup.kext in S / L / E. Refers to High Sierra Beta3 17a306f Link to comment Share on other sites More sharing options...
Orion's Sword Posted July 16, 2017 Share Posted July 16, 2017 Would you please share your untouched BGRT? Thanks As RehabMan said, this problem is due to non-ASCII characters in various ACPI table headers (ie. MATS, BGRT, etc). Here's the file you've requested: BGRT.aml Link to comment Share on other sites More sharing options...
Orion's Sword Posted July 16, 2017 Share Posted July 16, 2017 I installed High Sierra on an empty SSD formatted as APFS. It mounts and boots fine, but when Clover is scanning for entries it shows me nx_dev_init:705: Warning: superblock indicates jumpstart record but this driver was not loaded from that partition container_kb_get:544: Invalid on disk range pr_start_paddr 0 pr_block_count 0 keybag_operation:353: missing APFS/Container keybag (2) apfs_keybag_get:831: Failed to get apfs volume keybag, err = 2 er_state_obj_get_for_recovery:3539: No ER state object - rolling is not happening, nothing to recover APFSStart:1132: Mounting with apfs_efi_osx-621.0.0.1.32 efi_container_create:795: -efi_container_create, Status = 0000000000000007 and macOS is showing me the exact same thing in verbose mode. Anyone else with this issue or is it normal? I'm also having this in Clover and during boot. Link to comment Share on other sites More sharing options...
cecekpawon Posted July 16, 2017 Share Posted July 16, 2017 @Muntashir MEGA thanks brother! The problem remains the same 1 Link to comment Share on other sites More sharing options...
Recommended Posts