On Sun, 29 Sep 2007, Frederic Van Assche wrote: > Hi, > > I have 3 small issues with the alsa driver of the soundcard in my new laptop. > > 1. I have no master control. Sometimes I have a PCM control, which is only > mono and has no mute button. I tried the beta 1.0.15 driver a few days ago, > and I had a stereo master channel and a mono pcm channel, both with mute > controls, until my next reboot. I've been trying to get a master or pcm > channel with a mute control again, preferably stereo, but have been > unsuccessful. You obviously did not install the 1.0.15 drivers properly. > > 2. I would love to use the front microphone jack as a center/LFE output, as to This is a harware issue. Software cannot hook up wires from the output to the chips to an input jack. That has to have been done in hardware. > have 5.1 sound output. Right now, the only input I can turn into an output is > the line out jack, which isn't connected to any physical jack on this > machine. Is it possible to use this front microphone jack for center/LFE > output? This system has three jacks, two of which work as expected (front r/l > and rear r/l), and a third which is supposed to be a microphone input, but > appears to have output capabilities as well. The codec#0 file reports more > jacks, which have no physical connection, and the line in I'm able to switch > to an output from the mixer is one of those. > > 3. Recording seems to be troublesome. The built-in mic hasn't produced any > sound yet as far as I know, but the front microphone jack has. I haven't > really tested recording yet, but I can dig deeper into this if someone's > interested in helping me fix these issues. > > These are three minor issues which I hope can be fixed. I run the 1.0.14 alsa > userspace tools/libs and the built-in drivers of the 2.6.22.9 kernel (with > gentoo patches). Alsa modules load as auto-detected without custom > parameters. You ahve not told us which chipset nor which computer these are in. How do we know whether you are supposed to use custom stuff or not. Alsa autodetection is not alsa auto detection -- it is detection via some program in your distro (eg hal) You need to edit /etc/modprobe.conf yourself to make sure that the right options are presented to the module. The HDA is very widely used and abused. Every manufacturer seems to feel that they have to munge it into incompatibility themselves. Otherwise their engineers do not have enough to do. Alsa writers can only rush after them and try to sweep up the worst of the poop dropped from these out of control horses. > > I have attached /proc/asound/Intel/codec#0 for reference. > > Thanks, > Frederic > > -- William G. Unruh | Canadian Institute for| Tel: +1(604)822-3273 Physics&Astronomy | Advanced Research | Fax: +1(604)822-5324 UBC, Vancouver,BC | Program in Cosmology | unruh@xxxxxxxxxxxxxx Canada V6T 1Z1 | and Gravity | www.theory.physics.ubc.ca/ ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Alsa-user mailing list Alsa-user@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-user
