[PATCH] Add STAC9228 DMIC support, SRU TEST CASE

What is this? The internal mic for dell xps1330 for exemple?

Thank you for taking the time to report this bug and helping to make Ubuntu better. I'm reassigning to the kernel-team for their consideration. Thanks!

LEVIS Cyril wrote:
> What is this? The internal mic for dell xps1330 for exemple?
>
>
Actually, Dell XPS M1330

Hehey ! Cool Leann Ogasawara, thanks for the patch Matthew, now wait and see for the alsa/kernel update :)

edit: Ok Matthew :)
I'm so happy, i think i must find new bug and hardware drivers improvement to do :p

Ok this the last patch respun including the required dmux changes.

How can I easyly install and try it please?

Download the linux-source-2.6.22 package and apply the within the linux source directory with 'patch -p1 < stac9228_dmux_ubuntu.patch'. Be sure the hda-intel module is selected in the kernel config and build. You'll want to read the Ubuntu kernel howto if you don't know to make initrd image for the kernel modules.

hink I will wait for you or other package and update the module :-)

Regards :-)
(if i find time to try it i will say to you)

* -hink

Anyway to simply save ,compil the module, and replace it in the current kernel?
Sorry for my question

Ok this patch is be applied with the last one, it changes the dmux nid to a more sensible one(i.e the first one) which most capture apps use by default.

Cool :)

Do you know when is the next module update? :)

This patch contains all previous patches, and it includes the _right_ mixer for the cards that currently have DMIC.

Oops, I inappropriately changed this to "Fix Committed". This should only be done by an actual kernel dev. I'm flipping back to a "Triaged" state.

Tried the fix on a Vostro 1400 (uses STAC9228 too) , but, alas, no dice...

After patching the "patch_sigmatel.c" file in the kernel sources, i copied the resulting file over to a fresh download of the ALSA 1.0.14 drivers and built those instead. Saved me compiling the complete kernel :)

Ok this patch applied with the last one solves the issue, I know this because I tested it personally. Already applied to ALSA HG upstream.

I'm waiting for the update yet, I hope this is for this week :D

Accepted into gutsy-proposed, please test.

Works for me (DELL Inspiron 1420). The only problem is that you have to be very accurate when setting sound/capturing volume (you slide the bar to half of its length and get no sound), but it's probably a matter to discuss in another bug.

I meant "Works for me with the latest linux-backports-modules from gutsy-proposed". :) Sorry if my comment above was ambiguous.

gutsy-proposed fix works for me, however it is not very useful as yet as the capture volume on the mic is very, very low - perhaps unusable. Am I missing some switch or channel that might be able to give a capture boost?

You can adjust the capture volume by using "Digital" slider in the capture section. I tested the mic with gnome-sound-recorder, and volume was ok, but when using Skype I was heard so silent that one could hardly understand me...

I am also a 1420 owner, but am unable to duplicate Pawel's results. I am unable to record any sound using the microphone array using the the latest linux-backports-modules. I know the microphones work, because I tested them in Vista before I installed Ubuntu over it.

Pawel or Martin, if either of you could list steps for a testing procedure it would be much appreciated.

Thanks,

Harvey

That is exactly what I have done:

1) added gutsy-proposed to my sources.list
2) ran apt-get update
3) installed linux-backports-modules
4) restarted the laptop to reload the kernel and modules
5) ran alsamixer and set the following settings:
   Section: [All]
     Digital Input Source: Digital
     Input source: Front Mic (probably unnecessary)
   Section: [Capture]
     Capture: max volume, capture ON
     Digital: max volume
6) and, at last, started gnome-sound-recorder with input "Digital" to check if that worked - and it did :)

Hope this will help you.

Regards,
Paweł

