OS X compatible motherboard -> QUO

[oSxFr33k]

Hello,

 

Is the CPU power management for Quo native or do we need to run Piker Alpha's ssdtPRGen.sh to generate ssdt and place this in /oz/acpi/load?  The script actually generated ssdt and ssdt-1.aml and ssdt-2.aml.

 

Without the ssdt I get this in Console:

 

2/23/15 11:25:27.691 AM system_profiler[359]: platformPluginDictionary: Can't get X86PlatformPlugin, return value 0

 

 

With the ssdt in Efi/oz/acpi/load/ that message is no longer there.

 

 

 

Thanks

 

Edited;

 

That message is no longer there with or without the SSDT in /Efi/Oz/ACPI/Load

 

 

I do get this message though with or without ssdt:

 

2/23/15 12:13:48.000 PM kernel[0]: WARNING: IOPlatformPluginUtil : getCPUIDInfo: this is an unknown CPU model 0x3a

 

 

 

EDITED:

 

Forget about my PM and ssdt question, I used MacIASL and the System DSDT clearly shows the information on the CPU all is fine, no ssdt needed.  Still unclear about the Unknown CPU model?

[Micky1979]

Don't get me wrong but your pretese are silly since all your hardwers does not match any of real Mac in commerce... All your CPUs are supported and can work fine. "maybe" your power management can be "incomplete" or "unsupported"... but this message appeare to me a "printf" from an "if" statement wroted by a Dev in the source code. Maybe your CPU model does't exist in any real Mac......simply

EDIT

and maybe this must match the configurations define in a real SMBios...and this is very difficult to obtain.

[oSxFr33k]

Don't get me wrong but your pretese are silly since all your hardwers does not match any of real Mac in commerce... All your CPUs are supported and can work fine. "maybe" your power management can be "incomplete" or "unsupported"... but this message appeare to me a "printf" from an "if" statement wroted by a Dev in the source code. Maybe your CPU model does't exist in any real Mac......simply

EDIT

and maybe this must match the configurations define in a real SMBios...and this is very difficult to obtain.

 

 

Good point and its only a warning and according to Ioreg everything seems fine.

[Micky1979]

Yep exactly!

[IronManJFF]

Have a odd one here :

 

Firmware log shows

 

04:664 00:003 Found Darwin Kernel Version 14.1.0: Mon Dec 22 23:10:38 PST 2014; root:xnu-2782.10.72~2/RELEASE_X86_64 0x2C2A1000 Kernelcache

04:664 00:000 Injected Call __ZN12KLDBootstrap20readBooterExtensionsEv Into __ZN12KLDBootstrap23readPrelinkedExtensionsEP10section_64

04:666 00:001 Injecting FakeSMC (DADE1001-1B31-4FE4-8557-26FCEFC78275) "Driver-40B1A14" 154132 bytes

04:667 00:000 Injecting CPUSensors (DADE1006-1B31-4FE4-8557-26FCEFC78275) "Driver-40BEC08" 52232 bytes

04:669 00:001 Injecting O Family (DADE1007-1B31-4FE4-8557-26FCEFC78275) "Driver-40DBB94" 117652 bytes

04:671 00:002 Injecting GPUSensors (DADE1008-1B31-4FE4-8557-26FCEFC78275) "Driver-41084A8" 181416 bytes

04:674 00:003 Injecting VoodooHDA (DADE1009-1B31-4FE4-8557-26FCEFC78275) "Driver-413B8D8" 207064 bytes

 

But at boot system.log shows :

 

 

Feb 23 16:08:32 localhost kernel[0]: Refusing new kext org.netkas.driver.FakeSMC, v1290.0: already have prelinked v901.0.

Feb 23 16:08:32 localhost kernel[0]: Refusing new kext org.hwsensors.driver.CPUSensors, v1290.0: already have prelinked v901.0.

Feb 23 16:08:32 localhost kernel[0]: Refusing new kext org.hwsensors.driver.LPCSensors, v1290.0: already have prelinked v901.0.

Feb 23 16:08:32 localhost kernel[0]: Refusing new kext org.hwsensors.driver.GPUSensors, v1290.0: already have prelinked v901.0.

 

In System Profiler I see :

 

loaded kexts:

...

com.razer.common.razerhid 10.85

org.voodoo.driver.VoodooHDA 2.8.6

org.hwsensors.driver.LPCSensors 901

