From: Volker Armin Hemmann <volkerarmin@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ff & chromium trapped in deafness or how to configure ALSA correctly
Date: Sun, 21 Aug 2011 12:57:01 +0200 [thread overview]
Message-ID: <1417970.uqbLWRoAmB@localhost> (raw)
In-Reply-To: <4E50D481.1060503@gmail.com>
Am Sonntag 21 August 2011, 04:48:49 schrieb Dale:
> Maximilian Bräutigam wrote:
> > Hello all,
> >
> > I recently bought a Zotac Barebone ZBOX HD-AD02 AMD E-350 and installed
> > Gentoo on it, what is working more or less very well except the sound. I
> > did everything according to gentoo and gentoowiki docs, I installed (due
> > to laziness) a gentoo-sources kernel with genkernel and Sabayon linux
> > standard configuration, and I am using pulseaudio, but when I launch
> > firefox or chromium from console and play some sounds, I get lots of
> > these error messages:
> >
> > "ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave"
> >
> > I already googled for it but didn't find something helpful. The Zbox has
> > a HDMI and a standard device:
> >
> > # lspci -v | grep -i audio
> > 00:01.1 Audio device: ATI Technologies Inc Device 1314
> > 00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA) (rev
> > 40)
> >
> > # cat /proc/asound/cards
> >
> > 0 [Generic ]: HDA-Intel - HD-Audio Generic
> >
> > HD-Audio Generic at
> > 0xfeb44000 irq 40
> >
> > 1 [SB ]: HDA-Intel - HDA ATI SB
> >
> > HDA ATI SB at 0xfeb40000
> > irq 16
> >
> > You can find the complete alsa-info output at
> > http://paste.pocoo.org/show/461744/
> >
> > For me, the interesting part is this section:
> >
> > **** List of PLAYBACK Hardware Devices ****
> > card 0: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0]
> >
> > Subdevices: 1/1
> > Subdevice #0: subdevice #0
> >
> > card 1: SB [HDA ATI SB], device 0: ALC892 Analog [ALC892 Analog]
> >
> > Subdevices: 1/1
> > Subdevice #0: subdevice #0
> >
> > card 1: SB [HDA ATI SB], device 1: ALC892 Digital [ALC892 Digital]
> >
> > Subdevices: 1/1
> > Subdevice #0: subdevice #0
> >
> > Is is possible that ff and chromium are sending data to HDMI since it is
> > card 0? If you think, it would be helpful to disable card 0 or change
> > the order, please tell me how to do it?
> >
> > I highly appreciate all kinds of help!
> >
> > Kind regards,
> > der Max
>
> A silly question for a common problem. You did unmute the volume
> right? The default is to have everything muted so it is very common for
> folks to forget that little but important detail.
>
> Also, on one of my rigs, I had to unmute with both Kimix and alsamixer.
>
> Just a thought. I've done this myself.
and don't forget to mute spdif optical raw
and try without pulseaudio first.
>
> Dale
>
> :-) :-)
--
#163933
next prev parent reply other threads:[~2011-08-21 11:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-21 8:13 [gentoo-user] ff & chromium trapped in deafness or how to configure ALSA correctly Maximilian Bräutigam
2011-08-21 9:48 ` Dale
2011-08-21 10:57 ` Volker Armin Hemmann [this message]
2011-08-22 12:00 ` Maximilian Bräutigam
2011-08-21 10:24 ` Leonardo Guilherme
2011-08-21 11:41 ` pk
2011-08-22 11:56 ` Maximilian Bräutigam
2011-08-22 14:52 ` Paul Hartman
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=1417970.uqbLWRoAmB@localhost \
--to=volkerarmin@googlemail.com \
--cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox