Jump to content
InsanelyMac Forum
Sign in to follow this  
potuz

ALC889A pin configuration

Recommended Posts

Hello list, this might be in the opposite direction of what is usually asked here, but I have been having problems with this for over a year now. I own a macbook Air 2,1 with the Realtek ALC889A soundcard. I wiped out Mac OS X from it and installed only Linux (I have no interest on a flame war, just care about the codec in this post). The thing is that with the current Linux driver (ALSA) we can't make the mic work. Since you guys have developed tons of Kexts for this chip and the datasheet is not available I was wandering if you could put in me in the right direction.

 

As of now I could only figure out that using

 

0x18 as main speaker

0x14 as HP and switch

0x19 as HP when it is connected

 

I get audio in the main speaker and headphones appropriately. But I do not know which verb one should use to get the mic working.

 

Any help will be greatly appreciated.

 

Cheers,

 

R.

Share this post


Link to post
Share on other sites
Advertisement

Thanks, I had seen that article and actually it confuses me even more cause there are a couple of pin configurations there in verbs.txt which don't even match up with the working ones in linux... Perhaps I'll try to bug someone on IRC.

 

R.

 

Actually, what I need is in some sense the opposite of the tools in that HOWTO. Namely, that text is based in collecting information from a system in which the audio works. But if I collect from linux I'd get what I fed myself the driver. So what I was wandering is if there's an application for Mac OS X that would return the codec info from a working codec. In that case I can just install mac OS here and then I'll get the info I need.

 

Cheers,

 

R.

Share this post


Link to post
Share on other sites
So what I was wandering is if there's an application for Mac OS X that would return the codec info from a working codec. In that case I can just install mac OS here and then I'll get the info I need.

 

Not sure, I think that once you have sound working you can get all the info via IORegistryExplorer, which comes with Apple XCode. Also several tools are mentioned in the guide, you could probably use those somehow.

 

You could also extract it from the Registry in Windows, as explained in the guide. That's probably the least painful way as long as you don't mind installing Windows.

Share this post


Link to post
Share on other sites

I have that sound codec 10ec/0889 (not 0888).

 

I can send you the pinconfig from windows, the dump from Ubuntu and the dump from VoodooHDA from Snow 10.6.3 all from the same machine, an Intel mobo DP55KG with an i7 860 cpu and a Nvidia gt220 card (sound does not work) and gt9600 nvidia video card (sound does work, voodoohda dump).

 

Let me know what you want.

Share this post


Link to post
Share on other sites
Hello list, this might be in the opposite direction of what is usually asked here, but I have been having problems with this for over a year now. I own a macbook Air 2,1 with the Realtek ALC889A soundcard. I wiped out Mac OS X from it and installed only Linux (I have no interest on a flame war, just care about the codec in this post). The thing is that with the current Linux driver (ALSA) we can't make the mic work. Since you guys have developed tons of Kexts for this chip and the datasheet is not available I was wandering if you could put in me in the right direction.

 

As of now I could only figure out that using

 

0x18 as main speaker

0x14 as HP and switch

0x19 as HP when it is connected

 

I get audio in the main speaker and headphones appropriately. But I do not know which verb one should use to get the mic working.

 

Any help will be greatly appreciated.

 

Cheers,

 

R.

 

you macs alc889a there is no such thing as mac only supported alc885, also if it's a mac, i mean real mac then the pinconfigs are setup through bios and kernel called vendor widgets and mac have over 30 diffrent setups for alc885, if you wiped your mac and put linux on you would have to remap you pin configs in alsa to match a mac layout.

Share this post


Link to post
Share on other sites
you macs alc889a there is no such thing as mac only supported alc885, also if it's a mac, i mean real mac then the pinconfigs are setup through bios and kernel called vendor widgets and mac have over 30 diffrent setups for alc885, if you wiped your mac and put linux on you would have to remap you pin configs in alsa to match a mac layout.

 

That's exactly what I am asking for. The codec identifies itself as alc889a. It is a real macbook air 2,1 and I know that the pin configuration is set on EFI, but I do not know how to get it so that I can tell ALSA what the layout is and what verbs it should use to initialize the mic.

 

I am in the process of re-installing mac os X so that I can try and use IORegistryExplorer as suggested below. @RSN thanks for the offer, I am not sure if these are the same cards, but if I fail with IORegistryExplorer then I'll ask you for your dumps.

Share this post


Link to post
Share on other sites

Anybody got front mic working on ALC889A with AppleHDA/LegacyHDA. I'm waiting for this for quite a long time, I just hope we'll accomplish this someday ...

Share this post


Link to post
Share on other sites
you macs alc889a there is no such thing as mac only supported alc885

 

My apologies, it seems that I forgot about this cause I hadn't touched this issue for a while, you were right, alsa finds the codec as ALC889a but the codec shows:

