Jump to content

Lord Kamina

Members
  • Content Count

    23
  • Joined

  • Last visited

Everything posted by Lord Kamina

  1. So... I know HWMonitor has a fan controlling module, which can be accessed by hovering over the fans on the list of sensors. I also know this dialog does not generally show on hackintosh. There is evidently something the program is looking for, and that something determines whether to show it or not. I'm trying to figure out what that check is... Anybody familiar with the HWMonitor code, that might give me a hand with this?.
  2. Actually, the App Store problem can also be solved relatively easily by disabling network cards, deleting AppStores caches and NetworkInterfaces (Google it, there's at least one good tutorial) and then re-adding/re-enabling the network cards.
  3. Hey Beta; I finally got it! Check out the topic I posted in "User Guides"
  4. DISCLAIMER:I have made this guide for people using ATI/AMD GPUs because that is what I have, because as-far-as-I-know AMD uses only one audio codec and because it's what I've tried and know, works. Still, the principle should be just as valid for NVIDIA or even Intel HD cards. My Build: [*:27ud9cd4]Motherboard: Asus P5G41T-M LX PLUS [*:27ud9cd4]CPU: Intel E7400, overclocked @ 3.37GHz [*:27ud9cd4]Memory: 4GB Ram DDR3 1333 [*:27ud9cd4]Ethernet: Realtek RTL8169 [*:27ud9cd4]Audio Codec: ALC887-VD [*:27ud9cd4]Graphics: XFX Radeon HD 5570 1GB DDR3 [*:27ud9cd4]OS: Mountain Lion 10.8.2 I bought this Asus board a couple months ago and mostly it works very well. Now, when I bought it I looked at the audio codec but I didn't search for actual user experiences getting it to work (my mistake) and to my surprise, upon getting home I quickly realized that AppleHDA and my board just weren't the best of buddies. Flash-forward a couple of weeks and I'm resigned to using VoodooHDA. Now, VoodooHDA doesn't make friends with my HDMI audio so I have to choose between AppleHDA and HDMI or Voodoo and on-board and frankly, that sucks. The solution? Use both at the same time! Now, usually this will result in a kernel panic. Why? Because by default both these kexts try to match devices by their PCI-Class and logically end-up trying to take control of the same devices and that's not good. But, with a few minor edits it's possible to have them both coexist peacefully. Normally, AppleHDA(AppleHDA.kext/Contents/Plugins/AppleHDAController/Contents/Info.plist) will have these lines near the bottom: IOClass AppleHDAController IOPCIClassMatch 0x04020000&0xFFFE0000 IOProviderClass IOPCIDevice And VoodooHDA.kext/Contents/Info.plist will have these: IOClass VoodooHDADevice IOPCIClassMatch 0x04020000&0xFFFE0000 IOProviderClass IOPCIDevice See the similarity? Now, if instead you change them to the following (note, the actual values might and probably will change depending on your actual on-board codec and GPU) And Now Voodoo will know to try and match only your on-board audio and AppleHDA will know to try and match only your GPU's audio. Clearly, you're not yet quite done. For this to work, you will need more-or-less the same DSDT edits you would use to enable HDMI audio normally (and if you're using an AMD card like me, you need to be sure your Framebuffer is correct, which I won't go into now) The only departure from the tried-and-true DSDT edit for AMD cards is the following (I'm not entirely sure it is needed but I did it this way and it worked) You must add the layout-id that normally goes in the HDEF section to the HDAU section, like this: Once all that is done, you need to edit AppleHDA proper: Since Mountain Lion supports ATI HDMI audio OOB, you only need to change the layout/pathmap to suit your card. You will find numerous tutorials explaining in details how to do that. For now, what I did was use layout id: 1 and defined it thus: And then in Platforms.xml, I did this: The Node IDs I just get from a codec dump of my HDMI card done in Linux. After all this was done, I deleted all other layouts and Pathmaps (left the DSP section alone, though) and compressed those XMLs again using zlib.pl, just ran MyFix, rebooted and all was working as expected. [*:27ud9cd4]System Info: http://olarila.com/forum/viewtopic.php?f=6&t=63 [*:27ud9cd4]How to modify your DSDT to add your ATI/AMD GPU: http://rampagedev.wordpress.com/2012/07 ... dsdt-36-2/ [*:27ud9cd4]zlib.pl: http://www.olarila.com/forum/viewtopic.php?f=27&t=1702 I am attaching both my own modified AppleHDA (done as per the instructions here, the binary itself is intact, I just messed with the Info.plists, pathmaps and whatnot) and my IORegistry so you can have fun with it: AppleHDA_HDMI.kext.zip Tiamat_Voodoo_AppleHDA.ioreg.zip
  5. Sadly I know, and that was pretty much the "why" for this topic: Brainstorming lateral-thinking solutions and/or whining about my shit-luck with components.
  6. I am using VoodooHDA because AppleHDA didn't work either (I'll see if I can find an older IOReg with AppleHDA; with it, even the TV's brand was recognized in the Output options but there was still no sound) and Voodoo at least works with my onboard audio (which AppleHDA didn't) Edit: Here. I suppose I could have gotten the Framebuffer wrong that time but I don't think it's likely. dsdt_onboard-1_Tiamat.ioreg.zip
  7. What does a man have to do to be believed around here? Note the HDMI isn't actually connected in this IOReg (I did select it in the Sound Output, though) Archive.zip
  8. There is at least one on my topic in the "Post-Installation" forum. That one's probably with VoodooHDA but I'm sure I've got a few with AppleHDA also. In either case the kexts detects and attaches to the card but there's no sound.
  9. Yeah but I'm stuck with the local supply here in Chile. I could have always ordered something from overseas I guess, but it would have taken too long to get here.
  10. Yeah, that kind of sucks... :/ And I actually did a research before buying my current motherboard and GPU (but I never thought Asus ALC887 specifically and XFX 5570 had issues...) I guess I know better for next time, assuming next time I won't have enough to say "Screw this, I'll just get a Macbook Pro." Anyway, you know what makes it worse? That if I'd waited a month, I would have gotten the MSI 5770 for the same price I paid, that's the problem with buying "old-ish" hardware.
  11. I know. I'm asking beyond the Framebuffer. I have tried already every conceivable combination of modifications to my frame-buffer and HDMI audio just will not work (everything else is perfect).
  12. So as I have spammed and spewed all over the internet, I have been consistently sucking at choosing my hardware (somehow managing to get hardware that works except FOR THAT ONE VERSION _I_ GOT) and there's something that just sort of occurred to me regarding my 5570... Is there any way to actually modify how the cad connects to its ports? Can the encoder/transmitter be modified in the card's BIOS or something like that? Or are all those things inherent to the physical connections on it? Would it, for example, be possible to flash one GPU with the BIOS for the same GPU but by another manufacturer? Would that change anything, would it be the same?
  13. But, why? What did you find backing that? My codec is ALC887-VD, on Address 0. Does the layout number really matter? I used what the kext had for default and then manually edited both the layout to make sure it fitted with what I've really got and did the same for the pin configs and path maps. Wouldn't a wrong layout/kext make all devices disappear? Not, for example, if I open an audio application while IOregistryExplorer is open, it will be updated with a new IOAudioClient (or IOHDAClient, can't remember the proper name...) meaning the system IS recognizing the audio, and it does try to output sounds through the appropriate ports (seeing as I only get the clicking/popping noise if I select the actual port onto which the headphones are plugged in) P.S. I just attached my codec dump (from Ubuntu) and the codecgraph generated out of that dump. P.S.2. Hmm, if you said it because of the whole "layout-id: c" and "layout-id" Unicode("c") in the DSDT... I fell for it at the beginning too, but it appears to be one of IASL's compiling optimizations and mac apparently translates it to "99" wherever it actually matters. card0-codec#0.txt card0-codec#0.txt.svg.zip
  14. Errr... I did? It's in the attachments, along with the DSDT.
  15. Hello! I've been trying to get this audio to work properly for a few weeks now, so far unsuccessfully. Here's where I'm at: I've edited my DSDT properly, I dumped my codecs and got my verbs, I tried to patch my own AppleHDA (but I failed miserably , so instead I downloaded one of two 10.8.2 ALC887 AppleHDA.kexts found on osx86.net, though I only replaced the binary, since I had already edited my layout and pathmaps and pin configs) With that, I boot and get a single sound assertion from AppleHDAController (I've noticed a few others triggered under specific circumstances: trying to change the sample rate or bit-depth in the Audio/MIDI Setup, for example) but otherwise AppleHDA appears to load properly. My IOReg shows AppleHDA and all its components loaded, it shows several HDAStreams, etc etc. In devices, I can see a Line-in, Speakers, a Line-Out and a Digital Out. If I connect my headphones to the appropriate port and try changing the output volume I get a single, relatively loud "POP" and then nothing. So, it happens the first time a sound would be output through the phones after being plugged in, basically. And I have tried editing everything I can think off, with no success. Either I break it and the Devices stop showing or just nothing changes. Attached are the a screenshot , the DSDT I'm using and the IORegistry. So far, the only "weird" thing I've been able to notice is under "AppleHDADriver", the "PowerProfile" has "CurrentPowerLevel", "IdlePowerLevel" and "MaxPowerLimit" all set to 0x0. I have no idea if this is at all related but from the symptoms it seems to me like it could be a power issue? If not, maybe someone else will have a better answer? Archive.zip
×
×
  • Create New...