Pawel (sorry, don't have the special l),

I do not get the same results. And I am thinking it may be because I am using amd64 and not the 32bit version of Ubuntu 7.10.

Although I don't think it's necessary to install all the gutsy-proposed updates, I performed that anyway along with the rest of your steps.

When I run alsamixer, I do not get a digital input source item. But the rest of the items apply. I still receive no detectable input through the microphone array.

Afterwards, I installed the alsa-base_1.0.15-2ubuntu1_all.deb from Hardy. The Digital item appeared in alsamixer, but it did not resolve the issue either.

I'm looking for other suggestions. Best regards,

Harvey

I may be getting it wrong, but check which version of linux-backports-modules you have (should be 2.6.22-14.11),
and confirm that the package for your architecture is listed here: https://lists.ubuntu.com/archives/gutsy-changes/2007-November/010033.html

Regards,
Paweł

I don't feel so mentally underpowered now. The version I get, whether or not gutsy-proposed is selected: 2.6.22-14.9. And I can see in the us archives, that ... .11 is not available for amd64.

The email you attached shows that it should be available for amd64 (generic), but I can see it is not.

I guess I could go find the source package and create my own binary.

Thanks,

Harvey

----- Original Message ----
> From: Paweł Drewniak <email address hidden>
> To: <email address hidden>
> Sent: Tuesday, November 27, 2007 9:13:33 AM
> Subject: [Bug 153963] Re: [PATCH] Add STAC9228 DMIC support.
>
> I may be getting it wrong, but check which version
> of
>
 linux-backports-modules you have (should be 2.6.22-14.11),
> and confirm that the package for your architecture is listed
> here:
>
 https://lists.ubuntu.com/archives/gutsy-changes/2007-November/010033.html
>
> Regards,
> Paweł
>
> --
> [PATCH] Add STAC9228 DMIC support.
> https://bugs.launchpad.net/bugs/153963
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

I don't feel so mentally underpowered now. The version I get, whether or not gutsy-proposed is selected: 2.6.22-14.9. And I can see in the us archives, that ... .11 is not available for amd64.

The email you attached shows that it should be available for amd64 (generic), but I can see it is not.

I guess I could go find the source package and create my own binary.

Thanks,

Harvey

Attempted to build, but failed.

Later found that this had already been reported:

    https://launchpad.net/ubuntu/+source/linux-backports-modules-2.6.22/2.6.22-14.11 (see remarks at bottom under Build heading)

The fix doesn't work yet for amd64/Core 2 Duo, I may do a reinstall and test under i386.

linux-backports-modules (2.6.22/2.6.22-14.11) works without flaw with Gutsy i386 installed. The missing digital input source option is visible.

This is on an Inspiron 1420 with the microphone array in the display, minus the integrated webcam.

Good job, hope to figure this out for the Gutsy amd64 install.

side note:

This is the error I received when attempting to build for amd64:

find: debian/updates-modules-2.6.22-14-generic-di: No such file or directory
updates-modules-2.6.22-14-generic-di will be empty
make: *** [binary-udebs] Error 1

Support for the Dell XPS1330 and Inspiron 1420 microphones is in upstream ALSA.

linux-ubuntu-modules-2.6.22_2.6.22-14.38 adds support for external microphones on the Dell XPS1330 and Inspiron 1420. However, the complete fix, including built-in microphone support, is in linux-backports-modules which contains ALSA 1.0.15

ALSA 1.0.15 is in the mainstream kernel.

linux-ubuntu-modules-2.6.22_2.6.22-14.38 is currently in the unapproved queue

Accepted into gutsy-proposed, please test and give feedback here.

 linux-ubuntu-modules-2.6.22 (2.6.22-14.38) gutsy-proposed; urgency=low
 .
   [Amit Kucheria]
 .
   * Poulsbo: Update DRM driver to sync with moblin tree
 .
   [Phillip Lougher]
 .
   * Backport lookup_one_len_nd NFS changes from Unionfs 2.0
     - LP: #137765, 103044
   * Backport unionfs_statfs from Unionfs 2.0
     - LP: #137765, 103044
 .
   [Tim Gardner]
 .
   * postinst does not run depmod correctly.
     - LP: #134193
   * depmod uses incorrect options in postinst and postrm
     - LP: #134193
   * Add STAC9228 DMIC support.
     - LP: #153963
   * l-u-m ships with OLD cx2341x mpeg encoder firmware
     - LP: #99107
   * Prevent hard system locks when lirc_pvr150 is loaded
     - LP: #156747
   * Fix version ipw3945 string for Centrino Mobile Test (CMT).
     - LP: #128360

SRU TEST CASE: Prior to linux-ubuntu-modules-2.6.22-14.38 the external microphone on the Dell XPS1330 and Inspiron 1420 did not function. I have this hardware and can verify that this patch enables the external microphones. A more complete fix is in ALSA 1.0.15 which is in linux-backports-modules-2.6.22.

Since linux-backports-modules-2.6.22-14.11 will not build for amd64, I downloaded and installed the latest daily build of alsa-driver/lib/utils and applied the fixes to the alsa-driver as documented by Tim Gardner in ubuntu-gutsy-lbm/updates/sound/README.

The driver/lib/utils builds correctly, and the microphone now works on the 1420 in amd64 (as it does in i386). I don't know enough about the debian packaging/build system to identify why linux-backports-modules-2.6.22-14.11 will not build for amd64, but would guess that since I can build from source there may be something amiss with the package.

Best regards,

Harvey

I did that and it worked. But thesound isn't very good. I can hear a loud hizz sound in the background.

Is it just me or does everybody have that? Can I do something to remove the hizz sound?

frecon wrote:
> I did that and it worked. But thesound isn't very good. I can hear a
> loud hizz sound in the background.
>
> Is it just me or does everybody have that? Can I do something to remove
> the hizz sound?
>
>
Do you have the Digital gain mixer turned all the way up? If so, turn it
down a little should sound less hazy.

When I turn it down the hizz is less but also the sound. So I guess I have to live with it.

I have another problem as well. The recordning volume is ok in gnome-sound-recorder but not in x-lite or ekiga where's it's way low. Can I do something about that?

Try to set Capture level at highest level, and Digital a little lower... It
worked for me in Skype, and now works in every application.

Alsamixer does not show me a 'digital input source'. Just an 'input source'. I also only see HDA Intel, not the Sigmatel at all.

This is after reinstalling alsa at the behest of some other long bug / support entry here. Is there a way to get the sigmatel config back?

Benson Margulies wrote:
> Alsamixer does not show me a 'digital input source'. Just an 'input
> source'. I also only see HDA Intel, not the Sigmatel at all.
>
> This is after reinstalling alsa at the behest of some other long bug /
> support entry here. Is there a way to get the sigmatel config back?
>
>
Paste the results of 'cat /proc/asound/card0/codec#2'

Thanks,

Matt Ranostay

How come this fix is not available for amd64?

The linux-backports-modules is stuck at 2.6.22-14.9 so there is no fix for us :(

Hi!

I'm under AMD64/CoreDuo on Vostro 1400 (STAC9228) and successfully installed linux-backports-modules-2.6.22.14.21 via the gutsy-proposed repository. The Mic still don't work, and I have the DIGITAL bar on gnome-volume-control as I did before.

While running any instance that needs the Mic , I only can hear an horrible and loud noise. It doesn't matter how I turn up or down the CAPTURE and DIGITAL volumes. It's useless to talk anything.

While testing the audio capture on System > Preferences > Sound, I get the following error:
gconfaudiosrc ! audioconvert ! audioresample ! gconfaudiosink profile=chat

Harvey, can you please explain better what you did here? I would like to follow this procedure.
----------
Since linux-backports-modules-2.6.22-14.11 will not build for amd64, I downloaded and installed the latest daily build of alsa-driver/lib/utils and applied the fixes to the alsa-driver as documented by Tim Gardner in ubuntu-gutsy-lbm/updates/sound/README.

The driver/lib/utils builds correctly, and the microphone now works on the 1420 in amd64 (as it does in i386). I don't know enough about the debian packaging/build system to identify why linux-backports-modules-2.6.22-14.11 will not build for amd64, but would guess that since I can build from source there may be something amiss with the package.
----------

Thank You!

Greetings,

Have a Inspiron 1420. The patch worked great. I can now use the built in mic with really good volume! Built in web cam works also. Keep up the good work guys. (installed linux-backports-modules)

Greetings,

Related to the microphone TOO low issue (-50db): on a Dell XPS M1330.
Compiling ALSA from sources - amd64 arch.
I downloaded ALSA snapshot dated 10-Jan-2007 - it already has the patch + also explicitly detects now the M1330 model.
But the mic is still to low, so I searched in patch_sigmatel.c for the "sensibility" patch.... (does it has to make the mic more sensitive?)
- spec->dmux_nid = 0x1c;
+ spec->dmux_nid = 0x1b;
But dmux_nid was removed, there is a member called dmux_nids - which is a vector and contains in this case the patched element - 0x1b.
While have no ideea about these codes and dmux_nids - I think that all your changes are patch are included, and after that the structures slight refactored... but the mic is still unusable. Only thing you can do with it is record with audacity and normalize volume to -6db...? By no means u can't use kopete / skype with this!
So I guess this is still open?

Thanks!

rumburak wrote:
> Greetings,
>
> Related to the microphone TOO low issue (-50db): on a Dell XPS M1330.
> Compiling ALSA from sources - amd64 arch.
> I downloaded ALSA snapshot dated 10-Jan-2007 - it already has the patch + also explicitly detects now the M1330 model.
> But the mic is still to low, so I searched in patch_sigmatel.c for the "sensibility" patch.... (does it has to make the mic more sensitive?)
> - spec->dmux_nid = 0x1c;
> + spec->dmux_nid = 0x1b;
> But dmux_nid was removed, there is a member called dmux_nids - which is a vector and contains in this case the patched element - 0x1b.
> While have no ideea about these codes and dmux_nids - I think that all your changes are patch are included, and after that the structures slight refactored... but the mic is still unusable. Only thing you can do with it is record with audacity and normalize volume to -6db...? By no means u can't use kopete / skype with this!
>
If your talking about the internal digital microphone, it only supports
software gain, i.e you have to use the Softvol gain mixer which is
named 'Digital'.
> So I guess this is still open?
>
> Thanks!
>
>

Thanks,

Matt Ranostay

Matt,

Thanks for your help!
Eventually I got the mic working at an acceptable level using alsa's softvol plugin.
How to do that:
 - get the latest alsa-driver snapshot (12-Jan-2008).
 - get the alsa-utils, alsa-lib (1.0.15).
 - create/edit ~/.asoundrc (per user) - this is mine:
pcm.digmic {
        type softvol
        slave.pcm "default"
        control.name "digmic"
        control.card 0
        min_dB -30.0
        max_dB 30.0
}
The "digmic" is a name chosen by me as a new created recording device, which will be detected by an alsa-compliant application at it's start - you must select it for recording in the application's settings.
The "digmic" is a name chosen by me as a new mixer that will appear *after* starting using this device - this is not crap but a feature like the windows vista dinamic mixers which appear for every new application started.
Tested with skype and audacity - you can properly use the mic. There is a noticeable background noise - more powerful than the one in vista - but I can't tell for sure.
Also the "Digital" slider appears in the mixers, so both "digmic" and "Digital" will appear among the mixers and they both influence the volume. None will appear if you don't have this entry above in ~/.asoundrc. It's like a redundancy which doesn't make much sense to me - maybe I got something wrong, but in the end the mic is working...
Thanks guys!

Mihai

Hello!

I upgraded to Hardy, and at least got no error message anymore when testing the MIC at System > Preferences > Sound. But I still have no sound. I installed the following packages:

alsa-base-1.0.15-4ubuntu1
alsa-utils-1.0.15-2ubuntu1
linux-backports-modules-2.6.24-3.2-generic
linux-ubuntu-modules-2.6.24-3-generic-2.6.24-3.6

But all that I can hear from any record I do is that damn loud noise! I played a lot with the volume control, and got no success yet.

Anyone can help me?
Thanks!

Any news on the Vostro 1400.

(sorry, hit enter accidentally)

Any news on the Vostro 1400? I just bought one so I'm interested in see how things are going.
I'm willing to test new patches and report everything to help solving this.

Keyper7 wrote:
> (sorry, hit enter accidentally)
>
> Any news on the Vostro 1400? I just bought one so I'm interested in see how things are going.
> I'm willing to test new patches and report everything to help solving this.
>

That model should work as well with the lastest ALSA HG tree.

-Matt Ranostay

Sorry for the disappearance, I didn't receive my lappy yet.

As soon as it arrives, I'll post my results.

Okay, after so many posts here I'm a bit confused
(and interested, since I have a laptop with this mic)

So, please correct me where I am wrong (concerning the internal mic):

1) For Gutsy 32-bit, installing the latest linux-backports-modules should be enough.

2) For Gutsy 64-bit, compiling latest alsa image (Or perhaps 1.0.16rc1?) should be enough.

