Yes i know this, but i am not sure on how to properly insert it in the bootlist file.
Thats why i wanted to see a picture, or a copy paste of your entire code.
I dont know how to write and where.
<key> yaddayadda <key>
<yes> etc etc??
Add -v so you can see where you get stuck.
The debug=0x14e was needed for some specific asus boards and is not necessarily needed for you, try looking in the successful gigabyte threads for installmethods
I mean, how do i insert the debug=0x14e into the kernelfile, im kinda noob so i dont wanna mess anything up. So i asked for a screenshot of your kernelfile/bootfile? So i dont have to write debug=0x14e everytime i boot the os, thanks.
Ps its great that you are trying to narrow it down a bit...
Thanks for sharing that fuzzypanda, i know that it didnt work without me repairing permissions on the unibeast USB using johnkellers guide, so its an important step.
I finished the install yesterday, successfuly because someone found a solution here in another thread.
The trick to boot into osx 10.10 after installing, without -x (safe mode) was to add: debug=0x14e to the kernelflags.
Read about it here...
I was about to give up on this installmethod completely, because i know too little about making a hack, so it takes forever to get information for me. And everyone else has different boards than x99-e WS.
I have gotten further, installed the OS, ran multibeast, added bootflags with chameleonwizard, but i could only boot with -x until you posted this magnificent little line of letters that solved my headache that i had for 1 month with this motherboard.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.