• 0

Yosemite installer failing to boot, regardless of kernel or flags used
3 3

Question

I have tried pretty much all the AMD kernels and combinations of flags without being able to reach the Yosemite installer

 

I am trying to get this to install on an HP Pavillion DV5 AMD laptop.

 

Here is a video under of it hanging (it always hangs at the same place and in the same way with all kernels)

http://youtu.be/x7yJrG70mxY

Share this post


Link to post
Share on other sites

6 answers to this question

  • 0

@Jaco2K: Have you found a solution? Cos even I face the exact issue in my PC as well :(

 

CPU (Intel i7 4790K 4GHZ)
Motherboard (Asus Z97 pro (wi-fi ac))
Grpahics Card (Asus NVIDIA GeForce GTX 780 3GB)
Wi Fi adapater (Broadcom 802.11 ac Network Adapter)
SSD (Corsair Force LX SSD)
Hard Disk (Seagate Barracuda 2 TB)
Chipset (Intel® 9 series Chipset Family PCI Express)
RAM (Corsair Vengeance 1600 MHZ  16GB (2X8 GB))
Audio (Realtek ALC1150)

Share this post


Link to post
Share on other sites
  • 0

I tried the new release with no luck :(

 

I downloaded Yosemite-zone.DMG from this link and after successfull download I used TransMac to copy the image to my Kingston DataTraveler G4 (16GB) USB stick. When booting I used the below combination of boot flags but I ended up with the same error:

 

-f -x -v npci=0x2000 kext-dev-mode=1 PCIRootUID=0

-x -v npci=0x2000 kext-dev-mode=1

-v npci=0x2000

-x -v GraphicsEnabler=No IGPEnabler=Yes darkwake=0 PCIRootUID=0

 

Click to see the error 1417662076__wp_20141204_003.jpg

 

 

My configuration:

 

CPU (Intel i7 4790K 4GHZ)
Motherboard (Asus Z97 pro (wi-fi ac))
Graphic Card (NVIDIA GeForce GTX 780)
WiFi adapter (Broadcom 802.11 ac Network Adapter)
SSD (Corsair Force LX SSD)
HDD (Seagate Barracuda 2 TB)
Chipset (Intel® 9 series Chipset Family PCI Express)
RAM (Corsair Vengeance 1600 MHZ  16GB (2X8 GB)
)

 

PS: I am trying to install Yosemite on the Segate disk.

Share this post


Link to post
Share on other sites
  • 0

why are u using -x during install...safemode is used after install....n plz check the md5 checksum...then report back.

Share this post


Link to post
Share on other sites
  • 0

Any other ideas? I too was already and am using the latest (supposedly) fixed version

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
3 3