Issues with Z68X-UD3H-B3 Install

[Coldwrench]

Looking your comment i can only see 1 issue. You have a traditional spinning hard drive and TRIM option should not be selected. Other thing is without looking at the error screen no one will be able help you.

Here is what i suggest

...

Run multibeast with these settings and reboot with -v. If you get error then take a photo and attach it in the reply.

User DSDT or DSDT Free
ALC889 without DSDT
3rd Party SATA
Realtek Gigabite Ethernet
Legacy USB
Customization > 1080 Boot screen
SSDT - Sand Bridge i5
Mac Mini Profile

Did that and got an error running MultiBeast that "The Installation Failed." I attached a screenshot and the MB log.

Looks like the error might stem from a USB problem.

Dec  1 09:51:11 Administrators-Mac-Pro.local installd[605]: PackageKit: Executing script "./preinstall" in /private/tmp/PKInstallSandbox.QO83d9/Scripts/com.tonymacx86.MultiBeast.network.AppleRTL8169Ethernet.pkg.JCy9sT
Dec  1 09:51:11 Administrators-Mac-Pro.local installd[605]: PackageKit: Executing script "./preinstall" in /private/tmp/PKInstallSandbox.QO83d9/Scripts/com.tonymacx86.MultiBeast.system.IOUSBFamily.pkg.1ZG8C8
Dec  1 09:51:11 Administrators-Mac-Pro.local installd[605]: PackageKit: Shoving /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/Cleanup At Startup/PKInstallSandboxManager/1.sandbox/Root (4 items) to /
Dec  1 09:51:11 Administrators-Mac-Pro.local installd[605]: PackageKit: kextcache -system-caches
Dec  1 09:51:13 Administrators-Mac-Pro.local installd[605]: PackageKit: kextcache -update-volume / -Installer
Dec  1 09:51:14 Administrators-Mac-Pro.local installd[605]: kextcache: IOUSBAttachedSCSI.kext - no compatible dependency found for com.apple.iokit.IOUSBFamily.
Dec  1 09:51:14 Administrators-Mac-Pro.local installd[605]: kextcache: IOUSBAttachedSCSI.kext is missing dependencies (including anyway; dependencies may be available from elsewhere)
Dec  1 09:51:14 Administrators-Mac-Pro.local installd[605]: kextcache: IOUSBAttachedSCSI.kext - no compatible dependency found for com.apple.iokit.IOUSBFamily.
Dec  1 09:51:15 Administrators-Mac-Pro.local installd[605]: kextcache: IOUSBAttachedSCSI.kext - no compatible dependency found for com.apple.iokit.IOUSBFamily.
Dec  1 09:51:16 Administrators-Mac-Pro.local installd[605]: kextcache: IOUSBAttachedSCSI.kext - no compatible dependency found for com.apple.iokit.IOUSBFamily.
Dec  1 09:51:16 Administrators-Mac-Pro.local installd[605]: kextcache: Prelink failed for com.apple.iokit.IOUSBAttachedSCSI; aborting prelink.
Dec  1 09:51:16 Administrators-Mac-Pro.local installd[605]: kextcache: Failed to generate prelinked kernel.
Dec  1 09:51:16 Administrators-Mac-Pro.local installd[605]: kextcache: Child process /usr/sbin/kextcache[633] exited with status 71.
Dec  1 09:51:16 Administrators-Mac-Pro.local installd[605]: kextcache: Error 107 rebuilding /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache.
Dec  1 09:51:16 Administrators-Mac-Pro.local install_monitor[612]: Re-included: /Applications, /Library, /System, /bin, /private, /sbin, /usr
Dec  1 09:51:17 Administrators-Mac-Pro.local installd[605]: PackageKit: releasing backupd
Dec  1 09:51:17 Administrators-Mac-Pro.local installd[605]: PackageKit: allow user idle system sleep
Dec  1 09:51:17 Administrators-Mac-Pro.local installd[605]: PackageKit: Install Failed: Error Domain=PKInstallErrorDomain Code=121 "An error occurred while updating system extension information." UserInfo=0x7f8dbc602f10 {NSUnderlyingError=0x7f8dbc600400 "The operation couldn’t be completed. (kextcache error 71.)", NSLocalizedDescription=An error occurred while updating system extension information., arguments=(
	    "-update-volume",
	    "/",
	    "-Installer"
	)} {
	    NSLocalizedDescription = "An error occurred while updating system extension information.";
	    NSUnderlyingError = "Error Domain=kextcache Code=71 \"The operation couldn\U2019t be completed. (kextcache error 71.)\"";
	    arguments =     (
	        "-update-volume",
	        "/",
	        "-Installer"
	    );
	}
