Help - Search - Members - Calendar
Full Version: AD1984 used in Thinkpad X61 and L61 computers
InsanelyMac Forum > OSx86 Project > Hardware and Drivers > Sound
Pages: 1, 2, 3, 4
jacob019
Here's my research so far. Let's all give this some effort and get it sorted out.

After installing taruga's ad1986 patch I modified the plist files for AppleHDA.kext and AppleHDAController.kext to match our ad1984 by changing string 299112838 to 299112836. According to ioreg, AppleHDAController and IOHDACodecDevice load fine. The problem is now with IOHDACodecDriver.

I've noticed a clever solution at http://forum.insanelymac.com/index.php?showtopic=61513 for a different chip. This guy was stuck at exactly the same point and managed to resolve it. I think we can adapt his method to get our sound working.

It seems the next step involves modifying the Info.plist for ALCinject.kext. The layout-id field needs to be changed. It's important to modify the field with a property list editor, as a standard text editor doesn't display it right. Tarugas AD1986 patch has the field set to 13 or 0D000000 in hex. Based on the work of macdanger it seems we just need to try many values sequentially until one loads the driver. After we load the driver successfully then we can move on to fixing the codec.

The datasheet for our AD1984 can be found at: http://www.analog.com/UploadedFiles/Data_Sheets/AD1984.pdf
The linux codec dump is attached.

Post your thoughts and results here. We can do it!

Jacob
Wenle Z.
interesting... i wish someone can have this solve, so i can have a real insgtallatino on my X61
popophobia
Let's do this.

can you upload the modiefied AppleHDA.kext (modified so far) so we can work on it?

And, after sequentially trying all the values for layout-id, do we do ioreg to see if the driver is working?

I will try to look around to see what I can do. But yes, we need sound for X61. One step closer to completely functioning Mac.
jacob019
Popophobia,

Here's my AppleHDA.kext, the codec will still need some work. I've also included a few lines from "ioreg -l". These devices are nested sequentially. Notice how everything load up until IOHDACodecDriver where it says !registered, !matched (! meaning not). You may also notice that there is IOHDACodecDevice@0 and IOHDACodecDevice@1, we are only concerned with IOHDACodecDevice@0, the other one is the modem I believe. I believe we need to get ALCinject working first. Keep me posted.

AppleHDAController <class AppleHDAController, registered, matched, active, busy 0, retain 7>
IOHDACodecDevice@0 <class IOHDACodecDevice, registered, matched, active, busy 0, retain 6>
IOHDACodecDriver <class IOHDACodecDriver, !registered, !matched, active, busy 0, retain 5>
IOHDACodecFunction@1 <class IOHDACodecFunction, registered, matched, active, busy 0, retain 4>

This laptop really kicks ass as a hackintosh, everything's working great for me except audio and SpeedStep. I put in an atheros wifi card today and it works just like an airport express! If we get audio going we'll have the perfect machine. I'd buy a MacBook if they made them in 12"
popophobia
Got it. I'll try it out to see how I can do it.

So, after changing the kext file and fixing permission, do we have to reboot or is a kextload command sufficient?

Found this:
http://x86osx.com/bbs/view.php?id=freeboar...7c39bc46e3a6e0f

Seems like 1984 support is on the way.

(you can use google translate)
jacob019
it looks promising, but that post was in early January. After modifications run "sudo rm /System/Library/Extensions.*" That should be enough for the drivers to be reload next boot.
popophobia
Hey,
I found out something today. If you play a song in OS X and unplug the AC adapter, there's a short burst of sound from the speaker. Maybe there is something wrong with the power management control of HDA kext file.

I installed Azalia patch and was able to get the volume control (and this weird behaviour).

Here's part of the ioreg output

