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

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

16 Jan '08

Hi, I have recompiled the driver with --with-debug=detect. Dmesg output is attached to this mail. ALSA specificities seem to be present this time. Hope this helps. Best regards, Patrick > From: zhe.jiang(a)intel.com > To: fuuss(a)hotmail.com > Date: Tue, 15 Jan 2008 09:32:35 +0800 > CC: cmatsuoka(a)gmail.com; alsa-devel(a)alsa-project.org > Subject: Re: [alsa-devel] intel-hd on an intel G33 motherboard > > On Mon, 2008-01-14 at 17:11 +0000, De Fuuss wrote: >> The jumper is now set to enable onboard (Intel HDA) audio. >> At the back of the barebone there are 5 jacks (4 channels for 7.1 and 1 line in channel) + 1 spdif out. >> From these, using 6stack-hp, only the "Front L/R" jack works, none of the others >> On the front, there are 2 jacks (1 headphones and 1 microphone). The headphone jack works. >> > Can you tell us how you did the testing? >>From the driver code, it's not likely that all other jacks don't work. > > Because the driver support up-mixing, you can play a 2-channel music and > get sound from 4 jacks on the back panel. > > I read the dmesg output that you sent to me. > But there is no alsa debug info in it. > Did you really configure the driver with the option > "--with-debug=detect"? > If not, please try it and paste the dmesg info, it is helpful to trace > the issue. > > Best regards! > Jiang,zhe >> All the channels have been set to 100% in alsamixer. >> >> Considering that a week ago I had 0.0 and today I'm at 2.0, it's already a improvement. ;-) >> >> Patrick >> >>> Subject: Re: [alsa-devel] intel-hd on an intel G33 motherboard >>> From: zhe.jiang(a)intel.com >>> To: fuuss(a)hotmail.com >>> CC: cmatsuoka(a)gmail.com; alsa-devel(a)alsa-project.org >>> Date: Mon, 14 Jan 2008 16:43:00 +0800 >>> >>> On Mon, 2008-01-14 at 02:06 +0800, De Fuuss wrote: >>>> >>>> Following your advice, I tested per channel output. Using either >>>> 6stack-dig or 6stack-hp, I get noise from Front Left and Right jacks, >>>> using speaker-test (X=1 and 2) but not on any other channels. >>> >>> Hi, >>> Did you mean that after you changed the 'Jumper', >>> you could get the sound from the Front jack on the back channel? >>> >>>> Patrick >>>> >>>>> Date: Sun, 13 Jan 2008 01:01:50 -0200 >>>>> From: cmatsuoka(a)gmail.com >>>>> To: fuuss(a)hotmail.com >>>>> CC: zhe.jiang(a)intel.com; alsa-devel(a)alsa-project.org >>>>> Subject: Re: [alsa-devel] intel-hd on an intel G33 motherboard >>>>> >>>>> 2008/1/12 De Fuuss : >>>>> >>>>>> 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. >>>>> >>>>> I fixed the Inspiron output, and I'm adding the SG33G5M codec to the >>>>> codecgraph codecs collection (git repository at >>>>> http://helllabs.org/git/codecgraph.git). If nodes 0x14, 0x15, 0x16 >>>> and >>>>> 0x17 are the front, rear, clfe and side connectors in the back >>>> panel, >>>>> 6stack-hp should work (at least for the outputs). You can test the >>>>> outputs using "speaker-test -Dplug:surround71 -c8 -sX" (where X >>>> varies >>>>> from 1 to 8) and a pair of headphones. >>>>> _______________________________________________ >>>>> 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/ > > _______________________________________________ > 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/

2 1

Re: [alsa-devel] Splitting up the HDA-INTEL modules
by Jonathan Woithe 16 Jan '08

16 Jan '08

Marco Schuster wrote: > when I looked today through the files of the snd-hda-intel module, I > was a bit shocked by this complex amount of code (patch_realtek.c for > example). I would think about splitting up the code in a way each > chipset gets its own .c file - which will make debugging, patching or > editing a lot easier IMO, and for second people can then comment on > just their specific chipset in config. The problem with such a split is, as Tobin went on to say, that there are a lot of interdependencies and shared code within each chipset's family: > I don't think that it would be very easy, as there are several instances > where code relies on other codec definitions. One could argue that therefore we have toplevel realtek/sigmatek/etc "librarys" which are used by each chipset-specific driver but IMHO that is hardly going to count as a simplification. Tobin then said: > In all actuality, what is needed is a more generic driver that is driven > by userspace tools. ... Maybe we can get a core group together and > actually define and implement an API for this. I think this idea has merit and may be worth pursuing. I would be interested in assisting and providing input to the process although I haven't time at present to take a lead role. > My idea is a driver that takes settings from a config file that are > either 32bit register values (aka Sigmatel), or individual Node > parameters (Realtek, Conexant, etc). This way we can define model > config files, and associate their PCI Quirk in a central config file > that can be edited in userspace. This would be much easier to support, > for users, distro vendors, hardware vendors, and us. Agreed, at least in theory. There may be complications due to the varying topography of the chips; the userspace API may have to be relatively complex to support things like record source switch options (which are vastly different for diffenent chips). Even so, if we can get this to work the ongoing support effort for HDA will be much reduced so it's probably worth the effort. > I'll try to write up a proposal in the next few weeks, if we can get > others on board to work on this. I think this would be worth looking at. Regards jonathan

