Audigy issues with Fedora Core 2

[Beej-in-GA 0]

Greetings All,

I have recently upgraded to Fedora Core 2 from Fedora Core 1. In FC1 to get my sound card to work I would have to go to termminal window and type in at the prompt "emu-config -d" this told the driver (?) to use the digital port instead of the analog ones. When I first Updated to FC2, I would have to run alsamixer as root to un mute it. That worked, but last week, I updated the kernel and now the alsamixer solution doesn't work any more and running the previous kernel from the grub bootloader doesn't help. Can anybody help with this. The card works fine in Windows XP Home edition. How can I fix this? Thanks for your help. If you need more info to help, please ask, I am very new and not a programmer. Thanks for your time.

Best Regards,

Beej

[danleff 0]

Let's start with the basics. How did you upgrade the kernel, by "source" (using a kernel from kernel.org) or by up2date (Redhat Network)?

[Beej-in-GA 0]

Originally posted by danleff:

Quote:

Let's start with the basics. How did you upgrade the kernel, by "source" (using a kernel from kernel.org) or by up2date (Redhat Network)?

 

Hi Danleff,

I updated using the Up2date (Redhat Network) so the kernel is now 2.6.7-1.494.2.2 (I think) It gets hard to keep the numbers straight sometimes. It really is a pain to get older and slower. And should you need it, Windows and Fedora are on separate drives. As I said I am not a programmer and wouldn't know how to compile a kernel from source if my life depended on it. Any suggestions for a book to read about this stuff? I have been looking for one, but everything seems to stop short of where I need to go.

Thanks,

Beej

[Dapper Dan 0]

Hi Beej,

 

I understand your frustration. We live in a Windows world, and as Linux users have to know ten times as much, and in many cases, have to work ten times as hard to configure hardware for our OS of choice.

 

By the way, a lot of us here are (relatively) old men, so we certainly can empathize with the forgetfulness part! I'm 47.

 

[Beej-in-GA 0]

Originally posted by Dapper Dan:

Quote:

Hi Beej,

 

I understand your frustration. We live in a Windows world, and as Linux users have to know ten times as much, and in many cases, have to work ten times as hard to configure hardware for our OS of choice.

 

By the way, a lot of us here are (relatively) old men, so we certainly can empathize with the forgetfulness part! I'm 47.

 

Hi Dapper Dan,

It is good to know that I am in good company. Thanks for the post. Have fun the next three years. I turned 50 in April, in June my doctor gave me my "Birthday Present". The PSA came back clean. I really hate that.

Have you any suggestions for a book to buy? I already have the "Official Fedora Companion" by Nick Presley. Doesn't go much beyond installation it appears so far, but I got it for only 10 bucks. That's like half price so half way is about all I should expect I reckon.

Any tips on the SB Live! Audigy Platinum problem?

Later,

Beej

 

"Molon Labe!" (Come, take them!)

Leonidas of Sparta to Xerxes of Persia @ Thermopolae

[Beej-in-GA 0]

Originally posted by danleff:

Quote:

Let's start with the basics. How did you upgrade the kernel, by "source" (using a kernel from kernel.org) or by up2date (Redhat Network)?

 

Howdy All,

There is news on this issue. I updated the kernel to 2.6.8-1.521 using red hat network Up2date and then I did the following:

How I turned on Sound card. (SB Live! Audigy Platinum)

BY

Beej Smith

 

Using Kernel 2.6.8-1.521

 

1.First I opened Volume control in “Systray” and ensured that all listed settings were unlocked.

2. Then I opened a terminal window from the Fedora/System Tools menu and typed su at the prompt.

3.Entered “root” password at the prompt.

4. typed “alsamixer” at the prompt and un-muted the following.

A. Tone

B. Audigy Analog/digital Output Jack

5. Increased the following to Max Settings

A. Audigy CD

B. Audigy Capture

C. Front

D. CD

E. Center

F. Music

