Check pavucontrol (pulseaudio volume
control, install if necessary), I use usb devices that
occasionally glitch and get lost. If something is bound to it,
like a use a chrome-based voip service that if active, locks the
device, and a hard-disconnect means a reboot to see the usb
headset again. That's a major party foul, but such is life, and
you might see something similar if using usb devices I've found.
If local on-board sound, I'd say it's just flaky, or you broke
pulse somehow. I end up switching inputs and outputs a lot for
voip, music, and various input/outputs amount local sound,
headsets, other. Pulse does a good job, usually more kernel than
anything when devices arise, thus dmesg is you friend.
As stated, when sound devices get deadlocked with the kernel, a
reboot I've found is needed to fix as easiest resolution. You can
also likely rmmod the devices, and insmod them back, maybe, too
that occasionally works for me, but either way the kernel module
to hardware device interrupt map is broken at some level.
Caveat emptor with pavucontrol - I get it going batcrap crazy and
consuming 10gb of ram occasionally, wondering why I'm ever hitting
swap. Necessary evil I find, I just try not to leave running.
-mb
On 12/22/2015 11:00 PM, Michael Havens wrote:
Well, I thought I was going to turn my computer off
for th night but 45 minutes I turned it back on and everything
was fine.
now on to learning xsane!
On Wed, Dec 23, 2015 at 12:07 AM,
Michael Butash <
michael@butash.net>
wrote:
Do you even see anything with lspci or lsusb of your
soundcard? What kind of sound is it?
Updating kernel breaks things I've found (newish intel
z99 mobo did in earlier kernels), but unless hardware
changed, shouldn't unless something just fried or you
broke it to udev.
Look at your dmesg on boot, and run "alsamixer", if
neither see your sound, it fried, isn't getting probed
by udev, or some odd combination of that and bug. If
also sees it, pulseaudio should too. Everything (apps)
talks to pulse now as a default sink to userland, under
it is alsa, then your sound.
If alsa sees your sound, check pulseaudo. Install
pavucontrol and examine your devices as looking as they
should. Make sure your application in there is steering
to the right output sink.
It's like hooking up a stereo receiver or anything else,
output to input, output to input...
-mb
On 12/22/2015 08:46 PM, Michael Havens wrote:
how should I proceed?
On Tue, Dec 22, 2015 at
10:45 PM, Michael Havens <
bmike1@gmail.com>
wrote:
well... I decided to see if it
would get to the point where it asks if you
want to continue.... but ut didn't ask.....
it just reinstalled alsa. ALAS.... it did
not help any..... (how'd you like that play
on words?)
On Tue, Dec 22,
2015 at 10:37 PM, Michael Havens <
bmike1@gmail.com>
wrote:
sudo apt-get install
--reinstall alsa
????????????????????
--
:-)~MIKE~(-:
--
:-)~MIKE~(-:
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss
---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss
--
:-)~MIKE~(-:
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss 
(text/html)