3) For Hardy, it should just work.

4) In all cases, there is noticeable background noise and, although it does not render the
mic unusable, there's not a fix for it yet.

Sorry if I made some or several misinterpretations, but I'm really curious about the situation.

On Jan 28, 2008, at 10:11 PM, Sympy wrote:

> Okay, after so many posts here I'm a bit confused
> (and interested, since I have a laptop with this mic)
>
> So, please correct me where I am wrong (concerning the internal mic):
>
> 1) For Gutsy 32-bit, installing the latest linux-backports-modules
> should be enough.
>
Yes.
> 2) For Gutsy 64-bit, compiling latest alsa image (Or perhaps
> 1.0.16rc1?)
> should be enough.
>
I know that the latter would wok.
> 3) For Hardy, it should just work.
>
> 4) In all cases, there is noticeable background noise and, although
> it does not render the
> mic unusable, there's not a fix for it yet.
>
You probably have the softvol gain mixer all the way up(there is no
hardware gain on the codec), turn it down a little.
> Sorry if I made some or several misinterpretations, but I'm really
> curious about the situation.
>
> --
> [PATCH] Add STAC9228 DMIC support, SRU TEST CASE
> https://bugs.launchpad.net/bugs/153963
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Actually, I didn't try it yet, I want to make sure I understood everything before.

