Contribute
Register

Boot0...yes I read the sticky guide and it failed!

Status
Not open for further replies.
If the SSD wasn’t supported, I wouldn’t be looking at my desktop right now. I would have gotten some sort of kernel panic of some sort.View attachment 511037
if you need those boot arguments to be able to use your machine, why not add them to your config.plist?

GraphicsEnabler=Yes doesn't actually do anything on clover though
 
GraphicsEnabler=Yes doesn't actually do anything on clover though


Must be using Chimera, you cannot get the boot:0 error if you boot with Clover.

PCIRootUID=0 is default so shouldn't have to use that.
 
if you need those boot arguments to be able to use your machine, why not add them to your config.plist?

GraphicsEnabler=Yes doesn't actually do anything on clover though
I once edited the Plist and added the PCIRootUID and 0 respectively, but then after a few boots, something weird happened...
Update: so that string the admin wrote was long on my phone and I didn’t scroll all the way so I was missing part of the string. Now when I type it in, it says, the resource is busy. I cannot unmount the drive, probably because I’m using it. Do I need to boot into my old ssd, unmount the new ssd then run the command?
3BBBCC93-CCC4-42F3-AF53-D46DEF552857.jpeg
 
Must be using Chimera, you cannot get the boot:0 error if you boot with Clover.

PCIRootUID=0 is default so shouldn't have to use that.
Yes, I’m using Multibeast 7.5 Yosemite edition.
 
Bingo! I fixed the Boot0 issue. What I needed to do was connect the new ssd to sata port 0. Then I connected up my old SSD, booted into the old drive while the new one is connected. Unmount the new drive from disk utility, then run this command

dd if=/usr/standalone/i386/boot1h of=/dev/disk0s2

if done correctly you will get the screen that I’ve attached. The drive boots natively, but now I need to see about the plist, maybe someone could help me through that and I’ll be good to go!

So, don’t discount SK Hynix, try to sort through solutions first before saying YoUR HaRDwARE iS iNcOmPaTiBlE
C4E495D6-8489-4EFE-964C-8B2B031751B7.jpeg
 
I used Carbon Copy Clone to clone the drive. I learned that CCC did not copy over the EFI
By default Chimera was installed to the system partition not the EFI partition.

It can be moved :

 
Must be using Chimera, you cannot get the boot:0 error if you boot with Clover.

PCIRootUID=0 is default so shouldn't have to use that.
This is the last screen I see before my monitor goes to no signal.
6439132B-AF6B-4A96-B594-9ED5EE7DD329.png
 
See! Now I’ve learned something! That’s called team work! I’ll keep this in mind for the next build. I’m planning on building one more Hackintosh before Apple moves away from its Intel chips and manufacturing their own, killing off the Hackintosh community.
By default Chimera was installed to the system partition not the EFI partition.

It can be moved :

 
I'm confused. What have you done since post #15 to get the above lock-up?

I thought you'd sorted booting ...
The boot0 is fixed. The black screen needs plist edits.

I’ll have to add the key and string PCIRootUID and 0 respectfully to the plist to avoid me typing it in every time.
 
Status
Not open for further replies.
Back
Top