CODE
    | |   | +-o AppleAzaliaController  <class AppleAzaliaController, registered, matched, active, busy 0, retain 8>
    | |   |   | {
    | |   |   |   "IOProviderClass" = "IOPCIDevice"
    | |   |   |   "IOProbeScore" = 0
    | |   |   |   "CFBundleIdentifier" = "com.apple.driver.AppleAzaliaController"
    | |   |   |   "IOMatchCategory" = "IODefaultMatchCategory"
    | |   |   |   "IOPCIPrimaryMatch" = "0x26688086 0x27d88086 0x284b8086 0x32881106 0x026c10de 0x037110de 0x03e410de 0x03f010de 0x044a10de 0x044b10de 0x437b1002 0x43831002 0x75021039"
    | |   |   |   "IOPowerManagement" = {"ChildrenPowerState"=2,"CurrentPowerState"=2}
    | |   |   |   "IOClass" = "AppleAzaliaController"
    | |   |   | }
    | |   |   |
    | |   |   +-o IOHDAudioCodecDevice@0  <class IOHDAudioCodecDevice, registered, matched, active, busy 0, retain 6>
    | |   |   | | {
    | |   |   | |   "IOHDAudioCodecVendorID" = 299112836
    | |   |   | |   "IOHDAudioCodecRevisionID" = 1049600
    | |   |   | | }
    | |   |   | |
    | |   |   | +-o IOHDAudioCodecDriver  <class IOHDAudioCodecDriver, !registered, !matched, active, busy 0, retain 5>
    | |   |   |   | {
    | |   |   |   |   "IOProviderClass" = "IOHDAudioCodecDevice"
    | |   |   |   |   "IOProbeScore" = 0
    | |   |   |   |   "IOMatchCategory" = "IODefaultMatchCategory"
    | |   |   |   |   "IOClass" = "IOHDAudioCodecDriver"
    | |   |   |   |   "CFBundleIdentifier" = "com.apple.iokit.IOHDAudioFamily"
    | |   |   |   | }
    | |   |   |   |
    | |   |   |   +-o IOHDAudioCodecFunction@1  <class IOHDAudioCodecFunction, registered, matched, active, busy 0, retain 6>
    | |   |   |     | {
    | |   |   |     |   "IOHDAudioCodecFunctionSubsystemID" = 397025501
    | |   |   |     |   "IOHDAudioCodecFunctionGroupType" = 1
    | |   |   |     | }
    | |   |   |     |
    | |   |   |     +-o AppleAzaliaAudioCodecGeneric  <class AppleAzaliaAudioCodecGeneric, registered, matched, active, busy 0, retain 10>
    | |   |   |       | {
    | |   |   |       |   "IOProviderClass" = "IOHDAudioCodecFunction"
    | |   |   |       |   "IOProbeScore" = 0
    | |   |   |       |   "IOMatchCategory" = "IODefaultMatchCategory"
    | |   |   |       |   "IOHDAudioCodecFunctionGroupType" = 1
    | |   |   |       |   "IOClass" = "AppleAzaliaAudioCodecGeneric"
    | |   |   |       |   "CFBundleIdentifier" = "com.apple.driver.AppleAzaliaAudio"
    | |   |   |       | }
    | |   |   |       |
    | |   |   |       +-o AppleAzaliaAudioDriver  <class AppleAzaliaAudioDriver, registered, matched, active, busy 0, retain 6>
    | |   |   |         | {
    | |   |   |         |   "IOProbeScore" = 0
    | |   |   |         |   "IOAudioDeviceManufacturerName" = "Apple"
    | |   |   |         |   "InputSampleLatency" = 30
    | |   |   |         |   "CFBundleIdentifier" = "com.apple.driver.AppleAzaliaAudio"
    | |   |   |         |   "IOMatchCategory" = "IODefaultMatchCategory"
    | |   |   |         |   "IOPowerManagement" = {"CurrentPowerState"=1,"DriverChangePowerState"=1}
    | |   |   |         |   "IOAudioDeviceShortName" = "Built-in"
    | |   |   |         |   "IOProviderClass" = "AppleAzaliaAudioCodec"
    | |   |   |         |   "IOAudioDeviceCanBeDefaults" = 7
    | |   |   |         |   "IOAudioDeviceTransportType" = 1651274862
    | |   |   |         |   "IOAudioDeviceName" = "Built-in Audio"
    | |   |   |         |   "IOAudioDeviceModelID" = "AppleAzaliaAudioDriver:Built-in Audio"
    | |   |   |         |   "SampleOffsetPad" = 0
    | |   |   |         |   "IOClass" = "AppleAzaliaAudioDriver"
    | |   |   |         |   "OutputSampleLatency" = 30
    | |   |   |         | }
    | |   |   |         |
    | |   |   |         +-o AppleAzaliaAudioEngineOutput  <class AppleAzaliaAudioEngineOutput, registered, matched, active, busy 0, retain 21>
    | |   |   |           | {
    | |   |   |           |   "IOAudioEngineOutputSampleLatency" = 30
    | |   |   |           |   "IOAudioEngineDescription" = "HD Audio Output"
    | |   |   |           |   "IOAudioEngineNumActiveUserClients" = 0
    | |   |   |           |   "IOAudioEngineNumSampleFramesPerBuffer" = 16384
    | |   |   |           |   "IOAudioEngineSampleOffset" = 32
    | |   |   |           |   "IOAudioEngineClockDomain" = 87819776
    | |   |   |           |   "IOAudioEngineState" = 0
    | |   |   |           |   "IOAudioEngineFlavor" = 1
    | |   |   |           |   "IOAudioEngineGlobalUniqueID" = "AppleAzaliaAudioEngineOutput:0"
    | |   |   |           |   "IOAudioSampleRate" = {"IOAudioSampleRateFraction"=0,"IOAudioSampleRateWholeNumber"=44100}
    | |   |   |           |   "IOAudioEngineInputSampleLatency" = 30
    | |   |   |           |   "IOGeneralInterest" = "IOCommand is not serializable"
    | |   |   |           | }