What about the low volume problems? Do I have to do everything rumburak did?

Sorry for all the trouble.

Sympy wrote:
> Actually, I didn't try it yet, I want to make sure I understood
> everything before.
>
> What about the low volume problems? Do I have to do everything rumburak
> did?
>
Actually doing 'arecord -f cd foo.wav -t 10', will automagically create a Digital mixer,
then do a 'sudo alsactl store' to save the setting.

> Sorry for all the trouble.
>

Well the reason for the low volume, is that you basically have to talk really loud without
any software gain.

Well, as long as I don't have to talk loud WITH software gain, I'm fine with it. :)

Thanks for all the quick replies!

Okay, just one last doubt that came to my mind yesterday.

If a high softvol is what causes background noise, does that mean
that iI have to choose between talking loud and having noise?
Or is the noise only caused by REALLY high volume values?

Sympy wrote:
> Okay, just one last doubt that came to my mind yesterday.
>
> If a high softvol is what causes background noise, does that mean
> that iI have to choose between talking loud and having noise?
> Or is the noise only caused by REALLY high volume values?
>

Usually really high gain, remember every 10db is _doubling_ the gain, 2/3 of way up
is usually good.

Sympy
wrote:
Usually
really
high
gain,
remember
every
10db
is
_doubling_
the
gain,
2/3
of
way
up
is
usually
good.