org.hwsensors.driver.GPUSensors 901

org.hwsensors.driver.CPUSensors 901

org.netkas.driver.FakeSMC 901

...

 

 

 

 

 

I am thinking that the kernel take these extensions from S/L/E instead of Ozmosis .. can anyone confirm this ? Can I safely delete them from S/L/E if that is the case ?

Thanks 

[oSxFr33k]

I want to use the latest Kozlek Hwsensors and if I place them in /Efi/Oz/Darwin/Extensions/Common I get reboots.  Maybe the latest version has some conflict not sure but I would like to replace the one in the firmware with the latest one so I can use the latest CPU/GPU/ACPI sensors.  There is thread on this and going to read through carefully.  Just not sure if its as easy as it looks?

[Micky1979]

@IronManJFF you have  two FakeSMC.kext + plugins installed and one of it is already included in the kernelcache (the older one from the firmware?). Probably calling "sudo kextcache -system-prelinked-kernel" in terminal you can get the newer one... but I suppose that you will always have similar verbose in the log w/o deleting one of it...

[oSxFr33k]

Is there link to the VoodooHDA.kext used in the firmware?  I was able to update to the latest Kozlek sensors using the Oz tools but the VoodooHDA shares the same GUID as the FakeSMC.kext when converted to FFS.  For now I can just put the VoodooHDA in Efi/Oz/Darwin/Extensions/Common/  or /S/L/E until I figure out how to insert that file into the Oz firmware.

 

Thanks

[THe KiNG]

Is there link to the VoodooHDA.kext used in the firmware?  I was able to update to the latest Kozlek sensors using the Oz tools but the VoodooHDA shares the same GUID as the FakeSMC.kext when converted to FFS.  For now I can just put the VoodooHDA in Efi/Oz/Darwin/Extensions/Common/  or /S/L/E until I figure out how to insert that file into the Oz firmware.

 

Thanks

DO NOT mess GUID's used in OZ firmware, those are reserved and must be used as is, if you want to replace fakesmc and/or plug-ins use exact same GUID for each!.

OZ check those GUID's and setup/load drivers based on internal algorithm/variables setup.

[oSxFr33k]

DO NOT mess GUID's used in OZ firmware, those are reserved and must be used as is, if you want to replace fakesmc and/or plug-ins use exact same GUID for each!.

OZ check those GUID's and setup/load drivers based on internal algorithm/variables setup.

 

 

Well its only one conflict, voodooHDA and SmcEmulatorkext, I will try and figure out how to use the same GUID for SmcEmulatorKext.  The CPU,GPU and LPC sensors do use the same GUID, and they all use the GUID starting with DADE......  In the meantime is there a link to the VoodooHDA.kext used in the firmware?

 

Thanks

[IronManJFF]

Thanks to Micky 1979. I removed FakeSMC in S/L/E and rebuilt the prelinkled kernel (actuall the firmware version from H3C.1479 was newer than what i had in S/L/E)

HW monitor is much easier to interpret now.

 

So status for GTX 970 should now read as

 

 

 

I am happy to report that GTX 970 (MSI Gaming) works with 10.10.2 with Nividia web drivers with the following notice :

 

HW Monitor does not detect it and will not report GPU temp or fan speed

 

Watchdog service respawns all the time .. I am unsure ifthis is related to the new card .. the maessage might have been there all along since Yosemite and i just noticed it. Did some research and seems to be related to FakeSMC

[THe KiNG]

......  In the meantime is there a link to the VoodooHDA.kext used in the firmware?

No.

[oSxFr33k]

No.

 

I just modified Pavo's  "KextToFfs.command' script before running it each time, so it hard code the GUID without the wild card and ran the script for each kext one at a time and not all at the same time.  Worked perfectly all GUIDs assigned as they were originally.

 

Edited:

 

I went back to stock H3C.1479.  Its a bit unstable with the latest sensors not sure why but it has to reboot a couple of times before it does a complete boot to desktop. Maybe the combination of graphics card GTX650/latest sensors/voodoo?

[dwdrummer0]

Hello all.

 

I need help with a panic attack im getting every once in a while. My hack restarts then I receive this error report.  I suspect its something to do with my USB? Ive overclocked the system and verified its stablility with 8hrs of Prime95 so its not my hardware.

Here is my baisic hardware setup and the error report. USB 3 ports are working.

 

Quo Motherboard

32 GB ram

I7-3770k a 4.6ghz

