So you are using Pulse Audio - right?

When it breaks, try to seek some answers this way: 
dmesg
sudo systemctl status sound.target

Also try to fiddle with controls using native pulse audio mixer:
pavucontrol

Sometimes, pavucontrol is the only way I can get the sound/mic where I
need to.

Best luck, Tomas

On Mon, 2019-04-08 at 19:39 -0500, Chuck Hast wrote:
> Here is the results after the reboot.
> kp4djt@kp4djt64:~$ systemctl status alsa-state.service
> ● alsa-state.service - Manage Sound Card State (restore and store)
>    Loaded: loaded (/lib/systemd/system/alsa-state.service; static;
> vendor
> preset
>    Active: inactive (dead)
> Condition: start condition failed at Mon 2019-04-08 19:36:33 CDT;
> 1min 38s
> ago
>            └─ ConditionPathExists=/etc/alsa/state-daemon.conf was not
> met
>      Docs: man:alsactl(1)
> kp4djt@kp4djt64:~$ systemctl status alsa-restore.service
> ● alsa-restore.service - Save/Restore Sound Card State
>    Loaded: loaded (/lib/systemd/system/alsa-restore.service; static;
> vendor
> pres
>    Active: active (exited) since Mon 2019-04-08 19:36:33 CDT; 2min 8s
> ago
>      Docs: man:alsactl(1)
>   Process: 943 ExecStart=/usr/sbin/alsactl -E HOME=/run/alsa restore
> (code=exite
>   Process: 910 ExecStartPre=/bin/mkdir -p /run/alsa (code=exited,
> status=0/SUCCE
>  Main PID: 943 (code=exited, status=0/SUCCESS)
> 
> abr 08 19:36:33 kp4djt64 systemd[1]: Starting Save/Restore Sound Card
> State...
> abr 08 19:36:33 kp4djt64 systemd[1]: Started Save/Restore Sound Card
> State.
> kp4djt@kp4djt64:~$
> 
> And as usual the speakers are working just fine. But at some point
> they
> will fail during
> the night.
> 
> 
> 
> On Mon, Apr 8, 2019 at 7:37 PM Chuck Hast <wch...@gmail.com> wrote:
> 
> > Ken,
> > This is what I got from the first command:
> > ● alsa-state.service - Manage Sound Card State (restore and store)
> >    Loaded: loaded (/lib/systemd/system/alsa-state.service; static;
> > vendor
> > preset: enabled)
> >    Active: inactive (dead)
> > Condition: start condition failed at Wed 2019-04-03 22:35:45 CDT; 4
> > days
> > ago
> >            └─ ConditionPathExists=/etc/alsa/state-daemon.conf was
> > not met
> >      Docs: man:alsactl(1)
> > 
> > 
> > And the second command gave me this:
> > kp4djt@kp4djt64:~$ systemctl status alsa-restore.service
> > ● alsa-restore.service - Save/Restore Sound Card State
> >    Loaded: loaded (/lib/systemd/system/alsa-restore.service;
> > static;
> > vendor preset: enabled)
> >    Active: active (exited) since Wed 2019-04-03 22:35:45 CDT; 4
> > days ago
> >      Docs: man:alsactl(1)
> >   Process: 940 ExecStart=/usr/sbin/alsactl -E HOME=/run/alsa
> > restore
> > (code=exited, status=0/SUCCESS)
> >   Process: 936 ExecStartPre=/bin/mkdir -p /run/alsa (code=exited,
> > status=0/SUCCESS)
> >  Main PID: 940 (code=exited, status=0/SUCCESS)
> > 
> > abr 03 22:35:45 kp4djt64 systemd[1]: Starting Save/Restore Sound
> > Card
> > State...
> > abr 03 22:35:45 kp4djt64 systemd[1]: Started Save/Restore Sound
> > Card State.
> > kp4djt@kp4djt64:~$
> > 
> > But  I still have no audio... Something is broke, I will reboot it
> > and see
> > what I get.
> > 
> > 
> > On Mon, Apr 8, 2019 at 10:07 AM Ken Stephens <kennethgstephens@gmai
> > l.com>
> > wrote:
> > 
> > > Chuck,
> > > 
> > > You could be running alsa.  Check status by: systemctl status
> > > alsa-state.service<cr>
> > > 
> > > Another check:  systemctl status alsa-restore.service<cr>
> > > 
> > > Ken
> > > 
> > > On Sun, Apr 7, 2019 at 10:10 PM Chuck Hast <wch...@gmail.com>
> > > wrote:
> > > 
> > > > Folks, I thought I had a bad component on the mobo, but testing
> > > > seems
> > > 
> > > to be
> > > > sending me
> > > > in the direction of some software issue. I am running Mate
> > > > 18.04 I check
> > > > for updates auto-
> > > > magically, though I do not let the machine do auto-updates so I
> > > > can make
> > > > sure all is good.
> > > > 
> > > > At some point the machine started loosing the audio, A reboot
> > > > would
> > > 
> > > bring
> > > > it back for the
> > > > rest of the day but sometime during the night it would go away
> > > > again. I
> > > > thought  I had a bad
> > > > component but the other day I ran Ubuntu 18.04 off of a stick
> > > > on this
> > > > machine and the audio
> > > > was just fine. I let it go over night, still good audio. so it
> > > > looks
> > > 
> > > like
> > > > something is going on
> > > > software wise but I am not sure where to go after it, one thing
> > > > I
> > > 
> > > noticed
> > > > is there is poping
> > > > and crackling in the audio output, like something is trying to
> > > > do
> > > 
> > > something
> > > > but no joy.
> > > > 
> > > > If I reboot the machine I get the audio back until the next
> > > > day, so
> > > > something is happening
> > > > with the audio app.
> > > > 
> > > > I am trying to figure out how to troubleshoot this one.  Any
> > > > ideas?
> > > > 
> > > > 
> > > > --
> > > > 
> > > > Chuck Hast  -- KP4DJT --
> > > > I can do all things through Christ which strengtheneth me.
> > > > Ph 4:13 KJV
> > > > Todo lo puedo en Cristo que me fortalece.
> > > > Fil 4:13 RVR1960
> > > > _______________________________________________
> > > > PLUG mailing list
> > > > PLUG@pdxlinux.org
> > > > http://lists.pdxlinux.org/mailman/listinfo/plug
> > > > 
> > > 
> > > _______________________________________________
> > > PLUG mailing list
> > > PLUG@pdxlinux.org
> > > http://lists.pdxlinux.org/mailman/listinfo/plug
> > > 
> > 
> > 
> > --
> > 
> > Chuck Hast  -- KP4DJT --
> > I can do all things through Christ which strengtheneth me.
> > Ph 4:13 KJV
> > Todo lo puedo en Cristo que me fortalece.
> > Fil 4:13 RVR1960
> > 
> > 
> 
> 
_______________________________________________
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

Reply via email to