Actually, 6dB double the volume :)

      __________________________________________________________
Sent from Yahoo! Mail - a smarter inbox http://uk.mail.yahoo.com

i appollogize for that tight column - seems like yahoo plays tricks on me?

Vinicius Massuchetto:

I apologize for the very delayed response. A recent death in the family has taken me away from my hobbies for awhile.

Steps to reproduce success (amd64): I'll document these in more detail later, positively sometime this weekend.

Problems you are still having: If I remember right, the reason I used a daily alsa build and not the release version is because the necessary patching is not present in release 1.0.15. The downside to building alsa yourself, is that when the kernel is updated, you have to remember to rebuild alsa manually. Building alsa yourself also assumes you are comfortable compiling software on your own.

FYI: I've just noticed that DELL has updated its wiki page regarding this issue:
http://linux.dell.com/wiki/index.php/Ubuntu_7.10/Issues/Built_In_Digital_Mic_Does_Not_Work

They have a custom build in there...

No problems about compiling software. I rebuilded alsa 1.0.16rc1 and the daily build as well. The problem remains the same in both situations. The loud noise and the same error while testing the audio capture on System > Preferences > Sound:
gconfaudiosrc ! audioconvert ! audioresample ! gconfaudiosink profile=chat

I'm really sorry about your family, and I'll keep waiting for the tutorial for AMD64 until you feel ok to write it.