el31415
Any news on the sound for x61 ?
mulletman13
I would also like to know this, as I have a Thinkpad R61 with the same sound adapter.

Thanks!
stinkytofu
Hope for the best if this project is still going on... sound would be superb on T61's as well...
wildfire2
Yea, we need sound! T61 is awesome as Hackintosh. Also, what Atheros wifi card models works with this and do I need to make mods or does csard work out of the box?
stinkytofu
wildfire2

i use the thinkpad a/b/g card and it works.

use this guide here for editing the wireless

http://forum.thinkpads.com/viewtopic.php?t=52240

i have Nvidia NVS 140 M graphics card and i still dont have graphics acceleration - so the closest thing i can get is doing the same thing as that guy - 1440x900 manual edit.
mulletman13
I think our best bet is to try and get Taruga to personally look at it on his forum. I'm really hoping that we'll be able to get this.... an entire notebook manufacturer (Lenovo) uses this chip for their portables... he'd be helping a lot of people!

I read somewhere that there was some info about the card buried in 10.5.3 but I haven't updated yet. Anybody familiar?

Taruga's wiki is here:

http://wiki.taruga.net/

Sign up and make some noise!
jacob019
It's unfortunate that we've been unable to get sound going on this thing. For the most part I like my X61 hackintosh more than my macbook, but I've given up. I'm going to sell my X61 and buy an X60.
mulletman13
jacob,

Have you tried these things under 10.5.3? I get some different behaviour with the AD1984 and I hear that there is some mention of the codec in native OSX code. If not, can you tell me what to do so I can keep atempting things?

Thanks much!
jacob019
Hi Mulletman,

I haven't tried 10.5.3 yet. I have also heard these rumors, but no one has ever reported success. I'll try upgrading and see what happens.

Jacob
mulletman13
According to : http://www.thinkwiki.org/wiki/AD1984

