Ok.
So at this point, I have Battery Status and Brightness Control - Excellent - thank you very, very much.
So I change from NullCPU to AppleIntelCPU in MultiBeast (with DSDT - this just doesn't reflect that).
MultiBeast Configuration - 2015-08-01 08:44:32
-----------------------------------------------------------------
Drivers > Disk > TRIM Enabler > 10.10.3 TRIM Patch Drivers > Misc > FakeSMC v6.16.1372
Drivers > Misc > PS/2 Keyboard/Mice and Trackpads
Drivers > Network > Realtek > AppleRTL8169Ethernet 2.0.6
Drivers > System > Patched AppleIntelCPUPowerManagement > OS X 10.9.0
Bootloaders > Chimera v4.1.0
Customize > Boot Options > Basic Boot Options
Customize > Boot Options > Generate CPU States
Customize > Boot Options > Kext Dev Mode
Customize > Boot Options > Use KernelCache
Boots fine every time configured this way.
Went to use Patchmatic and it wouldn't work. I had used it before, but those files are old now. So I wanted to generate new ones, and it wouldn't work. It would create the Extract folder on the Desktop, but not any files within. The text in terminal didn't really give me a clue as to what the problem was, so I just moved on. The IASL tool wouldn't do me any good at this point (used it with earlier files previously), so I moved on.
Via IOReg, I check CPU0 - Doesn't show 8086. This is what it has:
CPU@0
AppleACPICPU
ACPI_SMC_PlatformPlugin
AppleACPICPUInterruptController
Not alarmed that it's not 8086 plugin.
Not exactly sure what to do for the SSDT generation (could not find steps anywhere), so I drag ssdtPRGen.sh to Terminal, and it generates this:
ssdtPRGen.sh v0.9 Copyright (c) 2011-2012 by † RevoGirl
v6.6 Copyright (c) 2013 by † Jeroen
v15.6 Copyright (c) 2013-2015 by Pike R. Alpha
-----------------------------------------------------------
Bugs >
https://github.com/Piker-Alpha/ssdtPRGen.sh/issues <
gDataPath: /Users/username/Library/ssdtPRGen/Data
System information: Mac OS X 10.10.4 (14E46)
Brandstring 'Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz'
Scope (_PR_) {220 bytes} with ACPI Processor declarations found in the DSDT (ACPI 1.0 compliant)
Generating ssdt.dsl for a 'MacBookPro9,2' with board-id [Mac-6F01561E16C75D06]
Ivy Bridge Core i5-3210M processor [0x306A9] setup [0x0603]
With a maximum TDP of 35 Watt, as specified by Intel
Number logical CPU's: 4 (Core Frequency: 2500 MHz)
Number of Turbo States: 6 (2600-3100 MHz)
Number of P-States: 20 (1200-3100 MHz)
Adjusting C-States for detected (mobile) processor
Injected C-States for CPU0 (C1,C3,C6,C7)
Injected C-States for CPU1 (C1,C2,C3)
Warning: 'cpu-type' may be set improperly (0x0603 instead of 0x0703)
Intel ACPI Component Architecture
ASL Optimizing Compiler version 20140926-64 [Nov 6 2014]
Copyright (c) 2000 - 2014 Intel Corporation
ASL Input: /Users/pauldlyon/Library/ssdtPRGen/ssdt.dsl - 270 lines, 8296 bytes, 48 keywords
AML Output: /Users/pauldlyon/Library/ssdtPRGen/ssdt.aml - 1681 bytes, 16 named objects, 32 executable opcodes
Compilation complete. 0 Errors, 0 Warnings, 0 Remarks, 0 Optimizations
Do you want to copy /Users/user/Library/ssdtPRGen/ssdt.aml to /Extra/ssdt.aml? (y/n)? y
WOW - I'M IMPRESSED!
It prompts to copy just the one top-level SSDT file to Extra when it actually generated 5, but I say 'Y' because the script is smarter than me regarding SSDT files. But all 5 are CPU related anyway - go figure?!?!.
So I uncheck Generate P and C states in Chameleon and select drop SSDT. My laptop booted fine with just the top level SSDT file in Extra. But bdmesg showed that it expected ACPI table in SSDT-1.
So I put all 5 SSDT files in Extra. Wouldn't boot (initial progress scroll ends with that box and a slashed circle over it).
Safe mode - Put just SSDT and SSDT-1 in Extra. Wouldn't boot (slashed circle).
Safe mode - Went back to just the one top level SSDT. Booted OK initially, but my laptop froze while typing this text.
Forced hard shutdown, boot, but wouldn't boot (slashed circle).
Safe mode - Removed all SSDTs and change Chameleon back to original state, and reloaded my MultiBeast config. Wouldn't boot (slashed circle).
Safe mode - Reloaded my MultiBeast Configuration again. Wouldn't boot (slashed circle).
Safe mode - Restarted with DSDT=NULL. Wouldn't boot (slashed circle). Now I'm at a loss.
I'm having a meltdown.... and I'm too old for that ;^)
Thankfully I had made copies of my DSDT and replace the one in Extra with a copy, and reloaded MultiBeast config again.
Boots fine now. Still have Battery Status and Brightness Control. I'm inclined to leave it this way.
Somehow the SSDTs corrupted my DSDT. But Chameleon's bsmesg log indicates it's generating two SSDTs when I don't have any custom ones in Extra, so do I need SSDTs from ssdtPRGen.sh when everything seems fine without those? Ready to move on to audio/sound.
So are those SSDTs that are generated by Chameleon in the background good enough?
I apologize for the lack of brevity, and I'm still thrilled that I have battery status and brightness control.