Symphony I/O

1TB SSD

2 x 1TB 7200RPM Drives

 

 

Anonymous UUID:      

Mon Feb 23 14:15:42 2015
panic(cpu 0 caller 0xffffff80006bdfbc): "complete() while dma active"@/SourceCache/xnu/xnu-2422.115.10/iokit/Kernel/IOMemoryDescriptor.cpp:2620
Backtrace (CPU 0), Frame : Return Address
0xffffff83b0da3970 : 0xffffff8000223139
0xffffff83b0da39f0 : 0xffffff80006bdfbc
0xffffff83b0da3a30 : 0xffffff7f8092db06
0xffffff83b0da3a70 : 0xffffff7f80923ab2
0xffffff83b0da3ac0 : 0xffffff7f80ed12ca
0xffffff83b0da3b10 : 0xffffff7f80ed4c3a
0xffffff83b0da3b60 : 0xffffff7f809bb114
0xffffff83b0da3bb0 : 0xffffff7f809b518e
0xffffff83b0da3c00 : 0xffffff7f809b525c
0xffffff83b0da3c30 : 0xffffff7f808217cd
0xffffff83b0da3d30 : 0xffffff7f811fc126
0xffffff83b0da3de0 : 0xffffff7f811fcf11
0xffffff83b0da3e20 : 0xffffff7f8120a82e
0xffffff83b0da3ed0 : 0xffffff7f81212469
0xffffff83b0da3ef0 : 0xffffff80006b1cd7
0xffffff83b0da3f30 : 0xffffff80006b06e2
0xffffff83b0da3f80 : 0xffffff80006b07b7
0xffffff83b0da3fb0 : 0xffffff80002d7c67
      Kernel Extensions in backtrace:
         com.apple.iokit.IOStorageFamily(1.9)[9B09B065-7F11-3241-B194-B72E5C23548B]@0xffffff7f80920000->0xffffff7f8094cfff
         com.apple.iokit.IOUSBFamily(686.4.1)[815E4F64-F2D5-3847-931A-BE755698D993]@0xffffff7f8081e000->0xffffff7f8088afff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[2852ACFE-FD28-3C37-9B39-885201BB8D25]@0xffffff7f807ef000
         com.apple.driver.AppleUSBXHCI(683.4)[4E4FC804-E1C5-3FA3-8A26-D5D8D7C76D91]@0xffffff7f811fb000->0xffffff7f81217fff
            dependency: com.apple.iokit.IOUSBFamily(686.4.1)[815E4F64-F2D5-3847-931A-BE755698D993]@0xffffff7f8081e000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[2852ACFE-FD28-3C37-9B39-885201BB8D25]@0xffffff7f807ef000
         com.apple.iokit.IOSCSIArchitectureModelFamily(3.6.7)[9E10AF10-FA6C-3261-B939-5D0BC025ED9E]@0xffffff7f809b0000->0xffffff7f809e0fff
         com.apple.iokit.IOSCSIBlockCommandsDevice(3.6.7)[EF296673-2159-39B8-8A9C-4010FFBF952E]@0xffffff7f80ed0000->0xffffff7f80ee7fff
            dependency: com.apple.iokit.IOSCSIArchitectureModelFamily(3.6.7)[9E10AF10-FA6C-3261-B939-5D0BC025ED9E]@0xffffff7f809b0000
            dependency: com.apple.iokit.IOStorageFamily(1.9)[9B09B065-7F11-3241-B194-B72E5C23548B]@0xffffff7f80920000

BSD process name corresponding to current thread: kernel_task
Boot args: slide=0

Mac OS version:
13F34

Kernel version:
Darwin Kernel Version 13.4.0: Wed Dec 17 19:05:52 PST 2014; root:xnu-2422.115.10~1/RELEASE_X86_64
Kernel UUID: 45486BF2-BDDE-34CB-8C71-606FF3FE181B
System model name: MacPro3,1 (Mac-F42C88C8)