Dec  1 09:51:17 Administrators-Mac-Pro.local Installer[597]: install:didFailWithError:Error Domain=PKInstallErrorDomain Code=121 "An error occurred while updating system extension information." UserInfo=0x7fe944d15ed0 {arguments=(
	    "-update-volume",
	    "/",
	    "-Installer"
	), NSLocalizedDescription=An error occurred while updating system extension information., NSUnderlyingError=0x7fe944df10e0 "The operation couldn’t be completed. (kextcache error 71.)"}
Dec  1 09:51:18 Administrators-Mac-Pro.local Installer[597]: Install failed: The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.
Dec  1 09:51:18 Administrators-Mac-Pro.local Installer[597]: IFDInstallController 42EA0D70 state = 7
Dec  1 09:51:18 Administrators-Mac-Pro.local Installer[597]: Displaying 'Install Failed' UI.
Dec  1 09:51:18 Administrators-Mac-Pro.local Installer[597]: 'Install Failed' UI displayed message:'The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.'.
Your list does not include FakeSMC, which RockStar did, so I'm going to try reinstalling with that option.

I notice that you differ from rockstar's instruction in that he has fakesmc and you didn't. I'm going to try again with fakesmc and see how that goes.

 

[leps85]

i resolve with 10.7.2 but i cant change resolution at the moment.
i try many text and ssmbios my system now have an intel hd 764mb at 1024x768
some help thxxx

 

[Coldwrench]

Some more information about MB failure...

I started going thru the options one at a time. Seems only those options which will install a kext cause the MB failure.

So I ran kextcache -update-volume and got the following error.

localhost:~ administrator$ sudo kextcache -update-volume /Volumes/MLITest/ -v 
rebuilding /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache
IOUSBAttachedSCSI.kext - no compatible dependency found for com.apple.iokit.IOUSBFamily.
IOUSBAttachedSCSI.kext is missing dependencies (including anyway; dependencies may be available from elsewhere)
IOUSBAttachedSCSI.kext - no compatible dependency found for com.apple.iokit.IOUSBFamily.
IOUSBAttachedSCSI.kext - no compatible dependency found for com.apple.iokit.IOUSBFamily.
IOUSBAttachedSCSI.kext - no compatible dependency found for com.apple.iokit.IOUSBFamily.
Prelink failed for com.apple.iokit.IOUSBAttachedSCSI; aborting prelink.
Failed to generate prelinked kernel.
Child process /usr/sbin/kextcache[312] exited with status 71.
Error 107 rebuilding /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache.

Looks like I'm not alone in this...
http://www.tonymacx86.com/mountain-...pdating-error-count-26-status-71-a-print.html
http://www.tonymacx86.com/mountain-lion-desktop-support/67917-cant-get-multibeast-run.html


This post talks about deleting the USB Bluetooth kext, but I use USB bluetooth and don't want to lose that!
http://www.tonymacx86.com/mountain-...minal-see-failed-kexts-help-me-plz-print.html

This post talks about deleting a single plugin in the USB Bluetooth kext.
http://www.tonymacx86.com/mountain-lion-desktop-support/78606-multibeast-5-1-1-fails-install.html

This post blames Legacy USB setting for the problem.
http://www.tonymacx86.com/multibeast-bug-reports/75839-multibeast-5-1-fails-4.html

This post simply says to remove IOUSBAttachedStorage.kext. It claims no USB Bluetooth problems.
http://www.insanelymac.com/forum/topic/284441-kernel-cache/

That seemed the safest thing to try, so I did. Didn't get very far:

localhost:Extensions administrator$ sudo kextcache -update-volume /Volumes/MLITest/ -v 
rebuilding /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache
kxld[com.apple.driver.CSRHIDTransitionDriver]: The super class vtable 'vtable for IOUSBCompositeDriver' for vtable 'vtable for CSRHIDTransitionDriver' is out of date. Make sure your kext has been built against the correct headers.
Link failed (error code 5).
Prelink failed for com.apple.driver.CSRHIDTransitionDriver; aborting prelink.
Failed to generate prelinked kernel.
Child process /usr/sbin/kextcache[383] exited with status 71.
Error 107 rebuilding /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache.

Looks like this is also ground that's already been covered... That kext is inside IOBluetoothFamily. This post gives more detail:
http://www.tonymacx86.com/mountain-...4-multibeast-install-failed-3.html#post500095

