- Alsa-devel - mailman.alsa-project.org

[alsa-devel] Red Hat
by Jaroslav Kysela 15 Jan '08

15 Jan '08

Hello all, I would like to annouce that I work for Red Hat, Inc. since beginning of year. You might noticed this in my signature for awhile already. I would like to thank to my previous employer - Novell, Inc. (SUSE) - for the support for the ALSA project and looking forward to continue with the ALSA project development under new employer. Jaroslav ----- Jaroslav Kysela <perex(a)perex.cz> Linux Kernel Sound Maintainer ALSA Project, Red Hat, Inc.

1 0

Re: [alsa-devel] intel-hd on an intel G33 motherboard
by De Fuuss 15 Jan '08

15 Jan '08

Hi, I reopened my shuttle case, closely inspected the motherboard and I think I found the issue. The onboard sound was factory set off (jumper), something which I must admit I did not check. However, I find it hard to imagine that XPC would sell their barebones with onboard sound off as a default. Even more weird, the headphones work when the onboard sound is "off". I get the uneasy feeling that something is messed up with this board. Anyway, for completeness' sake, I attached the results of amixer contents, cat /proc/asound/card0/codec#0 and dmesg for the module loaded as 6stack-dig. I have to try 6stack-hp again to confirm if I get something there. Patrick > From: zhe.jiang(a)intel.com > To: fuuss(a)hotmail.com > Date: Fri, 11 Jan 2008 12:58:07 +0800 > CC: alsa-devel(a)alsa-project.org > Subject: Re: [alsa-devel] intel-hd on an intel G33 motherboard > > On Thu, 2008-01-10 at 16:09 +0000, De Fuuss wrote: >> Hi, >> >> 6stack-dig, 6stack-hp: I tested all channels, and indeed I get sound but only from the headphone jack on the front. All other channels remain silent (front, center,rear,...) >> > Hi, > > It's a little weird that the sound only come from headphone. > Seems that the 0x1b is the hp pin and 0x14 is the Front line out pin. > Both of them are connected to 0x0c widget. > If there is sound on hp, there should be sound on Front line out. > > May you rebuild the alsa-driver with debug option to get some info? > ./configure --with-debug=detect; > make;make install; > > After reload the driver, > please show the result of "amixer contents", > "cat /proc/asound/card0/codec#0" and "dmesg". > > Thanks! >> Regards, >> >> Patrick >> >>> From: zhe.jiang(a)intel.com >>> To: fuuss(a)hotmail.com >>> Date: Thu, 10 Jan 2008 13:46:42 +0800 >>> CC: alsa-devel(a)alsa-project.org >>> Subject: Re: [alsa-devel] intel-hd on an intel G33 motherboard >>> >>> On Fri, 2007-12-28 at 19:09 +0800, De Fuuss wrote: >>>> >>>> Hi, >>>> >>>> Here's the pastebin information http://pastebin.ca/834640 >>>> >>>> That was using 3stack-6ch-dig >>> The 3stack-6ch-dig won't work because it use 0x18 and 0x1a as >>> the effective pins, which is different from your pins layout. >>>> >>>> For experimentation's sake: >>>> >>>> If I use 6stack-dig I get the following http://pastebin.ca/834644 >>>> If I use 6stack-hp I get the following http://pastebin.ca/834646 >>>> >>> Did you do any testing with those two configures? >>> After analyzing your information, >>> I guess that you can get voice from the output jacks with those >>> configurations. >>> >>> >>>> Thanks for helping me out. It would be nice if it worked :-) >>>> >>>> Patrick >>>> >>>>> From: tdavis(a)dsl-only.net >>>>> To: fuuss(a)hotmail.com >>>>> Date: Thu, 27 Dec 2007 20:22:57 -0800 >>>>> CC: alsa-devel(a)alsa-project.org >>>>> Subject: Re: [alsa-devel] intel-hd on an intel G33 motherboard >>>>> >>>>> Ok, need to step back in the thread a bit. Now that we've >>>> established >>>>> that this is not an Intel manufactured motherboard (not that they >>>> make >>>>> their own anymore), I need more detailed information on what the OS >>>>> see's. Please run >>>>> http://bulletproof.servebeer.com/alsa/scripts/alsa-info.sh and post >>>> the >>>>> link that it generates. This will give me a detailed snapshot of >>>> your >>>>> hardware that I can use for debugging. >>>>> >>>>> I will begin working on this as soon as I get this info. I hope to >>>> get >>>>> you enabled this weekend if possible, this year at the latest. :) >>>>> >>>>> Thanks, >>>>> >>>>> Tobin >>>> ---------------------------------------- >>>>> From: tdavis(a)dsl-only.net >>>>> To: fuuss(a)hotmail.com >>>>> Date: Thu, 27 Dec 2007 20:22:57 -0800 >>>>> CC: alsa-devel(a)alsa-project.org >>>>> Subject: Re: [alsa-devel] intel-hd on an intel G33 motherboard >>>>> >>>>> Ok, need to step back in the thread a bit. Now that we've >>>> established >>>>> that this is not an Intel manufactured motherboard (not that they >>>> make >>>>> their own anymore), I need more detailed information on what the OS >>>>> see's. Please run >>>>> http://bulletproof.servebeer.com/alsa/scripts/alsa-info.sh and post >>>> the >>>>> link that it generates. This will give me a detailed snapshot of >>>> your >>>>> hardware that I can use for debugging. >>>>> >>>>> I will begin working on this as soon as I get this info. I hope to >>>> get >>>>> you enabled this weekend if possible, this year at the latest. :) >>>>> >>>>> Thanks, >>>>> >>>>> Tobin >>>>> >>>>> >>>>> On Thu, 2007-12-27 at 00:33 +0000, De Fuuss wrote: >>>>> >>>>>> Hi Tobin, >>>>>> >>>>>> Thanks for you quick reply. >>>>>> >>>>>> I tried both 3stack-6ch and 3stack-6ch-dig (the card has a spdif >>>> out). I found out that when putting on headphones on a separate >>>> headphone jack I get some sound with both settings. Hoever, the front >>>> out l/r, center/bass sourround back l/r and side sourround l/r port >>>> remain silent. >>>>>> >>>>>> I set all channels to 80-100% in alsamixer. >>>>>> >>>>>> A few more details from my setup: >>>>>> Shuttle XPC SG33G5M >>>>>> Intel G33 Express + ICH9DH >>>>>> >>>>>> Interestingly, when I run alsamixer, it identifies the Chip as >>>> "Generic 1095 ID 1392", in other words in points to codec#1. I thought >>>> it should point to codec#0, e.g. RealTek ALC888 >>>>>> >>>>>> I have the strong impression that the channels are not truly set by >>>> alsamixer as they point to the wrong codec. I'm only a layman in ALSA, >>>> and I have no idea how to tell alsamixer to consider codec#0 instead >>>> codec#1. >>>>>> >>>>>> Do you have any idea on how to crack this nut? >>>>>> >>>>>> Below is the output of both codecs: >>>>>> >>>>>> Thank you. >>>>>> >>>>>> Best regards, >>>>>> >>>>>> Patrick >>>>>> >>>>>> ____________________ >>>>>> #cat /proc/asound/cards >>>>>> >>>>>> 0 [Intel ]: HDA-Intel - HDA Intel >>>>>> HDA Intel at 0xfdff8000 irq 22 >>>>>> >>>>>> # cat /proc/asound/Intel/codec#0 >>>>>> Codec: Realtek ALC888 >>>>>> Address: 0 >>>>>> Vendor Id: 0x10ec0888 >>>>>> Subsystem Id: 0x12970888 >>>>>> Revision Id: 0x100001 >>>>>> No Modem Function Group found >>>>>> Default PCM: >>>>>> rates [0x560]: 44100 48000 96000 192000 >>>>>> bits [0xe]: 16 20 24 >>>>>> formats [0x1]: PCM >>>>>> Default Amp-In caps: N/A >>>>>> Default Amp-Out caps: N/A >>>>>> Node 0x02 [Audio Output] wcaps 0x11: Stereo >>>>>> PCM: >>>>>> rates [0x560]: 44100 48000 96000 192000 >>>>>> bits [0xe]: 16 20 24 >>>>>> formats [0x1]: PCM >>>>>> Node 0x03 [Audio Output] wcaps 0x11: Stereo >>>>>> PCM: >>>>>> rates [0x560]: 44100 48000 96000 192000 >>>>>> bits [0xe]: 16 20 24 >>>>>> formats [0x1]: PCM >>>>>> Node 0x04 [Audio Output] wcaps 0x11: Stereo >>>>>> PCM: >>>>>> rates [0x560]: 44100 48000 96000 192000 >>>>>> bits [0xe]: 16 20 24 >>>>>> formats [0x1]: PCM >>>>>> Node 0x05 [Audio Output] wcaps 0x11: Stereo >>>>>> PCM: >>>>>> rates [0x560]: 44100 48000 96000 192000 >>>>>> bits [0xe]: 16 20 24 >>>>>> formats [0x1]: PCM >>>>>> Node 0x06 [Audio Output] wcaps 0x211: Stereo Digital >>>>>> PCM: >>>>>> rates [0x5e0]: 44100 48000 88200 96000 192000 >>>>>> bits [0x1e]: 16 20 24 32 >>>>>> formats [0x1]: PCM >>>>>> Node 0x07 [Vendor Defined Widget] wcaps 0xf00000: Mono >>>>>> Node 0x08 [Audio Input] wcaps 0x10011b: Stereo Amp-In >>>>>> Amp-In caps: ofs=0x0b, nsteps=0x1f, stepsize=0x05, mute=1 >>>>>> Amp-In vals: [0x9f 0x9f] >>>>>> PCM: >>>>>> rates [0x160]: 44100 48000 96000 >>>>>> bits [0x6]: 16 20 >>>>>> formats [0x1]: PCM >>>>>> Connection: 1 >>>>>> 0x23 >>>>>> Node 0x09 [Audio Input] wcaps 0x10011b: Stereo Amp-In >>>>>> Amp-In caps: ofs=0x0b, nsteps=0x1f, stepsize=0x05, mute=1 >>>>>> Amp-In vals: [0x9f 0x9f] >>>>>> PCM: >>>>>> rates [0x160]: 44100 48000 96000 >>>>>> bits [0x6]: 16 20 >>>>>> formats [0x1]: PCM >>>>>> Connection: 1 >>>>>> 0x22 >>>>>> Node 0x0a [Audio Input] wcaps 0x100391: Stereo Digital >>>>>> PCM: >>>>>> rates [0x560]: 44100 48000 96000 192000 >>>>>> bits [0x1e]: 16 20 24 32 >>>>>> formats [0x1]: PCM >>>>>> Connection: 1 >>>>>> 0x1f >>>>>> Node 0x0b [Audio Mixer] wcaps 0x20010b: Stereo Amp-In >>>>>> Amp-In caps: ofs=0x17, nsteps=0x1f, stepsize=0x05, mute=1 >>>>>> Amp-In vals: [0x80 0x80] [0x80 0x80] [0x9d 0x9d] [0x80 0x80] >>>> [0x9f 0x9f] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 >>>> 0x80] >>>>>> Connection: 10 >>>>>> 0x18 0x19 0x1a 0x1b 0x1c 0x1d 0x14 0x15 0x16 0x17 >>>>>> Node 0x0c [Audio Mixer] wcaps 0x20010f: Stereo Amp-In Amp-Out >>>>>> Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 >>>>>> Amp-In vals: [0x00 0x00] [0x00 0x00] >>>>>> Amp-Out caps: ofs=0x1f, nsteps=0x1f, stepsize=0x05, mute=0 >>>>>> Amp-Out vals: [0x1d 0x1d] >>>>>> Connection: 2 >>>>>> 0x02 0x0b >>>>>> Node 0x0d [Audio Mixer] wcaps 0x20010f: Stereo Amp-In Amp-Out >>>>>> Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 >>>>>> Amp-In vals: [0x00 0x00] [0x00 0x00] >>>>>> Amp-Out caps: ofs=0x1f, nsteps=0x1f, stepsize=0x05, mute=0 >>>>>> Amp-Out vals: [0x1f 0x1f] >>>>>> Connection: 2 >>>>>> 0x03 0x0b >>>>>> Node 0x0e [Audio Mixer] wcaps 0x20010f: Stereo Amp-In Amp-Out >>>>>> Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 >>>>>> Amp-In vals: [0x00 0x00] [0x00 0x00] >>>>>> Amp-Out caps: ofs=0x1f, nsteps=0x1f, stepsize=0x05, mute=0 >>>>>> Amp-Out vals: [0x1f 0x1f] >>>>>> Connection: 2 >>>>>> 0x04 0x0b >>>>>> Node 0x0f [Audio Mixer] wcaps 0x20010f: Stereo Amp-In Amp-Out >>>>>> Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 >>>>>> Amp-In vals: [0x80 0x80] [0x80 0x80] >>>>>> Amp-Out caps: ofs=0x1f, nsteps=0x1f, stepsize=0x05, mute=0 >>>>>> Amp-Out vals: [0x00 0x00] >>>>>> Connection: 2 >>>>>> 0x05 0x0b >>>>>> Node 0x10 [Vendor Defined Widget] wcaps 0xf00000: Mono >>>>>> Node 0x11 [Vendor Defined Widget] wcaps 0xf00000: Mono >>>>>> Node 0x12 [Vendor Defined Widget] wcaps 0xf00000: Mono >>>>>> Node 0x13 [Vendor Defined Widget] wcaps 0xf00000: Mono >>>>>> Node 0x14 [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out >>>>>> Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0 >>>>>> Amp-In vals: [0x00 0x00] [0x00 0x00] [0x00 0x00] [0x00 0x00] >>>> [0x00 0x00] >>>>>> Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 >>>>>> Amp-Out vals: [0x00 0x00] >>>>>> Pincap 0x083e: IN OUT HP Detect >>>>>> Pin Default 0x01014010: [Jack] Line Out at Ext Rear >>>>>> Conn = 1/8, Color = Green >>>>>> Pin-ctls: 0x40: OUT >>>>>> Connection: 5 >>>>>> 0x0c* 0x0d 0x0e 0x0f 0x26 >>>>>> Node 0x15 [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out >>>>>> Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0 >>>>>> Amp-In vals: [0x00 0x00] [0x00 0x00] [0x00 0x00] [0x00 0x00] >>>> [0x00 0x00] >>>>>> Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 >>>>>> Amp-Out vals: [0x00 0x00] >>>>>> Pincap 0x083e: IN OUT HP Detect >>>>>> Pin Default 0x01011012: [Jack] Line Out at Ext Rear >>>>>> Conn = 1/8, Color = Black >>>>>> Pin-ctls: 0x40: OUT >>>>>> Connection: 5 >>>>>> 0x0c 0x0d* 0x0e 0x0f 0x26 >>>>>> Node 0x16 [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out >>>>>> Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0 >>>>>> Amp-In vals: [0x00 0x00] [0x00 0x00] [0x00 0x00] [0x00 0x00] >>>> [0x00 0x00] >>>>>> Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 >>>>>> Amp-Out vals: [0x00 0x00] >>>>>> Pincap 0x0836: IN OUT Detect >>>>>> Pin Default 0x01016011: [Jack] Line Out at Ext Rear >>>>>> Conn = 1/8, Color = Orange >>>>>> Pin-ctls: 0x40: OUT >>>>>> Connection: 5 >>>>>> 0x0c 0x0d 0x0e* 0x0f 0x26 >>>>>> Node 0x17 [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out >>>>>> Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0 >>>>>> Amp-In vals: [0x00 0x00] [0x00 0x00] [0x00 0x00] [0x00 0x00] >>>> [0x00 0x00] >>>>>> Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 >>>>>> Amp-Out vals: [0x00 0x00] >>>>>> Pincap 0x0836: IN OUT Detect >>>>>> Pin Default 0x01012014: [Jack] Line Out at Ext Rear >>>>>> Conn = 1/8, Color = Grey >>>>>> Pin-ctls: 0x40: OUT >>>>>> Connection: 5 >>>>>> 0x0c 0x0d 0x0e 0x0f* 0x26 >>>>>> Node 0x18 [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out >>>>>> Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0 >>>>>> Amp-In vals: [0x00 0x00] [0x00 0x00] [0x00 0x00] [0x00 0x00] >>>> [0x00 0x00] >>>>>> Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 >>>>>> Amp-Out vals: [0x00 0x00] >>>>>> Pincap 0x08373e: IN OUT HP Detect >>>>>> Pin Default 0x01813040: [Jack] Line In at Ext Rear >>>>>> Conn = 1/8, Color = Blue >>>>>> Pin-ctls: 0x40: OUT >>>>>> Connection: 5 >>>>>> 0x0c 0x0d 0x0e* 0x0f 0x26 >>>>>> Node 0x19 [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out >>>>>> Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0 >>>>>> Amp-In vals: [0x00 0x00] [0x00 0x00] [0x00 0x00] [0x00 0x00] >>>> [0x00 0x00] >>>>>> Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 >>>>>> Amp-Out vals: [0x80 0x80] >>>>>> Pincap 0x08373e: IN OUT HP Detect >>>>>> Pin Default 0x02a19850: [Jack] Mic at Ext Front >>>>>> Conn = 1/8, Color = Pink >>>>>> Pin-ctls: 0x24: IN >>>>>> Connection: 5 >>>>>> 0x0c* 0x0d 0x0e 0x0f 0x26 >>>>>> Node 0x1a [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out >>>>>> Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0 >>>>>> Amp-In vals: [0x00 0x00] [0x00 0x00] [0x00 0x00] [0x00 0x00] >>>> [0x00 0x00] >>>>>> Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 >>>>>> Amp-Out vals: [0x00 0x00] >>>>>> Pincap 0x08373e: IN OUT HP Detect >>>>>> Pin Default 0x9993014f: [Fixed] Aux at Int ATAPI >>>>>> Conn = ATAPI, Color = Unknown >>>>>> Pin-ctls: 0x40: OUT >>>>>> Connection: 5 >>>>>> 0x0c 0x0d* 0x0e 0x0f 0x26 >>>>>> Node 0x1b [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out >>>>>> Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0 >>>>>> Amp-In vals: [0x00 0x00] [0x00 0x00] [0x00 0x00] [0x00 0x00] >>>> [0x00 0x00] >>>>>> Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 >>>>>> Amp-Out vals: [0x00 0x00] >>>>>> Pincap 0x08373e: IN OUT HP Detect >>>>>> Pin Default 0x02214020: [Jack] HP Out at Ext Front >>>>>> Conn = 1/8, Color = Green >>>>>> Pin-ctls: 0xc0: OUT HP >>>>>> Connection: 5 >>>>>> 0x0c* 0x0d 0x0e 0x0f 0x26 >>>>>> Node 0x1c [Pin Complex] wcaps 0x400001: Stereo >>>>>> Pincap 0x0820: IN >>>>>> Pin Default 0x411111f0: [N/A] Speaker at Ext Rear >>>>>> Conn = 1/8, Color = Black >>>>>> Pin-ctls: 0x20: IN >>>>>> Node 0x1d [Pin Complex] wcaps 0x400000: Mono >>>>>> Pincap 0x0820: IN >>>>>> Pin Default 0x4005a603: [N/A] Line Out at Ext N/A >>>>>> Conn = Optical, Color = UNKNOWN >>>>>> Pin-ctls: 0x20: IN >>>>>> Node 0x1e [Pin Complex] wcaps 0x400300: Mono Digital >>>>>> Pincap 0x0810: OUT >>>>>> Pin Default 0x01451130: [Jack] SPDIF Out at Ext Rear >>>>>> Conn = Optical, Color = Black >>>>>> Pin-ctls: 0x40: OUT >>>>>> Connection: 1 >>>>>> 0x06 >>>>>> Node 0x1f [Pin Complex] wcaps 0x400200: Mono Digital >>>>>> Pincap 0x0820: IN >>>>>> Pin Default 0x01c59160: [Jack] SPDIF In at Ext Rear >>>>>> Conn = Optical, Color = Pink >>>>>> Pin-ctls: 0x20: IN >>>>>> Node 0x20 [Vendor Defined Widget] wcaps 0xf00040: Mono >>>>>> Node 0x21 [Vendor Defined Widget] wcaps 0xf00000: Mono >>>>>> Node 0x22 [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] [0x00 0x00] [0x80 0x80] >>>> [0x00 0x00] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 >>>> 0x80] [0x80 0x80] >>>>>> Connection: 11 >>>>>> 0x18 0x19 0x1a 0x1b 0x1c 0x1d 0x14 0x15 0x16 0x17 0x0b >>>>>> Node 0x23 [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] [0x00 0x00] [0x80 0x80] >>>> [0x00 0x00] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 >>>> 0x80] [0x80 0x80] >>>>>> Connection: 11 >>>>>> 0x18 0x19 0x1a 0x1b 0x1c 0x1d 0x14 0x15 0x16 0x17 0x0b >>>>>> Node 0x24 [Vendor Defined Widget] wcaps 0xf00000: Mono >>>>>> Node 0x25 [Audio Output] wcaps 0x11: Stereo >>>>>> PCM: >>>>>> rates [0x560]: 44100 48000 96000 192000 >>>>>> bits [0xe]: 16 20 24 >>>>>> formats [0x1]: PCM >>>>>> Node 0x26 [Audio Mixer] wcaps 0x20010f: Stereo Amp-In Amp-Out >>>>>> Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 >>>>>> Amp-In vals: [0x00 0x00] [0x80 0x80] >>>>>> Amp-Out caps: ofs=0x1f, nsteps=0x1f, stepsize=0x05, mute=0 >>>>>> Amp-Out vals: [0x00 0x00] >>>>>> Connection: 2 >>>>>> 0x25 0x0b >>>>>> >>>>>> A second codec sits at /proc/asound/Intel/codec#0. A cat results >>>> in: >>>>>> >>>>>> Codec: Generic 1095 ID 1392 >>>>>> Address: 1 >>>>>> Vendor Id: 0x10951392 >>>>>> Subsystem Id: 0xffffffff >>>>>> Revision Id: 0x100000 >>>>>> No Modem Function Group found >>>>>> Default PCM: >>>>>> rates [0x0]: >>>>>> bits [0x0]: >>>>>> formats [0x0]: >>>>>> Default Amp-In caps: N/A >>>>>> Default Amp-Out caps: N/A >>>>>> Node 0x02 [Audio Output] wcaps 0x6211: Stereo Digital >>>>>> PCM: >>>>>> rates [0x7f0]: 32000 44100 48000 88200 96000 176400 192000 >>>>>> bits [0x1e]: 16 20 24 32 >>>>>> formats [0x5]: PCM AC3 >>>>>> Node 0x03 [Pin Complex] wcaps 0x40738d: Stereo Digital Amp-Out >>>>>> Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 >>>>>> Amp-Out vals: [0x80 0x80] >>>>>> Pincap 0x0894: OUT Detect >>>>>> Pin Default 0x18560010: [Jack] Digital Out at Int HDMI >>>>>> Conn = Digital, Color = Unknown >>>>>> Pin-ctls: 0x00: >>>>>> Connection: 1 >>>>>> 0x02 >>>>>> >>>>>> >>>>>>> From: tdavis(a)dsl-only.net >>>>>>> To: fuuss(a)hotmail.com >>>>>>> Date: Wed, 26 Dec 2007 11:30:28 -0800 >>>>>>> CC: alsa-devel(a)alsa-project.org >>>>>>> Subject: Re: [alsa-devel] intel-hd on an intel G33 motherboard >>>>>>> >>>>>>> Try "model=3stack-6ch". Also, if you look in the >>>>>>> >>>> alsa-driver-1.0.15/alsa-kernel/Documentation/Alsa-Configuration.txt >>>>>>> file, there are other models you can select for the alc883/888 >>>> codec. >>>>>>> >>>>>>> Let me know if this works and I'll add your system to the driver. >>>>>>> >>>>>>> Tobin >>>>>>> >>>>>>> On Wed, 2007-12-26 at 18:42 +0000, De Fuuss wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> Maybe I'm missing something, but I've failed to get even the >>>> slightest >>>>>>>> noise out of the onboard sound card from a Intel G33 motherboard. >>>> I >>>>>>>> tried the alsa drivers from the alsa-driver-1.0.15 package as >>>> well as >>>>>>>> the the alsa drivers provided by kernel 2.6.23 (built as >>>> modules), to >>>>>>>> no avail. >>>>>>>> >>>>>>>> The sound chip is identified as a Intel HDA / Realtek ALC888 on >>>> the Intel G33 ICH9 motherboard. >>>>>>>> >>>>>>>> After reading some of the documentation from the ALSA site and >>>> googling through half the internet I haven't found out yet if this >>>> specific sound card is supported by ALSA and if some module options >>>> must be passed (such as options snd-intel-hda model=.....). >>>>>>>> >>>>>>>> Could somebody be so kind as to point me into the right >>>> direction? >>>>>>>> >>>>>>>> Thank you. >>>>>>>> >>>>>>>> Best regards, >>>>>>>> >>>>>>>> Patrick >>>>>>>> >>>>>>>> _________________________________________________________________ >>>>>>>> Express yourself instantly with MSN Messenger! Download today >>>> it's FREE! >>>>>>>> http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ >>>>>>>> _______________________________________________ >>>>>>>> Alsa-devel mailing list >>>>>>>> Alsa-devel(a)alsa-project.org >>>>>>>> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel >>>>>>> >>>>>>> -- >>>>>>> Tobin Davis >>>>>>> >>>>>>> >>>>>>> TONY RANDALL! Is YOUR life a PATIO of FUN?? >>>>>>> _______________________________________________ >>>>>>> Alsa-devel mailing list >>>>>>> Alsa-devel(a)alsa-project.org >>>>>>> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel >>>>>> >>>>>> _________________________________________________________________ >>>>>> Express yourself instantly with MSN Messenger! Download today it's >>>> FREE! >>>>>> http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ >>>>>> _______________________________________________ >>>>>> Alsa-devel mailing list >>>>>> Alsa-devel(a)alsa-project.org >>>>>> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel >>>>> >>>>> -- >>>>> Tobin Davis >>>>> >>>>> >>>>> Authors are easy to get on with -- if you're fond of children. >>>>> -- Michael Joseph, "Observer" >>>> >>>> _________________________________________________________________ >>>> Express yourself instantly with MSN Messenger! Download today it's >>>> FREE! >>>> http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ >>>> _______________________________________________ >>>> Alsa-devel mailing list >>>> Alsa-devel(a)alsa-project.org >>>> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel >>>> >>>> >>> >>> _______________________________________________ >>> Alsa-devel mailing list >>> Alsa-devel(a)alsa-project.org >>> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel >> >> _________________________________________________________________ >> Express yourself instantly with MSN Messenger! Download today it's FREE! >> http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ > > _______________________________________________ > Alsa-devel mailing list > Alsa-devel(a)alsa-project.org > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