System uptime in nanoseconds: 31869646472518
last loaded kext at 10896678706: com.apple.filesystems.msdosfs    1.9 (addr 0xffffff7f810eb000, size 65536)
last unloaded kext at 186933599688: com.apple.driver.AppleFileSystemDriver    3.0.1 (addr 0xffffff7f81e7c000, size 8192)
loaded kexts:
com.nvidia.CUDA    1.1.0
com.paceap.kext.pacesupport.snowleopard    5.8
com.uaudio.driver.UAD2System    6.0.0
net.telestream.driver.TelestreamAudio    1.0.5
com.waves.driver.soundgrid    2.0.0
com.LivestreamProcaster.driver.ProcasterAudioRedirector    2.0.0
tc.tctechnologies.driver.PaeFireStudio    4.1.3 17357
com.evosx86.driver.lspcidrv    1111
com.digidesign.iokit.DigiDal    10.3.9f207
com.squirrels.airparrot.framebuffer    3
com.squirrels.driver.AirParrotSpeakers    1.8
com.apogeedigital.driver.Symphony64ThunderBridge    1.4.24
com.seagate.driver.PowSecLeafDriver_10_5    5.2.4
at.obdev.nke.LittleSnitch    4052
com.seagate.driver.PowSecDriverCore    5.2.4
org.hwsensors.driver.LPCSensors    820
org.hwsensors.driver.CPUSensors    820
org.netkas.driver.FakeSMC    820
org.tgwbd.driver.NullCPUPowerManagement    1111
com.apple.filesystems.msdosfs    1.9
com.apple.filesystems.autofs    3.0
com.apple.driver.AppleBluetoothMultitouch    80.14
com.apple.iokit.IOBluetoothSerialManager    4.2.7f4
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport    4.2.7f4
com.apple.driver.AppleMCCSControl    1.2.5
com.apple.iokit.IOUserEthernet    1.0.0d1
com.apple.Dont_Steal_Mac_OS_X    7.0.0
com.apple.driver.AppleHWAccess    1
com.apple.driver.AppleIntelHD4000Graphics    8.2.8
com.apple.driver.AppleLPC    1.7.0
com.apple.driver.AppleIntelFramebufferCapri    8.2.8
com.apple.driver.ACPI_SMC_PlatformPlugin    1.0.0
com.apple.iokit.IOUSBAttachedSCSI    1.0.5
com.apple.driver.MaxTranserSizeOverrideDriver    3.4.1
com.apple.driver.AppleUSBHub    683.4.0
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless    1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeLZVN    1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib    1.0.0d1
com.apple.BootCache    35
com.apple.driver.XsanFilter    404
com.apple.iokit.IOAHCIBlockStorage    2.6.0
com.apple.driver.Intel82574L    2.6.2b1
com.apple.driver.AppleFWOHCI    5.0.2
com.apple.driver.AppleAHCIPort    3.0.5
com.apple.driver.AppleUSBXHCI    683.4.0
com.apple.driver.AppleUSBEHCI    660.4.0
com.apple.driver.AppleRTC    1111
com.apple.driver.AppleACPIButtons    2.0
com.apple.driver.AppleHPET    1.8
com.apple.driver.AppleSMBIOS    2.1
com.apple.driver.AppleAPIC    1.7
com.apple.nke.applicationfirewall    153
com.apple.security.quarantine    3
com.apple.driver.AppleIntelCPUPowerManagement    217.92.1
com.apple.driver.AppleBluetoothHIDKeyboard    170.15
com.apple.driver.AppleHIDKeyboard    170.15
com.apple.kext.triggers    1.0
com.apple.driver.IOBluetoothHIDDriver    4.2.7f4
com.apple.driver.AppleMultitouchDriver    245.13.1
com.apple.iokit.IOUSBHIDDriver    660.4.0
com.apple.iokit.IOSerialFamily    10.0.7
com.apple.iokit.IOBluetoothHostControllerUSBTransport    4.2.7f4
com.apple.driver.AppleSMBusController    1.0.12d1
com.apple.iokit.IOSMBusFamily    1.1
com.apple.iokit.IOBluetoothFamily    4.2.7f4
com.apple.iokit.IOFireWireIP    2.2.6
com.apple.iokit.IOSurface    91.1
com.apple.iokit.IOAudioFamily    1.9.7fc2
com.apple.kext.OSvKernDSPLib    1.14
com.apple.iokit.IOAcceleratorFamily2    98.24
com.apple.AppleGraphicsDeviceControl    3.6.22
com.apple.iokit.IOGraphicsFamily    2.4.1
com.apple.driver.AppleSMC    3.1.8
com.apple.driver.IOPlatformPluginLegacy    1.0.0
com.apple.driver.IOPlatformPluginFamily    5.7.1d6
com.apple.iokit.IOUSBMassStorageClass    3.6.0
com.apple.driver.AppleUSBComposite    656.4.1
com.apple.iokit.IOUSBUserClient    660.4.2
com.apple.iokit.IOFireWireSBP2    4.2.6
com.apple.iokit.IOSCSIBlockCommandsDevice    3.6.7
com.apple.iokit.IOSCSIArchitectureModelFamily    3.6.7
com.apple.iokit.IONetworkingFamily    3.2
com.apple.iokit.IOFireWireFamily    4.5.5
com.apple.iokit.IOAHCIFamily    2.6.5
com.apple.iokit.IOUSBFamily    686.4.1
com.apple.driver.AppleEFINVRAM    2.0
com.apple.driver.AppleEFIRuntime    2.0
com.apple.iokit.IOHIDFamily    2.0.0
com.apple.security.sandbox    278.11.2
com.apple.kext.AppleMatch    1.0.0d1
com.apple.security.TMSafetyNet    7
com.apple.driver.AppleKeyStore    2
com.apple.driver.DiskImages    371.1
com.apple.iokit.IOStorageFamily    1.9
com.apple.iokit.IOReportFamily    23
com.apple.driver.AppleFDEKeyStore    28.30
com.apple.driver.AppleACPIPlatform    2.0
com.apple.iokit.IOPCIFamily    2.9
com.apple.iokit.IOACPIFamily    1.4
com.apple.kec.corecrypto    1.0
com.apple.kec.pthread    1
Model: MacPro3,1, BootROM MP31.006C.B05, 4 processors, Intel Core i7, 4.6 GHz, 32 GB, SMC 1.30f3
Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In
Memory Module: BANK 3/ChannelB-DIMM1, 8 GB, DDR3, 1600 MHz, Corsair, CMZ32GX3M4X1600C10
Memory Module: BANK 1/ChannelA-DIMM1, 8 GB, DDR3, 1600 MHz, Corsair, CMZ32GX3M4X1600C10
Memory Module: BANK 2/ChannelB-DIMM0, 8 GB, DDR3, 1600 MHz, Corsair, CMZ32GX3M4X1600C10
Memory Module: BANK 0/ChannelA-DIMM0, 8 GB, DDR3, 1600 MHz, Corsair, CMZ32GX3M4X1600C10
Bluetooth: Version 4.2.7f4 15112, 3 services, 23 devices, 1 incoming serial ports
Network Service: Ethernet 2, Ethernet, en0
PCI Card: Symphony 64 | ThunderBridge, Audio, Thunderbolt@220,0,0
Serial ATA Device: Samsung SSD 840 EVO 1TB, 1 TB
Serial ATA Device: ST1000DM003-1CH162, 1 TB
Serial ATA Device: ST1000DM003-1CH162, 1 TB
USB Device: Backup+ Desk
USB Device: Hub
USB Device: Symphony I/O : Symphony
USB Device: Hub
USB Device: FreeAgent GoFlex
USB Device: BCM20702A0
USB Device: Hub
USB Device: USB Storage
USB Device: Integrated USB Bridge
FireWire Device: unknown_device, Unknown
Thunderbolt Bus:

 

 

