Jump to content

balderdashian

Members
  • Content count

    32
  • Joined

  • Last visited

About balderdashian

  • Rank
    InsanelyMac Protégé
  1. I believe ugokind explains the problem in the post just before yours. It needs a different DSDT that apparently can be found somewhere in this thread.
  2. For anyone interested, I got a great working 10.8 setup with pcb rev 01 of this board. No special DSDT hacking or kexts. The only catch is that I don't use the onboard graphics. I have an EVGA GT 240 card. After my successful install I took it out and rebooted to test the on-boad graphics and it didn't boot. Changing to "GraphicsEnabler=No" may do the trick though. If I try it I'll edit this post EDIT: That didn't work either. Note that I only checked the HDMI output. Other video outputs might work, and a DSDT file might solve everything. I'd love to test it more and try to get it working but I'm having overheating issues when the onboard GPU is enabled. So for this layman's guide you need a supported graphics card, a USB pen drive (8gb), and a working OSX or OSX86 system (I used 10.6.6 - earlier versions may or may not work). Your Zotac board also requires 2GB of RAM or more. I did not test the onboard audio as I use HDMI audio. Ethernet works perfectly. 1. Set BIOS to standard settings used by people in this thread. Enable AHCI for SATA, enable HPET, disable serial port, set audio to "External Codec" and set the USB Legacy to Low Speed. * 2. Flash your BIOS with the modded firmware per the OP of this thread. 3. Use Google to find a popular, universal Mac application that's used to turn an 8gb or greater USB flash drive into a 10.8 install disk if you have the App Store version of the OS. 4. Set your BIOS to boot from the USB flash drive first. 5. Boot to it, open up Disk Utility, and prepare the hard drive volume you wish to install to (Mac OS Extended Journaled, GUID). 6. Install Mountain Lion to your new system disk. 7. Reboot, still booting from the USB flash drive, but select your new system disk in the bootloader menu. 8. Download the latest installer package for the Chimera or your favorite 10.8 compatible bootloader. Run it and install it to you system disk - BUT WAIT, this doesn't fully install it... 9. Bootloader installers seem to be unable to create the needed "/Extra" folder so create one manually on your system disk and copy the contents of the "/Extra" folder on the USB drive over to it. The folder is hidden, so use the Terminal or unhide it. 10. Unmount and unplug the USB drive and reboot using just your system disk. Voila. ** 11. If you have my graphics card and want HDMI audio, you'll need to download and install VoodooHDA 2.7.4 and reboot. Then open System Preferences/Sound and select the 2nd of 4 HDMI entries as your sound output device. Then go to /Applications/Utilities and open up Audio Midi Setup. Change your HDMI output format from 192k Hz to 48k. 12. Combo update to 10.8.1 did not cause any problems. * UPDATE 1: According to ugokind (post #757 in this thread), the modded BIOS uses an older type of DSDT entry that prevents the onboard Nvidia 9300 GPU from working in Lion and Mountain Lion. So you might want to just use the newer DSDT instead of doing the BIOS mod. ** UPDATE 2: This applies to those with my setup (EVGA GT 240 and possibly other graphics cards). Do not install VoodooHDA. It was responsible for all my inexplicable problems. The issue is that once installed and the kext cache is cleared, it works fine. But if I changed any audio settings or installed any additional hardware (like my USB Wifi, or my printer driver) the system would hang on reboot. Once I removed it from S/L/E, all my "PCI Configuration Begin" and KP problems ended. A workaround to still get HDMI audio is to search for a program on this board called VoodooLoader. Download it, and the VoodooPatcher, and patch it with the latest version of VoodooHDA.kext (2.7.4). This lets you manually load VoodooHDA when you need it without installing it. This usually works but sometimes causes a panic. It seems if you launch it and don't touch anything for 30 seconds, it's less likely to cause the KP.
  3. Scrax, Incredible! Works great!. Can't tell you how much I appreciate it. The only strange thing is that the DVI out works but not the HDMI plug (this is true when using any driver or even the 1280x1024-only unrecognized mode, so it's probably a hardware problem). But it doesn't matter because I'm still getting HDMI audio if I use a DVI-HDMI adapter. I didn't even think that was possible.
  4. Thanks! I'm trying to add the code seen here in tmongkol's post #260 on this page: http://www.insanelymac.com/forum/index.php...p;#entry1448833 Device (PEGP) { Name (_ADR, 0x00010000) Name (_PRW, Package (0x02) { 0x09, 0x05 }) Device (GFX0) { Name (_ADR, Zero) Method (_DSM, 4, NotSerialized) { Store (Package () { "AAPL,slot-name", "PCI x16", "@0,compatible", Buffer (0x0B) { "NVDA,NVMac" }, "@0,device_type", Buffer (0x08) { "display" }, "@0,name", Buffer (0x0F) { "NVDA,Display-A" }, "@1,compatible", Buffer (0x0B) { "NVDA,NVMac" }, "@1,device_type", Buffer (0x08) { "display" }, "@1,name", Buffer (0x0F) { "NVDA,Display-B" }, "NVCAP", Buffer (0x18) { /* 0000 */ 0x04, 0x00, 0x00, 0x00, 0x00, 0x00, 0x03, 0x00, /* 0008 */ 0x0C, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x07, /* 0010 */ 0x00, 0x00, 0x00, 0x00 }, "VRAM,totalsize", Buffer (0x04) { 0x00, 0x00, 0x00, 0x20 //change it for your graphic card }, "device_type", Buffer (0x0C) { "NVDA,Parent" }, "model", Buffer (0x15) { "nVidia GeForce GT240" //change it for your graphic card }, "rom-revision", Buffer () { "3172a" //change it for your graphic card. I am not sure about this. Some recommended use this "3172a." }, "hda-gfx", Buffer (0x0A) { "onboard-1" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } Device (HDAU) { Name (_ADR, One) Method (_DSM, 4, NotSerialized) { Store (Package (0x02) { "hda-gfx", Buffer (0x0A) { "onboard-1" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } } The above is for his Galaxy GT 240 in a Gigabyte motherboard. I have a Galaxy GT 220 and of course the Zotac ITX 9300 (revision 1). The DSDT I've been I believe is the one you posted on page 29. It is attached. dsdt.aml.zip
  5. Can somebody point a newb in the right direction? I have this board working fine with SL using the DSDT in this thread. I just got a new Nvidia GT 220 card I want to use. Can anyone give me any tips on how to edit the DSDT so this card works with the vanilla 10.6.4 kext? I know how to find all the data for my card using IORegistryExplorer, and I've seen some generic templates for inserting Nvidia GT 2xx cards. But any time I try to add to the PCI0 field, I always get compiler errors.
  6. balderdashian

    ALC889A, Gigabyte (Intel): now having a working front mic

    Thanks for trying, much appreciated. Can you recommend a specific PCI card I should buy? One that could perhaps give HDMI audio without any patching? In your instructions, you say the GT 220 is a good choice. Is that still the case?
  7. balderdashian

    ALC889A, Gigabyte (Intel): now having a working front mic

    @emt, Thanks, that compiled right, but now there's no sound device at all. I'll double check everything. Also, what is your audio setting in the BIOS? Are you using External Codec, or INT + EXT Codec?
  8. balderdashian

    ALC889A, Gigabyte (Intel): now having a working front mic

    Thanks, that's incredibly kind of you! I actually did open his dsdt. In mine, my audio section it has this: "device-type", Buffer (0x0F) { "Realtek ALC662" }, "PinConfigurations", Buffer (Zero) {} }, Local0) emt's same section has this: "device-type", Buffer (0x12) { "Realtek ALC662" }, "PinConfigurations", Buffer (One) { 0x00 }, "hda-gfx", Buffer (0x0A) { "onboard-1" } }, Local0) Anyways, I copied his into mine, but when I try to compile it, I get this error: "Error 4047 - Initializer list longer than declared package length" I'm guessing something at the top is stating how long the DSDT is supposed to be and by me adding to it, it doesn't like that. @ emt, I see there's discrepancies in hardware IDs between ours. I have the original rev. 1 of the board, you probably have a newer one. But I'm assuming that the "hda-gfx" part is the one I need to add. And yes, I am following the [GUIDE]+[sT...." thread as well. Getting HDMI working would be fantastic. I actually run everything in my home (TIVO, game consoles, media center, etc.) through a Monoprice HDMI matrix switch. So unlike most users with this board, I actually have real need for HDMI audio. Hope we get it working!
  9. balderdashian

    ALC889A, Gigabyte (Intel): now having a working front mic

    Thanks for the reply. I'm in the same situation as emt who has a stronger understanding of this, so I'll just follow your conversation with him/her.
  10. balderdashian

    ALC889A, Gigabyte (Intel): now having a working front mic

    HDMI audio works fine in Windows. It's a Zotac 9300 ITX.
  11. balderdashian

    ALC889A, Gigabyte (Intel): now having a working front mic

    Is HDMI audio possible with an onboard 9300 GPU (not a PCI card)?
  12. I just did that and it worked. Do you know if HDMI audio is possible as well?
  13. I have this board working great. I was hoping to get HDMI audio working like this guy did: http://www.insanelymac.com/forum/index.php...0941&st=758 I'm new to patching and he doesn't say which files to patch. Has anyone already done this for this board?
  14. balderdashian

    D945GCLF2 Snow Leopard

    Thanks a million for this mini guide. I had been running 10.5.8 (with the 10.5.6 kernel for Hyperthreading) as my main machine for about a year now. Using this as a guide (and all the other things people here contributed) I was able to get SL on there and working pretty easily. With my old Leo install, performance was an absolute joke (even with HT enabled). Even this site had trouble loading. Safari or FF made no difference. If I watched a low-quality FLash video from YouTube or something, I'd be lucky to get 5 frames per second. Now with SL it's incredibly faster. I can even watch high quality Flash videos on Hulu with the full frame rate - okay maybe a hiccup every minute or so but it's very smooth for the most part.
×