G. Surround

H. PCM Center

I. PCM Surround

J. PCM Front

K. PCM LFE

6. It is unknown to me Whether it was necessary to set all of these to max or 100 per cent, but I did it.

7. Then I detected sound card and played the test sound and it worked.

Can anyone tell me how set up something that will make this happen at boot up for all accounts which are at present only Root and my user account set up at installation.

Any further comments would be gratefully welcome. Thanks.

Later,

Beej

 

[Dapper Dan 0]

I wish I could help you Beej, but don't have an Audigy to play with. There should be someone here who can help you with this if we can keep this thread live long enough for them to see it...

 

 

[martouf 0]

DDan: it isn't a 'having or not having' Audigy problem.

 

it's an ALSA driver and system configuration problem.

 

beej: be root and use 'alsactl store' so save a config (levels, too)

you are happy with...

 

read all about it here and here.

 

 

[Beej-in-GA 0]

Originally posted by Dapper Dan:

Quote:

I wish I could help you Beej, but don't have an Audigy to play with. There should be someone here who can help you with this if we can keep this thread live long enough for them to see it...

 

Hey DDan,

Thanks for the reply and the effort to keep this thread visible. I think it worked. See Martouf's post below your own and my reply. I think what I say to him will be entertaining and give everyone a good laugh, due to my inexperience. I have never been bothered by the laughter of others at my expense. It is the price of learning, no? One should learn that they are not laughing at you but at themselves and *with* you. They were once where I am now. My hide is thick, I have a good sense of humor. ;-D

Later,

Beej

[Beej-in-GA 0]

Originally posted by martouf:

Quote:

DDan: it isn't a 'having or not having' Audigy problem.

 

it's an ALSA driver and system configuration problem.

 

beej: be root and use 'alsactl store' so save a config (levels, too)

you are happy with...

 

read all about it here and here.

 

 

Hi Martouf,

I went to both of the places you suggested and printed out the references to have handy when I boot up FC2 next. I assume that I go through the procedure I have found that makes the card operable, then use the alsactl thing to store or save the settings I work out, right? Also, then do I type everything between the # (pound sign) and --ignore- listed under kernel 2.6 in the second (alsa.opensrc.org) reference exactly as it appears making the appropriate sopund driver change? Sorry to be so thick, but I am new to this and don't know the syntax I need to use. Thank you for your patience and your time in helping me out here.

Best Regards,

Beej

[danleff 0]

The reason I asked about the kernel upgrade, is that when you use a new kernel from "source" (meaning that you build it from scratch) then I would expect you might run into issues. Not from an "up2date" update! This should not happen, but someone should post a solution when it becomes apparent, Too many people have these cards.

 

You should not be having this issue. But I will keep my eyes open to see what thers have experienced.

 

Martouf should be able to guide you through the steps.

 

Martouf please be gentle! Remember, with knowledge comes great responsibility...

 

Beej, I'm 48 and I'm glad there is someone older than me on this forum!

[Beej-in-GA 0]

Originally posted by martouf:

Quote:

DDan: it isn't a 'having or not having' Audigy problem.

 

it's an ALSA driver and system configuration problem.

 

beej: be root and use 'alsactl store' so save a config (levels, too)

you are happy with...

 

read all about it here and here.

 

Hi Martouf,

Okay, this is what is happening at the present time:

When I boot up as root, I go through the procedure I mentioned in the long post I made. Then I tested the card to see if I get sound. I did so then I opened a terminal window (still in root) and typed this "alsactl store" (without quotes) and hit return. It returned me to a root prompt. No acknowledgement as to whether the command had been accepted or not. I then closed the terminal window retested the card and logged out as root and in as my regular user account (beej). As beej I tested card to verify that I had sound and yes I do. Okay!!! Acid test time! I reboot computer. Logged in as beej and detected tested sound card, no sound. No Problemo, go through the "procedure" and then retest card, all is well. Then I reopened a terminal window type in su to go root and then the password and then at the root prompt, I type in "alsactl -h" and that returned "bash: alsactl : command not found". However, when I typed in "man alsactl" I get the manual listing that looks very similar to the listing on the web that you linked to. Is there some procedural error I am making here? Any clues. How do I enter the command as root to get it to take? The Manual says that I must use the formula "alsactl [options] [store|restore] <card # or ID>". Is there a tool in FC2 similar to device manager in Windows so that I can see what the Card number or ID might be? I don't seem to find any listed in the gnome desktop here. Any clues? Thanks for your help.

Later,

Beej

[Beej-in-GA 0]

Originally posted by danleff:

Quote:

The reason I asked about the kernel upgrade, is that when you use a new kernel from "source" (meaning that you build it from scratch) then I would expect you might run into issues. Not from an "up2date" update! This should not happen, but someone should post a solution when it becomes apparent, Too many people have these cards.

 

You should not be having this issue. But I will keep my eyes open to see what thers have experienced.

 

Martouf should be able to guide you through the steps.

 

Martouf please be gentle! Remember, with knowledge comes great responsibility...

 

Beej, I'm 48 and I'm glad there is someone older than me on this forum!

 

I think there is likely to be nore of us more senior types as time and disgust accumulates towards the crap from Redmon. But who knows for sure. I am very grateful for all the help from folks here and the friendly nature of it, as well. Thanks for the reply by the way.

Later,

Beej

 

[martouf 0]

beej, glad to see you're hanging in there...

 

you're on the right track. give yourself plus points.

 

I've been busy elsewhere with ndiswrapper issues (v0.9 and later)

so I haven't been 'round to follow along with every step.

 

believe me, I'm not having a laugh at anyone's expense.

 

if the name of the stored configuration is not specified, then the file

/etc/asound.state will be used to store or restore your card's config.

 

the card number need not be specified if you only have one sound card.

 

for example, SuSE 9.1 does "/usr/sbin/alsactl -f /etc/asound.state store"

when init invokes "/etc/init.d/alsasound stop",

and "/usr/sbin/alsactl -F -f /etc/asound.state restore" when init

invokes "/etc/init.d/alsasound start".

 

yours should do likewise, too.

 

if (as root) you get "not found" for "alsactl", it means "/usr/sbin" is not

in the PATH environment variable (envar). Check with "echo $PATH".

 

check contents of /etc/asound.state with "more /etc/asound.state"

and "ls -l /etc/asound.state".

 

once you've set all of your Audigy controls the way you like them,

then 'alsactl store' should save them for use later. Once stored,

'alsactl -F restore' should restore all of controls the way you set them.

 

you'll likely find the contents of asound.state mostly human readable (mostly harmless?),

with all of the controls you adjusted named and with suitable values.

 

I realize I may seem a bit "throw 'em in the deep end", but honestly,

I'm dropping you in right by the edge of the pool. 8)

 

[Beej-in-GA 0]

Originally posted by martouf:

Quote:

beej, glad to see you're hanging in there...

 

you're on the right track. give yourself plus points.

 

<snip>

if the name of the stored configuration is not specified, then the file

/etc/asound.state will be used to store or restore your card's config.

 

the card number need not be specified if you only have one sound card.

 

<Beej>

Okay, that is helpful! BTW the asound.state file is as it should be with the changes I made to it. I could look at it in my user acct. There is a sound card built in to my P4C800-E mobo, but it is disabled in bios.

 

<Martouf>

for example, SuSE 9.1 does "/usr/sbin/alsactl -f /etc/asound.state store"

when init invokes "/etc/init.d/alsasound stop",

and "/usr/sbin/alsactl -F -f /etc/asound.state restore" when init

invokes "/etc/init.d/alsasound start".

 

yours should do likewise, too.

 

 

if (as root) you get "not found" for "alsactl", it means "/usr/sbin" is not