Thank you!

Microphone is not working by default into the last alpha og hardy :(

I can't use the Dell custom fix due to (again) amd64. =P

Vinicius Massuchetto:

This isn't yet fixed in Hardy Desktop amd64 Alpha 4, yet. But they are promising to update alsa-driver to 1.0.16rc2, which makes the special fix I mentioned before a moot point. If you are still using Hardy you don't have to do any special but compile the 1.0.16rc2 alsa-driver.

Here's the steps to get you going:

1. Open https://help.ubuntu.com/community/HdaIntelSoundHowto

This will walk you through the steps of compiling the alsa-driver, libs, and utils. As far as required tools go, you may only need build-essential. If you aren't sure, it won't hurt to install them all.

2. Get the alsa stuff from http://www.alsa-project.org/main/index.php/Main_Page

For Hardy, all you need is alsa-driver. For Gutsy, just get the latest development versions of each and then follow the instructions. Don't forget to unmute the surround option, or no sound. If you are trying to get the mic to work, then you'll have to add to /etc/modprobe.d/alsa-base:

    options snd-hda-intel model=<3stack or dell-3stack work for me>

Then you have to set all the right options in alsamixer (or in gnome-volume-control), and voila your mic should work

Hope this helps

Here's my situation: I did a fresh install of Gutsy 64-bit on my new Vostro 1400 with the following board:

  00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02)

Initially I had no sound. Following several guides and forum posts, I added

  options snd-hda-intel model=3stack

to /etc/modprobe.d/alsa-base. This got sound working but with a few problems:

1 - Sound didn't work after suspending.
2 - I could get both headphone jacks working after fiddling with the mixers, but the second jack would
not disable the internal speakers and the jacks would not work at the same time.

Changing 3stack to 5stack fixed the first problem but not the second one. So I tried to install the
recently released alsa-1.0.16 to see if I could fix those problems and enable the internal mic.

I downloaded alsa-driver, alsa-firmware, alsa-lib, alsa-plugins and alsa-utils, all 1.0.16, from the
official site and compiled them all with ./configure, make, sudo make install.

The results couldn't be worse: my card stopped being detected. So following the guide in

  https://help.ubuntu.com/community/HdaIntelSoundHowto

I copied /lib/modules/2.6.22-14-generic/kernel/sound/pci/hda/snd-hda-intel.ko
to /lib/modules/2.6.22-14-generic/ubuntu/media/snd-hda-intel/snd-hda-intel.ko
and copied all modules in alsa's compile directory to /lib/modules/.../kernel/sound.

After doing that and a sudo depmod -a, things got a little better: my card was detected.