So I installed a copy of that at the top of S/L/E and reran MB. That didn't help. So I just ended up deleting the CSRHIDTransitionDriver kext. That finally allowed MB to complete without error.

Interesting to note that I didn't check Legacy USB when I did my original installs (based on Alfa's instructions) and never had this problem. So I am left to suppose that it's that option which triggered all the incompatibilities. How did RocKetstaR get past this? Guess I'll have to do another clean install and skip the Legacy USB option to see if MB succeeds.

Let's see how it goes!

-------------

Well, installed from scratch into a new partition and I get *no* MultiBeast errors running without the Legacy USB option.

Sad to say, though, I still get the black screen. No video.

 

[Coldwrench]

Well, I'm about to pull my hair out.

Lots of builds and testing. In all cases so far, I've gotten to the black screen.

Result of clean build with alfa/rockstar settings:
User DSDT
ALC889 w/o DSDT
3rd party SATA
FAKE SMC
Realtek Gigabyte Ethernet
*no* Legacy USB
USB 3.0 Caldigit
1080 Patch
MacMini profile
i5 SSDT.

Results uploaded as FirstBootToBlack.txt file.

Then tried booting again with GraphicsEnabler=No. No change. Results in SecondBootToBlackUnderUnibestGraphicsmodeNo.txt.

Then patched the AppleIntelHD3000Graphics and AppleIntelSNBGraphicsFB kexts to include 0x01128086 device ids (from another TM thread). No difference. Results in ThirdBootToBlackAfterPatchingKexts.txt.

Separately, I dl'd some older HD3000 kexts and installed them. They worked, except for some tearing on the screen. Also, the OpenGL test in XBench didn't display anything. (Loved the 190fps result though!)


One thing to note: I've got multiple partitions and the one I'm booting from isn't the first one. though I always select the test partition at boot time. My first partition is working with an 8600GT card and I don't want to lose that minimum functionality.


Folks - any suggestions?

Is there a DSDT to be added or some different boot loader?

Thanks in advance for any suggestions.

 

[Azimuth1]

Well, I'm about to pull my hair out.

Lots of builds and testing. In all cases so far, I've gotten to the black screen.

Result of clean build with alfa/rockstar settings:
User DSDT
ALC889 w/o DSDT
3rd party SATA
FAKE SMC
Realtek Gigabyte Ethernet
*no* Legacy USB
USB 3.0 Caldigit
1080 Patch
MacMini profile
i5 SSDT.

Results uploaded as FirstBootToBlack.txt file.

Then tried booting again with GraphicsEnabler=No. No change. Results in SecondBootToBlackUnderUnibestGraphicsmodeNo.txt.

Then patched the AppleIntelHD3000Graphics and AppleIntelSNBGraphicsFB kexts to include 0x01128086 device ids (from another TM thread). No difference. Results in ThirdBootToBlackAfterPatchingKexts.txt.

Separately, I dl'd some older HD3000 kexts and installed them. They worked, except for some tearing on the screen. Also, the OpenGL test in XBench didn't display anything. (Loved the 190fps result though!)


One thing to note: I've got multiple partitions and the one I'm booting from isn't the first one. though I always select the test partition at boot time. My first partition is working with an 8600GT card and I don't want to lose that minimum functionality.


Folks - any suggestions?

Is there a DSDT to be added or some different boot loader?

Thanks in advance for any suggestions.

I'm sorry for all the troubles you are going through! ...

Let's start again from the scratch, can we?
do you set the BIOS properly? is firewire disabled? is the com port disabled? and everything is set as per http://www.tonymacx86.com/123-how-up...herboards.html ? I suggest you to go into bios and 1st:

load the default setting so we will restore the defaults, then follow the above link, and then be sure to disabled the com port. Do NOT install any graphich card at this time.

Only 1 HDD (is it reliable?) and 1 USB stick (connected to an USB 2 port, better if you use the back ones directly connected yout motherboard - just in case there is some issue with your cabinet!). Do NOT connect the HDD to other Sata port than the Intel p0 . If you have and DVD reader, disconnect it.

Then ONLY mouse and keyboard connected via USB (no BT at all at this stage), these connected directly on the rear of you mobo too.

Monitor connected to the DVI port of the mobo.

Format and re-install. Install MB 5.1.3 as per the settings we provided and then report here. Don't do anything ELSE.

I hope it helps.

 

[Going Bald]

@coldwrench