Thank you!

[THe KiNG]

Provide full DarwinDumper(zip) with everything connected that you use daily(when you get the panics).

Hello all.

 

I need help with a panic attack im getting every once in a while. My hack restarts then I receive this error report.  I suspect its something to do with my USB?

[dwdrummer0]

Will do. Thank you!

[IronManJFF]

This may sound stupid but have you done a memtest ? I had a similar issue when i built my hack but it was because of a faulty RAM stick

[stayupforever909]

So don't know if this has been mentioned here, but now that Apple has enabled two step verification on iMessage and FaceTime, it allowed me to log in without the contact Apple error. We'll see if it continues without issue, but I thought it was interesting. I'm still running on "stock" Oz values of Mac Pro 3,1 and generated serial and whatnot. Anybody else notice this?

 

 I know I am a bit late to the party but just checked mine and found it was working I put in the values some time ago using this MLBGenL-2.sh.zip  from http://www.insanelymac.com/forum/topic/303073-pattern-of-mlb-main-logic-board/

 

Me to on stock values with generated serial (been using since 2009)

 

Messages Facetime both working now 

 

Lazy I know but all credit to the authors espcialy holyfield for starting the topic

[dwdrummer0]

This may sound stupid but have you done a memtest ? I had a similar issue when i built my hack but it was because of a faulty RAM stick