However, I now have no sound. Nothing. It's like the same situation I had after the fresh install,
only with more mixers. As far as I know, everything is unmuted in alsamixer.

Any clues?

Any news on an amd64 build of linux-backports-modules-2.6.22-14.11?

Does anyone knows the reason why the build failed so far?

Sympy:

I don't know the reason - https://bugs.launchpad.net/dell/+bug/153963/comments/40

But I do know that the workaround for Gutsy is to build alsa yourself using this information - https://wiki.ubuntu.com/HdaIntelSoundHowto?highlight=%28hda%29

The only gotcha with that method though, is that everytime your kernel is updated, you will have to rebuild alsa.

Regards,

Harvey

Confirming bug resolution on Hardy Desktop amd64 Alpha 4 on the Dell Inspiron 1420. The latest update to the kernel in Hardy (2.6.24-7) resolves this issue (and another alsa issue). Big thanks to Daniel Chen (crimsun) and his help in #ubuntu+1 on this issue!

After the kernel is updated you have to perform the following steps to get the microphone to work (this assumes you already have alsa/pulseaudio sound working:

1. open alsamixer
1.a. unmute IEC958
1.b. change Digital Input Source to Digital Mic 1
2. close alsamixer
3. open gnome-volume-control
3.a. navigate to Edit > Preferences
3.b. check the Digital box (or all of them if you prefer)
3.c. open the Recording tab
3.d. raise the volume from 0 to 100
4. open sound recorder and test!

I don't know why alsamixer doesn't show the Digital volume, this may be due to the alsamixer version.

Hi Harvey, thanks for the reply.

I tried to compile alsa-drivers, alsa-lib and alsa-utils like in the link
you gave me. configure, make and make install went without
problems, but after I rebooted my sound simply vanished.

The sound was not working out of the box, I had to put
options probe_mask=1 model=3stack to get it to work, but
after the alsa 1.0.16 installation is not working again.

I executed alsamixer and unmuted everything that was being
shown, but didn't make any difference. Does alsamixer have
extra hidden mixers that I have to do something to access?

It currently shows Master, PCM, Front, Surround, Center, LFE,
Line In, Mic as 0, Analog L and Swap Cen, all unmuted. The
last four have no mixer bar.

:(

Sympy:

For my laptop model, the only gotcha is to unmute surround in either alsamixer or gnome-volume-control and then reboot or restart alsa. This gets alsa working normally for me. Otherwise I don't get sound.

To get the mic working, try following the instructions in the comment above. You have to configure through both alsamixer and gnome-volume-control. Doubleclicking the speaker icon (upper right panel) will open gnome-volume-control.

Hope this helps you,

Harvey

Sound is back!

I just found out that I had to use model=dell-3stack. This not
only gave my sound back but also finally made "Digital"
appear on the mixer list.

Gonna need some time to actually test the internal mic now,
but things are definitely improving.

Hope to return here with good news for Vostro 1400 users.

Thanks, Harvey!

It worked! The internal mic finally worked! Excellent job, guys!

That said, I'm stuck at three things:

1) The background hiss is quite loud. I think I can use Skype, but I'm curious:
is this going to be fixed eventually or is more likely a hardware issue?

2) How can I use an external mic if I want to? I plugged one and fiddled with
the mixers and volume options, but had no success.

3) I can't use two headphones at the same time. The two jacks work separately
(although the second one doesn't turn off the speakers and I have to do it
manually), but the first one disables the second, so I can't use both at the
same time...

Any ideas? Should I file a separate bug report for this?

Ugh, now I just found out that after compiling alsa 1.0.16 I can't install
the latest nvidia proprietary driver (169.09).

