Jump to content

[HOW TO] Patch AppleHDA - Knowledge Base

THe KiNG

By THe KiNG,
in Guides and Tutorials

 Share
392 posts in this topic

Recommended Posts

ovof
ovof
Posted
Posted

Hi all,

 

i use the 132 Extra method to have a vanilla installation, and needed kext elsewhere.

 

Everything works : lan, video, PM...

 

But still an issue with AppleHDA patched for GAP35 DS3R Mobo.

 

If i put the patched kext in /System/Library/Extensions : sound works

 

If i put it inside /Extra/Extensions.mkext; no sound !! Even if i delete the same kext in /System/Library/Extensions to avoid conflicts

 

 

Help me :) Why does this kext dont accept the DFE 132 - Extra Method ????

Link to comment
Share on other sites
Pink Waters
Pink Waters
Posted
Posted
Hi all,

 

i use the 132 Extra method to have a vanilla installation, and needed kext elsewhere.

 

Everything works : lan, video, PM...

 

But still an issue with AppleHDA patched for GAP35 DS3R Mobo.

 

If i put the patched kext in /System/Library/Extensions : sound works

 

If i put it inside /Extra/Extensions.mkext; no sound !! Even if i delete the same kext in /System/Library/Extensions to avoid conflicts

Help me ;) Why does this kext dont accept the DFE 132 - Extra Method ????

because AppleHDA does not run from the extra partition, you need legacy drivers ie: HDAEnabler, HDAController and HDAPlatformDriver.

Link to comment
Share on other sites
Toasted Logic
Toasted Logic
Posted
Posted
Soon (less then a month I hope) a new driver will fix all this. I can't say more about this b/c is not my work and the announce should be made by the maker, so IMHO better focus your energy to something else, soon all this patching hda stuff will go on the dark...

As example I've stopped patching AD1988b @ 99% only mute and input amp boost to fix remained...

 

Any chance this new driver might support my ALC663 (Asus M70VM-X1 laptop)? There is a small group of us on the forum who can't seem to figure out the kext to make this card work.

Link to comment
Share on other sites
Cool McCool
Cool McCool
Posted
Posted

You just open up your favorite editor & edit it. I use vi for fast edits, but since its a bit cryptic you might be more comfortable with something like nano or Smultron.

 

The Info.plist file itself can be found in the Contents directory in a kext. For example, the Info.plist file for the AppleHDA.kext can be found here: /System/Library/Extensions/AppleHDA.kext/Contents/Info.plist

 

Since you have an ALC888, I would recommend installing ALCinject.kext into your /System/Library/Extensions directory, and getting an AppleHDA.kext which works for the ALC888 and putting it in there too. Be sure to set your permissions (755) and ownership (root:wheel) settings correctly. Once you get that you can set up your EFI strings.

 

I know you are using Chameleon already, but I'll add this stuff below for people who need it...

 

If you have your audio EFI strings properly defined and set up, you won't need an injector, such as ALCinject.kext. All you will need is an AppleHDA.kext for your hardware and your EFI strings defined in com.apple.Boot.plist. That file resides in /Library/Preferences/SystemConfiguration. (If you are using an EFI partition, the file can be placed there.) The trick is, in order to get your EFI strings set up, you first need working sound, for which the ALCinject (or some other injector) comes in handy. You'll also need a good AppleHDA.kext for your hardware. You will ALWAYS need an AppleHDA.kext that works with your hardware regardless of whether you are using an injector or EFI strings.

 

 

To get your audio (and video) working using EFI strings you'll need to be booting a vanilla kernel using EFI.

 

You can do it using Chameleon. To find out more, do a Google search for: "Chameleon: Bring Mac OS X Developers Together"

 

or netkas PC EFI. Do a Google search for: "netkas forum" and go to the PC EFI section.

 

or using an EFI partition *which is best but only works for retail installations). Munky has some good instructions here:

Boot from EFI partition, zero modification installs...

 

To get your EFI strings set up, netkas has a good set of instructions here. Do a Google search for: "How To: EFI GFX+Audio Introduction & Tutorial"

 

You'll need his GFXUtil for building both audio & video EFI strings:

GFXUtil

 

If you need to create your own AppleHDA, Taruga has good instructions here:

AppleHDA Solution - Work in progress, Main Thread

 

Many people find OSXTools useful:

