Dear All
How can one restart alsa?
I have already tried:
# /sbin/service alsasound restart alsasound: unrecognized service #
Thanks in advance,
Paul
On Saturday 05 August 2006 17:01, Paul Smith wrote:
Dear All
How can one restart alsa?
I have already tried:
# /sbin/service alsasound restart alsasound: unrecognized service #
Thanks in advance,
Paul
Hi Paul. I've always used the following on FC, su'ed to root.
/etc/rc.d/init.d/alsasound stop /etc/rc.d/init.d/alsasound start /etc/rc.d/init.d/alsasound restart
Nigel.
On 8/5/06, Nigel Henry cave.dnb@tiscali.fr wrote:
How can one restart alsa?
I have already tried:
# /sbin/service alsasound restart alsasound: unrecognized service #
Hi Paul. I've always used the following on FC, su'ed to root.
/etc/rc.d/init.d/alsasound stop /etc/rc.d/init.d/alsasound start /etc/rc.d/init.d/alsasound restart
Thanks, Nigel, but I get
# /etc/rc.d/init.d/alsasound restart bash: /etc/rc.d/init.d/alsasound: No such file or directory #
Paul
On Saturday 05 August 2006 17:46, Paul Smith wrote:
On 8/5/06, Nigel Henry cave.dnb@tiscali.fr wrote:
How can one restart alsa?
I have already tried:
# /sbin/service alsasound restart alsasound: unrecognized service #
Hi Paul. I've always used the following on FC, su'ed to root.
/etc/rc.d/init.d/alsasound stop /etc/rc.d/init.d/alsasound start /etc/rc.d/init.d/alsasound restart
Thanks, Nigel, but I get
# /etc/rc.d/init.d/alsasound restart bash: /etc/rc.d/init.d/alsasound: No such file or directory #
Paul
That's odd. I've just been into FC5, presuming that's what your using, to check it out, and alsasound is there. I am using a kernel from planetccrma, along with Alsa stuff, and sound apps from them, but Alsa, when I installed FC5 worked just fine OOTB with my Ensoniq card.
What machine is this on? And are you using a roll your own kernel?
Have you had Alsa working on it?
Will you post the output of /sbin/lsmod.
Also, run. cat /proc/asound/cards and cat /proc/asound/version
Do you see any output with those?
Also, have a look in /etc/rc.d/init.d , and see if there is anything Alsa related.
Over to you.
Nigel.
At 6:23 PM +0200 8/5/06, Nigel Henry wrote:
On Saturday 05 August 2006 17:46, Paul Smith wrote:
On 8/5/06, Nigel Henry cave.dnb@tiscali.fr wrote:
How can one restart alsa?
I have already tried:
# /sbin/service alsasound restart alsasound: unrecognized service #
Hi Paul. I've always used the following on FC, su'ed to root.
/etc/rc.d/init.d/alsasound stop /etc/rc.d/init.d/alsasound start /etc/rc.d/init.d/alsasound restart
Thanks, Nigel, but I get
# /etc/rc.d/init.d/alsasound restart bash: /etc/rc.d/init.d/alsasound: No such file or directory #
Paul
That's odd. I've just been into FC5, presuming that's what your using, to check it out, and alsasound is there. I am using a kernel from planetccrma, along with Alsa stuff, and sound apps from them, but Alsa, when I installed FC5 worked just fine OOTB with my Ensoniq card.
FWIW, I'm also using FC5, but "locate alsasound" finds no files and "yum provides alsasound" with the usual repos finds no matches. There are no modules with alsa in the name. Yet sound works here, VIA chipset, AC'97 audio. ____________________________________________________________________ TonyN.:' mailto:tonynelson@georgeanelson.com ' http://www.georgeanelson.com/
On Saturday 05 August 2006 18:55, Tony Nelson wrote:
At 6:23 PM +0200 8/5/06, Nigel Henry wrote:
On Saturday 05 August 2006 17:46, Paul Smith wrote:
On 8/5/06, Nigel Henry cave.dnb@tiscali.fr wrote:
How can one restart alsa?
I have already tried:
# /sbin/service alsasound restart alsasound: unrecognized service #
Hi Paul. I've always used the following on FC, su'ed to root.
/etc/rc.d/init.d/alsasound stop /etc/rc.d/init.d/alsasound start /etc/rc.d/init.d/alsasound restart
Thanks, Nigel, but I get
# /etc/rc.d/init.d/alsasound restart bash: /etc/rc.d/init.d/alsasound: No such file or directory #
Paul
That's odd. I've just been into FC5, presuming that's what your using, to check it out, and alsasound is there. I am using a kernel from planetccrma, along with Alsa stuff, and sound apps from them, but Alsa, when I installed FC5 worked just fine OOTB with my Ensoniq card.
FWIW, I'm also using FC5, but "locate alsasound" finds no files and "yum provides alsasound" with the usual repos finds no matches. There are no modules with alsa in the name. Yet sound works here, VIA chipset, AC'97 audio. ____________________________________________________________________ TonyN.:' mailto:tonynelson@georgeanelson.com ' http://www.georgeanelson.com/
Hi Tony. Thats interesting. I've just booted up the other FC5 which doesn't have the planetccrma kernel, and the associated kernel-modules-alsa package on it, and your quite right. No /etc/rc.d/init.d/alsasound. There is an /etc/alsa directory with and alsa.conf file, a cards directory, and a PCM directory, with another few bits, and cat /proc/asound/cards, cat /proc/asound/version, and /sbin/lsmod show that Alsa is installed ok.
It must be that installing the planetccrma kernel, and associated kernel-modules-alsa package, that has created the alsasound file.
So the question remains. How, if you are using Fedora kernels, do you start and stop Alsa?
I must admit that I only had a quick look in the non planetccrma FC5, and perhaps there is a script somewhere that allows you to stop and start Alsa.
Nigel.
At 8:10 PM +0200 8/5/06, Nigel Henry wrote:
On Saturday 05 August 2006 18:55, Tony Nelson wrote:
At 6:23 PM +0200 8/5/06, Nigel Henry wrote:
On Saturday 05 August 2006 17:46, Paul Smith wrote:
On 8/5/06, Nigel Henry cave.dnb@tiscali.fr wrote:
How can one restart alsa?
I have already tried:
# /sbin/service alsasound restart alsasound: unrecognized service #
Hi Paul. I've always used the following on FC, su'ed to root.
/etc/rc.d/init.d/alsasound stop /etc/rc.d/init.d/alsasound start /etc/rc.d/init.d/alsasound restart
Thanks, Nigel, but I get
# /etc/rc.d/init.d/alsasound restart bash: /etc/rc.d/init.d/alsasound: No such file or directory #
Paul
That's odd. I've just been into FC5, presuming that's what your using, to check it out, and alsasound is there. I am using a kernel from planetccrma, along with Alsa stuff, and sound apps from them, but Alsa, when I installed FC5 worked just fine OOTB with my Ensoniq card.
FWIW, I'm also using FC5, but "locate alsasound" finds no files and "yum provides alsasound" with the usual repos finds no matches. There are no modules with alsa in the name. Yet sound works here, VIA chipset, AC'97 audio.
Hi Tony. Thats interesting. I've just booted up the other FC5 which doesn't have the planetccrma kernel, and the associated kernel-modules-alsa package on it, and your quite right. No /etc/rc.d/init.d/alsasound. There is an /etc/alsa directory with and alsa.conf file, a cards directory, and a PCM directory, with another few bits, and cat /proc/asound/cards, cat /proc/asound/version, and /sbin/lsmod show that Alsa is installed ok.
It must be that installing the planetccrma kernel, and associated kernel-modules-alsa package, that has created the alsasound file.
So the question remains. How, if you are using Fedora kernels, do you start and stop Alsa?
Is ainit the thing? (man 8 ainit, from apropos alsa)
I must admit that I only had a quick look in the non planetccrma FC5, and perhaps there is a script somewhere that allows you to stop and start Alsa.
____________________________________________________________________ TonyN.:' mailto:tonynelson@georgeanelson.com ' http://www.georgeanelson.com/
On Sunday 06 August 2006 05:55, Tony Nelson wrote:
At 8:10 PM +0200 8/5/06, Nigel Henry wrote:
On Saturday 05 August 2006 18:55, Tony Nelson wrote:
At 6:23 PM +0200 8/5/06, Nigel Henry wrote:
On Saturday 05 August 2006 17:46, Paul Smith wrote:
On 8/5/06, Nigel Henry cave.dnb@tiscali.fr wrote:
> How can one restart alsa? > > I have already tried: > > # /sbin/service alsasound restart > alsasound: unrecognized service > #
Hi Paul. I've always used the following on FC, su'ed to root.
/etc/rc.d/init.d/alsasound stop /etc/rc.d/init.d/alsasound start /etc/rc.d/init.d/alsasound restart
Thanks, Nigel, but I get
# /etc/rc.d/init.d/alsasound restart bash: /etc/rc.d/init.d/alsasound: No such file or directory #
Paul
That's odd. I've just been into FC5, presuming that's what your using, to check it out, and alsasound is there. I am using a kernel from planetccrma, along with Alsa stuff, and sound apps from them, but Alsa, when I installed FC5 worked just fine OOTB with my Ensoniq card.
FWIW, I'm also using FC5, but "locate alsasound" finds no files and "yum provides alsasound" with the usual repos finds no matches. There are no modules with alsa in the name. Yet sound works here, VIA chipset, AC'97 audio.
Hi Tony. Thats interesting. I've just booted up the other FC5 which doesn't have the planetccrma kernel, and the associated kernel-modules-alsa package on it, and your quite right. No /etc/rc.d/init.d/alsasound. There is an /etc/alsa directory with and alsa.conf file, a cards directory, and a PCM directory, with another few bits, and cat /proc/asound/cards, cat /proc/asound/version, and /sbin/lsmod show that Alsa is installed ok.
It must be that installing the planetccrma kernel, and associated kernel-modules-alsa package, that has created the alsasound file.
So the question remains. How, if you are using Fedora kernels, do you start and stop Alsa?
Is ainit the thing? (man 8 ainit, from apropos alsa)
____________________________________________________________________
TonyN.:' mailto:tonynelson@georgeanelson.com ' http://www.georgeanelson.com/
I tried that. Ainit only seems to be dealing with dmix, and dsnoop. I've had all sorts of sound apps playing with ainit stopped. It's ironic. I've often had problems not getting the sound working, but never an instance of trying to stop it, and it won't stop. lol.
Janina has just suggested copying the alsasound script from my FC5 with planetccrma install, to the FC5 without planetccrma. I'm gonna try that. It will be an interesting experiment.
Apart from that, it would appear that with FC5 OOTB there is no way to stop, start, or restart Alsa, apart from shutting down, and rebooting.
As always, I'm willing to be proved wrong, and shot down in flames.
Nigel.
Nigel Henry writes:
On Saturday 05 August 2006 17:46, Paul Smith wrote:
On 8/5/06, Nigel Henry cave.dnb@tiscali.fr wrote:
How can one restart alsa?
snip snip ...
That's odd. I've just been into FC5, presuming that's what your using, to check it out, and alsasound is there. I am using a kernel from planetccrma,
Precisely why you have the alsasound service. You're using the CCRMA kernel, and therefore also the CCRMA alsa-utils, most likely.
In their infinite wisdom, Fedora appears to believe that sound is not a service, or not something that might require restarts without a reboot. I find that strange thinking, but they don't ask me. Clearly, CRMA also believes that sound might require a restart--but that expertise has also not impressed the Fedora decision makers.
You need a copy of the alsasound script from the CCRMA packages. Just plop it into /etc/init.d and you'll be good to go with the traditional:
service alsasound start/restart/stop
Janina
On Monday 07 August 2006 17:17, Janina Sajka wrote:
Nigel Henry writes:
On Saturday 05 August 2006 17:46, Paul Smith wrote:
On 8/5/06, Nigel Henry cave.dnb@tiscali.fr wrote:
How can one restart alsa?
snip snip ...
That's odd. I've just been into FC5, presuming that's what your using, to check it out, and alsasound is there. I am using a kernel from planetccrma,
Precisely why you have the alsasound service. You're using the CCRMA kernel, and therefore also the CCRMA alsa-utils, most likely.
I've used planetccrma since not long after I'd got into computing with FC1. Couldn't get the sound working until I found planetccrma by accident, but I'm very gratefull that I came across the site, and all the audio apps. Being able to stop and start Alsa has been quite usefull, as you get error messages if there is a problem with stopping or starting it. I'd had problems on FC1, and 2 with the USB midi keyboard being detected as card 0, and consequently the soundcard as card 1 was producing no sound, but since FC3 that problem has been resolved. OOTB, FC3,4, and 5 have set the cards in the correct order. The actual soundcard as card 0, and the USB midi keyboard is ignored. a /etc/modprobe.conf only shows the actual soundcard, and not the USB midi keyboard, so this is obviously being handled automagically somehow, because the keyboard works.
In their infinite wisdom, Fedora appears to believe that sound is not a service, or not something that might require restarts without a reboot. I find that strange thinking, but they don't ask me. Clearly, CRMA also believes that sound might require a restart--but that expertise has also not impressed the Fedora decision makers.
You need a copy of the alsasound script from the CCRMA packages. Just plop it into /etc/init.d and you'll be good to go with the traditional:
service alsasound start/restart/stop
I'll try that. I have one FC5 install with planetccrma, and the other FC5 without. I'll borrow the alsasound script from the planetccrma one.
It is usefull to be able to stop and start Alsa. I have seen quite a few folks having problems with the snd-hda-intel driver on laptops. Apparently there are variations in the soundcard chip on some laptops causing the snd-hda-intel driver not to work, and being able to stop and start Alsa is easier than having to reboot to restart Alsa, after you have tried something new to get the soundcard working.
Janina
Thanks for that.
Nigel.
Nigel Henry writes:
On Monday 07 August 2006 17:17, Janina Sajka wrote:
Nigel Henry writes:
On Saturday 05 August 2006 17:46, Paul Smith wrote:
On 8/5/06, Nigel Henry cave.dnb@tiscali.fr wrote:
How can one restart alsa?
snip snip ...
That's odd. I've just been into FC5, presuming that's what your using, to check it out, and alsasound is there. I am using a kernel from planetccrma,
Precisely why you have the alsasound service. You're using the CCRMA kernel, and therefore also the CCRMA alsa-utils, most likely.
I've used planetccrma since not long after I'd got into computing with FC1. Couldn't get the sound working until I found planetccrma by accident, but I'm very gratefull that I came across the site, and all the audio apps. Being able to stop and start Alsa has been quite usefull, as you get error messages if there is a problem with stopping or starting it. I'd had problems on FC1, and 2 with the USB midi keyboard being detected as card 0, and consequently the soundcard as card 1 was producing no sound, but since FC3 that problem has been resolved. OOTB, FC3,4, and 5 have set the cards in the correct order. The actual soundcard as card 0, and the USB midi keyboard is ignored. a /etc/modprobe.conf only shows the actual soundcard, and not the USB midi keyboard, so this is obviously being handled automagically somehow, because the keyboard works.
In their infinite wisdom, Fedora appears to believe that sound is not a service, or not something that might require restarts without a reboot. I find that strange thinking, but they don't ask me. Clearly, CRMA also believes that sound might require a restart--but that expertise has also not impressed the Fedora decision makers.
You need a copy of the alsasound script from the CCRMA packages. Just plop it into /etc/init.d and you'll be good to go with the traditional:
service alsasound start/restart/stop
I'll try that. I have one FC5 install with planetccrma, and the other FC5 without. I'll borrow the alsasound script from the planetccrma one.
It is usefull to be able to stop and start Alsa. I have seen quite a few folks having problems with the snd-hda-intel driver on laptops. Apparently there are variations in the soundcard chip on some laptops causing the snd-hda-intel driver not to work, and being able to stop and start Alsa is easier than having to reboot to restart Alsa, after you have tried something new to get the soundcard working.
Janina
Thanks for that.
Nigel.
You're very welcome. I don't have a single machine that I haven't copied my CCRMA alsasound script to /etc/init.d -- even though I don't generally run CCRMA kernels for other reasons.
Janina
Actively yanking this alsa provided script from the Fedora rpm boggles my mind.
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
On 8/7/06, Janina Sajka janina@rednote.net wrote:
You need a copy of the alsasound script from the CCRMA packages. Just plop it into /etc/init.d and you'll be good to go with the traditional:
service alsasound start/restart/stop
I'll try that. I have one FC5 install with planetccrma, and the other FC5 without. I'll borrow the alsasound script from the planetccrma one.
I have searched for the alsasound script but I cannot find it. Any help?
Thanks in advance,
Paul
Paul Smith wrote:
I have searched for the alsasound script but I cannot find it. Any help?
Thanks in advance,
Paul
What do you have in /etc/init.d? It should be in there if you have alsa installed.
On 8/22/06, Mark Haney mhaney@ercbroadband.org wrote:
I have searched for the alsasound script but I cannot find it. Any help?
What do you have in /etc/init.d? It should be in there if you have alsa installed.
Thanks, Mark, but it not there:
# dir /etc/init.d acpid gpm named rpcgssd anacron haldaemon nasd rpcidmapd apmd halt netdump rpcsvcgssd apt hidd netfs saslauthd atd hplip netplugd sendmail autofs hsqldb network single avahi-daemon httpd NetworkManager smartd avahi-dnsconfd iptables NetworkManagerDispatcher spamassassin bluetooth irda nfs sshd capi irqbalance nfslock syslog cpuspeed isdn nscd vncserver crond killall ntpd webmin cups kudzu pand winbind cups-config-daemon lirc portmap wpa_supplicant dhcdbd lisa psacct xfs diskdump lm_sensors rdisc ypbind dund mdmonitor readahead yum firstboot mdmpd readahead_early functions messagebus restorecond #
Paul
Paul Smith wrote:
Thanks, Mark, but it not there:
# dir /etc/init.d acpid gpm named rpcgssd anacron haldaemon nasd rpcidmapd apmd halt netdump rpcsvcgssd apt hidd netfs saslauthd atd hplip netplugd sendmail autofs hsqldb network single avahi-daemon httpd NetworkManager smartd avahi-dnsconfd iptables NetworkManagerDispatcher spamassassin bluetooth irda nfs sshd capi irqbalance nfslock syslog cpuspeed isdn nscd vncserver crond killall ntpd webmin cups kudzu pand winbind cups-config-daemon lirc portmap wpa_supplicant dhcdbd lisa psacct xfs diskdump lm_sensors rdisc ypbind dund mdmonitor readahead yum firstboot mdmpd readahead_early functions messagebus restorecond #
Paul
Strange. Okay, have you queried rpm to see if it's installed? What's the output of rpm -qa | grep alsa say?
I don't remember exactly how FC handles it, but is alsa a kernel module or built into the kernel on your system?
On 8/22/06, Mark Haney mhaney@ercbroadband.org wrote:
Strange. Okay, have you queried rpm to see if it's installed? What's the output of rpm -qa | grep alsa say?
I don't remember exactly how FC handles it, but is alsa a kernel module or built into the kernel on your system?
# rpm -qa | grep alsa alsa-utils-1.0.11-4.rc2 java-1.5.0-sun-alsa-1.5.0.06-1jpp alsa-lib-1.0.11-4.rc2 alsa-lib-devel-1.0.11-4.rc2 #
Regarding your second question, I do not really know how to answer them.
Paul
Paul Smith wrote:
On 8/22/06, Mark Haney mhaney@ercbroadband.org wrote:
Strange. Okay, have you queried rpm to see if it's installed? What's the output of rpm -qa | grep alsa say?
I don't remember exactly how FC handles it, but is alsa a kernel module or built into the kernel on your system?
# rpm -qa | grep alsa alsa-utils-1.0.11-4.rc2 java-1.5.0-sun-alsa-1.5.0.06-1jpp alsa-lib-1.0.11-4.rc2 alsa-lib-devel-1.0.11-4.rc2 #
Regarding your second question, I do not really know how to answer them.
Paul
Run an 'lsmod' and see if alsa is listed (or anything with 'snd' in the used by column). I'm nowhere near an FC5 box with sound, as my laptop is Gentoo and all my FC boxes are servers, so I'm not sure what I should be seeing on that front. I doubt seriously that FC's implementation of also would be THAT different from any other distro.
On 8/22/06, Mark Haney mhaney@ercbroadband.org wrote:
Strange. Okay, have you queried rpm to see if it's installed? What's the output of rpm -qa | grep alsa say?
I don't remember exactly how FC handles it, but is alsa a kernel module or built into the kernel on your system?
# rpm -qa | grep alsa alsa-utils-1.0.11-4.rc2 java-1.5.0-sun-alsa-1.5.0.06-1jpp alsa-lib-1.0.11-4.rc2 alsa-lib-devel-1.0.11-4.rc2 #
Regarding your second question, I do not really know how to answer them.
Run an 'lsmod' and see if alsa is listed (or anything with 'snd' in the used by column). I'm nowhere near an FC5 box with sound, as my laptop is Gentoo and all my FC boxes are servers, so I'm not sure what I should be seeing on that front. I doubt seriously that FC's implementation of also would be THAT different from any other distro.
OK:
# /sbin/lsmod | grep snd snd_hda_intel 22613 2 snd_hda_codec 141761 1 snd_hda_intel snd_seq_dummy 8133 0 snd_seq_oss 37185 0 snd_seq_midi_event 11841 1 snd_seq_oss snd_seq 59441 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event snd_seq_device 13005 3 snd_seq_dummy,snd_seq_oss,snd_seq snd_pcm_oss 43985 1 snd_mixer_oss 21825 2 snd_pcm_oss snd_pcm 88005 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss snd_timer 28613 2 snd_seq,snd_pcm snd 59973 9 snd_hda_intel,snd_hda_codec,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer soundcore 14113 3 snd snd_page_alloc 14665 2 snd_hda_intel,snd_pcm #
Paul
On 8/22/06, Paul Smith phhs80@gmail.com wrote:
Strange. Okay, have you queried rpm to see if it's installed? What's the output of rpm -qa | grep alsa say?
I don't remember exactly how FC handles it, but is alsa a kernel module or built into the kernel on your system?
# rpm -qa | grep alsa alsa-utils-1.0.11-4.rc2 java-1.5.0-sun-alsa-1.5.0.06-1jpp alsa-lib-1.0.11-4.rc2 alsa-lib-devel-1.0.11-4.rc2 #
Regarding your second question, I do not really know how to answer them.
Run an 'lsmod' and see if alsa is listed (or anything with 'snd' in the used by column). I'm nowhere near an FC5 box with sound, as my laptop is Gentoo and all my FC boxes are servers, so I'm not sure what I should be seeing on that front. I doubt seriously that FC's implementation of also would be THAT different from any other distro.
OK:
# /sbin/lsmod | grep snd snd_hda_intel 22613 2 snd_hda_codec 141761 1 snd_hda_intel snd_seq_dummy 8133 0 snd_seq_oss 37185 0 snd_seq_midi_event 11841 1 snd_seq_oss snd_seq 59441 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event snd_seq_device 13005 3 snd_seq_dummy,snd_seq_oss,snd_seq snd_pcm_oss 43985 1 snd_mixer_oss 21825 2 snd_pcm_oss snd_pcm 88005 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss snd_timer 28613 2 snd_seq,snd_pcm snd 59973 9 snd_hda_intel,snd_hda_codec,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer soundcore 14113 3 snd snd_page_alloc 14665 2 snd_hda_intel,snd_pcm #
In addition, here
'ainit psmith stop'
returns to the prompt but it does not stop the music playing.
Paul
Mark Haney writes:
Paul Smith wrote:
I have searched for the alsasound script but I cannot find it. Any help?
Thanks in advance,
Paul
What do you have in /etc/init.d? It should be in there if you have alsa installed.
Stripped by FC for some reason I don't understand. I get mine from CCRMA. I'm attaching. Let me know if that doesn't come through.
Janina
-- Fere libenter homines id quod volunt credunt.
Mark Haney Sr. Systems Administrator ERC Broadband (828) 350-2415
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
On 9/8/06, Janina Sajka janina@rednote.net wrote:
I have searched for the alsasound script but I cannot find it. Any help?
What do you have in /etc/init.d? It should be in there if you have alsa installed.
Stripped by FC for some reason I don't understand. I get mine from CCRMA. I'm attaching. Let me know if that doesn't come through.
Thanks, Janina, but getting
# /etc/rc.d/init.d/alsasound restart bash: /etc/rc.d/init.d/alsasound: Permission denied #
What permission precisely should I give to alsasound?
Paul
Paul Smith wrote:
On 9/8/06, Janina Sajka janina@rednote.net wrote:
I have searched for the alsasound script but I cannot find it. Any
help?
What do you have in /etc/init.d? It should be in there if you have
alsa
installed.
Stripped by FC for some reason I don't understand. I get mine from CCRMA. I'm attaching. Let me know if that doesn't come through.
Thanks, Janina, but getting
# /etc/rc.d/init.d/alsasound restart bash: /etc/rc.d/init.d/alsasound: Permission denied #
What permission precisely should I give to alsasound?
Paul
You have to run it as root.
On 9/8/06, Mikkel L. Ellertson mikkel@infinity-ltd.com wrote:
I have searched for the alsasound script but I cannot find it. Any
help?
What do you have in /etc/init.d? It should be in there if you have
alsa
installed.
Stripped by FC for some reason I don't understand. I get mine from CCRMA. I'm attaching. Let me know if that doesn't come through.
Thanks, Janina, but getting
# /etc/rc.d/init.d/alsasound restart bash: /etc/rc.d/init.d/alsasound: Permission denied #
What permission precisely should I give to alsasound?
You have to run it as root.
Thanks, Mikkel, but I ran the command as root.
Paul
On 9/8/06, Paul Smith phhs80@gmail.com wrote:
I have searched for the alsasound script but I cannot find it. Any
help?
What do you have in /etc/init.d? It should be in there if you have
alsa
installed.
Stripped by FC for some reason I don't understand. I get mine from CCRMA. I'm attaching. Let me know if that doesn't come through.
Thanks, Janina, but getting
# /etc/rc.d/init.d/alsasound restart bash: /etc/rc.d/init.d/alsasound: Permission denied #
What permission precisely should I give to alsasound?
You have to run it as root.
Thanks, Mikkel, but I ran the command as root.
After
chmod +x /etc/rc.d/init.d/alsasound
I got
# /etc/rc.d/init.d/alsasound stop Shutting down sound driver: ERROR: Module snd_hda_intel is in use ERROR: Module snd_hda_codec is in use by snd_hda_intel ERROR: Module snd_mixer_oss is in use ERROR: Module snd_pcm is in use by snd_hda_intel,snd_hda_codec ERROR: Module snd_timer is in use by snd_pcm ERROR: Module snd is in use by snd_hda_intel,snd_hda_codec,snd_mixer_oss,snd_pcm,snd_timer done #
So, apparently, alsasound does not work properly.
Paul
On Tuesday 22 August 2006 13:35, Paul Smith wrote:
On 8/7/06, Janina Sajka janina@rednote.net wrote:
You need a copy of the alsasound script from the CCRMA packages. Just plop it into /etc/init.d and you'll be good to go with the traditional:
service alsasound start/restart/stop
I'll try that. I have one FC5 install with planetccrma, and the other FC5 without. I'll borrow the alsasound script from the planetccrma one.
I have searched for the alsasound script but I cannot find it. Any help?
Thanks in advance,
Paul
If this is a straight FC5 install, without installing the planetccrma kernel, and associated kernel-modules-alsa, there isn't an alsasound script.
Alsa is obviously being started at bootup on FC5 in some different way, but I havn't discovered how yet.
Whether this is specific to FC5, I don't know. When I installed FC3, and 4, Alsa worked out of the box, and there was no good reason to root around the filesystem seeing what bits were, or were not there. Then I installed the planetccrma stuff, which I always do, and the script is at /etc/rc.d/init.d , as it always had been since I've been using FC with planetccrma.
Nigel.
At 2:55 PM +0200 8/22/06, Nigel Henry wrote:
On Tuesday 22 August 2006 13:35, Paul Smith wrote:
On 8/7/06, Janina Sajka janina@rednote.net wrote:
You need a copy of the alsasound script from the CCRMA packages. Just plop it into /etc/init.d and you'll be good to go with the traditional:
service alsasound start/restart/stop
I'll try that. I have one FC5 install with planetccrma, and the other FC5 without. I'll borrow the alsasound script from the planetccrma one.
I have searched for the alsasound script but I cannot find it. Any help?
Thanks in advance,
Paul
If this is a straight FC5 install, without installing the planetccrma kernel, and associated kernel-modules-alsa, there isn't an alsasound script.
Alsa is obviously being started at bootup on FC5 in some different way, but I havn't discovered how yet.
...
Fedora appears to use ainit to start alsa (man 8 ainit, via "apropos alsa"). ____________________________________________________________________ TonyN.:' mailto:tonynelson@georgeanelson.com ' http://www.georgeanelson.com/
On Tuesday 22 August 2006 19:16, Tony Nelson wrote:
At 2:55 PM +0200 8/22/06, Nigel Henry wrote:
On Tuesday 22 August 2006 13:35, Paul Smith wrote:
On 8/7/06, Janina Sajka janina@rednote.net wrote:
You need a copy of the alsasound script from the CCRMA packages. Just plop it into /etc/init.d and you'll be good to go with the traditional:
service alsasound start/restart/stop
I'll try that. I have one FC5 install with planetccrma, and the other FC5 without. I'll borrow the alsasound script from the planetccrma one.
I have searched for the alsasound script but I cannot find it. Any help?
Thanks in advance,
Paul
If this is a straight FC5 install, without installing the planetccrma kernel, and associated kernel-modules-alsa, there isn't an alsasound script.
Alsa is obviously being started at bootup on FC5 in some different way, but I havn't discovered how yet.
...
Fedora appears to use ainit to start alsa (man 8 ainit, via "apropos alsa").
Hi Tony. This thread was running a while back, and I think you mentioned "ainit" then. I tried it on FC5, (Not the one with planetccrma on it). I had some music playing using Mhwaveedit, which uses Alsa, and did an "ainit stop" which returned me to the prompt, indicating it had stopped, but the music was still playing.
The man page for ainit indicates that it's to do with dmix, and dnoop, and admittadly both used by Alsa.
Have YOU managed to stop Alsa using ainit?
I don't if you've used the planetccrma stuff, which puts the alsasound shellscript in /etc/rc.d/init.d, but this is what I get on FC2 for a stop, and then start of Alsa using it (no music playing)
[djmons@localhost djmons]$ su Password: [root@localhost djmons]# /etc/rc.d/init.d/alsasound stop Shutting down sound driver [ OK ] [root@localhost djmons]# /etc/rc.d/init.d/alsasound start Starting sound driver snd-ens1371 [ OK ] Starting sound driver snd-ens1371 [ OK ] Starting sequencer [ OK ] Starting sequencer driver snd-seq-midi [ OK ] Restoring sound driver settings [ OK ] [root@localhost djmons]#
And if I have music playing using Alsa, running alsasound stop, closes the sound app, and shuts down Alsa as above.
Back to ainit. Dmix, as far as I understand, allows you to use more than one audio app (both using Alsa) at the same time, on a soundcard that is not capable of multiple audio streams (no hardware mixing), which includes most cards, like the Ensoniq one on this machine. My other machine which has an Audigy2 soundblaster, does have hardware mixing, so dmix doesn't come into the equation with that card.
I will experiment on the non planetccrma FC5. I'll try running 2 Alsa using audio apps. Then I'll run ainit stop, and see if one of the apps stops working. If ainit only controls dmix, and dsnoop (the capture part), and as far as I know, dmix only comes into play when you want to play more than one Alsa using app at the same time, then, an "ainit stop" should either result in losing one of the apps, or breaking the machine.
I'm also going to post this query to the alsa-user list, as it's a bit puzzling. Hopefully someone there might be using FC5.
That's enough rambling on.
Nigel.
At 9:45 PM +0200 8/22/06, Nigel Henry wrote:
On Tuesday 22 August 2006 19:16, Tony Nelson wrote:
...
Fedora appears to use ainit to start alsa (man 8 ainit, via "apropos alsa").
Hi Tony. This thread was running a while back, and I think you mentioned "ainit" then. I tried it on FC5, (Not the one with planetccrma on it). I had some music playing using Mhwaveedit, which uses Alsa, and did an "ainit stop" which returned me to the prompt, indicating it had stopped, but the music was still playing.
The man page for ainit indicates that it's to do with dmix, and dnoop, and admittadly both used by Alsa.
Have YOU managed to stop Alsa using ainit?
No.
"ainit tonyn stop" removes the lock files when I run it as root, and doesn't remove them when run as tonyn, but I can still play sounds after running it either way.
I don't if you've used the planetccrma stuff, which puts the alsasound shellscript in /etc/rc.d/init.d, but this is what I get on FC2 for a stop, and then start of Alsa using it (no music playing)
...
I have not used PlanetCCRMA kernels. They appear to do it differently from Fedora. ____________________________________________________________________ TonyN.:' mailto:tonynelson@georgeanelson.com ' http://www.georgeanelson.com/
On Sat, 2006-08-05 at 16:46 +0100, Paul Smith wrote:
On 8/5/06, Nigel Henry cave.dnb@tiscali.fr wrote:
How can one restart alsa?
I have already tried:
# /sbin/service alsasound restart alsasound: unrecognized service #
Hi Paul. I've always used the following on FC, su'ed to root.
/etc/rc.d/init.d/alsasound stop /etc/rc.d/init.d/alsasound start /etc/rc.d/init.d/alsasound restart
Thanks, Nigel, but I get
# /etc/rc.d/init.d/alsasound restart bash: /etc/rc.d/init.d/alsasound: No such file or directory #
Paul
I don't know why this is true on your machine but it seems clear you don't have alsasound as an initscript on your machine. -- ======================================================================= This fortune intentionally left blank. ======================================================================= Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam@sbcglobal.net
On Sat, 05 Aug 2006 16:02:44 -0500 Aaron Konstam akonstam@sbcglobal.net wrote:
On Sat, 2006-08-05 at 16:46 +0100, Paul Smith wrote:
On 8/5/06, Nigel Henry cave.dnb@tiscali.fr wrote:
How can one restart alsa?
I have already tried:
# /sbin/service alsasound restart alsasound: unrecognized service #
Hi Paul. I've always used the following on FC, su'ed to root.
/etc/rc.d/init.d/alsasound stop /etc/rc.d/init.d/alsasound start /etc/rc.d/init.d/alsasound restart
Thanks, Nigel, but I get
# /etc/rc.d/init.d/alsasound restart bash: /etc/rc.d/init.d/alsasound: No such file or directory #
Paul
I don't know why this is true on your machine but it seems clear you don't have alsasound as an initscript on your machine.
My question is, how do other Fedora Core 5 users have this service on their systems? An expansion based on a previous email on this subject: their appears to be no /etc/rc.d/init.d/ directories in any of the three alsa RPM's that ship with Fedora Core 5: http://www.afolkey2.net/Projects/Files_alsa-lib-devel.txt http://www.afolkey2.net/Projects/Files_alsa-lib.txt http://www.afolkey2.net/Projects/Files_alsa-utils.txt
As their appear to only be three alsa* RPM's in Fedora Core 5, do other have /etc/rc.d/init.d/alsasound because it is in some other package? Such as one that is not in Core or Extras?
I'm going to check the Fedora Core 4 & Fedora Core 3 alsa RPM's to see if the file is in those.
Steven P. Ulrick
On Saturday 05 August 2006 11:01, Paul Smith wrote:
How can one restart alsa?
I have already tried:
# /sbin/service alsasound restart alsasound: unrecognized service #
This indicates that the service is not enabled.
See chkconfig(8).
You may need to do
chkconfig --level 235 alsasound on
Or...
The error may indicate that the service is not installed.
On Sat, 5 Aug 2006 12:16:07 -0400 "Garry T. Williams" gtwilliams@gmail.com wrote:
On Saturday 05 August 2006 11:01, Paul Smith wrote:
How can one restart alsa?
I have already tried:
# /sbin/service alsasound restart alsasound: unrecognized service #
This indicates that the service is not enabled.
See chkconfig(8).
You may need to do
chkconfig --level 235 alsasound onOr...
The error may indicate that the service is not installed.
Hello, Everyone On our Fedora Core 5 system, the output of "rpm -qa | grep alsa" is as follows: [root@afolkey2 ~]# rpm -qa | grep alsa alsa-lib-devel-1.0.11-4.rc2 alsamixergui-0.9.0-0.2.rc1.fc5 alsa-tools-1.0.10-2.fc5 alsa-lib-1.0.11-4.rc2 alsa-utils-1.0.11-4.rc2
"yum list | grep alsa" outputs the following: [root@afolkey2 ~]# yum list | grep alsa ftp://mirror.newnanutilities.org/pub/fedora/linux/extras/5/i386/repodata/repomd.xml: [Errno 4] IOError: <urlopen error (-2, 'Name or service not known')> Trying other mirror. alsa-lib.i386 1.0.11-4.rc2 installed alsa-lib-devel.i386 1.0.11-4.rc2 installed alsa-tools.i386 1.0.10-2.fc5 installed alsa-utils.i386 1.0.11-4.rc2 installed alsamixergui.i386 0.9.0-0.2.rc1.fc5 installed balsa.i386 2.3.12-1.fc5 extras kadu-alsa_sound.i386 0.5.0-0.6.20060730svn. extras
As this "appears" to show that there are no other "alsa" packages in Core or Extras, and since I have no "alsasound" service my FC5 machine, how would one go about getting that service?
Steven P. Ulrick
On Sat, 2006-08-05 at 15:27 -0500, Steven P. Ulrick wrote:
As this "appears" to show that there are no other "alsa" packages in Core or Extras, and since I have no "alsasound" service my FC5 machine, how would one go about getting that service?
It's gotta be in there somewhere under some alias as when you make changes under kde using the control center to your sound service it stops and restarts something somehow.
Huh? God, that confused me too!!