Why? I would understand if the ubuntu package nvidia-glx-new didn't work
(and it probably doesn't), but the latest should work...

Hi,

this update breaks the hardware AC3/DTS output on my Intel Mac Mini.

Downgrading to 2.6.22-14.37 restores the digital output to normal behaviour :
sudo apt-get install linux-ubuntu-modules-2.6.22-14-generic=2.6.22-14.37

In my /etc/modprobe.d/alsa-base, I've got :
options snd-hda-intel model=macmini

Regards,
Patrick.

As for the both headphones not working at the same time, this is a fixed issue in ALSA HG.
http://mailman.alsa-project.org/pipermail/alsa-devel/2008-February/006222.html

Great news! I will test it later. :)

Too bad it's probably too late to be included in Hardy now... or is it?

Developing the last comment a bit more, what are the chances that the two headphones
fix will be available in Hardy? I'm asking this because Alsa 1.0.17 will probably be released
only after Hardy's release date.

I would think that the posts here are (other than status changes to the bug) to either help the developers with valuable info or to request help when you really need it but all your efforts like rtfm failed.

I just thought it was a valid question about the status of the bug, because a
negative answer would mean that the headphone fix won't be available in Hardy.

Sorry if I disrupted the purpose of this report.

I have a Vostro 1400 and ran through all the steps listed in this thread, and have had no luck getting the digital mic to work:

First,I placed "options snd-hda-intel model=dell-3stack" into /etc/modprobe.d/alsa-base

Then I followed the steps that Pawel proposed:

1) added gutsy-proposed to my sources.list -- done
2) ran apt-get update -- done
3) installed linux-backports-modules -- done
4) restarted the laptop to reload the kernel and modules -- done
5) ran alsamixer and set the following settings:
   Section: [All]
     Digital Input Source: Digital -- PROBLEM!

In alsamixer, there is a "Digital" slider, but I am unable to select "Digital" (or anything for that matter) for the "Digital Input Source."

After that try failed, I followed what Sympy did, building ALSA 1.0.16 from source. It built and installed no problem, and upon reboot the sound worked fine. However, the mic was in the same situation as before ( a "digital" slider but no option to set "digital" or "digital mic" as the Digital Input Source.

Sympy, I'd be very curious to hear how you got the mic to work, or if anyone else has any ideas I would be more than happy to try them.

I am running Kubuntu 7.10 and do not have gnome volume control. I was wondering if it does anything that alsamixer does not do. If so, what can I use in KDE to do the same thing that the gnome volume control does?

Copied l-b-m to gutsy-updates.

The bug task for the somerville project has been removed by an automated script. This bug has been cloned on that project and is available here: https://bugs.launchpad.net/bugs/1306173

Reviewed: https://review.opencontrail.org/41158
Committed: http://github.com/Juniper/contrail-web-controller/commit/af93eedb64cffbbc68ac839f6679f19d527149a9
Submitter: Zuul v3 CI (<email address hidden>)
Branch: master

commit af93eedb64cffbbc68ac839f6679f19d527149a9
Author: Manoj Naik <email address hidden>
Date: Wed Mar 28 15:14:59 2018 -0700

Fixing the error while add/edit port when no Security group is present.

We were wrongly adding default SG to the list even if the SG was not present
as part of fixing the bug 153963
Removed the wrong code.

Fixed UT Testcase

Change-Id: I2116d3df90244c6e478182f1b2ad9b74d074eaa3
Closes-Bug: #1757514
Related-Bug: #1539639

Reviewed: https://review.opencontrail.org/41408
Committed: http://github.com/Juniper/contrail-web-controller/commit/871ad0d9f2b47b05a0ab327ffeeac79248e09d21
Submitter: Zuul v3 CI (<email address hidden>)
Branch: R5.0

commit 871ad0d9f2b47b05a0ab327ffeeac79248e09d21
Author: Manoj Naik <email address hidden>
Date: Wed Mar 28 15:14:59 2018 -0700

Fixing the error while add/edit port when no Security group is present.

We were wrongly adding default SG to the list even if the SG was not present
as part of fixing the bug 153963
Removed the wrong code.

Fixed UT Testcase

Change-Id: I2116d3df90244c6e478182f1b2ad9b74d074eaa3
Closes-Bug: #1757514
Related-Bug: #1539639