OSXTools

 

Here is another link which might help you. It is old, but still it might have some useful links and information.

Solutions for Audio Problems, A Compilation

 

I hope this helps.

Link to comment
Share on other sites
sweetsteal
sweetsteal
Posted
Posted

I have successfully followed the guide and have a working alc268 driver for my acer aspire one.. however i cant get the microphone working.... strange thing is that if i follow the verb guide in this post i get this:

 

01271C11 01271D01 01271EA0 01271F90 01371C0F 01371D00 01371E00 01371F40 01471C40 01471D01 01471E13 01471F90 01571C41 01571D40 01571E21 01571F01 01671C0F 01671D00 01671E00 01671F40 01871C10 01871D01 01871EA0 01871F90 01971C0F 01971D00 01971E00 01971F40 01A71C20 01A71D30 01A71E81 01A71F01 01C71C0F 01C71D00 01C71E00 01C71F40 01D71C0F 01D71D00 01D71E00 01D71F40 01E71C0F 01E71D00 01E71E00 01E71F40

 

Which shows me all my devices...However i get no sound from speaker and mic is very low with no input volume at all!!!

 

however when i use these verbs from a different kext i d/l online:

 

0023B000 00237000 00237100 0033B000 00337000 00337100 00E37000 00E37100 00E3B000 00E70100 00F37000 01037000 01470740 0143B080 01470C02 014707C0 01470884 015707C0 0153B080 01570C02 01570740 01670740 0163B080 01870724 0183B080 01270724 0123B080 01270C08 012707C0 01270884 01A70720 01A3B080 01C70720 01C3B080 01D70720 01D37000 02337000 02337100 02337200 02337300 02437000 02437100 02437200 02437300

 

i get sound out of my speakers, but still end up with the microphone issue.......Unfortunatly, I cant make heads or tails of these verbs as they dont seem to follow any of the patterns decsribed in this post... can anyone shed some light for me PLEASSE!!!

 

thanks,

sweetsteal

 

Also is there anywhere in particular we can look for information on this upcoming driver it would be awesome to see something like that come around....

Link to comment
Share on other sites
  • 2 weeks later...
fingerr
fingerr
Posted
Posted

Hi all,

 

I'd like to ask if there is a chance to get rid of ALCinject by using entries in DSDT.aml table?

Right now I use binary hacked AppleHDA.kext by Taruga for my ALC0861 and I don't know if this is possible....

 

I've tried to follow this guide, but finally I got lost.

 

If someone can try to help me, here is linux codec dump of my card:

Codec: Realtek ALC861
Address: 0
Vendor Id: 0x10ec0861
Subsystem Id: 0x11791205
Revision Id: 0x100300
No Modem Function Group found
Default PCM:
rates [0x140]: 48000 96000
bits [0xe]: 16 20 24
formats [0x1]: PCM
Default Amp-In caps: N/A
Default Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
GPIO: io=0, o=0, i=0, unsolicited=0, wake=0
Node 0x03 [Audio Output] wcaps 0x405: Stereo Amp-Out
 Amp-Out caps: N/A
 Amp-Out vals:  [0x00 0x00]
 Converter: stream=0, channel=0
 Power: setting=D0, actual=D0
Node 0x04 [Audio Output] wcaps 0x405: Stereo Amp-Out
 Amp-Out caps: N/A
 Amp-Out vals:  [0x80 0x80]
 Converter: stream=0, channel=0
 Power: setting=D0, actual=D0
Node 0x05 [Audio Output] wcaps 0x405: Stereo Amp-Out
 Amp-Out caps: N/A
 Amp-Out vals:  [0x80 0x80]
 Converter: stream=0, channel=0
 Power: setting=D0, actual=D0
Node 0x06 [Audio Output] wcaps 0x405: Stereo Amp-Out
 Amp-Out caps: N/A
 Amp-Out vals:  [0x80 0x80]
 Converter: stream=0, channel=0
 Power: setting=D0, actual=D0
Node 0x07 [Audio Output] wcaps 0x605: Stereo Digital Amp-Out
 Amp-Out caps: N/A
 Amp-Out vals:  [0x00 0x00]
 Converter: stream=0, channel=0
 Digital:
 Digital category: 0x0
 Power: setting=D0, actual=D0
