From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: linux-sound@vger.kernel.org
Subject: Re: [RFT/PATCH] Re: Sound problem after suspend. Kernel
Date: Tue, 28 Mar 2000 16:55:00 +0000 [thread overview]
Message-ID: <marc-linux-sound-95426323324069@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-95424773409649@msgid-missing>
Aki M Laukkanen wrote:
>
> On Mon, 27 Mar 2000, HvR wrote:
> > the gpm killing is really necessary without this the
> > sound module will not unload!!!
>
> Really? That seems odd.
>
> > > With kernel version 2.3.99-pre3 sound words until I
> > > suspend my Toshiba
> > > Satellite Pro 445CDX, but after resuming it will
> > > produce no sound.
> > > This problem came in with the sound clean-ups after
> > > version 2.3.49.
>
> I have a Toshiba Satellite 220CS laptop which has a OPL3-SA1 sound
> chip. However I've never gotten the opl3sa1 driver to recognise it as such
> so I've used the bare ad1848 (MS Sound System) driver instead. Unlike in
> the case above I've never had working sound after suspend.
>
> This is an experimental patch which fixes the suspend problem for me and
> I'd appreciate if people would test it.
>
> ------------------------------------------------------------------------
> Name: ad1848-suspend.patch
> ad1848-suspend.patch Type: Plain Text (TEXT/PLAIN)
> Encoding: BASE64
Nice, looks good to me.
A lot of drivers need to move in this direction... :) Thanks for
posting the patch.
Jeff
--
Jeff Garzik | Tact is the ability to tell a man
Building 1024 | he has an open mind when he has a
MandrakeSoft, Inc. | hole in his head. (-random fortune)
prev parent reply other threads:[~2000-03-28 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-28 12:45 [RFT/PATCH] Re: Sound problem after suspend. Kernel version Aki M Laukkanen
2000-03-28 16:55 ` Jeff Garzik [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=marc-linux-sound-95426323324069@msgid-missing \
--to=jgarzik@mandrakesoft.com \
--cc=linux-sound@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.