Re: Guide: GA-Z68X-UD3H-B3 with ATI 6870 - Clean Lion Install
Gordo, thanks so much. I'm almost out of hot water...a few follow-ups--some questions, as well as some comments and info, just for info for both you and the forum:
1) Audio: I looked closely at Toledo's guide for HDMI audio and saw that it was likely that I would lose other audio outputs if I make the required changes to get HDMI audio to work. So I dropped trying to get HDMI to work and am just using the optical audio out through the motherboard, into a home audio setup I have (I'd really like both HDMI + optical to work, but battle for another day). Weird thing: when I connected the audio and switched the various OS audio setups to point to it, sound worked right away. But volume control was disabled, both in the upper right of the screen and when using a volume adjuster on my Logitech bluetooth keyboard. For the heck of it, I hit the mute button on the keyboard, which didn't actually make the sound go away, but did show a "no" (circle with diagonal cross) sign on the screen with a volume slider, all of which appeared for a few moments. I think I may have rebooted then. Somewhere in during all this, the ETHERNET dropped out...bizarre. I rebooted, re-ran Multi-beast (in the way I describe in 4(a) below), had an install failure but rebooted anyway, and now both ethernet and audio are working. But with the volume/audio stuff grayed out in the upper right and still no way to adjust volume or mute. Is this normal?? Any ideas, or is optical audio beyond the scope of your testing?
2) Video: turns out the video acceleration (QE/IC) may have been working fine all along. Despite searching extensively, I'm not sure there exists a definitive way to test whether QE/IC is fully working in Lion (know of anything better than what's below?). But some link that I had first looked at kept referring to the card or driver show up in the PCI Card in System Profiler, and it never did. This is what I've been trying to see for the last several weeks. But after some more searching today, I came across the following, which gives three "tests" that I passed:
http://www.phacks.net/hackintoshosx86-h ... re-active/. Note that to get the "ripple" to show, you have to uncheck show dashboard as a space within mission control, as detailed here:
http://www.insanelymac.com/forum/index. ... pic=259457. So, does this mean QE/IC is "fully" working, or is there a better way to test that I just haven't found?
3) Chimera: thanks for the guidance. I had the boot order right in one place in BIOS (order of HDDs), but not in the other (HDDs before USB, CD-ROM, etc.). Boots very fast now after post! Any idea how to change which OS boots by default, how to not show certain drives, etc.? I can't seem to find much documentation on Chamelon...Tony links to the following, which is basically empty:
http://forge.voodooprojects.org/p/chameleon/
4) Misc.
a) How exactly should I be using Multi-beast when re-running it its first use? Do you just check ALL options that you actually want--so the new checked options are installed when re-running and that the ones that were checked on previous install but unchecked when re-running? Or is it cumulative, so what was checked previously stays and new checks are added? (If this, then how do you remove things?) In any case, it typically tells me that install failed upon re-running Multi-beast, which, when I get paranoid makes me pull the hard drive, reinitialize in another mac, and start from scratch...which probably isn't the right thing?
b) I noticed that TRIM (SSD feature) was added to the latest Multi-beast and F10 mobo version added to the DSDT database--should we be upgrading/using these? Any idea what the new DSDT changes encompass?
c) FYI, I just tried building and installing the DIY airport extreme from
http://x86wifi.blogspot.com/2010/04/how ... -card.html. Not working...it shows up in details about the system, but the AirPort utility doesn't find it. I suspect it's a HW issue, but really not sure. Will look into it more and report back if anything, just noting it now in case it has something to do with this build and others are experiencing it?