after spending more time researching this, it seems the missing alsasound script
in Fedora Core N is either a big packaging mistake or the result of a deliberate
design change.
 
what you're experiencing is probably better called "ALSA Adventures",
and I don't have any problem with you using the words I've posted here,
but you must be made aware that all of the words posted here are entirely
" 2002-2004 Philipp Esselbach - All Rights Reserved".
 
so I'm not the final word on getting permission for re-use or re-publication.
 
The Choices
1. Go With What Planet CCRMA Provides (assume it's a packaging mistake)
2. Go With The Flow (assume it's a design change)
 
Pros and Cons
If you choose #1, you get an ALSA update from 1.0.3a to 1.0.5a-1 plus the
'missing' alsasound script.
 
If you choose #2, you keep your 1.0.3a, get to edit a couple files, add the
alsasound script from the alsa-utils sources (or I can send you one) and then
make the right file links so init does what's needs as you change run levels
during boot and shutdown.
 
In both cases, you'll need to make sure the right links are there for init.
 
Choice #1
Based on the output of "uname -p" ('i586' or 'i686') grab the i586 or i686 flavor
made by Planet CCRMA.
 
Grab alsa-utils and alsa-lib and alsa-oss and alsa-lib-jack-plugin.
 
If doing "rpm -Uhv alsa-*rpm" complains about something missing, then just
pick what you need from here.
 
Choice #1b
Just grab alsa-driver. Either flavor, doesn't matter. It contains nothing executable
you will use except the alsasound script.
 
You don't actually update your ALSA drivers, though. You just fix the
packaging mistake.
 
as root from root's home directory (/root):

Quote:[size:2]mkdir tempcp /whereever-you-have/saved/the/rpm/alsa-driver-*rpm temp
cd temp
rpm2cpio alsa-driver-*rpm > alsa-driver.cpio
cpio --extract < alsa-driver.cpio
cp alsasound /etc/init.d

 
Choice #2
You'll be editing /etc/modules.conf and /etc/modprobe.conf.local.
One or both of these files have the string 'snd-card' or something like 'audigy'
in them.
Check with "grep snd-card /etc/name-of-the-mod-file" and
"grep udig /etc/same-as-just-a-moment-ago".
 
These files will need stanza that look like this:

Quote:[size:2]# Note: for use under 2.4, changes must also be made to modules.conf!alias snd-card-0 snd-audigyModuleName
install snd-audigyModuleName /sbin/modprobe --first-time --ignore-install snd-audigyModuleName && { /usr/sbin/alsactl -F restore >/dev/null 2>&1 || :; }
remove snd-audigyModuleName { /usr/sbin/alsactl store >/dev/null 2>&1 || :; } ; /sbin/modprobe -r --first-time --ignore-remove snd-audigyModuleName

YMMV: need to find your existing 'snd-card' lines to figure outwhat the Audigy driver is named.
 
Note: the stanza has only four lines - the 'install' and 'remove' lines are long.
 
Ensure init can find alsasound
To check to be sure all of the right file links have been made, do
"find /etc/rc.d/rc* -name \*alsa\*".
 
You should have pairs of files which look like "Sxxalsasound" and "Kxxalsasound"
(where 'xx' are digits) in at least 'rc2.d', 'rc3.d' and 'rc5.d'. (the /etc/rc.d/rcX.d dirs
correspond to init runlevels - see /etc/inittab for more info).
 
If you need to create the links for init's benefit, then do:

Quote:[size:2]ln -sf /etc/init.d/alsasound /etc/rc2.d/S12alsasoundln -sf /etc/init.d/alsasound /etc/rc2.d/K10alsasound
ln -sf /etc/init.d/alsasound /etc/rc3.d/S12alsasound
ln -sf /etc/init.d/alsasound /etc/rc3.d/K10alsasound
ln -sf /etc/init.d/alsasound /etc/rc5.d/S12alsasound
ln -sf /etc/init.d/alsasound /etc/rc5.d/K10alsasound

YMMV: might need to use /etc/rc.d/rcX.d/ instead. check before you attempt this. 
 

Originally posted by martouf:

Quote:after spending more time researching this, it seems the missing alsasound scriptin Fedora Core N is either a big packaging mistake or the result of a deliberate
design change.
<snip>
 
The Choices
1. Go With What Planet CCRMA Provides (assume it's a packaging mistake)
2. Go With The Flow (assume it's a design change)
 
Pros and Cons
If you choose #1, you get an ALSA update from 1.0.3a to 1.0.5a-1 plus the
'missing' alsasound script.
 
If you choose #2, you keep your 1.0.3a, get to edit a couple files, add the
alsasound script from the alsa-utils sources (or I can send you one) and then
make the right file links so init does what's needs as you change run levels
during boot and shutdown.
 
In both cases, you'll need to make sure the right links are there for init.
 
Choice #1
Based on the output of "uname -p" ('i586' or 'i686') grab the i586 or i686 flavor
made by Planet CCRMA.
 
Grab alsa-utils and alsa-lib and alsa-oss and alsa-lib-jack-plugin.
 
If doing "rpm -Uhv alsa-*rpm" complains about something missing, then just
pick what you need from here.
 
Choice #1b
Just grab alsa-driver. Either flavor, doesn't matter. It contains nothing executable
you will use except the alsasound script.
 
You don't actually update your ALSA drivers, though. You just fix the
packaging mistake.
 
as root from root's home directory (/root):

Quote:[size:2]mkdir tempcp /whereever-you-have/saved/the/rpm/alsa-driver-*rpm temp
cd temp
rpm2cpio alsa-driver-*rpm > alsa-driver.cpio
cpio --extract < alsa-driver.cpio
cp alsasound /etc/init.d

 
Choice #2
You'll be editing /etc/modules.conf and /etc/modprobe.conf.local.
One or both of these files have the string 'snd-card' or something like 'audigy'
in them.
Check with "grep snd-card /etc/name-of-the-mod-file" and
"grep udig /etc/same-as-just-a-moment-ago".
 
<Snip>
 

 
I too have been trying to research this and I have not come up with the info you have. How are you doing this? I am most appreciative of the help and time you have put in on this, but if I could do it myself, so much the better, yes? On one of my woodworking newsgroups, yhere is an abbreviation DAGS for "Do A Google Search". Usually typed in exasperation after repeated attempts to help some one with a problem thought long solved. Is that how you found the info on CCRMA? What was the query you typed in? I have tried "ALSAsound", but hadn't found that page. I may have not seen it, or something.
 
Thanks for the tip on use and re-use of materials posted here. I shall try, with due diligence, to get in touch with the owner of the copyright should I use direct quotes. I will definitely include a link to this site. It has been of incalculable value to me and would be to anyone else as well.
 
It smells to me like we're sneaking up on a solution here. I think that I will try option #1 in your last post. I will need the i686 as I have a Northwood P4 2.4GHz processor by Intel. Sounds like the better plan for variety of reasons. I will post results. Who makes the call? Thanks again.

Hi Martouf,
Okay, I have d/l'ed the things you said to get. I have run "rpm -Uhv alsa-*rpm" command you suggested. and this is what was returned:
 
[root@rapid_roy root]# rpm -Uhv alsa-*rpm
/etc/security/selinux/file_contexts: No such file or directory
warning: alsa-driver-1.0.5a-1.cvs.rhfc2.ccrma.i686.rpm: V3 DSA signature: NOKEY, key ID 68d9802a
error: Failed dependencies:
kernel-module-alsa = 1.0.5a-1.cvs.rhfc2.ccrma is needed by alsa-driver-1.0.5a-1.cvs.rhfc2.ccrma
libjack.so.0 is needed by alsa-lib-jack-plugin-1.0.5-1.cvs.rhfc2.ccrma
 
I have gone to the link you posted. The latest kernel module I can find is:
kernel-module-alsa 2.6.7-1.437.1
I am running kernel 2.6.8-1.521. It lookd like there is a conflict here. What do you think? Also, I cannot find libjack.so.0 in the list. Nor is it in the list of files in the RPM. Is this one that is created somehow?
 
I tried #1b.
 
At the cpio --extract stage, I got a long long list of no such file or directory statements. I then did a man on the cpio command. Is it possible that I need to make the command line say:
cpio --extract --make_directories < alsa-driver.cpio and will it do the making of directories in the temp directory I had just created. I think that would be what PKunzip would do in DOS, if memory serves. Although, I don't recall having to tell it to make the directories. It should have done it as a metter of course or at least have prompted me that I needed to do something else. The reason I ask is that the alsasound file is in the /etc/rc.d/init.d directory as shown in the content of rpm list in the CCRMA page link as "/etc/rc.d/init.d/alsasound". Thanks for your comments on this.
 
 
[Edited by beej-in-ga on 2004-08-27 10:24:28]
 

Hi Martouf,
Here's what I did. I went to linuxquestions.org for their man pages on line. I reread the cpio page and then typed the following into a terminal window:
 
cpio --extract --make-directories < alsa-driver.cpio
 
It made the directories etc and usr and extracted the files and subdirectories as needed. I then copied the file alsasound into the exist /etc/init.d directory as indicated in your post. I then tried to reboot the machine to see if anything had changed. There was no indication that anything had changed, i.e., there was no sound from the sound card until I manually typed in "alsactl -F retore" in a terminal window as root. I guess I have missed a step somewhere along the line. But:
 
[root@rapid_roy root]# ls -l /etc/init.d/alsasound
-rwxr-xr-x 1 root root 7512 Aug 27 12:39 /etc/init.d/alsasound
 
This file does now exist. When I look for it in a file browser window, the icon for it has a small blue square on it with sh in white letters on it. I don't know what this means. I do know that if I double click on it, it does not open in a text window as other files do. In fact none of these "sh" files will do this. Must be some kind of protection on them. In answer to your quote in choice #2, here is the contents of modprobe.conf as it is now. I have changed nothing in it, it is as it has been since the beginning:
 
# Note: for use under 2.4, changes must also be made to modules.conf!
alias eth1 8139too
alias ieee1394-controller ohci1394
alias snd-card-0 snd-emu10k1
install sound-slot-0 /sbin/modprobe --first-time --ignore-install sound-slot-0 && { /bin/aumix-minimal -f /etc/.aumixrc -L >/dev/null 2>&1 || :; }
remove sound-slot-0 { /bin/aumix-minimal -f /etc/.aumixrc -S >/dev/null 2>&1 || :; } ; /sbin/modprobe -r --first-time --ignore-remove sound-slot-0
alias usb-controller1 ehci-hcd
alias usb-controller2 uhci-hcd
 
It seems there are more than four lines, but the others seem to refer to firewire and usb controllers. If memory serves, I think there are usb connections to the SB live Audigy and I know there are IR and (1) firewire (1394) connection on both the card and the livedrive on the front of the computer. I do not know what other information I can give you to help with this. If I've left you in the dark somewhere, just ask and I will attempt to find the information you need. Thanks again for your help.
 
Your Friend,
Beej
 
 

gradually, the layers of the Vidalia are revealed..
 
I thought you were running FC2? not FC2+updates. ok, well, in that case
choice #1 isn't available, exactly. Trying to get the job done with pre-packaged
stuff and not build from source...
 
You've compensated for me missing a vital cpio param, that's good, but my bad.
You've copied the alsasound script to where it needs to be, that's good.
 
You skipped the "Ensure init can find alsasound" part, not so good. ;(
 
Plan A
Rebooting won't do anything if init can't find the appropriate Sxxalsasound entry
which will cause it to start up the sound system.
'S' is for 'S'tart and 'K' is for 'K'ill, and the 'xx' number is for sequencing.
 
You can easily test just the alsasound script as root (here are examples):
"/etc/init.d/alsasound start"
"/etc/init.d/alsasound status"
"/etc/init.d/alsasound stop"
 
Double-clicking on a shell script file (hence the 'sh' abbr) won't necessarily
do anything good. In this alsasound case, it's expecting a parameter.
 
Make those entries for init, then (as root) "telinit 1".
Once you've reached runlevel 1 (wait for it), then "telinit 5".
If you want to save time waiting for X Windows to start, then "telinit 3".
(how to test this stuff without rebooting)
 
Plan B
edit modprobe.conf, making changes only within the curly braces
(the '{' and '}' chars).
 
rip out the aumix stuff to put in the alsactl stuff in its place.
( don't forget to
"cp /etc/modprobe.conf /etc/modprobe.conf.saved-just-in-case"
before you start editing )
 

Originally posted by martouf:

Quote:gradually, the layers of the Vidalia are revealed..  
I thought you were running FC2? not FC2+updates. ok, well, in that case
choice #1 isn't available, exactly. Trying to get the job done with pre-packaged
stuff and not build from source...
 
You've compensated for me missing a vital cpio param, that's good, but my bad.
You've copied the alsasound script to where it needs to be, that's good.
 
You skipped the "Ensure init can find alsasound" part, not so good. ;(
 
Plan A
Rebooting won't do anything if init can't find the appropriate Sxxalsasound entry
which will cause it to start up the sound system.
'S' is for 'S'tart and 'K' is for 'K'ill, and the 'xx' number is for sequencing.
 
You can easily test just the alsasound script as root (here are examples):
"/etc/init.d/alsasound start"
"/etc/init.d/alsasound status"
"/etc/init.d/alsasound stop"
 
Double-clicking on a shell script file (hence the 'sh' abbr) won't necessarily
do anything good. In this alsasound case, it's expecting a parameter.
 
Make those entries for init, then (as root) "telinit 1".
Once you've reached runlevel 1 (wait for it), then "telinit 5".
If you want to save time waiting for X Windows to start, then "telinit 3".
(how to test this stuff without rebooting)
 
Plan B
edit modprobe.conf, making changes only within the curly braces
(the '{' and '}' chars).
 
rip out the aumix stuff to put in the alsactl stuff in its place.
( don't forget to
"cp /etc/modprobe.conf /etc/modprobe.conf.saved-just-in-case"
before you start editing )

Hi Martouf,
Sorry I thought I made it clear what kernel I was running. My Bad. Regarding Plan A:
 
Which init file is it that I must edit, how do I edit it, and what is it that I should type?
I assume that somewhere I have to put in the string "Sxxalsasound" but I don't know where and do use the XX or is there an actual number I should put instead?
 
Regarding Plan B:
 
I'll be switched if I can figure that file out. It looks to me like it tells something to start and then immediately tells it to ignore it. True? Do I get this right? If I take out the reference to the aumix stuff and put in "alsactl -F restore" between th { and } then that will work?
Your friend,
Beej

guess I'm being as clear as the Savannah after a big rain storm..
 
Plan A needed your referring back to an earlier post.. the one with
the Ensure init can find alsasound section in it.. no matter, though,
I'll repeat it here:
 
Ensure init can find alsasound
To check to be sure all of the right file links have been made,
do "find /etc/rc.d/rc* -name \*alsa\*".
 
You should have pairs of files which look like "Sxxalsasound" and "Kxxalsasound"
(where 'xx' are digits) in at least 'rc2.d', 'rc3.d' and 'rc5.d'. (the /etc/rc.d/rcX.d dirs
correspond to init runlevels - see /etc/inittab for more info).
 
If you need to create the links for init's benefit, then do:

Quote:ln -sf /etc/init.d/alsasound /etc/rc2.d/S12alsasoundln -sf /etc/init.d/alsasound /etc/rc2.d/K10alsasound
ln -sf /etc/init.d/alsasound /etc/rc3.d/S12alsasound
ln -sf /etc/init.d/alsasound /etc/rc3.d/K10alsasound
ln -sf /etc/init.d/alsasound /etc/rc5.d/S12alsasound
ln -sf /etc/init.d/alsasound /etc/rc5.d/K10alsasound

YMMV: might need to use /etc/rc.d/rcX.d/ instead. check before you attempt this. 
In Other Words
If you run the 'find' command above, and don't find pairs of files with names
like "[sK][0-9][0-9]alsasound" (in regexp form) then you'll need to create them
using the 'ln' commands listed above.
 
After they've been created, and only then, will the alsasound script be
called by init when your system changes run levels and automatically
start/stop your sound system.
 
Still with me on this?
 
as for the stuff in the curly braces, the ">/dev/null 2>&1" is confusing you?
 
all that means is to redirect stdout to /dev/null and combine stdout and stderr.
IOW: send any output it might generate to /dev/null. make it silent.
but still do something - just prevent it being able to complain if it can't.
 

Originally posted by martouf:

Quote:guess I'm being as clear as the Savannah after a big rain storm.. 
Plan A needed your referring back to an earlier post.. the one with
the Ensure init can find alsasound section in it.. no matter, though,
I'll repeat it here:
 
Ensure init can find alsasound
To check to be sure all of the right file links have been made,
do "find /etc/rc.d/rc* -name \*alsa\*".
 
You should have pairs of files which look like "Sxxalsasound" and "Kxxalsasound"
(where 'xx' are digits) in at least 'rc2.d', 'rc3.d' and 'rc5.d'. (the /etc/rc.d/rcX.d dirs
correspond to init runlevels - see /etc/inittab for more info).
 
If you need to create the links for init's benefit, then do:

Quote:ln -sf /etc/init.d/alsasound /etc/rc2.d/S12alsasoundln -sf /etc/init.d/alsasound /etc/rc2.d/K10alsasound
ln -sf /etc/init.d/alsasound /etc/rc3.d/S12alsasound
ln -sf /etc/init.d/alsasound /etc/rc3.d/K10alsasound
ln -sf /etc/init.d/alsasound /etc/rc5.d/S12alsasound
ln -sf /etc/init.d/alsasound /etc/rc5.d/K10alsasound

YMMV: might need to use /etc/rc.d/rcX.d/ instead. check before you attempt this. 
In Other Words
If you run the 'find' command above, and don't find pairs of files with names
like "[sK][0-9][0-9]alsasound" (in regexp form) then you'll need to create them
using the 'ln' commands listed above.
 
After they've been created, and only then, will the alsasound script be
called by init when your system changes run levels and automatically
start/stop your sound system.
 
Still with me on this?
 
as for the stuff in the curly braces, the ">/dev/null 2>&1" is confusing you?
 
all that means is to redirect stdout to /dev/null and combine stdout and stderr.
IOW: send any output it might generate to /dev/null. make it silent.
but still do something - just prevent it being able to complain if it can't.

 
Hi Martouf,
After reading your post, doing pennance by banging my head on the tiled concrete floor of my office, invoking the help of the computer Gods, and offering a Jolt/Coffee mix sacrifice to the Mother Goddess. I typed in the incantation you specified, and for good measure shook a bag of Dark Chocolate/almond nuggets at the cpu case. Then I tried the telinit test you provided and lo and behold it bloody WORKED!!!!!!!!!!!!!! I did do a second find out of curiosity and was rewarded with a long list of files. You expected as much, right? Now can you tell me what all that ln -sf stuff is? Oh and BTW, This problem is solved for this kernel. Do you think I will have to do it again for a future update of FC2? Thanks for your help and I am sorry that I took up so much of your time. You are ACES in my book!
Best Regards,
Beej
 

An interesting twist ... did a kitchen sink FC2 install, the audigy 2 zs is detected and cd player works, but alsa/mplayer/xmms/etc attempts, including the 'test' from the boxed "Soundcard Detection" result in a heavy buzz. No errors in the logs for the driver loads, module loads, device init, or access attempts. No indication that the kernel, drivers, oss/alsa subsystems, or applications have detected anything wrong. Also checked the alsa and vol mixers. And moved the dvd (holding the audio cd) from the audigy digital in to aux and cdin ports, no change. And checked for misplaced dev symlinks and/or oddly configured dev nodes in the various apps. And yes, it works just fine under win2k and os2/warp. Ideas appreciated ....
 
Creative Audigy 2 ZS
Tyan Tiger MPX S2466
Athelon MP 2800+ dual
 
Fedora Core 2 plus bits (below)
alsa-utils-1.0.3-1
alsa-lib-1.0.3a-2
 
Module Size Used by
snd_pcm_oss 45220 0
snd_mixer_oss 17792 3 snd_pcm_oss
snd_emu10k1 77572 3
snd_rawmidi 21792 1 snd_emu10k1
snd_pcm 76420 2 snd_pcm_oss,snd_emu10k1
snd_timer 22404 1 snd_pcm
snd_seq_device 10120 2 snd_emu10k1,snd_rawmidi
snd_ac97_codec 54916 1 snd_emu10k1
snd_page_alloc 12036 2 snd_emu10k1,snd_pcm
snd_util_mem 7168 1 snd_emu10k1
snd_hwdep 10372 1 snd_emu10k1
snd 43876 12 snd_pcm_oss,snd_mixer_oss,snd_emu10k1,snd_rawmidi,snd_pcm,snd_timer,snd_seq_device,snd_ac97_codec,snd_util_mem,snd_hwdep
soundcore 10336 3 snd
 
Additional stuff I've added:
./tv/xaw/v4l-conf-3.73-0.i386.rpm
./tv/xaw/libquicktime-0.9.3-1.1.fc2.fr.i586.rpm
./tv/xaw/tv-fonts-1.1-0_3.rhfc2.at.noarch.rpm
./tv/xaw/zvbi-0.2.8-1.1.fc2.fr.i386.rpm
./tv/xaw/xawtv-3.93-15.rhfc2.at.i386.rpm
./tv/tvtime/tvtime-0.9.12-5.i386.rpm
./wine/wine-20040914-1fc2winehq.athlon.rpm
./tk/tk-devel-8.4.5-8.i386.rpm
./tk/tk-8.4.5-8.i386.rpm
./filesystem/kernel-ntfs-smp-2.6.5-1.358.i686.rpm
./graphics/freeglut-devel-2.2.0-0.11.fr.i386.rpm
./graphics/freeglut-2.2.0-0.11.fr.i386.rpm
./edonkey/edonkeyclc-1.0.2-1.i386.rpm
./edonkey/ed2k-gtk-gui-0.6.3-2.i386.rpm
./video/mplayer/mplayer-1.0-0.10.pre4.1.fc2.fr.i386.rpm
./video/mplayer/lirc-0.6.6-2.1.fc2.fr.i386.rpm
./video/mplayer/libpostproc-1.0-0.10.pre4.1.fc2.fr.i386.rpm
./video/mplayer/mplayer-fonts-1.1-2.fr.noarch.rpm
./video/mplayer/mplayer-skins-1.3-3.fr.noarch.rpm
./video/mplayer/lzo-1.08-3.1.fc2.fr.i386.rpm
./video/mplayer/faad2-2.0-1.1.fc2.fr.i386.rpm
./video/xine/libdvdplay-1.0.1-4.1.fc2.fr.i386.rpm
./video/xine/libdvdcss-1.2.8-4.1.fc2.fr.i386.rpm
./video/xine/libdvdread-0.9.4-5.1.fc2.fr.i386.rpm
./video/xine/libdvdcss-devel-1.2.8-4.1.fc2.fr.i386.rpm
./video/xine/libdvdread-devel-0.9.4-5.1.fc2.fr.i386.rpm
./video/xine/lame-3.96-1.1.fc2.fr.i386.rpm
./video/xine/libmad-0.15.1b-2.1.fc2.fr.i386.rpm
./video/xine/libdvdnav-devel-0.1.9-3.1.fc2.fr.i386.rpm
./video/xine/libdvdplay-devel-1.0.1-4.1.fc2.fr.i386.rpm
./video/xine/xine-0.99.1-1.1.fc2.fr.i386.rpm
./video/xine/xine-lib-devel-1.0.0-0.13.rc4a.1.fc2.fr.i386.rpm
./video/xine/xine-lib-1.0.0-0.13.rc4a.1.fc2.fr.i386.rpm
./video/xine/libdvdnav-0.1.9-3.1.fc2.fr.i386.rpm
./video/common/libfame-devel-0.9.1-1.1.fc2.fr.i386.rpm
./video/common/xvidcore-devel-1.0.0-1.1.fc2.fr.i386.rpm
./video/common/xvidcore-1.0.0-1.1.fc2.fr.i386.rpm
./video/common/aalib-1.4.0-5.1.fc2.fr.i386.rpm
./video/common/libfame-0.9.1-1.1.fc2.fr.i386.rpm
./video/common/aalib-devel-1.4.0-5.1.fc2.fr.i386.rpm
 

I had a problem with my Audigy 2 ZS not working on Fedora Core 3 test 1 (Fedora Core version 2.90).
The solution was to unplug my USB logitech 3000 webcam before booting my system.