linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Pfeiffer <roto@gmx.net>
To: "Michel Dänzer" <michel@daenzer.net>
Cc: linuxppc-dev@ozlabs.org, Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [Done #2] Re: snd-aoa: Sound gone after snd-aoa updates, on PB5, 8
Date: Tue, 30 May 2006 13:23:14 +0200	[thread overview]
Message-ID: <20060530112314.GA3250@localhost> (raw)
In-Reply-To: <1148975072.27856.294.camel@thor.lorrainebruecke.local>

On Tue, May 30, 2006 at 09:44:32AM +0200, Michel Dänzer wrote:
> On Tue, 2006-05-30 at 00:17 +0200, Wolfgang Pfeiffer wrote:
> > 
> > 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
> 
> See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=369478 and friends.

Thanks. 

And the bug already seems to be fixed with a new version: I just
installed it (libasound2 1.0.11-7) and at least alsamixer and amixer
started without error. Plus: Restarting the KDE sound system after
installing this new version also worked liked a charm.

Thanks to everyone involved :)

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

      reply	other threads:[~2006-05-30 11:23 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
2006-05-30  7:44       ` Michel Dänzer
2006-05-30 11:23         ` Wolfgang Pfeiffer [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=20060530112314.GA3250@localhost \
    --to=roto@gmx.net \
    --cc=johannes@sipsolutions.net \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=michel@daenzer.net \
    /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).