Actually, I may run that to see where im at. Im running at stock voltage for these vengence sticks (With tighter timings) but ive seen that these sticks have a tough time with anything over stock settings. Maybe increasing Ram voltage from 1.5 to 1.525 or 1.55?

[InsaneHack]

Out of interest are QUO Computer likely to produce a new version of their Mac compatible motherboard? Apparently the first boards shipped mid-2013 according to the Kickstarter page and I notice they aren't showing any motherboards in stock on their website at the moment so I assume they are out of stock. Just curious ...   

 

EDIT: Just noticed that although the motherboard product page is currently empty, the motherboard is for sale from other parts of the site. Still wondering whether they will produce newer boards though ...

[valiant]

Hi. I've recently done a clean install of Yosemite on my QUO mb. I'm wondering if there's a new version of the QUO Audio Update.pkg? The one I have only goes up to 10.9. I had audio working before, but that was on a 10.9 install that got migrated to 10.10 and audio kept on working. I can't figure out how to get it to work from a clean 10.10 install.

[genzai]

Hi. I've recently done a clean install of Yosemite on my QUO mb. I'm wondering if there's a new version of the QUO Audio Update.pkg? The one I have only goes up to 10.9. I had audio working before, but that was on a 10.9 install that got migrated to 10.10 and audio kept on working. I can't figure out how to get it to work from a clean 10.10 install.

If you are using the latest OZ BIOS, Audio works OOB- so sounds like you are doing something wrong.

g\

[toastie]

Audio was tricky for me as well. For some reason, it was using the black port on the back for speakers initially. After a number of months and an install of Windows on another disk, output switched to the correct green jack.

[genzai]

Hello fine group,

after buying this board last black friday- I finally have gotten around to building a system with it. Generally very impressed with the design and OZ implementation. I thought i might just use clover but I am loving the way this board works with OZ.

 

The setup went really well and everything is working as expected so far. I even have a gtx 970 working in the last slot, mostly for cuda support.

 

A couple of questions have come up that i can use guidance on.

First, has anyone posted an overlocking guide for this board? I have always overlocked my hacks with good success, and i know there are many variables involved in getting a proper OS X overlock. However this board is behaving quite differently in this regard from any other boards i have used. 

 

On my other UEFI based Ivy systems, the current method is i use turbo ratios to overlock. i set the first ratio to one higher than the other 3 and i use an ssdt from SSDTPRGen with a -TURBO flag set to the first higher ratio. This seems to always provide the result that "about this mac" shows the non-turbo CPU speed but the cpu will happily turbo up to the ratio i set the bottom 3 cores to. This also shows up clearly in stat menus.

 

On the QUO board I am not having luck with this method or anything else i have tried yet. The system seems to not do any turbo at all in fact. It caps at 35x.

- If i leave the bios settings all at default/auto it switches between x16 and x35- never see it turbo to x39 which the cpu should do. 

- If i set the turbo ratios as i do the other Ivy systems it performs the exact same way.

In both the above cases about this mac also shows a 3.5ghz cpu

- If i set all 4 turbo ratios to 42x, about this mac shows a 4.2ghz cpu but my actual performance still just jumps between x16 and x35

- If i disable turbo, or put it at auto ratios, and use the cpu multip[lier to set to 42x, it also shows in about this mac in as 4.2ghz but the same issue of just 16x and 35x in usage.

 

To me, this seems like an ssdt issue. I generated an ssdt and placed it in EFI:Efi/Oz/Acpi/Load (on both drives i have installed since they both have an EFI path now) but nothing changes- In fact i suspect that for some reason SSDT is not even loading.

 

Anyway i was hoping someone could point me to a post that already covers exact OC procedure on this board, but if none exists, can those with a working OC please enlighten me?

 

System Config:

Quo-AOS

SysDef: imac 13,2 (airplay works, well regarded for ivy platform, set via nvram)

3770K

HD4000 enabled + GTX970, both working great

OS X 10.10.2 ssd, win8.1 hdd

Latest OZ Bios (H3C.1479)

 

Thanks,

g\

[valiant]

If you are using the latest OZ BIOS, Audio works OOB- so sounds like you are doing something wrong.

g\

 

Ah... I'm using whatever the BIOS was before the reinstall - ¿ something 828 ? or 838?

 

Where would I find the latest BIOS?

 

TIA