All of lore.kernel.org
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Regarding Audio Drivers
Date: Sat, 12 May 2018 20:58:32 +0200	[thread overview]
Message-ID: <20180512185832.GA27006@kroah.com> (raw)
In-Reply-To: <CAEy6Yz7iE067R0s-KP8Eh11T2u1y9eaPC1QMJdisGEZQhMvLpw@mail.gmail.com>

On Sat, May 12, 2018 at 11:14:50PM +0530, Divanshu Singh wrote:
> Respected Reader
> 
> I am a long time Linux user. I am a full-time web developer but I have some
> knowledge of C, C++ and bit of x86 assembly.
> 
> I have 4 Linux system at my home - a MacBook Air, 2 HP and 1 Dell and
> recently I found that none of them is able to detect or work with an
> external microphone. I have tried every possible configuration in ALSA that
> made sense but nothing worked. I also tried re-installing drivers for my
> sound cards. Searching the Internet, I realized that I am not alone there
> are thousands of Linux users who face the same problem. I found this long
> answer explaining why this problem exists with Linux system.
> 
> https://unix.stackexchange.com/questions/381071/headphones-with-combo-jack-force-internal-mic-for-input-and-headphones-for-outp
> 

All this means is that for your specific laptop version, you need a
quirk to be able to properly control the microphone.  It's not a big
deal, just determining how to do that is a bit tricky.

I suggest emailing the Linux kernel sound developers at
alsa-dev at alsa-project.org and provide the exact kernel version you are
using (first try the latest release to be sure it's not already fixed),
and any hardware information you can provide as well.

The developers there will probably ask you for more specific things, and
you all can work from there.

Best of luck!

greg k-h

  reply	other threads:[~2018-05-12 18:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-12 17:44 Regarding Audio Drivers Divanshu Singh
2018-05-12 18:58 ` Greg KH [this message]
2018-05-12 19:03   ` Divanshu Singh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180512185832.GA27006@kroah.com \
    --to=greg@kroah.com \
    --cc=kernelnewbies@lists.kernelnewbies.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.