the AD1984 shares a bus with the modem... I'm not entirely sure what they are talking about in that Wiki, but it seems that in whatever OS they are talking about the sound card would not work until the modem was initialized..... I haven't tried it, but do our modems work? Are they initialized at all?
jacob019
ALSA is for linux sound. From what I gather, they're just saying that you can't disable the modem in the bios without affecting the sound. It shouldn't matter for us, you don't actually need modem drivers loaded, and the hardware is definitely initialized as it shows up in ioreg.
mulletman13
Got it. I installed your modified AppleHDA.kext in 10.5.3, and it takes away the functionality of the volume buttons. Additionally all media plays for about two seconds and then stops. I know it wasn't a completed HDA or anything whatsoever, I'm just trying to see what was modified and where to go from here. I have a lot of time on my hands at this point, and I'd like to try whatever I can-- I'm just not entirely sure on where to start.
mulletman13
QUOTE(jacob019 @ Mar 10 2008, 06:02 AM) *
Here's my research so far. Let's all give this some effort and get it sorted out.

After installing taruga's ad1986 patch I modified the plist files for AppleHDA.kext and AppleHDAController.kext to match our ad1984 by changing string 299112838 to 299112836. According to ioreg, AppleHDAController and IOHDACodecDevice load fine. The problem is now with IOHDACodecDriver.

I've noticed a clever solution at http://forum.insanelymac.com/index.php?showtopic=61513 for a different chip. This guy was stuck at exactly the same point and managed to resolve it. I think we can adapt his method to get our sound working.

It seems the next step involves modifying the Info.plist for ALCinject.kext. The layout-id field needs to be changed. It's important to modify the field with a property list editor, as a standard text editor doesn't display it right. Tarugas AD1986 patch has the field set to 13 or 0D000000 in hex. Based on the work of macdanger it seems we just need to try many values sequentially until one loads the driver. After we load the driver successfully then we can move on to fixing the codec.

The datasheet for our AD1984 can be found at: http://www.analog.com/UploadedFiles/Data_Sheets/AD1984.pdf
The linux codec dump is attached.

Post your thoughts and results here. We can do it!

Jacob



I just want to get this straight so I can start getting some work done.

So the first thing that I did was install Taruga's 1986 patch. Then I changed 299112838 to 299112836. Just curious -- but where does this number come from? In any case, after I did that, I open up Info.plist in ALCinject.kext and sequentially change the layout-id field? How am I sure that the driver loads? ALCInject.kext will appear in ioreg? Sorry, macdanger's post didn't really lead me to understand what was going on.

Nevertheless what numbers have you tried in ALCInject's plist? I'm sure we would have a legion of people behind us trying different things if there are more clear-cut instructions smile.gif

Thanks!
jacob019
I'm pleased that you're interested. 299112836 is the decimal equivalent of 11d41984 (the vendor id and product code for our device). Type "ioreg -l" into the terminal. This lists all the hardware and how it's connected, similar to windows device manager in tree view, but with more detail. Look for AppleHDAController. This is where macos recognizes our audio hardware device. Several subnodes must be connected to it in order to have usable audio. Even after the hardware is all properly recognized, we will have to adjust the codec so that the driver can speak the proper language to the audio chip. The goal right now is just to make the audio chip recognized completely, after that we may still have broken audio, but we should hear something from the speaker when sound is played, even if it is all garbled. The subnodes in my ioreg output are:
| | | +-o AppleHDAController <class AppleHDAController, registered, matched, active, busy 0, retain 7>
| | | +-o IOHDACodecDevice@0 <class IOHDACodecDevice, registered, matched, active, busy 0, retain 6>
| | | | +-o IOHDACodecDriver <class IOHDACodecDriver, !registered, !matched, active, busy 0, retain 5>
| | | | +-o IOHDACodecFunction@1 <class IOHDACodecFunction, registered, matched, active, busy 0, retain 4>
| | | +-o IOHDACodecDevice@1 <class IOHDACodecDevice, registered, matched, active, busy 0, retain 6>

there are more detals listed but this is the gist of it. The last line IOHDACodecDevice@1 represents our modem, this should be ignored. Notice how lines all say registered, matched except IOHDACodecDriver? If your output is like this than you've gotten as far as I have. Macdanger was able to get IOHDACodecDriver loaded for his unsupported card. Changing tarugas driver gets us this far, but working on ALCinject.kext should get IOHDACodecDriver working. It will be a tedious process, with many reboots, and I'm not even 100% confident that it will work, but macdanger made it work.

To see if you're successful type "ioreg -l|grep IOHDACodecDriver"
we only care about the first line, if you are successful then !resgistered, !matched will turn into registered, matched

Jacob
mulletman13
I know I'm going to sound like a complete idiot here (sorry for that-- I do know my way around things I'm just a bit confused here), but I don't seem to even have IOHDACodecDevice.kext at all. I don't have any IOHDA* kext's whatsoever. I've looked in AppleHDA.kext for them (but I was pretty sure they were full extensions), but to no avail. Typing that command in Terminal shows absolutely nothing.

10.5.2 iAtkos vanilla kernel install, with kaly combo update to 10.5.3. Would you be able to upload it at all if possible?

Oh yes, and FINALLY: I'm editing with Apple's Property List Editor. The layout-id is written as a data class, and the value is <0c000000>. I have no clue what to convert this to, or how to convert it to numbers that make sense to me.

I assumed it was hexadecimal to decimal like this:

http://www.statman.info/conversions/hexadecimal.html

But that converts 0c000000 to a gigantic number. I'd appreciate any help. And what should I start at? 1 - ... sky's the limit? 0? Thanks for holding my hand through this.

Edit: I'm going right back to stock 10.5.2 so I can start over (I am pretty sure my Extension folder is messed up).
mulletman13
Alright... after having some issues I finally got back to 10.5.2, and was able to get started.

I've done decimal values from 00-53 (00 to 35 in hex) so far and nothing has turned the '!matched' to 'matched'. What are the range of numbers that it could possibly be? What numbers have you tried?

If anybody is interested in getting a chunk of numbers done, post up here what you're interested in doing! Be sure to follow the first post in this topic.

My system is as follows: Have an ALCInject.kext on the desktop that is owned by the current user (so it can be edited out of command line). I had Property List Editor, Terminal, and kext helper all open at startup. Upon startup, I would run the command to check and see if IOHDACodecDriver was matched. When I found it wasn't, I would open-->recent ALCInject.kext on the desktop.... edit the layout-id field to the next sequential one then save it. I would drag that kext into kext helper and run that. That replaces ALCinject, changes the permissions back to root only, and also touches Extensions.mkext in order to reload each boot.