Node 0x08 [Audio Input] wcaps 0x10051b: Stereo Amp-In
 Amp-In caps: ofs=0x02, nsteps=0x0d, stepsize=0x0b, mute=1
 Amp-In vals:  [0x0a 0x0a] [0x0a 0x0a] [0x0a 0x0a] [0x0a 0x0a] [0x0a 0x0a] [0x0a 0x0a]
 Converter: stream=0, channel=0
 SDI-Select: 0
 PCM:
rates [0x140]: 48000 96000
bits [0x2]: 16
formats [0x1]: PCM
 Power: setting=D0, actual=D0
 Connection: 6
 0x0d* 0x0c 0x0f 0x10 0x11 0x15
Node 0x09 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x0a [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x0b [Pin Complex] wcaps 0x400581: Stereo
 Pincap 0x081f: OUT HP Detect Trigger ImpSense
 Pin Default 0x01014110: [Jack] Line Out at Ext Rear
Conn = 1/8, Color = Green
DefAssociation = 0x1, Sequence = 0x0
Misc = NO_PRESENCE
 Pin-ctls: 0x40: OUT
 Unsolicited: tag=00, enabled=0
 Power: setting=D0, actual=D0
 Connection: 1
 0x16
Node 0x0c [Pin Complex] wcaps 0x400581: Stereo
 Pincap 0x0837: IN OUT Detect Trigger ImpSense
 Pin Default 0x9983012e: [Fixed] Line In at Int ATAPI
Conn = ATAPI, Color = Unknown
DefAssociation = 0x2, Sequence = 0xe
Misc = NO_PRESENCE
 Pin-ctls: 0x20: IN
 Unsolicited: tag=00, enabled=0
 Power: setting=D0, actual=D0
 Connection: 1
 0x19
Node 0x0d [Pin Complex] wcaps 0x400581: Stereo
 Pincap 0x08337: IN OUT Detect Trigger ImpSense
Vref caps: HIZ 50
 Pin Default 0x01a19920: [Jack] Mic at Ext Rear
Conn = 1/8, Color = Pink
DefAssociation = 0x2, Sequence = 0x0
Misc = NO_PRESENCE
 Pin-ctls: 0x24: IN VREF_80
 Unsolicited: tag=00, enabled=0
 Power: setting=D0, actual=D0
 Connection: 1
 0x18
Node 0x0e [Pin Complex] wcaps 0x400581: Stereo
 Pincap 0x0817: OUT Detect Trigger ImpSense
 Pin Default 0x411111f0: [N/A] Speaker at Ext Rear
Conn = 1/8, Color = Black
DefAssociation = 0xf, Sequence = 0x0
Misc = NO_PRESENCE
 Pin-ctls: 0x40: OUT
 Unsolicited: tag=00, enabled=0
 Power: setting=D0, actual=D0
 Connection: 1
 0x19
Node 0x0f [Pin Complex] wcaps 0x400581: Stereo
 Pincap 0x0833f: IN OUT HP Detect Trigger ImpSense
Vref caps: HIZ 50
 Pin Default 0x411111f0: [N/A] Speaker at Ext Rear
Conn = 1/8, Color = Black
DefAssociation = 0xf, Sequence = 0x0
Misc = NO_PRESENCE
 Pin-ctls: 0x40: OUT VREF_HIZ
 Unsolicited: tag=00, enabled=0
 Power: setting=D0, actual=D0
 Connection: 1
 0x1a
Node 0x10 [Pin Complex] wcaps 0x400581: Stereo
 Pincap 0x0833f: IN OUT HP Detect Trigger ImpSense
Vref caps: HIZ 50
 Pin Default 0x411111f0: [N/A] Speaker at Ext Rear
Conn = 1/8, Color = Black
DefAssociation = 0xf, Sequence = 0x0
Misc = NO_PRESENCE
 Pin-ctls: 0x20: IN VREF_HIZ
 Unsolicited: tag=00, enabled=0
 Power: setting=D0, actual=D0
 Connection: 1
 0x1b
Node 0x11 [Pin Complex] wcaps 0x400001: Stereo
 Pincap 0x0863: IN Balanced Trigger ImpSense
 Pin Default 0x99330121: [Fixed] CD at Int ATAPI
Conn = ATAPI, Color = Unknown
DefAssociation = 0x2, Sequence = 0x1
Misc = NO_PRESENCE
 Pin-ctls: 0x00:
Node 0x12 [Pin Complex] wcaps 0x400301: Stereo Digital
 Pincap 0x0810: OUT
 Pin Default 0x411111f0: [N/A] Speaker at Ext Rear
Conn = 1/8, Color = Black
DefAssociation = 0xf, Sequence = 0x0
Misc = NO_PRESENCE
 Pin-ctls: 0x40: OUT
 Connection: 1
 0x07
Node 0x13 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x14 [Audio Mixer] wcaps 0x20010b: Stereo Amp-In
 Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
 Amp-In vals:  [0x00 0x00] [0x00 0x00]
 Connection: 2
 0x0d 0x10
Node 0x15 [Audio Mixer] wcaps 0x20050f: Stereo Amp-In Amp-Out
 Amp-In caps: ofs=0x0c, nsteps=0x17, stepsize=0x0b, mute=1
 Amp-In vals:  [0x12 0x12] [0x92 0x92] [0x12 0x12]
 Amp-Out caps: ofs=0x0c, nsteps=0x0c, stepsize=0x0b, mute=1
 Amp-Out vals:  [0x0c 0x0c]
 Power: setting=D0, actual=D0
 Connection: 3
 0x11 0x14 0x1c
Node 0x16 [Audio Mixer] wcaps 0x20010b: Stereo Amp-In
 Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
 Amp-In vals:  [0x00 0x00] [0x00 0x00]
 Connection: 2
 0x03 0x15
Node 0x17 [Audio Mixer] wcaps 0x20010b: Stereo Amp-In
 Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
 Amp-In vals:  [0x00 0x00] [0x00 0x00]
 Connection: 2
 0x04 0x15
Node 0x18 [Audio Mixer] wcaps 0x20010b: Stereo Amp-In
 Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
 Amp-In vals:  [0x00 0x00] [0x00 0x00]
 Connection: 2
 0x05 0x15
Node 0x19 [Audio Mixer] wcaps 0x20010b: Stereo Amp-In
 Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
 Amp-In vals:  [0x00 0x00] [0x00 0x00]
 Connection: 2
 0x06 0x15
Node 0x1a [Audio Mixer] wcaps 0x20010b: Stereo Amp-In
 Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
 Amp-In vals:  [0x80 0x80] [0x80 0x80] [0x00 0x00] [0x00 0x00]
 Connection: 4
 0x04 0x06 0x15 0x03
Node 0x1b [Audio Mixer] wcaps 0x20010b: Stereo Amp-In
 Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
 Amp-In vals:  [0x80 0x80] [0x80 0x80] [0x00 0x00] [0x00 0x00]
 Connection: 4
 0x04 0x06 0x15 0x03
Node 0x1c [Audio Mixer] wcaps 0x20010b: Stereo Amp-In
 Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
 Amp-In vals:  [0x00 0x00] [0x00 0x00]
 Connection: 2
 0x0c 0x0f
Node 0x1d [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x1e [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x1f [Pin Complex] wcaps 0x400581: Stereo
 Pincap 0x0817: OUT Detect Trigger ImpSense
 Pin Default 0x411111f0: [N/A] Speaker at Ext Rear
Conn = 1/8, Color = Black
DefAssociation = 0xf, Sequence = 0x0
Misc = NO_PRESENCE
 Pin-ctls: 0x40: OUT
 Unsolicited: tag=00, enabled=0
 Power: setting=D0, actual=D0
 Connection: 1
 0x18
Node 0x20 [Pin Complex] wcaps 0x400581: Stereo
 Pincap 0x0817: OUT Detect Trigger ImpSense
 Pin Default 0x411111f0: [N/A] Speaker at Ext Rear
Conn = 1/8, Color = Black
DefAssociation = 0xf, Sequence = 0x0
Misc = NO_PRESENCE
 Pin-ctls: 0x40: OUT
 Unsolicited: tag=00, enabled=0
 Power: setting=D0, actual=D0
 Connection: 1
 0x17
Node 0x21 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x22 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x23 [beep Generator Widget] wcaps 0x70000c: Mono Amp-Out
 Amp-Out caps: ofs=0x0f, nsteps=0x0f, stepsize=0x0b, mute=1
 Amp-Out vals:  [0x8f]

 

p.s.

HDAEnabler is/does the same as ALCinject?

Thanks in advance,

fingerr,

Link to comment
Share on other sites
Nips
Nips
Posted
Posted

@MasterChief: I'm with you on this. I'm having the same problem.

 

First of all, let me say THANK YOU to everyone who has posted here. There is a wealth of information.

 

The problem is, I'm having some trouble understanding it. I'm guessing that english may be a second (or third) language to many of the posters here, and while most of it is easy to understand, there are some things that just don't make sense to me personally.

 

I need a couple of answers to really help me understand how this works. If anyone can help, I'd really appreciate it.

 

1: As I understand it, there are ONLY 2 files that need to be edited. These are The AppleHDAController Info.Plist AppleHDAPlatformDriver Info.Plist . Am I Correct?

 

2: Once the files are edited, they must be placed in System/Library/Extensions. Is this correct?

 

3: ALCInject.kext is required unless you have properly done your DSDT patching. Is this correct?

 

4. Can some explain with some certainty EXACTLY how the pin configurations are determined, and how they are inserted into the AppleHDAPlatformDriver info.plist?

 

Here is a snippet from the first post:

 

Internal Mic (Pink): 8 35 25

Mic (Pink): 9 34 24

Line in (Blue): 8 35 26

Front (Green): 20 12 2 *[FIXED] SPEAKER AT INT ATAPI on my lappie

Rear (Black): 21 13 3

Sub/Center (Orange): 22 14 4

Side (Red): 23 15 5

Headphones: 27 38 37 *[JACK] HP OUT AT EXT REAR I set it as 27 12 2 on my lappie

SPDIF IN: 10 31

SPDIF OUT: 30 6

 

I'm at a loss for how most of these were determined, especially after loooking at his attached .svg diagram, especially because there are 11 connections on some of the mixers. For some pin configs he picks the first one, some the 2nd. If you look at his SVG diagram, the 2 mic inputs (internal and external) BOTH have lines going to 24 and 25, so why did he pick the ones he did for each? Was it just trial and error?

 

this post in this thread asks this question PERFECTLY. Nobody answered it. If someone can answer this, I think I can finally get the audio working for the D945GLCF2.

 

If I get back answers to these that are unclear to me I will try to get them clarified for everyone. I'd like to put together a coherent guide from the information as well.

 

Thanks in advance to anyone who is able to help me on this.

Link to comment
Share on other sites
THe KiNG
THe KiNG
Posted
  • Author
Posted
@MasterChief: I'm with you on this. I'm having the same problem.

 

First of all, let me say THANK YOU to everyone who has posted here. There is a wealth of information.

 

The problem is, I'm having some trouble understanding it. I'm guessing that english may be a second (or third) language to many of the posters here, and while most of it is easy to understand, there are some things that just don't make sense to me personally.

 

I need a couple of answers to really help me understand how this works. If anyone can help, I'd really appreciate it.

 

1: As I understand it, there are ONLY 2 files that need to be edited. These are The AppleHDAController Info.Plist AppleHDAPlatformDriver Info.Plist . Am I Correct?

Correct

2: Once the files are edited, they must be placed in System/Library/Extensions. Is this correct?

yes and also u can put then in Extensions.mkext if you use /extra method

3: ALCInject.kext is required unless you have properly done your DSDT patching. Is this correct?

ALCInject is so old... hdaenabler is a better solution also u can use dsdt injection or com.apple.boot.plist injection ALL does the same thing

4. Can some explain with some certainty EXACTLY how the pin configurations are determined, and how they are inserted into the AppleHDAPlatformDriver info.plist?

That you have to figure out by yourself, you have my examples look on svg then on my kexts and u will see...

Here is a snippet from the first post:

I'm at a loss for how most of these were determined, especially after loooking at his attached .svg diagram, especially because there are 11 connections on some of the mixers. For some pin configs he picks the first one, some the 2nd. If you look at his SVG diagram, the 2 mic inputs (internal and external) BOTH have lines going to 24 and 25, so why did he pick the ones he did for each? Was it just trial and error?

Linux dump is sometimes dumb...and YES its a trial and error stuff...Also the svg is just to give u an idea(graphical) on how codec works and what are the connections, from there you have to play and mix :)

this post in this thread asks this question PERFECTLY. Nobody answered it. If someone can answer this, I think I can finally get the audio working for the D945GLCF2.

Forget about ATOM ALC663... I have the same board and all I get was just info in system profilers and system preferences sliders and all sh*t but not a DAMN sound!

If I get back answers to these that are unclear to me I will try to get them clarified for everyone. I'd like to put together a coherent guide from the information as well.

Be my guest I'm tired of all this...

Thanks in advance to anyone who is able to help me on this.

As I said earlier just wait for a proper solution....will be out soon, I hope...

@ Master Chief I dont see the point in messing ppl mind with another "complex" guide lol just make a script for that.

Link to comment
Share on other sites
Master Chief
Master Chief
Posted
Posted
As I said earlier just wait for a proper solution....will be out soon, I hope...

@ Master Chief I dont see the point in messing ppl mind with another "complex" guide lol just make a script for that.

 

Excuse me? Let's just assume that you have issues with the English language (no offense) because I do not "mess" with other peoples mind. What I do is filling up the gaps and answer the questions that I, and apparently others with me here, had after reading your guide - thanks for writing it though.

 

Hey, I'm not the average type of guy. I know that. I'm also not someone who keeps waiting, indefinitely (what should we do if people like you go missing?). No. I rather learn, know what I am doing - and I am pretty good at it looking at my work (use Mozilla Firefox/SeaMonkey and you make my day, thanks).

Link to comment
Share on other sites
macgirl
macgirl
Posted
Posted
As I said earlier just wait for a proper solution....will be out soon, I hope...

@ Master Chief I dont see the point in messing ppl mind with another "complex" guide lol just make a script for that.

"Soon" is never soon enough :D

Link to comment
Share on other sites
THe KiNG
THe KiNG
Posted
  • Author
Posted
Excuse me? Let's just assume that you have issues with the English language (no offense) because I do not "mess" with other peoples mind. What I do is filling up the gaps and answer the questions that I, and apparently others with me here, had after reading your guide - thanks for writing it though.

 

Hey, I'm not the average type of guy. I know that. I'm also not someone who keeps waiting, indefinitely (what should we do if people like you go missing?). No. I rather learn, know what I am doing - and I am pretty good at it looking at my work (use Mozilla Firefox/SeaMonkey and you make my day, thanks).

 

Yes, I'm not a native english speaker...no need to remind me that.

Seems that you didn't understand what I was trying to say...so again I said something like that: There is no need to confuse people more then I did(yes my guide is not the best one but its the only one...), IMHO is better to create scripts that does the same job as you described in your topic.

Also best pin configuration/verbs you can get IMO is from vista. Why? B/c at least on vista you can be 100% sure that codec is working proper, I dont trust linux and especial ALSA! Linux dump is very good for 1 thing: Codec Graph.

So if someone still want to mess with applehda take my advice, install a free copy of vista, install audio driver, take from registry pin configurations and use DiaboliK Vista HDA Verb Converter to get stage 1 verb for patching, then you can erase vista and go to happy patching using my guide as reference....

"Soon" is never soon enough :wacko:

Right, but also you know that this is a fun job and people have to care first of their "real" life/job ....

I'm sure of one thing: Voodoo FTW! :wub:

Be Patient....

Link to comment
Share on other sites
macgirl
macgirl
Posted
Posted
Right, but also you know that this is a fun job and people have to care first of their "real" life/job ....

I'm sure of one thing: Voodoo FTW! :D

Be Patient....

Right, I was just joking.

 

Anyway meanwhile I can make the Digital Mic of the M1330/M1530 work (alone) so I learn something in this process that the biggest profit.

Link to comment
Share on other sites
Master Chief
Master Chief
Posted
Posted
...Seems that you didn't understand what I was trying to say...so again I said something like that: There is no need to confuse people more then I did(yes my guide is not the best one but its the only one...), IMHO is better to create scripts that does the same job as you described in your topic.

 

We're all here with one purpose, to get our audio going - one way or the other. I'm with you about having scripts, but please understand that I can't write a script without first knowing what we need. In fact nobody can. That's the only reason why I started to write down some of my findings - even if it takes me ages to finds the things I am looking for.

 

Peace!

Link to comment
Share on other sites
cparm
cparm
Posted
Posted
I'm sure of one thing: Voodoo FTW! :)

 

yeah, it seems that voodoo team, working on a universal driver, I also know that Taruga working on a similar project

 

I don't know if they work together, but I think the mod of AppleHDA.kext will be soon unnecesary :)

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...