Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Jaroslav Kysela <perex@suse.cz>
Cc: Jakob Lell <jlell@jakoblell.de>, Alsa-devel@lists.sourceforge.net
Subject: Re: snd_trident in 2.6.5 doesn't work after suspending to disk.
Date: Tue, 13 Apr 2004 12:05:57 +0200	[thread overview]
Message-ID: <s5hisg48a62.wl@alsa2.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0404091318200.3733@pnote.perex-int.cz>

At Fri, 9 Apr 2004 13:18:42 +0200 (CEST),
Jaroslav wrote:
> 
> On Fri, 9 Apr 2004, Jakob Lell wrote:
> 
> > Hi,
> > I'm using Linux 2.6.5 and the driver snd_trident. When I suspend to
> > disk (echo -n 4 > /proc/acpi/sleep) and resume again, the sound driver
> > won't work any more. It will work again after running rmmod
> > snd_trident;modprobe snd_trident. However, to do so I have to kill all
> > programs using sound (i.e. artsd, mplayer,...). Is there any way to
> > make sound work again after suspending without terminating all
> > this programs?
> 
> The trident driver does not have suspend/resume code yet.

it does, but IIRC it's untested...

BTW, ACPI suspend on 2.6.x seems problematic with the current ALSA
implementation.  i'll work on this, too.


Takashi


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

      reply	other threads:[~2004-04-13 10:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-09  9:46 snd_trident in 2.6.5 doesn't work after suspending to disk Jakob Lell
2004-04-09 11:18 ` Jaroslav Kysela
2004-04-13 10:05   ` Takashi Iwai [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=s5hisg48a62.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=Alsa-devel@lists.sourceforge.net \
    --cc=jlell@jakoblell.de \
    --cc=perex@suse.cz \
    /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