From: Wolfgang Pfeiffer <roto@gmx.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [Done] Re: snd-aoa: Sound gone after snd-aoa updates, on PB5,8
Date: Tue, 30 May 2006 00:17:30 +0200 [thread overview]
Message-ID: <20060529221730.GA3138@localhost> (raw)
In-Reply-To: <1148869725.3918.12.camel@localhost.localdomain>
Hi All
Sorry for responding a bit late: I had to leave the house today ...
On Mon, May 29, 2006 at 12:28:45PM +1000, Benjamin Herrenschmidt wrote:
> On Mon, 2006-05-29 at 04:17 +0200, Wolfgang Pfeiffer wrote:
> > On Mon, May 29, 2006 at 04:00:27AM +0200, Wolfgang Pfeiffer wrote:
> > >
> > > Hi
> > >
> > > After some updates from http://johannes.sipsolutions.net/snd-aoa.git/
> > > in the last few hours/minutes sound's gone here. Without changing
> > > sound settings intentionally here.
> > >
> > >
> >
> > On Debian/unstable:
> > After downgrading libasound2 from 1.0.11-6 to 1.0.11-3 I have sound
> > again: 1.0.11-6 was, IINM, installed a few hours ago, which
> > - as it seems - broke sound here.
>
> Have you tested that it wasn't just the renaming/re-ordering of some
> controls ? Alsa is pretty bad with that, you may just have to go back to
> alsamixer and reset some controls after updating the driver.
That's what I tried after reading your mail:
$ apt-cache policy libasound2
libasound2:
Installed: 1.0.11-6
Candidate: 1.0.11-6
The problem is: with libasound2 1.0.11-6 I cannot even *start*
alsamixer:
------------------------
$ alsamixer
ALSA lib control.c:816:(snd_ctl_open_noupdate) Invalid CTL default
alsamixer: function snd_ctl_open failed for default: No such file or directory
-------------------------
----------------------------
$ alsamixer -c 0
ALSA lib control.c:816:(snd_ctl_open_noupdate) Invalid CTL hw:0
alsamixer: function snd_ctl_open failed for hw:0: No such file or directory
---------------------------
amixer:
------------------------
$ amixer -dD controls
ALSA lib control.c:816:(snd_ctl_open_noupdate) Invalid CTL controls
amixer: Mixer attach controls error: No such file or directory
---------------------------
But the last 2 examples may hint amixer at least sees some sound card:
---------------
$ amixer -c 1 controls
Invalid card number.
Usage: amixer <options> [command]
Available options:
[ ... ]
---------------------
-------------------
$ amixer -c 0 controls
ALSA lib control.c:816:(snd_ctl_open_noupdate) Invalid CTL hw:0
amixer: Control hw:0 open error: No such file or directory
-----------------------
Suggestions? Did I miss something?
Thanks in anticipation
Best Regards
Wolfgang
--
Wolfgang Pfeiffer: /ICQ: 286585973/ + + + /AIM: crashinglinux/
http://profiles.yahoo.com/wolfgangpfeiffer
Key ID: E3037113
http://keyserver.mine.nu/pks/lookup?search=0xE3037113&fingerprint=on
next prev parent reply other threads:[~2006-05-29 22:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-29 2:00 snd-aoa: Sound gone after snd-aoa updates, on PB5,8 Wolfgang Pfeiffer
2006-05-29 2:17 ` [Done] " Wolfgang Pfeiffer
2006-05-29 2:28 ` Benjamin Herrenschmidt
2006-05-29 22:17 ` Wolfgang Pfeiffer [this message]
2006-05-30 7:44 ` Michel Dänzer
2006-05-30 11:23 ` [Done #2] Re: snd-aoa: Sound gone after snd-aoa updates, on PB5, 8 Wolfgang Pfeiffer
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=20060529221730.GA3138@localhost \
--to=roto@gmx.net \
--cc=benh@kernel.crashing.org \
--cc=johannes@sipsolutions.net \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).