3 7

[alsa-devel] [PATCH] cs4231: remove one busy wait
by Krzysztof Helt 14 Jan '08

14 Jan '08

From: Krzysztof Helt <krzysztof.h1(a)wp.pl> This busy_wait is not needed after latest changes to the cs4231-lib Signed-off-by: Krzysztof Helt <krzysztof.h1(a)wp.pl> --- Just after this busy wait is 1ms sleep then waiting loop. --- linux-2.6.22/sound/isa/cs423x/cs4231_lib.c 2007-09-11 00:02:15.000000000 +0200 +++ linux-2.6.23/sound/isa/cs423x/cs4231_lib.c 2007-09-11 00:03:36.619095346 +0200 @@ -332,7 +332,6 @@ void snd_cs4231_mce_down(struct snd_cs42 !(chip->hardware & (CS4231_HW_CS4231_MASK | CS4231_HW_CS4232_MASK))) { return; } - snd_cs4231_busy_wait(chip); /* * Wait for (possible -- during init auto-calibration may not be set) ---------------------------------------------------------------------- Chcesz kupic aparat? Sprawdz, ktory jest najlepszy! Kliknij >>> http://link.interia.pl/f1cd3

2 1

[alsa-devel] Si3054 and Lenovo3000 n100
by Vasily Khoruzhick 14 Jan '08

14 Jan '08

Hi, I have problems with setting up internal modem (regular si3054 sitting on hda bus) with subj notebook. During boot I get following message in dmesg: ALSA /var/tmp/portage/media-sound/alsa-driver-9999/work/alsa-driver/pci/hda/../../alsa-kernel/pci/hda/patch_si3054.c:237: si3054: cannot initialize. EXT MID = 0000 And then when I try to use slmodem I get following repeating messages from slmodemd: <598.472031> main: alsa xrun: try to recover... <598.475735> main: alsa xrun: recovered. <598.475792> main: dev read = 0 I've tried to use alsa-driver-1.0.15 and latest alsa-driver from hg tree I can provide any additional info, just ask ;) Regards Vasily

3 4

Re: [alsa-devel] [Alsa-user] Intel HDMI Audio Output
by Lee Revell 14 Jan '08

14 Jan '08

On Jan 13, 2008 5:46 AM, Paul McEnery <pmcenery(a)gmail.com> wrote: > Following an email to the manufacturers European support representatives, I > was asked to try the following custom version of ALSA: > > > http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PFid=24&Lev… > > > I am working on building and trying these drivers, but have a couple of > questions in the meantime: > > 1. Does anyone know what the status of HDMI audio support is (in particular > Intel)? > > 2. Any idea why Realtek are maintaining their own version of drivers? Is > this a legal/licensing issue? Jaroslav and Takashi-san, Any idea why Realtek is still maintaining their forked ALSA? I thought you guys raised the issue with them a while back and they agreed to submit their changes through the standard process. Lee

2 1

[alsa-devel] [PATCH] hda_intel: Fix multiple device support by incrementing device count
by Andrew Paprocki 13 Jan '08

13 Jan '08

Fixes multiple device support by incrementing the static device counter at the end of the azx_probe() call. Without this, subsequent probes would always use the index specified for the first card. Signed-off-by: Andrew Paprocki <andrew(a)ishiboo.com> diff -r acdc98363786 -r bde9dbdbd2ba pci/hda/hda_intel.c --- a/pci/hda/hda_intel.c Fri Jan 11 18:15:26 2008 +0100 +++ b/pci/hda/hda_intel.c Sat Jan 12 18:59:58 2008 -0500 @@ -1933,6 +1933,7 @@ static int __devinit azx_probe(struct pc chip->running = 1; power_down_all_codecs(chip); + dev++; return err; }

2 1

[alsa-devel] [PATCH] hda: Fix 5.1 sound in Dell 6stack ALC888 HDA
by Claudio Matsuoka 13 Jan '08

13 Jan '08

This patch fixes 5.1 surround output and headphone detection in the Dell Inspiron 530 and possibly other Dell systems using the ALC888 codec (mode 6stack-dell). This configuration is very similar to 6stack-hp, which also has rear/clfe channels swapped if compared to the standard ALC883 6stack configuration. (This is my first mercurial-generated patch, I added the signed-off line by hand and the user name in the header is an internal address, please correct that if needed.)

2 1

[alsa-devel] Realtek ALC883 support on Albatron KI690-AM2 motherboard
by Andrew Paprocki 13 Jan '08

13 Jan '08

Hello everyone, I'm currently trying to get the ALC883 on the Albatron KI690-AM2 motherboard working under ALSA and I'm running into problems with some of the ports. From looking at the patch_realtek.c file inside the intel_hda driver, it appears there are many variants of hookups to this chipset which all require some manual configuration in the driver. I've tried what appears to be the closest match (ALC883_6ST_DIG or 6stack-dig), but it still does not enable all of the ports. The motherboard webpage is here: http://www.albatron.com.tw/English/product/mb/pro_detail.asp?rlink=Specific… The board has two audio stacks on the back panel. Facing the jack inputs, the left-hand stack contains: <S/PDIF output> <TOSLINK w/ green cover> Next to that stack is a larger 6-stack with the following configuration: <blue> <black> <green> <pink> <grey> <TOSLINK w/ pink cover> The box is running a stock debian 2.6.18-4-486 kernel. The kernel outputs this at startup if the "6stack-dig" model is not explicitly supplied: hda_codec: Unknown model for ALC883, trying auto-probe from BIOS... hda-intel: Invalid position buffer, using LPIB read method instead. When using the "6stack-dig" mode, ALSA sees two devices: card 0: SB [HDA ATI SB], device 0: ALC883 Analog [ALC883 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: SB [HDA ATI SB], device 2: ALC883 Digital [ALC883 Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 When attempting to use ALSA to open the first device in raw mode to output to each stereo pair separately, 5 pairs are detected, and the outputs appear as follows... Pair 1: <green> (working) Pair 2: <pink> (working) Pair 3: <black> (working) Pair 4: (no audio) Pair 5: (no audio) No sound can be heard from the blue or grey jacks in any configuration. I'm wondering if a special entry is needed in patch_realtek.c to handle this board's usage of the ALC883. I am willing to try changing the code and testing if someone can point me to what might need to be done. 01:05.2 Audio device: ATI Technologies Inc Unknown device 7919 Subsystem: Albatron Corp. Unknown device 5000 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 64, Cache Line Size: 4 bytes Interrupt: pin B routed to IRQ 3 Region 0: Memory at fdffc000 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable- Address: 0000000000000000 Data: 0000 Thanks, -Andrew

2 6

[alsa-devel] Hotplug plugin
by Erik Slagter 13 Jan '08

13 Jan '08

Sorry for crossposting, but this is a problem I am not quite sure might be solved by users or developers. Also I am not too lazy to do a little development myself, if that appears to be necessary. This is my setup: - internal snd-hda soundcard connected to speakers in the bathroom playing 24x7 music; - jvc amplifier in living room with integrated USB sound device. The USB sound device in the amplifier vanishes when the amplifier is powered down. So... this is my problem. I want to have 24x7 music on the internal soundcard and on the amplifier. When the amplifier is switched off, no audio should be send there (of course) but playback should resume as soon as the amplifier is switched on and the USB device re-appears. I created a "tee" construction using asound.conf which adresses both soundcards, this works. At least... until the amplifer is switched off and the USB device disappears. Then the sound playing application gets an error and quits. I tried these approaches for a solution: - pulseaudio, using hal-detection and "combined" device: doesn't work because a removed device is never reinserted into the combined device; - alsa extplug: easy to create, no worries about the "slave" device, you get it for free, but I abandoned the idea as there is probably no way to recreate the slave pcm while the "owner" remains active. - alsa ioplug, attempt 1: there is probably no way to to address and recreate the "slave" (which I open myself in the plugin using snd_pcm_open) in such a way that it is completely transparent to the application that it is talking to the "slave" (not a "real" alsa slave) instead of the ioplug plugin - alsa ioplug, attempt 2: I tried to make the callback functions of the ioplug call the callbacks of the "slave" directly, but that probably isn't going to work either (too much callbacks in the pcm struct that have no equivalent in the ioplug struct) - alsa ioplug, attempt 3: open and write to the hardware devices directly. Abonded it as well because this cannot practically be done, as you'd need parts copies of header files from the kernel and alsalib for hidden data structures. Anyone ideas to solve this in a neat way? (preferrably using an alsa plugin; for the moment I am using a self-made external program that alsa dumps it sound to (file plugin) and uses two alsa-player processes to get the audio to the devices)

2 4

[alsa-devel] Disabling buffer fill level preprocessing by ALSA
by Lennart Poettering 12 Jan '08

12 Jan '08

Hi! In PulseAudio I want to schedule on my own when I need to write audio data into the device and when not. To achieve that I want to be notified via poll() whenever a period boundary is passed (i.e. when an IRQ happens), but only then. That's different from the usual mode where you are notified via poll() whether there is space in the playback buffer that needs to be filled up. On OSS the mmap() mode enables a mode like I described above. After enabling mmap() the application can decide by itself what it considers full and what empty in the dma buffer, and use GETOPTR to query the playback position. poll() on the OSS fd will directly reflect the sound card IRQs and is not influenced if you ever wrote data to device or not. I assume that I can enable a mode like that with one of the SW params. But quite frankly the docs for it are not enlighening at all. Lennart -- Lennart Poettering Red Hat, Inc. lennart [at] poettering [dot] net ICQ# 11060553 http://0pointer.net/lennart/ GnuPG 0x1A015CC4

4 10