I've updated my build's description with my 10.9 trials, still have to try ElliotForceLegacyRTC to try and get rid of CMOS errors created by 10.9...
Oh, and I've also noticed two errors on boot:
- IOBLUETOOTH HCI CONTROLLER (but not always... )
- AGPM CONTROLLER — UNKNOWN PLATFORM (I've seen someone has edited a .plist file inside the kext to trick the OS to recognize the graphics card...)
Well done on your success installing 10.9 and figuring out how to get it all running smoothly! :thumb up:
I have Darkwake=0 in my plist now but I still can't wake-from-sleep. However the AppleRTC patch *has* cured the CMOS resets. Honestly these are the things I fear the most because they have the power to actually dig very deep into the computer's hardware and do damage. Luckily Gigabyte Z68 motherboards also have dual-BIOS as a back-up recovery option.
This is one of th main reasons why I dislike editing the DSDT
Dual boot OS X is surely something that will confuse Chimera, so I think the dual hard-disk is the right way to go!
I guaranty you I never had to reset my BIOS or any other problem in nearly one year of dual SL / ML on the same disk.
Though I don’t know exactly what Chimera does to the BIOS (if 'she' does anything... ), I believe it’s rather 10.9 that writes something there as if it were the P-RAM of a real Mac (hence CMOS errors).
To my understanding, the process is: Multibeast writes something (DSDT? or the result of DSDT settings?) in the boot sector to tell the pc what is the first file to run and maybe basic settings, then the file named ‘boot’ is run, it reads the parameters in the Extra folder (org.chameleon.Boot.plist and maybe DSDT.aml — I should try to throw it away to see if it’s needed every time... ) and when everything is ok to trick OSX, it is run as if in a normal Mac, plus the needed kexts to deal with the differences.
I may be wrong in some detail, but I’m pretty sure the overall picture is there.
(actually, I haven't found anywhere a clear explanation of the process, that's what's missing, in my opinion)
As for destroying your pc, are you sure it's possible to write something somewhere that can't be reset? I'd be surprised MB and that DSDT thing could go so deep in the machine, but I'm not a PC specialist, I confess...
Yes, I think you have written a good description of how things work during boot.
You are right, it would be great to see a clear description of how Chimera works. We know there is some EFI trickery going one but not much more!
Well CMOS resets on my set up only started with Mountain Lion. Quite a shock when they happen as you have to go into the BIOS and reset all Mac-related settings (H-PET, AHCI etc) or the system will not boot. Not as easy as it seems as my motherboard will not recognise a USB keyboard to enter BIOS unless because of a crash. I have to plug in my old PS/2 keyboard to get access!
My fear over these resets is because normally the BIOS is a carefully protected area with a back-up copy on board to aid recovery.
I have read of examples where people (with more knowledge than me!) modify a DSDT to enable more voltage to be passed to a certain port (USB for example). This kind of control strikes me as very "dangerous' to the health of the motherboard if mis-handled
I understand and share your fear about BIOS!
Mine is not reset after running 10.9 but shows a "checksum error" — which is not good neither...
I've just discovered this: http://www.tonymacx86.com/general-h...s-mac-experiencing-data-loss-maverick-os.html
Just as if we needed some more caution before tickling our macs with mavericks...
Forget what I said a few days ago and stay with ML for the time being, it's probably the best policy if you wanna be safe!
Luckily, although I do own an external WD MyBook drive and a WD Passport, I don't use their utility software. Hopefully that will keep me safe ...
Yes, I think I agree with your recommendation. In my case there seems to have been a "Golden Spot" for features and reliability. As I have mentioned before this was at ML 10.8.3 when everything worked perfectly.
I am now awaiting the arrival of my new USB sound card - an Asus Xonar U3