From: "Olivier Crête" <olivier.crete@ocrete.ca>
To: Raymond Yau <superquad.vortex2@gmail.com>
Cc: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: Surround sound not working on ALC887 based motherboard
Date: Wed, 15 Jan 2014 12:50:38 -0500 [thread overview]
Message-ID: <1389808238.4661.24.camel@TesterBox> (raw)
In-Reply-To: <CAN8cciZLSbxWVSbpzNkqQ2e1_O9StWCMgYcoTsHdB6gfCkpEWw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2744 bytes --]
On Wed, 2014-01-15 at 15:35 +0800, Raymond Yau wrote:
>
>
>
> 2014/1/15 Olivier Crête <olivier.crete@ocrete.ca>
> Hi,
>
>
> > > I have a Asus P5G41T-M LX Plus motherboard which
> is ICH7 +
> > > Realtek
> > > ALC887-VD, alsa only lets me access the first 2
> channels
> > > (stereo), but
> > > not the 6 other ones. It works fine in Windows.
> > >
> > > Trying to run this after killing pulseaudio fails:
> > >
> > > $ aplay -D surround40:0 -f S16_LE -r 44100 -c
> 4 /dev/zero -v
> > > Playing raw data '/dev/zero' : Signed 16 bit
> Little Endian,
> > > Rate 44100 Hz, Channels 4
> > > aplay: set_params:1239: Channels count non
> available
> > >
> > >
> > > Output from alsa-info:
> > >
> http://www.alsa-project.org/db/?f=fe378d28f0dbb5a427b005d20866a762fd37d31a
> >
> > >
> > > post output of pactl list or pulseaudio verbose log
> >
> > http://www.ocrete.ca/surround/pactl-list.txt
> > http://www.ocrete.ca/surround/pulseaudio-vv.txt
> >
> > > you have to change channel mode from 2ch to 6ch to retask
> the input
> > > jacks as output if your motherboard only have three audio
> jacks at
> > > rear panel
> >
> > How would one do that ? Pulseaudio only offers Stereo
> profiles.
>
>
> amixer -c0 set "Channel Mode" "6ch"
>
>
> >
> > > do you mean pulseaudio cannot probe the surroun40 or surround51
> > > profile ?
> >
> > Yes, but I can't use it with aplay even without pulseaudio running.
> >
> > > Simple mixer control 'Channel Mode',0
> > > Capabilities: enum
> > > Items: '2ch' '4ch' '6ch'
> > > Item0: '2ch'
> >
> >
>
>
> > For some reason didn't get your last email, but I saw I saw it on
> the
> > archive.. Thanks for your solution, it worked! Definitely something
> > PulseAudio should expose better.
>
>
>
>
> do it really work since rear mic become active port even when it had
> been retasked as output ?
The 6 outputs work at the same time. I didn't try it as a mic as I don't
have a mic here...
> Ports:
> analog-input-front-mic: Front Microphone (priority: 8500, not available)
> analog-input-rear-mic: Rear Microphone (priority: 8200, available)
> analog-input-linein: Line In (priority: 8100, available)
> Active Port: analog-input-rear-mic
--
Olivier Crête
olivier.crete@ocrete.ca
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2014-01-15 17:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 16:53 Surround sound not working on ALC887 based motherboard Olivier Crête
2014-01-13 10:16 ` Raymond Yau
2014-01-13 20:12 ` Olivier Crête
2014-01-14 6:34 ` [alsa-devel] " Raymond Yau
[not found] ` <1389719312.4661.21.camel@TesterBox>
2014-01-15 7:35 ` Raymond Yau
2014-01-15 17:50 ` Olivier Crête [this message]
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=1389808238.4661.24.camel@TesterBox \
--to=olivier.crete@ocrete.ca \
--cc=alsa-devel@alsa-project.org \
--cc=superquad.vortex2@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox