Search results

Good to hear your up and running! If you want to keep messing around with kexts, SR tools might be worth using so you can revert back easily... http://tonymacx86.blogspot.com/2012/05/sr-tools-kext-management-undo-version.html Cheers

Dont think you are naive... we all went though this at some point. installed kexts go into /system/library/extensions. You need to delete it from there. Also, when you try to boot after deleting the kext use the kernel flag "KernelCache=no". That should prompt the system to reload the kexts...

Can you adjust the boot flags at the chameleon menu

Well, it looks that you have a failure with the NVEnabler.kext. Either way, you can't have both voodoo and the realtek drivers. I'd think you could get rid of the voodoo.kext since it's in the backtrace, which should restore your "bootability".

GraphicsEnabler=No?

Can you post a picture of the kernel panic? Hard to diagnose issue without the more info

You have a couple of issues there... your calling PCIRootUID 2x? it should be either 0 or 1. ncpi should be 0x3000. Darkwake is either Yes or No, not 0. Do you have a fusion drive setup? I assume so given you boot argument "boot-uuid=xxxxx... and rd=*uuid. Try getting rid of those flags.

I have the best luck using macpro5,1. Here is my boot.plist if you want a look... <?xml version="1.0" encoding="UTF-8"?><!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>EthernetBuiltIn</key>...

You shouldn't need to install anything from MultiBeast, if you read the description you'l see that none of the patches apply to your card. Have you changed GraphicsEnabler=No in the org.chameleon.Boot.plist? I'm running a 660Ti and that is the only setting needed.

Use the steps for making a fusion drive, just modify for one drive. Review here: http://www.tonymacx86.com/mountain-lion-desktop-guides/79406-guide-fusion-drive-using-tonymacx86-tools-chimera-18.html Essentially, 1. Make a USB with your /Extra folder and the boot, boot0 and boot1h files from...

Did you make sure that the Super Duper copy is 1st in the boot priority list? If so, try manually installing the appropriate files...

Follow your suggestion #2. I was able to boot no problem with that method. Using the installer will only put files under the root of your fused system, and not the Boot OS X partition. However, the chameleon fix did not work for me, so be prepared. I think it has to do with the nvram.dylib...

Have you confirmed that the disk with chimera installed on it has the highest boot priority in the BIOS?

Thanks for the reply MacMan. I suppose I must be doing something wrong then I have attempted to hide one of the OS X fusion drive partitions via name, UID, hd(x,y) (using identifiers listed by "diskutil list" and TAB from the chimera menu). I guess I'll keep looking for the answer. Thanks again!

I would love the see the ability to hide OS X partitions. This would be especially nice given the our DIY fusion drives - there is no need no view both "boot os x" partitions. Thanks! Keep up the great work!

At the chimera menu, add the whole string between the quotes (but no quotes). Remember, if it doesn't load try setting the PCIRootUID=0 in the string. The GPU should be fine for installation, you just won't get full acceleration before you install and run MultiBeast. AHCI must be selected or...

I assume you get to the chimera selection screen when you boot and your freezing at the white boot screen. Try entering the kernel flags "-v npci=0x3000 PCIRootUID=1". PCIRootUID could also be 0 so try that to if the previous doesn't work. cheers

My Fusion Drive is up and running perfectly. However, I have an aesthetic question... Does anyone else have both "Boot OS X" partitions showing up in chimera (one from the SSD and the other from the HDD, labeled as "BOOT OS X" and "BOOT OS X 1")? Oddly, my drive is not named Boot OS X...

I can also confirm that this fixes the iCloud issue. THANKS airecken!

1. BBedit 2. vim