From: Jeremy Abbott <jkbullfrog@comcast.net>
To: linux-newbie@vger.kernel.org
Subject: Re: a sound problem solution?
Date: Tue, 11 Jan 2005 12:39:20 +0000 [thread overview]
Message-ID: <41E3C8F8.80607@comcast.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0501102258510.7477@localhost.localdomain>
James Miller wrote:
>...So, all would be fine if I could
>just keep my computer from suddenly ceasing to output sound for unknown
>reasons. I'm not really interested in troubleshooting the sound server so
>much as I am in a way of possibly resetting it short of rebooting the
>machine. Is there a way to do this, i.e., to shutdown, then restart the
>sound server to see if I can get the sound back without a reboot?
>
>A few details, in case it's helpful. This is Ubuntu, a Debian variant.
>Sound hardware uses the snd_via82xx module--auto-detected and set up by
>the OS on installation. Things I've noted that cause sound output to
>cease: plugging/unplugging the speakers while the computer is running;
>plugging a usb device into a hub mounted on top of the computer case; and
>today I can't say that anything in particular caused this. The symptom is
>an end to all sounds: no music will play, nor will system sounds. Only the
>PC speaker remains operational. Sound comes back after a reboot. I'm
>hoping there's a way to stop, then restart the sound server and that this
>might resolve the problem when it occurs. I think this distro must use the
>ALSA sound server, if I've understood correctly these technical details.
>
>Any advice? Go back to using a stereo-type device for sound and just use
>my computer for computing, perhaps?
>
On my distro (Gentoo), when I wish to restart a daemon, I type:
/etc/init.d/<daemonname> restart
or
/etc/init.d/<daemonname> stop
/etc/init.d/<daemonname> start
NOTICE: Do not include the < or the> on either side of the name.
I've not used any Debian varients, so I hope this helps.
Jeremy Abbott
jkbullfrog@comcast.net
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2005-01-11 12:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-11 5:33 a sound problem solution? James Miller
2005-01-11 12:39 ` Jeremy Abbott [this message]
2005-01-11 14:31 ` Ray Olszewski
2005-01-11 21:32 ` Jim Nelson
2005-01-12 20:00 ` Can't locate module memory_cs chuck gelm
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=41E3C8F8.80607@comcast.net \
--to=jkbullfrog@comcast.net \
--cc=linux-newbie@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.