Hi
I've recently bought a PC with these specs:
MOBO Asus Z97-PRO (wifi) CPU i5-4590 3.3 GHz RAM 16 GB 1866 Mhz Crucial GPU Gigabyte NVIDIA GTX 760 SDD Samsung 840 EVO 250 GB HD 3 TB Wdigital SATA
My intention was installing a dual boot w7/osx. As expected, the windows 7 partition has been working with no problem, its installation being a piece of cake. The osx partition, not so much.
Last week I started with the niresh 10.9 iso file (USB flavour), which is really straightforward to install. The only problem was the nvidia native graphics, which didn't work (neither in the installer nor in the ssd installed niresh, blank screen), so I had to boot with nv_disable=1 which made everything functional (1024 x 768), but not really crisp and smooth. With multibeast I installed chimera 3, and no problem whatsoever to dual boot. Kextbeast + toleda wifi + "multibeast audio for my mobo" did the final trick and I was happy for a while.
Ok, I said: "as my 2 ssd partitions (w7/osx) are more or less empty, and if I break things nothing really happens, let's be adventurous and try yosemite 10.10.0 with unibeast/multibeast -> chimera 4". And I did that. Under my 10.9 niresh I just downloaded the Yosemite.APP from the app store, I followed all the unibeast steps in last week tutorials, and apparently everything became installed.
I have to say I had to patch unibeast with the yosemite MBR OSInstaller.pkg/mpkg (no problem, just a piece of cake).
Graphics worked natively crispy and sharp (1920 x 1200) WHILE USING THE INSTALLER, so I got really happy in anticipation... But once I installed yosemite on the ssd, I let it boot, and the graphics didn't work (grey screen, black screen, random behaviour), so I tried "nv_disable=1" and at least, osx yosemite booted from my ssd. The problem is nv_disable=1 under my ssd yosemite is REAL REAL slow and almost unusable (unlike in niresh 10.9, where it was moderately usable).
Anyway, I finally started trying to fine tune yosemite using the last version of multibeast, allegedly optimized for it. Well, after some "random kexting" I might have messed something using it, as currently, I can only boot the ssd version of yosemite USING MY BOOTABLE YOSEMITE USB (the one used to install it). If I try to boot from my ssd, It just gets locked (even using -x, -f, etc...)
If I don't specify -v at boot, whenever the progress bars reaches 45% or so, a "forbidden" symbol appears on the screen. If I specify -v I can see what happens in the background:
Look at it: http://imgur.com/LxwMOmA It says: "Still waiting for root device".
I'm really bored of reboots (really, in the last 3 days I might have rebooted my PC thousands of times). I started to mess with my SDD/Extra/org.chameleon.Boot.plist file, and currently its contents are these:
<?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>Default Partition</key> <string>hd(0,1)</string> <key>Timeout</key> <string>3</string> <key>Kernel Flags</key> <string>ahcidisk=1 debug=8 USBBusFix=Yes kext-dev-mode=1 cpus=1 -f</string> </dict>
I don't know if something is wrong... In fact, the kernel flags section is somehow crazy, as none of these flags seem to do a thing...
The problem has worsen a bit 2 days ago, (I don't know why): Now, if I want to boot from the YOSEMITE UNIBEAST USB stick, "its clover boot" appears on screen (I thing it's a clover), and I can select my SSD yosemite installed version. The problem is I'm forced to use the -x flag, (and/or sometimes -f, I'm not sure), if I don't use -x, it doesn't boot at all even from USB (from SSD never booted no matter the flags). In the past I didn't need that flag...
I don't know which extra kexts I've added via multibeast in the last days (I can't remember having added many, and/or switched many options), as I thought it kept some kind of log of the kext files it has added. But no, there's not a clear way to "rollback" the addtition of its kexts...
Some hours ago, I managed (I don't know how (!!)) to boot from my yosemite USB, but without using -x, so graphics worked natively!! But I'm not being able to replicate it again, I don't know what to do, or what did the trick. Now some kernel panics appear, etc... and I'm forced to boot with -x again :/
My theory, is in the last days I've installed some kext via multibeast which is interfering with normal boot, and/or normal root device detection.
I have to say in the rare cases where yosemite-ssd manages to boot, sound and wifi are enabled, as I installed 2 kexts that provide these 2 services (toleda wifi with kext beast, and some multibeast audio kext already listed when installed niresh, and working again in yosemite). But when booting with -x, slow graphics (right resolution), I have wifi, but no sound.
My second theory is "if my yosemite USB installer can/could boot a proper session, why my ssd installed version can't?". I would really like to "transfer" the proper kexts/boot options living in my USB to my SSD and thus maybe the SSD would boot as the USB does.
Any other hints? I feel I'm still in the phase "Both ssd partitions are somehow empty and I could afford reinstalling OSX (and/or w7) again". But I'm starting to get tired of it. Apparently W7 partition is rock solid and I haven't had any problem to boot it freely in any moment, I'm not expecting to reinstall it... But I'm afraid my chances are rising with Yosemite...
Sorry for the messy facts explanation. Any piece of shed light will be welcome :)
Thanks in advance.
submitted by friguron
[link] [comment]
What is missing? Please comment to help! ...[source] For more info try www.iatkos.net
Post a Comment