Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: noreply@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000337]: "alsactl restore" always fails
Date: Wed, 16 Jun 2004 22:04:29 +0200	[thread overview]
Message-ID: <c38df2522fce57a0ba68fa8008a4ebfb@bugtrack.alsa-project.org> (raw)


The following bug has been SUBMITTED.
======================================================================
https://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=0000337
======================================================================
Reported By:                kuulasma
Assigned To:                tiwai
======================================================================
Project:                    ALSA - driver
Bug ID:                     337
Category:                   PCI - nm256
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
Distribution:               Debian sarge
Kernel Version:             Linux 2.6.6-1-686
======================================================================
Date Submitted:             06-16-2004 22:04 CEST
Last Modified:              06-16-2004 22:04 CEST
======================================================================
Summary:                    "alsactl restore" always fails
Description: 
Dell Latitude CPt with an NM256ZX fails always to restore previously saved
state. Command "alsactl store" succesfully stores current state but
"alsactl restore" always fails to restore previous state. The OSS driver
works fine.

Example:
----------------------------------------------------------
# alsactl restore
alsactl: set_control:966: Cannot write control '2:0:0:CD Playback
Switch:0' : Invalid argument
----------------------------------------------------------
======================================================================

Bug History
Date Modified  Username       Field                    Change              
======================================================================
06-16-04 22:04 kuulasma       New Bug                                      
06-16-04 22:04 kuulasma       Distribution              => Debian sarge    
06-16-04 22:04 kuulasma       Kernel Version            => Linux 2.6.6-1-686
======================================================================




-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND

             reply	other threads:[~2004-06-16 20:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-16 20:04 noreply [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-06-22 16:51 [ALSA - driver 0000337]: "alsactl restore" always fails noreply
2004-06-22 19:35 noreply
2004-06-30 14:29 noreply
2004-07-02  5:12 noreply
2004-07-16 10:02 noreply
2004-09-24 11:40 bugtrack

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=c38df2522fce57a0ba68fa8008a4ebfb@bugtrack.alsa-project.org \
    --to=noreply@alsa-project.org \
    --cc=alsa-devel@alsa-project.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