If you select UserDSDT or EasyBeast (doesn't matter) FakeSMC is installed - no need to select it again - in fact this may be the problem as having it "selected" twice may be causing it not to be installed at all. When you run MultiBeast and select UserDSDT, expand the window and look at the bottom pane of the window. It tells you everything that UserDSDT (or whatever you have hi-lited) installs and where it installs it.

 

[Coldwrench]

I'm sorry for all the troubles you are going through! ...

Let's start again from the scratch, can we?
do you set the BIOS properly? is firewire disabled? is the com port disabled? and everything is set as per http://www.tonymacx86.com/123-how-up...herboards.html ? I suggest you to go into bios and 1st:

load the default setting so we will restore the defaults, then follow the above link, and then be sure to disabled the com port. Do NOT install any graphich card at this time.

Only 1 HDD (is it reliable?) and 1 USB stick (connected to an USB 2 port, better if you use the back ones directly connected yout motherboard - just in case there is some issue with your cabinet!). Do NOT connect the HDD to other Sata port than the Intel p0 . If you have and DVD reader, disconnect it.

Then ONLY mouse and keyboard connected via USB (no BT at all at this stage), these connected directly on the rear of you mobo too.

Monitor connected to the DVI port of the mobo.

Format and re-install. Install MB 5.1.3 as per the settings we provided and then report here. Don't do anything ELSE.

I hope it helps.

Did all the good stuff in re. setup and BIOS. Only deviations I saw were:
- I had hard drive on P2, DVD on P4 and had selected UEFI instead of SATA for booting options.
So I moved the hard drive to P0, disconnected the DVD, reset the BIOS by loading "optimal settings" and set up according to the link in your post.


You didn't mention exactly whose instructions to follow, so I started with the instructions MiniITX gave in post #79.

Not surprisingly, because it included Legacy USB, MB threw an installation error. Same problem I documented in post #84 above.

I don't think there's anything in the BIOS that would affect the problems I'm seeing just running MB.

How are you using the current MultiBeast without running into the installation failure? I downloaded 5.1.3-1 from TM, where the Multibeast app is dated 10/27/2012 10:40 and 25,443,158 bytes in length.


So, I restored the install from before I ran MB (thank you super duper) and ran MB again, this time leaving out the Legacy USB option. Installation was successful.

When I boot that partition, I get an Apple logo of the right size, rather than the giant one for a screen with the wrong resolution. But in the end, no go. Black screen. When I boot from my UB SD card and select the new partition, I also end up with a black screen. Nothing that looks like an error during boot with -v, or showing in dmesg. (I've already loaded those) I have to boot back to my pre-MB partition, using UB.

I'm attaching the profile report before I ran MB (in the zip file) and a screenshot of the extensions that changed afterward.

One question I do have is, "How does OSX recognize my HD3000 with a device id of 0112 instead of 0126? Is Chimera doing some patching/injection?

I really appreciate all your help, but something has to be different here. Just can't figure out what it is!

 

[Azimuth1]

Did all the good stuff in re. setup and BIOS. Only deviations I saw were:
- I had hard drive on P2, DVD on P4 and had selected UEFI instead of SATA for booting options.
So I moved the hard drive to P0, disconnected the DVD, reset the BIOS by loading "optimal settings" and set up according to the link in your post.


You didn't mention exactly whose instructions to follow, so I started with the instructions MiniITX gave in post #79.

ok, good!

Not surprisingly, because it included Legacy USB, MB threw an installation error. Same problem I documented in post #84 above.

I don't think there's anything in the BIOS that would affect the problems I'm seeing just running MB.

Never istall the Legacy USB drivers coming from Multibeast. The legacy option in BIOS is standard (and necessary) but we are talking about different things. OSX has USB2 drivers and stacks so for those ports there is no problem at all. The problems arise from the USB3 Etron chip and the lack of support for it.

How are you using the current MultiBeast without running into the installation failure? I downloaded 5.1.3-1 from TM, where the Multibeast app is dated 10/27/2012 10:40 and 25,443,158 bytes in length.

Yes!

So, I restored the install from before I ran MB (thank you super duper) and ran MB again, this time leaving out the Legacy USB option. Installation was successful.

IHMO this was a bad move! For what I've understood OSX has no "plug'n'play" features (or very limited), meaning it's not "aware" of any hardware changes as Windows is since Win95. And that's reasonable as OSX works upon a "fix" hardware platform.

So if you change parameters in BIOS as you did, good practice is to re-install everything and not to restore the vanilla version of OSX. I know it's frustrating and time comsuming but don't take shortcut. I guess OSX must work with the right HW/BIOS configuration and MB doesn't help because it just adds drivers and dependencies, but many of these are already set by OSX ML vanilla during the 1st install.

I can tell you that all the times I changed my BIOS settings (at least before UEFI) I had a crash, even with 10.7.x . And I can tell that I experienced MB failing the installation over OSX 10.8.x for 5 (!!!) times because I tried to install it on a vanilla version when I've already changed something in BIOS.

That said, I noticed you can boot from UEFI boot drive, while I had to select SATA p0 otherwise I don't boot.

Another Q: which version of i5 do you own? which motherboard video port did you choose to connect your monitor at?

 

[Coldwrench]

Never istall the Legacy USB drivers coming from Multibeast. The legacy option in BIOS is standard (and necessary) but we are talking about different things. OSX has USB2 drivers and stacks so for those ports there is no problem at all. The problems arise from the USB3 Etron chip and the lack of support for it.

I certainly buy that. Alas, most of the instructions given in this forum, including MiniITX' (and NO criticism intended here!) specify "Legacy USB" as something to set.

IHMO this was a bad move! For what I've understood OSX has no "plug'n'play" features (or very limited), meaning it's not "aware" of any hardware changes as Windows is since Win95. And that's reasonable as OSX works upon a "fix" hardware platform.

So if you change parameters in BIOS as you did, good practice is to re-install everything and not to restore the vanilla version of OSX. I know it's frustrating and time comsuming but don't take shortcut. I guess OSX must work with the right HW/BIOS configuration and MB doesn't help because it just adds drivers and dependencies, but many of these are already set by OSX ML vanilla during the 1st install.

I can tell you that all the times I changed my BIOS settings (at least before UEFI) I had a crash, even with 10.7.x . And I can tell that I experienced MB failing the installation over OSX 10.8.x for 5 (!!!) times because I tried to install it on a vanilla version when I've already changed something in BIOS.

That said, I noticed you can boot from UEFI boot drive, while I had to select SATA p0 otherwise I don't boot.

Now I think you might be hitting on something here... Prior to ML, I believe all Apple retail installations included drivers intended for their entire product non-server line. All drivers were included and, I believe, all were copied to your hard drive at install time.

However, my download of ML came through the app store from my 10.7.3 installation. That wasn't set up as a Mac Mini or iMac, but a Mac Pro. A quick google on the topic suggest that Apple provides different versions of the *recovery* install image based on the downloading machine's type/attributes. Links http://nellen.it/blog/2012/01/downloading-hardware-specific-lion-installers, http://afp548.com/2012/05/30/understanding-installesd-recovery-hd-internet-recovery and http://nellen.it/blog/2012/01/downloading-hardware-specific-lion-installers. I got my 10.7 (.2 or .3?) Lion installation from my macbook pro running SL.

Begs the question "Is the ML install I purchased from the App Store different than the one you have?" The file shows version 1.3.19. The md5 command doesn't work on folders, but the result of the following command, when executed from the UB main folder, is: 4452d184c3451528ce8d388ffdb565b6. I'll try to mount the disk with the original download and get a hash for that file, in case UB is modifying the installation esd.

find Install\ OS\ X\ Mountain\ Lion.app/ -type f -exec cat {} \; | md5

Before I start another round installations, I'd like to find out whether I have the same installation esd as everyone else here. Can any other folks run the above command on their original installation images and report the version and MD5 hash value?

Another Q: which version of i5 do you own? which motherboard video port did you choose to connect your monitor at?

Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz, Family 6, Model 42(02Ah), Stepping 7. I did note earlier that my HD3000 graphics device id is 0x0112. A lot of posting say that's unique to the i5-2500K. Is that the same as yours? I used the DVI port.

I'm attaching a "sysctl -a" output with all the ugly details.

There is also a lot of posting by folks with problems wherein the video after reboot is blank or all scrambled in the upper half and the lower half is the white background with the circular boot animation. I have that problem with some installations (e.g. non MacMini) and solved it by downloading older kexts, though other problems resulted (see earlier posts). Folks on this thread, however didn't show any of those problems. Hard to attribute to hardware versions, BIOS settings or installed software versions.

Again, thanks for digging into all this.

 

[Coldwrench]

Managed to mount the drive with the original ML installation esd files...

MD5 is 54da168e620c918f285337b9c2eb6941. Not the same as I found on my UB installation SD card. I will see if I can re-download the ML installation from the App Store on my MacBook Pro instead of my old mackintosh and see if I get the same file.