From: Chris Brennan <xaero@xaerolimit.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] sudden sound loss
Date: Thu, 10 Apr 2008 11:52:25 -0400 [thread overview]
Message-ID: <47FE37B9.6000603@xaerolimit.net> (raw)
In-Reply-To: <1207835083.7554.39.camel@ws2912.agr.st.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I would check that the device is unmusted w/ alsamixer, if alsasound
didn't properly terminate on the reboot, then alsa will default to a
muted state.
Raffaele BELARDI wrote:
| On Thu, 2008-04-10 at 08:22 -0400, Mark Haney wrote:
|
|> I'll do that, but it doesn't make a lot of sense for it to work
|> flawlessly for over a month with the same configuration then suddenly
|> stop working. At least not without logging some sort of hardware
|> problem, which I'm not seeing.
|>
|
| You are right, I had missed that the problem had shown up _before_
| kernel upgrade. Sorry, no other ideas.
|
| raf
|
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFH/je58hUIAnGfls4RAnG4AKCXwy5QK3uuali2d56XaBqE6RrP4gCdGMc7
WAP1iOyFK2d+5/LsgrIhAII=
=7O+P
-----END PGP SIGNATURE-----
--
gentoo-amd64@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-04-10 15:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-10 11:43 [gentoo-amd64] sudden sound loss Mark Haney
2008-04-10 12:16 ` Raffaele BELARDI
2008-04-10 12:22 ` Mark Haney
2008-04-10 13:44 ` Raffaele BELARDI
2008-04-10 15:52 ` Chris Brennan [this message]
2008-04-10 12:45 ` Beso
2008-04-10 14:13 ` [gentoo-amd64] " Duncan
2008-04-10 14:30 ` Mark Knecht
2008-04-10 15:02 ` Duncan
2008-04-10 16:49 ` Mark Haney
2008-04-10 17:10 ` Mark Knecht
2008-04-10 17:20 ` Mark Haney
2008-04-10 17:43 ` Mark Knecht
2008-04-10 19:33 ` Duncan
2008-04-10 19:45 ` Mark Knecht
2008-04-11 8:14 ` Beso
2008-04-12 2:29 ` Duncan
2008-04-11 11:16 ` Mark Haney
2008-04-11 11:33 ` Raffaele BELARDI
2008-04-11 13:24 ` Mark Knecht
2008-04-11 14:33 ` Raffaele BELARDI
2008-04-11 15:32 ` Mark Knecht
2008-04-12 16:32 ` Duncan
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=47FE37B9.6000603@xaerolimit.net \
--to=xaero@xaerolimit.net \
--cc=gentoo-amd64@lists.gentoo.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