Just get a USB bluetooth dongle, then once you plug it in, just go to Systems preferences and setup bluetooth. Bluetooth on hackintosh is as simple as plug n play.
So I was able to fix this by rebooting the machine from USB, then selecting my OS X installation and specifying safe mode to boot (-x -v). That got me into my system, after which I was able to run Multibeast and voila, everything works now.
Thanks to whoever mentioned about booting into USB as...
Article: OS X 10.10.1 Update
I was finally able to get my build working after the update. I booted from USB and selected my OS X drive and booted it up in safe mode. That got me into the os and was able to install multibeast.
Anyone?
My system specs:
- ASrock z77 Pro3
- Intel Ivy Bridge i5 (using Intel HD4000)
- No discrete graphics
I've also tried the following: -x -v -f GraphicsEnabler=No PCIRootUID=0 cpus=1 npci=0x2000
and that doesn't work either.
I had 10.10 working well with most everything working, but like always I have trouble getting back into the system after software updates. After installing the 10.10.1 update, the systems hangs on reboot. I've tried the following options but no luck: -x -v
Can anyone give some other options...
Never mind my last post, I just had to go to the Output tab and select internal speakers, and then I could control the output volume. Works like a champ!
Thanks for posting your solution and seems to work for my ASRock z77 Pro board (same drivers tho).
Having said that the volume is extremely low compared to my previous mavericks setup. Have you noticed the same issue as well? My internal sound is completely maxed out and I can barely hear it.
Thanks for the responses guys!! In my case it was an issue with the my HDMI port on my case. I tried replugging it back it and it worked (seems to happen from time to time).
Also wanted to add that this started happening after the 5.0.1 update. It was working fine with the 5.0 version (at least i could install, booting yosemite on its own was a whole another issue).
I have the exact problem. Booting with -v simply stops sending signal to the monitor and goes to sleep. I believe the last step was something along the lines of power management incomplete (couldn't read it because the screen went blank right after).
I basically started with a fresh copy of...
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.