Giacomoleopardo Build - ZOTAC Z77-ITX WiFi - Core i7-3770T - MacMini 6,2

[wildwillow]

Hi minihack, I've never purchased videos from iTunes, so I can't tell for sure. Let's see if somebody here has the same issue. That is quite strange, does it happen only with Zotac boards?

Sorry to butt in to your thread, I was having a discussion with minihack on his own thread, to see if you can view iTunes content. Although you haven't purchased any movies, to test go to iTunes store/films and try watching a trailer. Returns with the same result for H77 chipset.

 

[giacomoleopardo]

Sorry to butt in to your thread, I was having a discussion with minihack on his own thread, to see if you can view iTunes content. Although you haven't purchased any movies, to test go to iTunes store/films and try watching a trailer. Returns with the same result for H77 chipset.

Thanks for the info. Bumped in minihack's thread

 

[Stork]

Concur with it might being a Z77 motherboard series problem. My other 1st and 2nd i3/i5/i7 system can view the iTunes trailers w/o a problem. IIRC, there was a fix for iTunes 10 which involved selecting 32bit instead of 64bit in the iTunes 10 Get Info window. But, iTunes 11 broke that fix. We don't know how to fix the problem or if there is a fix.

 

[giacomoleopardo]

Concur with it might being a Z77 motherboard series problem. My other 1st and 2nd i3/i5/i7 system can view the iTunes trailers w/o a problem. IIRC, there was a fix for iTunes 10 which involved selecting 32bit instead of 64bit in the iTunes 10 Get Info window. But, iTunes 11 broke that fix. We don't know how to fix the problem or if there is a fix.

Tried with downgraded iTunes 10.7, but still the issue remains even in 32 bit mode

 

[parallel]

Hmmm, well, I seem to have found a potential cause of my problems. IOAcceleratorFamily.kext seems to conflict with something. I say this because if I delete it, I can boot with UseKernelCache=No and Azalia enabled and then everything else loads - AGPM and AppleHDA. Obviously, without IOAcceleratorFamily though, the HD4000 won't load. Once I've done that though, I can re-install it using KextBeast, and then manually load it and the hd4000 kext, rebuild the cache with kextwizard and boot using the kernel cache. Then everything loads, but I guess not correctly since I still don't get QE/CI. Not sure whether it is something with AppleFrameBufferCapri though since when this loads, I get a DRMStatus issue.(I have tried: applying edits using the patch in post 4 to the vanilla,tried using the supplied kext from Giac in post 4, also tried unpatched, and manually patching just the connector definition, ie changing 04 for 08 only) all still produce the DRMStatus error.

I attach IOReg and DSDT for comparison. although DSDT in patched using PJALM's 2 patches as detailed in OP, so should be no surprises there!

 

[parallel]

I have noticed on comparing against your ioreg 10.8.4 Giac, that I don't get Device MEI showing in my ioreg despite it being listed in the DSDT. Since this is connected to AppleIntelFrameBufferCapri (according to your ioreg - AppleIntelMEIDriver -and the Capri info.plist), it could be the cause of my problems. Any thoughts on how to fix though? - Or, eek, do you think it could be a problem with my board / processor?

 

[minihack]

I have noticed on comparing against your ioreg 10.8.4 Giac, that I don't get Device MEI showing in my ioreg despite it being listed in the DSDT. Since this is connected to AppleIntelFrameBufferCapri (according to your ioreg - AppleIntelMEIDriver -and the Capri info.plist), it could be the cause of my problems. Any thoughts on how to fix though? - Or, eek, do you think it could be a problem with my board / processor?

Hi,
Device MEI in the DSDT is only for a Sandy Bridge CPU. Get rid of it for Ivy Bridge CPU as it was only put there (by me) to block the capri kext from loading and to make the sandy bridge frame buffer load.
Do not use my old DSDT for Ivy Bridge as it was made by me when I had a i5 2500k on my Zotac board - better to switch to the one from this thread or better still patch your own.

 

[parallel]

Hi Minihack,

Thank you for the reply. I patched a clean DSDT from my system, using the two patches by PJALM as noted in post #1 here. The Device MEI isn't present in the "Clean" DSDT, meaning it is added by the patches. Considering that it matches the code used here, (device ID 3A1E) which ProteinShake says is to prevent the SB Framebuffer blocking the Capri one, I see no issue in having it. But I will give it a go since I have no other ideas. I will add, that even with it in my DSDT, the device isn't injected (or at least detected as such) as you can see in my attached IOReg. The reason why I thought it might be needed is because Giacomoleopardo has the device in his (confirmed fully working) 10.8.4 build in his IOReg (attached).

As I say, thanks for the reply. If you have any other suggestions for full QE/CI, please let me know!

EDIT Removed Device MEI from DSDT and rebooted - no change to system performance / loading kexts and still no QE/CI.

 

[parallel]

Hi Giacomoleopardo,

I'm sure you're happy with your build as it is, but just a thought on the ACD from on board Mini DisplayPort. I've noticed my display(Dell U2711) works intermittently through the on board Mini DisplayPort at Bios, but, if I let it boot fully to desktop/login screen(or where I should see it since I only have one monitor!), I can sleep wake the machine through the power button and up it comes. I get the impression it's to do with the initialisation of the display. Just a thought.

 

[giacomoleopardo]

Hi Giacomoleopardo,

I'm sure you're happy with your build as it is, but just a thought on the ACD from on board Mini DisplayPort. I've noticed my display(Dell U2711) works intermittently through the on board Mini DisplayPort at Bios, but, if I let it boot fully to desktop/login screen(or where I should see it since I only have one monitor!), I can sleep wake the machine through the power button and up it comes. I get the impression it's to do with the initialisation of the display. Just a thought.

Thanks for the heads up, man, but not even the bios screen shows up. Nor in windows 7, with ACD drivers already installed from boot camp (installed using hdmi display, of course)