[Solved] Can My Audio Driver Be Manually restarted?

[azziam]

I use a soundcard based on the Envy24 chipset and I use Envy24 Control from the repos to control I/O routing, Volumes, etc.  The card and driver as shown in Hardware>Manage your hardware> in the PCLOS CC is:

Code: [Select]

Identification
Vendor: ‎VIA Technologies Inc.

Description: ‎ICE1712 [Envy24] PCI Multi-Channel I/O Controller

Media class: ‎Multimedia audio controller

Connection
Bus: ‎PCI

PCI domain: ‎0

Bus PCI #: ‎4

PCI device #: ‎8

PCI function #: ‎0

PCI revision: ‎0x02

Vendor ID: ‎0x1412

Device ID: ‎0x1712

Driver
Module: ‎snd_ice1712

Alternative drivers: ‎unknown

Recently, my desktop machine has been "sleepable" with no problem except it comes back up with no sound.  Regardless of that, sometimes sound just quits working.  Rebooting always gets it back but I need to know if there is a simpler way to get the audio back on.  I tried as root entering "open snd_ice1712" and that didn't get me any sound.  Any ideas?  

[AndrzejL]

Hi Azziam.

Try this:

Code: [Select]

kdesu -c "service alsa force-restart"
in the konsole or from the Alt-f2 level and give root password when asked.

Regards.

Andy

[azziam]

Hi Azziam.

Try this:

Code: [Select]

kdesu -c "service alsa force-restart"
in the konsole or from the Alt-f2 level and give root password when asked.

Regards.

Andy

Thanks, I put it to sleep (clear out with nothing spinning) and brought it back up.  BTW, up till recent updates my CricKet wireless modem would need to be unplugged and plugged back in before it would be found again but now it can just be restarted with a click.  That's good.  So...

I'm using PCLOS-GNOME so I tried like this:
[pete@localhost ~]$ su -c "service alsa force-restart"
Password:
bash: service: command not found
[pete@localhost ~]$ su
Password:
[root@localhost pete]# service alsa force-restart
bash: service: command not found
[root@localhost pete]# alsa force-restart
bash: alsa: command not found
[root@localhost pete]# force-restart alsa
bash: force-restart: command not found
[root@localhost pete]#

Sorry I don't know CLI commands very well so I'm ready for the next suggestion.

[azziam]

Now it's working.  I'd left out a hyphen after su.  So the following worked just as you spelled it out minus the kde.  I also left out the "c" after the hyphen.  What does it do?

I used:

Code: [Select]

[pete@localhost ~]$ su -
Password:
[root@localhost ~]# service alsa force-restart
Doing alsactl to store mixer settings...                        [  OK  ]
but first, terminating (SIGTERM) pid   7016  7016...            [  OK  ]
WARNING: Module snd_mixer_oss already in kernel.
 snd_ice1712.                                                   [  OK  ]
Doing alsactl to restore mixer settings:                        [  OK  ]
[root@localhost ~]#

Thanks a bunch!  Putting this machine to sleep rather than shutting everything down will be a major time-saver for me and I have to have audio.

[T6]

su is to run a command as superuser, root mode, you just need to write su alone not su - or anything else

the main reason i never use hibernate or suspend to ram is that, some hardware refuses to wake up sometimes, on windows and in linux, good to know that in linux there is a solution

[azziam]

I also left out the "c" after the hyphen.  What does it do?

Never mind my dumb question.  I'm not quite helpless so I tried su --help.  Thanks again, Andy!

[azziam]

su is to run a command as superuser, root mode, you just need to write su alone not su - or anything else

the main reason i never use hibernate or suspend to ram is that, some hardware refuses to wake up sometimes, on windows and in linux, good to know that in linux there is a solution

T6, it might just be the Gnome version that needs the su - in some cases.  I should find out more about why that is.  If you look at the lines I typed in the console you'll see the difference it made.  Without the hyphen, the commands weren't recognized and the prompt didn't look the same.  It's been probably just in the last year we got informed about the hyphen in the PCLOS-Gnome forums so something had changed.  Never needed it before that.

[T6]

yes, i have read about differences in console between versions, i personally only use kde4 and konsole using bash

in general it should only be su but as you say, you found differences

[Old-Polack]

su is to run a command as superuser, root mode, you just need to write su alone not su - or anything else

the main reason i never use hibernate or suspend to ram is that, some hardware refuses to wake up sometimes, on windows and in linux, good to know that in linux there is a solution

Sorry but that's wrong. With su you can see by the prompt he remained in his normal user's home directory, so uses the normal user's $PATH, and the command service alsa force-restart could not be found. Using su - the prompt shows he is now in root's home ~ and the command can then be found because now the root $PATH is being used.

[root@fatman ~]# which service
/sbin/service

[azziam]

su is to run a command as superuser, root mode, you just need to write su alone not su - or anything else

the main reason i never use hibernate or suspend to ram is that, some hardware refuses to wake up sometimes, on windows and in linux, good to know that in linux there is a solution

Sorry but that's wrong. With su you can see by the prompt he remained in his normal user's home directory, so uses the normal user's $PATH, and the command service alsa force-restart could not be found. Using su - the prompt shows he is now in root's home ~ and the command can then be found because now the root $PATH is being used.

[root@fatman ~]# which service
/sbin/service

Actually, Old Polack, using just the su w/o hyphen it put me into some limbo area with the prompt shown as [root@localhost pete]# instead of [root@localhost ~]# as su - will produce.  In that odd state with my name in it brought by su alone, some simple commands work (gimp does) and some don't (gedit doesn't).  Rather than be confused I'll try to remember the hyphen every time I need root privilege  

I'm just happy to now have a machine I can put totally to sleep and save all states.  Even the terminal has all the stuff I typed in before sleeping/waking up several times now.  Pretty cool.  I might be afraid of the next big batch of updates.

[Old-Polack]

su is to run a command as superuser, root mode, you just need to write su alone not su - or anything else

the main reason i never use hibernate or suspend to ram is that, some hardware refuses to wake up sometimes, on windows and in linux, good to know that in linux there is a solution

Sorry but that's wrong. With su you can see by the prompt he remained in his normal user's home directory, so uses the normal user's $PATH, and the command service alsa force-restart could not be found. Using su - the prompt shows he is now in root's home ~ and the command can then be found because now the root $PATH is being used.

[root@fatman ~]# which service
/sbin/service

Actually, Old Polack, using just the su w/o hyphen it put me into some limbo area with the prompt shown as [root@localhost pete]# instead of [root@localhost ~]# as su - will produce.  In that odd state with my name in it brought by su alone, some simple commands work (gimp does) and some don't (gedit doesn't).  Rather than be confused I'll try to remember the hyphen every time I need root privilege  

I'm just happy to now have a machine I can put totally to sleep and save all states.  Even the terminal has all the stuff I typed in before sleeping/waking up several times now.  Pretty cool.  I might be afraid of the next big batch of updates.

That is not limbo, that is the difference between su and su -; which $PATH is used by each. Read the explanation again.

In a terminal as your normal user, enter   $PATH       <Enter>

You will see where the system will search, to find any command entered by your normal user.

Try again as su and it should be the same. Try once more as su - and it should be different, including those directories reserved for root only applications.