1 0

[alsa-devel] HDA: Enable chipset gcap usage
by Tobin Davis 15 Jan '08

15 Jan '08

I tweaked this as promised, and ran it through the checkpatch.pl utility from kernel git tree. I have tested it on my Asus Z62F laptop as well as a few systems in my work environment without issue. Summary: hda_intel.c use gcap register to determine number of streams supported by southbridge. This patch quieries the southbridge for the number of streams supported by the southbridge in most chipsets, and reads these values from the chipset directly. Most systems are hardwired for 4 streams in each direction, but newer chipsets change that capability. As a fallback, the old hardcoded method is still available. Signed off by Tobin Davis <tdavis(a)dsl-only.net>

2 2

[alsa-devel] Fwd: surround51 lfe/center/front channel cross-talk with intel8x0 board
by Matt Hirsch 15 Jan '08

15 Jan '08

I sent this to alsa-users and didn't get any response. I'd be grateful if someone had some suggestions for getting around the problem described below. Thanks very much, Matt ---------- Forwarded message ---------- From: Matt Hirsch <matthew.hirsch(a)gmail.com> Date: Jan 5, 2008 1:20 AM Subject: surround51 lfe/center/front channel cross-talk with intel8x0 board To: alsa-user(a)lists.sourceforge.net I have an AC'97 based onboard sound card in my system (snd_intel8x0 driver). I'm using it in 6ch mode to drive two front speakers, two rear speakers and a subwoofer and center channel. Using speaker-test with the surround51 plug (or any other alsa program with that plug) to send audio to channel 5 (center in alsamixer) produces an attenuated signal on channel 2 (right front in alsamixer) and likewise, sending audio to channel 6 (lfe in alsamixer) produces an attenuated signal on channel 1 (left front in alsamixer). In summary: speaker-test -tsine -f200 -Dsurround51 -c6 -s1 tone on left front speaker only speaker-test -tsine -f200 -Dsurround51 -c6 -s2 tone on right front speaker only speaker-test -tsine -f200 -Dsurround51 -c6 -s3 tone on left rear speaker only speaker-test -tsine -f200 -Dsurround51 -c6 -s4 tone on right rear speaker only speaker-test -tsine -f200 -Dsurround51 -c6 -s5 tone on center speaker, and quieter tone on right front speaker speaker-test -tsine -f200 -Dsurround51 -c6 -s6 tone on lfe, and quieter tone on left front speaker Any help or suggestions as to getting rid of this crosstalk would be greatly appreciated! Here's what I've tried so far: If I don't use the surround51 plug, and use default (hw:0) instead, the channels are all in a different order, but the same effect occurs (crosstalk between two channels). I tried sequentially setting and un-setting all of the modes and buttons in the alsa mixer, such as high-pass filter (on/off), surround jack mode (shared/independent), line jack sense (on/off), exchanging front/surround, etc. Nothing seemed to have any effect. When I exchange the front and surround speakers, the cross talk is also exchanged (i.e. it shows up on the rear speakers rather than the front speakers). I'm running fedora 8, so I started with the latest fedora 8 alsa rpms (1.15). When this didn't work I compiled a recent CVS snapshot (12/25/07) against my kernel and installed it. Same results as above. My hardware shows up in lspci as: 00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] AC'97 Sound Controller (rev a0) My kernel is 2.6.23.9-85.fc8 Thanks, Matt

2 2

[alsa-devel] ALC268 test model not working
by Marco Schuster 15 Jan '08

15 Jan '08

Hi all, finally I got the patch applied to kernel src :) But it doesn't work correctly, because when running alsamixer, dmesg tells "hda_codec: num_steps = 0 for NID=0x1d", and alsamixer fails with alsamixer: function snd_mixer_load failed: Invalid argument. Is this some obscure bug in the notebook hardware or some driver bug? Marco (note, I apply against .24-rc6 still)

3 4

[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