Tornadozx Posted July 17, 2015 Share Posted July 17, 2015 Hi guys, I've tried to update my 10.10.1 hack to 10.10.4 but failed with kernel panics on older chameleon and with chameleon posted on the previous page it simply hang after bluetooth controller. This how it looks with the old chameleon I use to boot up to 10.10.3 The arguments tried to boot with: -f -v -x cpus=1 npci=0x2000 npci=0x3000 Clover does not boot with sandbox deny messages (as said on the forums clover won't boot w/o caches), however I tried to use the option with patching caches on the fly - same result. With the new Chameleon it does boot without the problems in the image, however it hangs on bluetooth transport. I've tried several ways: 1. using my existing working 10.10.1 installation cloned to another HDD and applying a combo patch to 10.10.4 and gils83 package. 2. using a installed os 10.10.4 unpacked to the HDD with replaces kernel and kexts. Maybe some ideas? P.S. Can anyone tell how to rebuild the kernel caches for CLOVER from terminal from another working Mac OS? KextUtil does not seem to work... Hack CPU is A8 APU + AMD GPU Link to comment Share on other sites More sharing options...
Allan Posted July 17, 2015 Share Posted July 17, 2015 Done! Link to comment Share on other sites More sharing options...
Tornadozx Posted August 3, 2015 Author Share Posted August 3, 2015 Thanks but the solution did not work(caches) and did not fix the issue. I've fixed the permissions, so now no "omitting" messages. Boots up with newer chameleon, but then simply hangs with no HDD activity or error/panics etc. I have no more idea, either the MB or the CPU is not supported or I should try to create my own 10.10.4 usb. Will try again and report. Link to comment Share on other sites More sharing options...
Tornadozx Posted August 7, 2015 Author Share Posted August 7, 2015 I think you can close the thread, with a fresh install and trying to add the AMD kernel kext everything works. However updating a older Niresh 10.10.1 install fails with sandbox deny messages and kernel panic. Link to comment Share on other sites More sharing options...
spakk Posted August 7, 2015 Share Posted August 7, 2015 The problem has already been Discussed Sufficient and there are therefore solutions to resolve the issue on AMD.AMD issues include, Should in the page where AMD specific problems are discussed.I am of the opinion, the AMD-specific problems and questions should be asked on the right side, because it is otherwise confusing for Intel users. Link to comment Share on other sites More sharing options...
Tornadozx Posted August 8, 2015 Author Share Posted August 8, 2015 I did not get any response about my issue(Sandbox Deny), however the initial message was in AMD thread, so I don't get you. Link to comment Share on other sites More sharing options...
Recommended Posts