Anyways like I said this system worked well-- but alas I have not gotten any results yet.
Taruga
I always use layout id = 12 not 13. It can be any number, that's not important if the layout id and path maps are linked to the layout id.
QUOTE(jacob019 @ Mar 10 2008, 07:02 AM) *
It seems the next step involves modifying the Info.plist for ALCinject.kext. The layout-id field needs to be changed. It's important to modify the field with a property list editor, as a standard text editor doesn't display it right. Tarugas AD1986 patch has the field set to 13 or 0D000000 in hex. Based on the work of macdanger it seems we just need to try many values sequentially until one loads the driver. After we load the driver successfully then we can move on to fixing the codec.
No need for translation, itīs a copy of one of my posts here at Insanely Mac
QUOTE(popophobia @ Mar 14 2008, 09:21 AM) *
Got it. I'll try it out to see how I can do it.So, after changing the kext file and fixing permission, do we have to reboot or is a kextload command sufficient?Found this:http://x86osx.com/bbs/view.php?id=freeboar...7c39bc46e3a6e0fSeems like 1984 support is on the way.(you can use google translate)
jacob019
I'm honored to see a post from Taruga in this thread. It seems we need to study up on path maps. Thank you Targua!
Taruga
You can try the layout-ids you want.... apple doesn't use ad1984, nor the driver is ready for it. So, it wonīt match any layout-idīs as all of them were made for sigmatel and realtek.
You can force things up but the result and work in the way can be disappointing.
AD198x codecs are very different than other audio codecs apple uses, they require powering up some nids and the driver doesn't seem to do it by itself.
My best successful attempt to get AD198x working was with AD1988b, and it took me more than a month. I had to use codec programming as I did with a few other codecs before.
One thing that you have in advantage is having the codec to try with.... as it will require lots, and lots of attempts to get any result .... if any you will get.
Some codec Iīve fixed in a couple of hours, others in a couple of days, others in a month (like ad1988b) and others in a couple of months (like ALC861 for F3JC notebook).
And with AD1988b I really had to buy a board just to get it thru, else I would be testing this one with users for about a year, and even with it to test... it took a month

PS- You all are forgetting the importante stuff ... AppleHDAController ConfigData property where the codec programing goes.
And to understand it, youīll need HDA Intel Specification Reference Manual as well as the Codec Datasheet... and you must think like a computer and not like a human wink.gif
jacob019
Thank you for the great info Taruga, it will help us move in the right direction. Unfortunately our datasheet (found here) provides less info than other 198X chips, but it will help. Is there anything we can do to force IOHDACodecDriver to be recognized for testing purposes?
popophobia
Hi all, I'm installing OS X 10.5.2 on a separate hdd to test this. Hopefully we can get this done soon.

Glad that this topic is active again smile.gif
T u r b o
Hey all,

I've worked with Taruga a bit on getting the AD1984 in my T61 working, and thanks to some of his insights I can get all components matched/loaded with the 10.5.2 driver. There is still no sound - the driver complains about the nodes being powered down (D3 state).

I wrote a script to generate config-data that should power up all nodes but it's still not making the driver happy:

CODE
Sound assertion "( ( kIOAudioDeviceActive != fCurrentPowerState ) && ( kAppleHDAIOAudioDeviceForcedActive != fCurrentPowerState ) )" failed in "/SourceCache/AppleHDA/AppleHDA-156.1.19/AppleHDA/AppleHDAEngine.cpp" at line 653 goto Exit


It should be possible to patch the driver to get everything powered up.

- Turbo
Riotz
You guys are doing awesome work here. I hope you are successful so that everyone who is stuck without sound on this chip has a way out. I am definitely going to track this topic.

Cheers

Riotz
jacob019
Great work turbo! Could you post your work thus far?
mulletman13
Glad to hear it Turbo! VERY excited this topic is active again! Let's push it until we get it running!

Oh and Taruga -- if you ever need to VNC into my machine or anything I'm always available (as are other people here). Some of these things are beyond the scope of my understanding, but I'll read up on it and try to help however I can.

.... then perhaps we can get to work on the display brightness issue........ wink.gif
mulletman13
The thing that bothers me about the powering of nodes messing this up is the short burst of sound when unplugging the AC adapter. Does it switch to some interim power state before moving to OS to the battery? ... sorry that sounded stupid. Hardware-wise I know that it just moves immediately, but I'm curious as to why everything is satisfied momentarily when unplugging.... hrmmm...

Sorry for being here for moral support, but if there is anything tedious/ time consuming you need I'm here 8)
T u r b o
QUOTE(mulletman13 @ Jun 23 2008, 09:41 PM) *
The thing that bothers me about the powering of nodes messing this up is the short burst of sound when unplugging the AC adapter. Does it switch to some interim power state before moving to OS to the battery? ... sorry that sounded stupid. Hardware-wise I know that it just moves immediately, but I'm curious as to why everything is satisfied momentarily when unplugging.... hrmmm...