odec: 0x10ec0885
Address: 0
Function Id: 0x101
Vendor Id: 0x10ec0885
Subsystem Id: 0x106b3500
Revision Id: 0x100103

Anyway, the question is the same, I'd like to know what are the pin configs and the verbs that mac os X sends to the vendor widgets to initialize the mic.

 

Thanks

 

R.

Share this post


Link to post
Share on other sites
My apologies, it seems that I forgot about this cause I hadn't touched this issue for a while, you were right, alsa finds the codec as ALC889a but the codec shows:

odec: 0x10ec0885
Address: 0
Function Id: 0x101
Vendor Id: 0x10ec0885
Subsystem Id: 0x106b3500
Revision Id: 0x100103

Anyway, the question is the same, I'd like to know what are the pin configs and the verbs that mac os X sends to the vendor widgets to initialize the mic.

 

Thanks

 

R.

 

 

 

If you have a real mac, use sys info, goto audio, look at what ID is using, most of apple alc885 dont use codec verbs, only like 3-4 alc885 layouts use it, you can control a codec through bios if you know what your doing with editing.

 

Once you get the ID number, open up AppleHDA --> Plugins --> The platform kext and find the matching ID then check in Plugins --> Hardware kext to see if ID links with verbs.

Share this post


Link to post
Share on other sites
If you have a real mac, use sys info, goto audio, look at what ID is using...

 

...Once you get the ID number, open up AppleHDA --> Plugins --> The platform kext and find the matching ID then check in Plugins --> Hardware kext to see if ID links with verbs.

Alright, I've played quite a while looking through all the info.plist in the relevant kexts to no avail. The id is 0x10DECB79 which corresponds to an alc885 and I can't find anything in the kexts that is specific to this id. This I guess agrees with your comment:

 

most of apple alc885 dont use codec verbs, only like 3-4 alc885 layouts use it, you can control a codec through bios if you know what your doing with editing.

 

Also here, I couldn't find absolutely no information online about this. There's nothing in either the UEFI specification v 2.3 nor in the UEFI shell specification v. 2.0 so if there's a way of controlling the codec through EFI as you suggest I'd greatly appreciate if you can point me to any info online on the topic.

 

Thanks,

 

R.

Share this post


Link to post
Share on other sites

Hello again, from time to time I spend some time in this problem. I looked again in the plists and I don't understand how I missed this, but I guess the relevant part of the plist is:

 


<dict>

<key>MicAttributes</key>

<integer>28</integer>

<key>MicInfo</key>

<string>Sampled on rising edge</string>

<key>NodeID</key>

<integer>39</integer>

<key>PinConfigDefault</key>

<integer>2426405136</integer>

</dict>[code]

 

Which tells me nothing. In particular I don't have a node 0x27=39 (at least not that hda-analyzer sees) so it's not surprising that if I send the corresponding verbs to set_config_default I don't get anything. Also, I don't see how setting the pinconfigdefault could affect my not having the mic working.

 

As for the sampled on rising edge, I don't know how to use this info.. any ideas?

 

Thanks,

 

R.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Posts

    • Hi @fabiosun and thank's for your patience with an old and stubborn man.   I am 100 % sure that my MSR 0xE2 register is unlocked thank's to you.   My system is 100% stable and I haven't had one kp with this configuration in the last two weeks.    I'm now running without TSCAdjustReseat.kext and I can't se any issues in performance with or without that kext. What I however can se is that the amount of total energy consumed during the test-cycle are 10 times higher without the kext (three times Cinebench CPU and two times Luxmark open CL) as you can see in the output from my AppleIntelInfo.kext attached in my earlier post.   I have tested running Cinebench five times in a row with or without TSC kext and have exactly the same performance (see attached files). Temperature is not a problem at all.   Everything seems to be fine so I guess I have to wait and see if upcoming 10.13.5 maybe recognise Intel Xeon w series processor as native.     
    • Tried with HPET enabled and disabled so I don't think it's that. I'd tried with bus ratio before to no effect but wouldn't hurt to try again. The clock runs at the correct speed.
    • could be an HPET / TSC Sync issue. does your system clock slow down or run faster then it should. also check cpu and buss ratios.
    • @MacPeet El capitan. It has t7700 cpu, so HS is not option for now. Have to find t9500 cpu. I bought this laptop for 30euros 3 weeks ago, with everything working, battery like new, it looks like from store, 4gb ram, 1920x1200 17" screen, replaced wifi and put SSD. Also sleep and hibernation working, native brightness, volume touch buttons work. Windows was not option because of broken  touchpad drivers, and linux because of slow graphics. Here everything works like it should.   AD1981 is also on thinkpad T60. I searched everywhere, but no solution. Here is some half working legacy driver, don't know how binary was patched(if it was): https://forum.thinkpads.com/viewtopic.php?t=85344&start=28#p564260
    • the slowness is most likely IM's host provider. we used to use ONE.com but they sucked and it was super slow so we switched and things definitely got better on the slowness front


×