in the PATH environment variable (envar). Check with "echo $PATH".

 

<BEEJ>

Logged in ROOT ACCOUNT it is there in path, but not as BEEJ account, even as su. Don't know how to fix this. It seems to me that as beej with su (in terminal) I could do about anything before.

 

<Martouf>

check contents of /etc/asound.state with "more /etc/asound.state"

and "ls -l /etc/asound.state".

 

<BEEJ>

This works in beej account and is correct as stated previously.

 

<Martouf>

once you've set all of your Audigy controls the way you like them,

then 'alsactl store' should save them for use later. Once stored,

'alsactl -F restore' should restore all of controls the way you set them.

 

<BEEJ>

Yes, again, when I log in as ROOT Account I can go into a terminal window ad do this and it works. Thanks for the explanation. Now I understand what to do. However, I still cannot access this command in the terminal logged in to the BEEJ account. So at present the sequence is this: Log in as root open terminal window use alsactl command log out and back in as BEEJ and sound card works. Still seems awkward but will suffice until I can figure a better way.

 

<Martouf>

you'll likely find the contents of asound.state mostly human readable (mostly harmless?),

with all of the controls you adjusted named and with suitable values.

 

 

I realize I may seem a bit "throw 'em in the deep end", but honestly,

I'm dropping you in right by the edge of the pool. 8)

 

<BEEJ>

Yes, I found the asound.state file almost a breeze to read. Long though. Lots and lots of PCM send volume settings to get through. Sorry to seem so thick, but I seem to have slowed down a might in the last few years. You aren't being any harder on me now than Dad was when he taught me to swim. It was easy once I got out of the bag of big rocks.

 

I really do want to thank you for your help and patience here. Could you recommend a book that will teach some of this stuff. I have looked around at some of the college sites around here for a listing of a Linux Class, but no jo7y. My thought was to find a course and then ask at the school book store for the course book. Probably the long way round, but hey, worth a shot, no?

Later,

Beej

[martouf 0]

glad to hear the burlap had a touch of dry rot

 

what?! 'thick'? no way! (really, no way!)

 

you've been at this for what? 5 days (clock time)?

 

you want me to tell you about fussing with a HP 6340 Pavillion

with its almost-but-not-quite Soundblaster 5 plug-n-pray sound chip?

for three weeks?

 

"A mind once expanded by a new idea, never returns to its original shape."

-- Oliver Wendell Holmes

(the quote is quite likely paraphrased)

 

hmm.. does that go for waistlines, too? :x

 

say, what's the output of 'cat /proc/asound/cards'?

and do you have a /etc/init.d/alsasound file?

 

the 'root' that is init should do the card restoration automagically

during the boot process. You're doing manually what should be happening

without your intervention.

 

also, try 'su - root' instead of simply 'su' and check the PATH envar.

I'll gladly explain if you note a difference.

 

[danleff 0]

ahh...yes.those HP, Gateway and Dell SB "legacy" cards. Still have not found mine to look at. Can you say frustration!

[martouf 0]

card, I wish. naww, onboard PnP chip - can you imagine?!

 

[Beej-in-GA 0]

Originally posted by martouf:

Quote:

glad to hear the burlap had a touch of dry rot

 

what?! 'thick'? no way! (really, no way!)

 

you've been at this for what? 5 days (clock time)?

 

you want me to tell you about fussing with a HP 6340 Pavillion

with its almost-but-not-quite Soundblaster 5 plug-n-pray sound chip?

for three weeks?

 

"A mind once expanded by a new idea, never returns to its original shape."

-- Oliver Wendell Holmes

(the quote is quite likely paraphrased)

 

hmm.. does that go for waistlines, too? :x

 

say, what's the output of 'cat /proc/asound/cards'?

and do you have a /etc/init.d/alsasound file?

 

the 'root' that is init should do the card restoration automagically

during the boot process. You're doing manually what should be happening

without your intervention.

 

also, try 'su - root' instead of simply 'su' and check the PATH envar.

I'll gladly explain if you note a difference.

 

Hi Martouf,

Okay some changes here! First I shall answer your questions, or rather, the ones I can understand.

Your quote that you paraphrased, most assuredly does not go for waistlines. Waistlines are never affected by ideas but rather by the intake of calories and the expenditure thereof afterwards. I have ample evidence existing here. Further, as age increases, the exercise needed to expend those acquired calories increases exponentially. So sayrth the wise Cardilologist. The one who takes my and my insurance companies money. Me I am just an electrician.

 

I have tried to find the things you asked about. Here goes:

 

The cat gives:

[beej@rapid_roy beej]$ cat /proc/asound/cards

0 [Audigy ]: Audigy - Sound Blaster Audigy

Sound Blaster Audigy (rev.3) at 0xdf80, irq 11

 

There is no alsasound file in the directory you asked about, though the directories do indeed exist. Should there be some file like that? If so can I create it, how, and what should it say? Hint: Put I need to type in quotes, I understand to remove the quotes.

 

As Regular User the $PATH yields:

[beej@rapid_roy beej]$ echo $PATH

/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/home/beej/bin

 

after using the su - root it yields:

/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/root/bin

 

I do indeed notice the difference. Can I infer from this that the command is referencing a different path statement that the root account has access to that the beej account does not? Is the /etc/init.d directory common to both accounts? I do not find it duplicated so it would seem it must be. Unless it is hidden somehow and I thought that Linux didn't do that the way Dos and Windows did. Gods above, below , and to the sides, I wish there was a course available for this stuff. It would be worth the price of admission to just have the knowledge whether I wanted to use it or no. I took French and German in High School, and then wound up in Asia in the PI when I was a sailor. In the PATH statement above for the root I see several sbin references, what are they? And what does sbin mean? Bin means Binary, right?

Oh well, I guess I had better stop and let you fill me in. Perhaps it will become clearer after I read your answer. Oh and, as you knew it would, after using the su - root command the alsactl command worked no worries.

 

Thanks again for all your help. And while I haven't been at this particular problem for long, you dont know how long I have been charging at this brickwall (Linux in general) before I tumbled on to this forum. One of my "Friends" suggested I try it as an aside in casual conversation. Coming here has been very like having found the matches after discovering the candle is in the holder. A huge relief to have light.

[martouf 0]

it's too bad that waistlines, once expanded, never quite return

to their original shape.

 

actually, there are courses for this stuff.

prep work for the RHCT certification would do.

there's also a very fine "LPI Linux Certification" book from O'Reilly.

 

getting back to the sound card:

 

$ cat /proc/asound/cards

0 [Audigy ]: Audigy - Sound Blaster Audigy

Sound Blaster Audigy (rev.3) at 0xdf80, irq 11

 

^^ means only one sound card was detected during startup and a driver has

been loaded for it.

 

the initial '0' is the Card ID#, which isn't all that important now that it's

proved there is but one card. If two had been detected, that could have caused

the automagic config restore to fail.

 

the difference between 'su' and 'su - root' is the former gives you the privilege

of root but with the envars (PATH is one of them) set to a default,

while the latter sets up the environment the same as logging in as root.

(you get the environ and privilege with 'su - root', only the privilege

with 'su')

 

I went on a file hunt in the Fedora Core 2 mirrors, looking for the package

which should have provided you the /etc/init.d script for saving and restoring

your sound card setup. I looked at 'alsa-lib', 'alsa-utils', 'alsa-lib-devel'

and 'initscripts'. No joy. ;(

 

Would you tell me what you get when you run:

"rpm -qf /etc/init.d/alsasound"

 

anyone reading this: if you are running FC2, please see if you have an

'alsasound' (or 'sound' or 'soundcard') init script, run the rpm cmd using the

full name of the script, and post results here.

 

see, I'm wondering at this point, has a soundcard system config step gotten

skipped? or has the installation of one of the FC2 packages gone wrong?

 

I'd like to figure that out before creating a unique/custom solution

applicable only to your system.

 

[Beej-in-GA 0]

Originally posted by martouf:

Quote:

it's too bad that waistlines, once expanded, never quite return

to their original shape.

 

actually, there are courses for this stuff.

prep work for the RHCT certification would do.

there's also a very fine "LPI Linux Certification" book from O'Reilly.

 

getting back to the sound card:

 

$ cat /proc/asound/cards

0 [Audigy ]: Audigy - Sound Blaster Audigy

Sound Blaster Audigy (rev.3) at 0xdf80, irq 11

 

^^ means only one sound card was detected during startup and a driver has

been loaded for it.

 

the initial '0' is the Card ID#, which isn't all that important now that it's

proved there is but one card. If two had been detected, that could have caused

the automagic config restore to fail.

 

the difference between 'su' and 'su - root' is the former gives you the privilege

of root but with the envars (PATH is one of them) set to a default,

while the latter sets up the environment the same as logging in as root.

(you get the environ and privilege with 'su - root', only the privilege

with 'su')

 

I went on a file hunt in the Fedora Core 2 mirrors, looking for the package

which should have provided you the /etc/init.d script for saving and restoring

your sound card setup. I looked at 'alsa-lib', 'alsa-utils', 'alsa-lib-devel'

and 'initscripts'. No joy. ;(

 

Would you tell me what you get when you run:

"rpm -qf /etc/init.d/alsasound"

 

anyone reading this: if you are running FC2, please see if you have an

'alsasound' (or 'sound' or 'soundcard') init script, run the rpm cmd using the

full name of the script, and post results here.

 

see, I'm wondering at this point, has a soundcard system config step gotten

skipped? or has the installation of one of the FC2 packages gone wrong?

 

I'd like to figure that out before creating a unique/custom solution

applicable only to your system.

 

Hi Martouf,

Here is the results of the query you asked me to run:

 

[root@rapid_roy root]# rpm -qf /etc/init.d/alsasound

error: file /etc/init.d/alsasound: No such file or directory

 

As I said yesterday, this file does not exist, though the directories /etc/init.d does exist. And, according to what I can tell, there seems to be no file there that makes reference in the name to Creative or CL, SoundBlaster or SB, Live or Audigy. Nor is there anything with an obvious connect to a sound card in evidence. Though, truth to tell, I probably wouldn't know it if it bit me on the bum. I see what you mean, I think. Is this correct? When I made changes to the Alsamixer and then stored those changes with the alsactl store command. Then a file should have been setup calling for a check of the asound.state file during the boot up sequence. Such a file would be called a script, right? But how would that file have been made unless I made it myself, which I did not. Mainly because I don't know how. Or should maybe there should be a reference to the alsactl command or asound.state in the /etc/modprobe.conf file?

 

Thanks for the info on the book. I'll look into it. I will also look into the course you mentioned. Any idea as to which sort of school would teach such a course. I would think it would be one of the tech related schools, but not necessarily some place like Georgia Tech. More probably DeVry or something, yes? By the way, I have taken to copying and pasting the posts in this thread in a file in Open Office. It will make a good study in how to troubleshoot a problem in Fedora/Linux. I am preparing a page for me web site called Linux Adventures which will be a sort of this is what I ran into and how with help from others the bugs were ironed out kind of thing. I probably will not use direct quotes but will paraphrase if you don't mind.

 

Best Regards,

Beej

[martouf 0]

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 temp

cp /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

[/color]

 

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

[/color]

YMMV: need to find your existing 'snd-card' lines to figure out

what 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/S12alsasound

ln -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

[/color]

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

 

 

[Beej-in-GA 0]

Originally posted by martouf:

Quote:

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.

<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 temp

cp /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

[/color]

 

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.

[Beej-in-GA 0]

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]

 

[Beej-in-GA 0]

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