Sorry for being here for moral support, but if there is anything tedious/ time consuming you need I'm here 8)


What kext are you using exactly that works with this short burst of sound? Can you send it to me?

I have a few ideas on what might cause a symptom like that - on my system I haven't gotten a peep out of it yet.

- Turbo
mulletman13
I just performed a 100% fresh install and the behaviour is gone now. I know for a fact that Popophobia had the same thing happen to him-- hopefully he could upload his kext files. I believe he said all he did was apply the Azalia patch (which I am unable to find) after a fresh install.
jacob019
I don't think the burst of sound means anything. When linux windows or the bios utility are loaded on my X61, the computer will make a sound whenever the ac adapter is unplugged or replugged. I think this sound popophobia is experiencing must be related to this. I don't think the azalia driver works at all with our chip.

EDIT: based on the response below, I am wrong about this.
mulletman13
Well I've disabled all beeps and everything regarding power changes and the like. Basically what happened is I'd play a song in iTunes... unplug the AC Adapter, and I'd hear the song playing for a half second or so. Same thing with videos, or anything involving any *actual* sound and not alert messages.

On another note, is anybody having issues with their fans? My laptop seems to be running hot and although I removed the termal kext's in installation, I can't figure out what's up at this point.
jacob019
QUOTE(mulletman13 @ Jun 23 2008, 07:57 PM) *
On another note, is anybody having issues with their fans? My laptop seems to be running hot and although I removed the termal kext's in installation, I can't figure out what's up at this point.


we don't have speedstep so the computer will run a bit hot, but it's not too bad. Let's stay on the topic of AD1984 audio in this thread. Perhaps you could restore your computer to the state it was in when you experienced this audio unplug phenomenon, then post your HDA kext.
mulletman13
I've been trying various different kext's that I may have installed when I got this thing to happen, but I still am unable to replicate it. Hopefully popophobia can chime in on what he did. I know it seems like I'm making this up-- it was one of the first things I did on my laptop after installing OSX, so it might have been before/during or after installing a bunch of other kext's and such. I'll keep trying to replicate it.
popophobia
Hi guys,I can still reproduce the short burst of music when plug/unplug the AC adapter.

Basically Azalia patch moved ALCInject.kext, AppleHDA.kext into AzaliaBackup and create AppleAzaliaAudio.kext in system/library/extensions folder.
I'll try to find the patch again.

But I'm sure it's not the only way to get the short burst of sound. If you check taruga site, seems like there are 2-3 users experienced the same thing without azalia patch. I'll try to install iAtkos 2.0 and see if I can get the same symptom.

Anyway, my system still has the symptom, let me know what kext you would want to look at.

I went ahead and attach the ioreg output and AppleAzaliaAudio.kext. Hopefully it'll have some use.

In ioreg there are a few entries linked back to appleazalia codecs. I'm sure you can get something out of it.
mulletman13
http://forum.insanelymac.com/index.php?showtopic=36520

