Cyberdevs Posted September 2, 2017 Share Posted September 2, 2017 Hi Guys would appreciate any help. I'm getting a kernel panic as attached when booting the installer for High Sierra dev beta 9. I've tried also tried the Public beta. USB installer with createinstallmedia Clover r4189 Only FakeSMC kext (no plugins) in Other apfs.efi from BaseSystem in drivers64UEFI Boot arguments: -v kext-dev-mode=1 maxmem=4096 BIOS options: XMP Memory - Profile1 Internal Graphics: Disabled xHCI - Auto xHCI Hand-off / EHCI Hand-off - Enabled OS Type: Other Boot mode selection: UEFI Only VT-d - Disabled EFI with debug.log attached and specs are in my sig. Make sure you have SerialIO disabled and use this efi and see if you can boot using it. Update: Also set xHCI to enabled aushack-EFI.zip 1 Link to comment Share on other sites More sharing options...
aushack Posted September 2, 2017 Share Posted September 2, 2017 I'm not sure as related by ergo before #3414 r4189 is the good choice. I stayed on r4184 too with no issue. (perhaps r4187 that I have tested too) You need to add some kexts as tell Chris1111 : FakeSMC_CPUSensors.kext FakeSMC_GPUSensors.kext Perhaps Nulcpupowermanagement You can also put on ACPI/origin/ your DSDT and in patched your SSDT Thanks! Tried adding those sensor plugins to FakeSMC and adding Nullcpupowermanagement.kext and same issue. I don't use a DSDT with my Yosemite main install. Before I tried using my SSDT in ACPI/Patched and same issue so I am not using it in the installer now. Edit: Tried using my SSDT in ACPI/Patched and same as attached Make sure you have SerialIO disabled and use this efi and see if you can boot using it. Update: Also set xHCI to enabled Thanks! Serial port already disabled (updated OP) and set xHCI to Enabled. Tried your EFI and I get the attached. It's something! Link to comment Share on other sites More sharing options...
Cyberdevs Posted September 2, 2017 Share Posted September 2, 2017 Thanks! Tried adding those sensor plugins to FakeSMC and adding Nullcpupowermanagement.kext and same issue. I don't use a DSDT with my Yosemite main install. Before I tried using my SSDT in ACPI/Patched and same issue so I am not using it in the installer now. Edit: Tried using my SSDT in ACPI/Patched and same as attached Thanks! Serial port already disabled (updated OP) and set xHCI to Enabled. Tried your EFI and I get the attached. It's something! Remove the OSXAptiofixDrv.efi from /EFI/Clover/drivers64UEFI and add the OSXAptiofixDrv2.efi that you already have in your EFI folder. Link to comment Share on other sites More sharing options...
aushack Posted September 2, 2017 Share Posted September 2, 2017 Removed OSXAptiofixDrv and used OSXAptiofixDrv2 and gets stuck on the attached. Also now my BIOS seems to screw up after booting the installer. I have to load optimised defaults and set my options back to boot into my main install. Link to comment Share on other sites More sharing options...
Cyberdevs Posted September 2, 2017 Share Posted September 2, 2017 try this config. config.plist.zip Link to comment Share on other sites More sharing options...
aushack Posted September 2, 2017 Share Posted September 2, 2017 Now it gets the same kernel panic as my OP Thanks a lot for your help so far Link to comment Share on other sites More sharing options...
Cyberdevs Posted September 2, 2017 Share Posted September 2, 2017 Now it gets the same kernel panic as my OP Thanks a lot for your help so far Well this process can be a little bit daunting so let's continue our tests in PM. I don't want to make a mess here with the EFI folders and config files Link to comment Share on other sites More sharing options...
pinarek Posted September 2, 2017 Share Posted September 2, 2017 Other Problem: Xtrafinder from trankyman is expired. Build 0.26 Info Message coms from 01.09.2017 Will trankyman a new Build Write ? Link to comment Share on other sites More sharing options...
Derty Posted September 2, 2017 Share Posted September 2, 2017 Update DP9 succeed As Beta 7, Beta 8, Beta 9 not allowed Hot-swap (Hot-Plug) internal hard drive on my system. well then it is not a personal problem ... Link to comment Share on other sites More sharing options...
brumas Posted September 2, 2017 Share Posted September 2, 2017 If you look at your own preboot.log, you can see that you didn't disable CsmVideoDxe-64. 0:270 0:001 Loading CsmVideoDxe-64.efi status=Success You also have kexts in your Other folder that are loading when you said you just used FakeSMC and VoodooPS2Controller. 33:607 0:012 Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\Other 33:607 0:000 Extra kext: EFI\CLOVER\kexts\Other\ACPIBatteryManager.kext 33:660 0:053 Extra kext: EFI\CLOVER\kexts\Other\Lilu.kext 33:677 0:016 Extra kext: EFI\CLOVER\kexts\Other\IntelGraphicsFixup.kext 33:688 0:011 Extra kext: EFI\CLOVER\kexts\Other\AppleBusPowerControllerEC0.kext 33:706 0:017 Extra kext: EFI\CLOVER\kexts\Other\FakeSMC.kext 33:725 0:019 Extra kext: EFI\CLOVER\kexts\Other\AsusNBFnKeys.kext 33:738 0:013 Extra kext: EFI\CLOVER\kexts\Other\VoodooI2C.kext 33:766 0:028 Extra kext: EFI\CLOVER\kexts\Other\RealtekRTL8111.kext 33:781 0:015 Extra kext: EFI\CLOVER\kexts\Other\VoodooPS2Controller.kext 33:787 0:005 Extra PlugIn kext: EFI\CLOVER\kexts\Other\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Keyboard.kext 33:827 0:039 Extra PlugIn kext: EFI\CLOVER\kexts\Other\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Mouse.kext 33:856 0:029 Extra PlugIn kext: EFI\CLOVER\kexts\Other\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Trackpad.kext 33:902 0:045 Extra kext: EFI\CLOVER\kexts\Other\VoodooHDA.kext Keep working at this. It look me 6 days to figure out what I needed to do and to actually do it. If it helps, compare your preboot.log with mine. mnfesq.bootlog.log.txt Mine's pretty messy. You can see that I start using one config.plist (which I use for Sierra) and switched to a different config.plist to boot to High Sierra. You can also see that I have multiple DSDT files and use DSDT.aml to boot to Sierra and DSDT1.aml to boot to High Sierra. I have to have separate DSDT files because, when I disable my Radeon GPU in my DSDT, I get a KP in Sierra but HAVE TO disable my Radeon GPU in order to get High Sierra to boot. with the help of friends I managed to overcome the error setting is necessary to disable the built-in video and right now I have 9 beta. 1 Link to comment Share on other sites More sharing options...
Matgen84 Posted September 2, 2017 Share Posted September 2, 2017 well then it is not a personal problem ... What do you mean by that? Link to comment Share on other sites More sharing options...
chris1111 Posted September 2, 2017 Share Posted September 2, 2017 Hola Update fine from Cancun Mexico HP Probook 6570B Also downloading Installer Beta -9 short trip one week here 7 Link to comment Share on other sites More sharing options...
Derty Posted September 2, 2017 Share Posted September 2, 2017 Hola Update fine from Cancun Mexico HP Probook 6570B Also downloading Installer Beta -9 short trip one week here Go to see Chichen itza!!!! I love mexico...!!!!! What do you mean by that? my grammar is not good .... I have the same problem. 2 Link to comment Share on other sites More sharing options...
Matgen84 Posted September 2, 2017 Share Posted September 2, 2017 my grammar is not good .... I have the same problem. If I found a solution, I post in this thread. Sorry for my bad english Link to comment Share on other sites More sharing options...
pinarek Posted September 2, 2017 Share Posted September 2, 2017 I also had the same problem with my Laptop Medion with the hot-plug of the eSata-SSD in DP9. Link to comment Share on other sites More sharing options...
BALDY_MAN Posted September 2, 2017 Share Posted September 2, 2017 HOW I INSTALED DP9 disabled patched webdriver onDP8 installed DP9 from updates. reloaded patched kext. Apple GraphicsControler.kext NVDAStartupWebkext. with kext wizard. and Restarted. Enabled patched webdriver 1 Link to comment Share on other sites More sharing options...
alfaSZ Posted September 2, 2017 Share Posted September 2, 2017 For both of you, I had the same problem as you and fixed it. I had to remove my discreet GPU from my DSDT so that only the Intel HD GPU shows up in System Info. I also had to remove my custom SSDT and let Clover make my SSDT (Generate PStates, Generate CStates, Enable C7) It took a while to get this right but it worked for me. I have the same problem but I only have 2 discreet GPUs - no internal Intel HD to fall back on. It appeared around dp5 or dp6 just like for the earlier cases mentioned... Do we know what exactly is causing it? Anyone else care to comment? Link to comment Share on other sites More sharing options...
dehjomz Posted September 2, 2017 Share Posted September 2, 2017 I have the same problem but I only have 2 discreet GPUs - no internal Intel HD to fall back on. It appeared around dp5 or dp6 just like for the earlier cases mentioned... Do we know what exactly is causing it? Anyone else care to comment? I have two discrete GPUs, a 1080ti in slot 0 with no drivers for high Sierra beta and a old 660ti in slot 1. I do it this way since the osx has built in osx acceleration for the 660ti and using the 10.12.6 webdrivers on 10.13 was a nightmare for me. In prior betas, high Sierra would not boot at all if two discrete were in my system. It was so bad that Intel graphics 530 wouldn't load at all if a discrete card was in my system. But as of DP8, two discrete cards can (again) coexist peacefully. But what happens now is that the window server doesn't load on the card without a driver (my 1080ti). So since that card is in slot 0, the motherboard routes the boot-time video thru it. So after clover boots from the 1080ti, the verbose-mode output stops at gIOScreenLockState, and it would appear that the system has hanged. But that's not the case. Instead the window server loads on the 660ti that has built in acceleration . So I just switch monitor inputs to the 660ti card and I'm good to go. 1 Link to comment Share on other sites More sharing options...
alfaSZ Posted September 2, 2017 Share Posted September 2, 2017 I have two discrete GPUs, a 1080ti in slot 0 with no drivers for high Sierra beta and a old 660ti in slot 1. I do it this way since the osx has built in osx acceleration for the 660ti and using the 10.12.6 webdrivers on 10.13 was a nightmare for me. In prior betas, high Sierra would not boot at all if two discrete were in my system. It was so bad that Intel graphics 530 wouldn't load at all if a discrete card was in my system. But as of DP8, two discrete cards can (again) coexist peacefully. But what happens now is that the window server doesn't load on the card without a driver (my 1080ti). So since that card is in slot 0, the motherboard routes the boot-time video thru it. So after clover boots from the 1080ti, the verbose-mode output stops at gIOScreenLockState, and it would appear that the system has hanged. But that's not the case. Instead the window server loads on the 660ti that has built in acceleration . So I just switch monitor inputs to the 660ti card and I'm good to go. Hmm interesting. I guess I'm out of luck with two GTX 1080s then?.. They did work up until dp6 is the annoying thing Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
dehjomz Posted September 2, 2017 Share Posted September 2, 2017 Hmm interesting. I guess I'm out of luck with two GTX 1080s then?.. They did work up until dp6 is the annoying thing Sent from my iPhone using Tapatalk Have you tried using the 10.12.6 webdrivers? I tried them briefly and although acceleration sucked, both discrete cards would load and system would even sleep. I suspect if/when Nvidia releases High siera webdrivers things will be back to normal. Link to comment Share on other sites More sharing options...
alfaSZ Posted September 2, 2017 Share Posted September 2, 2017 Have you tried using the 10.12.6 webdrivers? I tried them briefly and although acceleration sucked, both discrete cards would load and system would even sleep. I suspect if/when Nvidia releases High siera webdrivers things will be back to normal. Yes I had been using them until dp5. But even without them I could go through the high sierra install using basic vga drivers, and install them afterwards Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
dehjomz Posted September 2, 2017 Share Posted September 2, 2017 Yes I had been using them until dp5. But even without them I could go through the high sierra install using basic vga drivers, and install them afterwards Sent from my iPhone using Tapatalk Interestingly for me, the installer works (with both cards installed) by using VGA mode on the 1080ti (in slot 0), but not on the main installation. Weird. Also, using nv_disable=1 boot flag to force VGA graphics causes the webserver to infinitely crash/respawn. But what I do is after an update, use Lilu/NvidiaGraphicsFixup to boot into the OS and then run AGDPFIX. For me, Lilu is unstable on high Sierra and causes kernel panics randomly so I don't use it. Link to comment Share on other sites More sharing options...
alfaSZ Posted September 2, 2017 Share Posted September 2, 2017 Interestingly for me, the installer works (with both cards installed) by using VGA mode on the 1080ti (in slot 0), but not on the main installation. Weird. Also, using nv_disable=1 boot flag to force VGA graphics causes the webserver to infinitely crash/respawn. But what I do is after an update, use Lilu/NvidiaGraphicsFixup to boot into the OS and then run AGDPFIX. For me, Lilu is unstable on high Sierra and causes kernel panics randomly so I don't use it. So in other words this is just a different manifestation of the usual MacPro6,1 AGDP issue? I'll try booting with MacPro5,1 to check .. Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
dehjomz Posted September 2, 2017 Share Posted September 2, 2017 So in other words this is just a different manifestation of the usual MacPro6,1 AGDP issue? I'll try booting with MacPro5,1 to check .. Possibly. Real empiricists test! I'm using iMac17,1 so I have the black screen issue after each update. Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
sandro_desktop Posted September 2, 2017 Share Posted September 2, 2017 Yes still getting (macbook-pro.home.com.apple.xpc.launchd[1] (com.apple.windowserver) <notice>: service only ran for 8 seconds. Pushing respawn out by 10 seconds) on high Sierra Beta 7 with laptop HD4600 hi niknod, I had the same problem, and I've solved it by patching DSDT and SSDTs, following RehabMan's guides: VERY IMPORTANT: PLEASE READ! (ABOUT TONYMACX86 AND iATKOS M / Y / EC / SR) Why InsanelyMac does not support tonymacx86 cheers! Link to comment Share on other sites More sharing options...
Recommended Posts