steve-tmq Posted February 1, 2018 Share Posted February 1, 2018 Hi to you all. Let me give you some background before I ask my question. I am writing this on a Lenovo G50-70 i3 running Maverics so the kernel had to be patch and I needed the boot flags cpus=1 dart=0 VT-d.I'v said all this so you know the experience I have. I now have a Gigabyte B85M-D3H with Intel G3220 CPU and 2Gb RAM. I have tried Maverics and Mountain Lion using myHack. Both reboot at the same place; when using boot flag -v I get screen after screen showing its reading the kext's then just as the last one is read the system reboots. If i don't use the -v option I get a blank screen for 2 seconds or so and then the apple logo on gray screen comes up and system reboots after less than a second.I'v tried boot flags cpus=1 dart=0 VT-d PCIRoot=1 in differient(sorry for the spelling I am dyslexic..) combinationsDose any one have any ideas for me to try? Link to comment Share on other sites More sharing options...
Moderators Jake Lo Posted February 1, 2018 Moderators Share Posted February 1, 2018 You need a patched kernel for myHack or enable KernelPM for Clover ConfigLook here under Min Requirement for MacOS and the patched kernelsYour Haswell system require a minimum of 10.8.5, I suggest you go with 10.9.x Link to comment Share on other sites More sharing options...
steve-tmq Posted February 1, 2018 Author Share Posted February 1, 2018 Thank you for your help but I think you have misread my post and jumped in with the obvious answer 10.9 with a patched kernel was the first install I tried because its the one I installed on my laptop. As I said in my post, The problem I am having is NOT the haswell early reboot problem that is fixed by the patch.The symptoms of the haswell early boot problem are different. With the haswell the kernel reboots before the kext's are read. the problem I am having is after the kext's are read as seen when using the -v flag.I moved to an older version of OS X (10.8) because the G3220 is older than the i3 I have in the laptop and as the (10.9) patched kernel did not work I thought it was too new. Link to comment Share on other sites More sharing options...
Moderators Jake Lo Posted February 1, 2018 Moderators Share Posted February 1, 2018 With the Clover boot disk, boot with verbose + debug 0x100 mode The debug 0x100 will not reboot the system on KP or error Post the KP for review Link to comment Share on other sites More sharing options...
steve-tmq Posted February 2, 2018 Author Share Posted February 2, 2018 myHack makes a "chameleon" boot disk. Dose debug 0x100 work in chameleon and do you no how to set it? What do you type on the boot options line. "-v cpus=1 dart=0 VT-d" do you add "debug=0x100" or "?" Link to comment Share on other sites More sharing options...
Administrators Bronxteck Posted February 4, 2018 Administrators Share Posted February 4, 2018 gees its been a while... it might be debug=0x100 like you stated. here is a list Link to comment Share on other sites More sharing options...
Recommended Posts