I believe that was the patch that I had installed (which does exactly what Popophobia's post says). The odd thing is it isn't giving me that symptom at all anymore. As for the other people on Taruga's wiki-- that was me. I posted once when it worked, then said that 10.5.3 broke that symptom from happening.

I'm tearing my hair out trying to replicate it-- I have absolutely no clue as to why it isn't happening for me again.

There was another thread on here where somebody (I believe his name was Agent) mentioned their audio worked with a Kalyway install, but not with an iAtkos install at all.

I'm using your kext file that you posted here (running off a clean and new iAtkos v2.0 installation) and am not getting that symptom whatsoever. AFAIK Kalyway comes with pre-patched audio, or gives options to run some sorts of audio patches at install whereas iAtkos doesn't. Please disregard my posts on Taruga's wiki-- although I experienced the symptom I really don't recall which installation I was on (it may have been an iAtkos installed over a Kalyway 10.5.1 installation). I had been working late nights and installed a crapload of patches.
popophobia
http://forum.insanelymac.com/index.php?s=&...st&p=793653


Someone reported sound on R61 - another AD1984 working with AppleAzalia...

I'm PMing him to get more details..
jacob019
this azalia business is exciting, I had given up on that route. Please keep up the research. I'll give it a close look over the weekend and see if I can't help.
mulletman13
Tried a Kalyway 10.5.1 install, but couldn't get anything working right at all.

Is there a difference between running GUID and MBR at all?
jacob019
QUOTE(mulletman13 @ Jun 23 2008, 11:09 PM) *
Tried a Kalyway 10.5.1 install, but couldn't get anything working right at all.

Is there a difference between running GUID and MBR at all?


not really, you can't run a vanilla kernel under MBR mode, but in my experience it works better, especially for multibooting.
popophobia
Ok, here is the exciting bit:

I installed the OS X using both iAtkos 2.0 and Kalyway 10.5.2 on a separate HDD (2 installs on 2 partitions). Here are the results:

1. Kalyway: No wireles, no volume controller on first boot. However, on my second boot, HDA Output was added to SysPref>Sound>Output. The short burst of sound occurs every disconnecting AC. Wireless works in a blink of an eye after copy the kext from iAtkos (Atheros 5005g hack I think). No reboot required.

2. iAtkos: better integration, everything is there after the first boot. Same, short burst is fully replicated and occurs everytime.


One side note: when I use the dock and remove them without turning off the laptop, there is some kind of sound at the speaker. This leads me to believe that the problem is not in the codec, but in the power of the small speaker alone. I'm looking to do some Azilia mod (it was not applied to any of the above installations). thinkpad.com forums have some nice info about this. I might try that.

I think if you can get a blank hdd (or a partition to spare), install these new version and give it a spin. Totally worthed. I was too worry about having to do everything from scratch. It's not even that bad.
mulletman13
Popophobia -- were these under GUID or MBR? I'm not getting the symptom under any conditions with either (under MBR).

jacob -- I was not aware that vanilla was unable to run on MBR? Installing via iAtkos I installed all stock files (Vanilla 9.2.2 and even the stock AppleACPIPlatform.kext) and all ran completely fine.

Anyways I'm done with reinstalling everything just to replicate it. Now that we have popophobia getting the same result consistantly that's excellent.
popophobia
Make sure you have the volume slider. Without it, no sound will be produced, pulling the cord or not.

I installed the default for Kalyway DVD, audio section (includes the Intel HDA and a few other i think).

Curiously, the sound card is identified as Intel HDA with device ID. I'm still on Kalyway 10.5.2.

I installed with GUID, but either case, it does not affect the sound nor the driver. Just the way it boot up. My first installation was MBR.
T u r b o
QUOTE(popophobia @ Jun 24 2008, 01:42 AM) *
Hi guys,I can still reproduce the short burst of music when plug/unplug the AC adapter.

Basically Azalia patch moved ALCInject.kext, AppleHDA.kext into AzaliaBackup and create AppleAzaliaAudio.kext in system/library/extensions folder.
I'll try to find the patch again.

But I'm sure it's not the only way to get the short burst of sound. If you check taruga site, seems like there are 2-3 users experienced the same thing without azalia patch. I'll try to install iAtkos 2.0 and see if I can get the same symptom.

Anyway, my system still has the symptom, let me know what kext you would want to look at.

I went ahead and attach the ioreg output and AppleAzaliaAudio.kext. Hopefully it'll have some use.

In ioreg there are a few entries linked back to appleazalia codecs. I'm sure you can get something out of it.


Hey popophobia,

Your ioreg is cut off - can you re-run like this and post the output?

CODE
ioreg -w0 -lif > ~/ioreg.txt


- Turbo
popophobia
Hmm sorry about that

Here it is again.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.