well you got them in there after all eh - Yeah I think you are still using your old driver. I would go ahead and do a clean reinstall then - or even just clean all the audio modules and reinstall only alsa. Should be ok since you know you can get the modules back in later.

PS - you may want to write them down so you can insert them later.

Good one.

I think I'll just clean all the audio modules and reinstall alsa and see what happens, before I do something really drastic like go back to Windows (just kidding, really )

To all: thanks for your patient help. You have helped me learn much more than I knew before!

Peace . . .

That's cool - it's the only way to learn - patience.
Keep the winbox as a backup until you get the hang of it - you will be surprized how quickly linux comes to you. Just gotta learn it.
Anyway

Peace to you too - and dont forget the *afferos [ I just graduated from a newbie sometime recently - woo-hoo heh heh heh ]

Peace

Well, after spending most of the day with ALSA, I am very happy to share that it is up and running and sounds much better than the other driver (when I test the sound with the sound configuration tool the guitar doesn't crackle anymore). I unstalled my i810_audio driver, cleaned out ALSA and reinstalled ALSA.

Now flash audio is not chipmunky (which was the initial problem that got me into ALSA). However, it is still a little choppy as though the sound has to catch up with the video. I turned on ARTS to change the frequency from 48000 kH, but then flash audio wouldn't play at all. Turned off ARTS and flash audio is back.

One, hopefully final, question, how does one go about tweaking the sound frequency without going through ARTS. I am thinking that might make a difference with flash.

I cannot thank you enough for helping me get ALSA installed. A truly learning experience.

Peace . . .

(a very happy) penguinsrcool

Nice one! Brilliant!
At that point - I found alot of the sound was still being played thru the OSS drivers. I did not look too much into changing the frequency from 48khz as it resolved itself after installing the soundblaster live 5.1 card [which I knew would do it]. Certain 3D games had no sound but others did. Everything seemed to work after installing sb live - except oddly enough quake3 now had now sound and it did before sblive - I installed aglaophone that runs off the alsa drivers - which it turned out I cannot really use anyway but it's installed - now quake worked ha hah ha. go figure.

I am curious - are you able to bring up "alsamixer" ? For some reason I still get this error:
function snd_ctl_open failed for default: No such file or directory
- I am pretty optimistic that having installed the SB live 5.1 card if I removed and reinstalled ALSA from scratch it may well work - but I can't be bothered. I might do that later on sometime If I need a better mixer.

penguin i have the same problem, but i don't know how tu uninstall all sound drivers - how do you do that?
i'll have no problems reinstalling it (i did it 3-4 times)...
this seems to be the solution to one of the most often problems with linux -HELP ME PLEASE!!!!

here I posted this in another thread:

NB to uninstall ALSA in order to reinstall:

[I open two consoles both as root I run the search on one console and remove the files with the other with the other - copy and paste is really handy here].

#run a search for anything with "alsa" in it:
find / -name "*alsa*"

~ IMPORTANT ~
On my system Red Hat installed a program called Balsa - dont remove any Balsa related files. If in doubt leave them. I left all the help files and man pages index.html pages etc as they are not important to remove. If in doubt leave them.

copy the location of the alsa related files by selecting the text [this will copy in linux]

go to your other terminal

rm -rf and then paste by clicking your mouse scroller

it should look something like

rm -rf /usr/location/location/alsa folder

go thru all the alsa locations

[back to the search terminal]

type

lsmod

this is to show all the modules

remove the snd modules on the other terminal by

modules -R snd-whatever

when you have gotten everything you have an alsa free system - relatively.

Hope these instructions are not too confusing

mossy

mossy,

Regarding alsamixer and the error, "function snd_ctl_open failed for default: No such file or directory", I got the same error.

I found in another forum an answer which worked for me. In your alsa-driver directory there should be a script "snddevices." I ran the script ./snddevices and alsamixer worked.

For more info see the following link where I found the solution: http://www.music.columbia.edu/piperm...ly/005671.html

Hope this helps.

Nechos: I basically did what mossy did to remove all alsa stuff before reinstalling alsa. I located my original sound driver (i810_audio) in /usr/src/linux-2.4.20-20.9/drivers/sound and removed it before installing alsa. (Got that idea from mossy.)

As always, note where you remove drivers just in case they need to be reinstalled.

Peace . . .

penguinsrcool

ha ha ha ha ha it worked!
THANKS!!!

hey penguinsrcool -

just though i'd let you know about this - check this filesharing program out:

http://gift.sourceforge.net/
daemon:
download it here if your insterested: http://heanet.dl.sourceforge.net/sou...-0.11.4.tar.gz
fontend:
you will need a [giFToxic link below] frontend for the daemon:

http://heanet.dl.sourceforge.net/sou...c-0.0.9.tar.gz

it didn't work for me!!! why?!?
i couldn't edit modules.conf - couldn't save, don't know why. could that be ther reason?
tried to run those modprobes - it said: failed...what am i doing wrong?!?

I use vi/vim to edit my dox -

copy your addition straight out of the instructions [ just highlighting it will do this in linux]
go to the correct directory where the file is...type:
vi modules.conf
press i for insert mode..
paste your addition to the file at the bottom [pressing your scroller down will do this in linux]
press w to write [save]
press q to quit
see man vi or vi --help

show me exactly what you are typing when trying to insert the modules and are you root?

# ALSA portion
alias char-major-116 snd
alias snd-card-0 snd-intel8x0
# module options should go here

# OSS/Free portion
alias char-major-14 soundcore
alias sound-slot-0 snd-card-0

# card #1
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss


yes, i was root. i tried this a couple of times and now when i vi modules.conf it says:
E325: ATTENTION
Found a swap file by the name ".modules.conf.swp"
owned by: root dated: Sun Sep 28 14:31:19 2003
file name: /etc/modules.conf
modified: YES
user name: root host name: localhost
process ID: 2097
While opening file "modules.conf"
dated: Mon Sep 29 01:05:45 2003
NEWER than swap file!

(1) Another program may be editing the same file.
If this is the case, be careful not to end up with two
different instances of the same file when making changes.
Quit, or continue with caution.

(2) An edit session for this file crashed.
If this is the case, use ":recover" or "vim -r modules.conf"
to recover the changes (see ":help recovery").
If you did this already, delete the swap file ".modules.conf.swp"
to avoid this message.

Swap file ".modules.conf.swp" already exists!
[O]pen Read-Only, (E)dit anyway, (R)ecover, (Q)uit, (D)elete it:

I would copy the file somewhere safe first.

did you close the file after your first attempts to edit it?

hmm Im not sure what you may have done to get that.

are there more than one versions listed [or with a .swp extention?]
if not then just to be safe I would prolly just copy the original somewhere safe and reboot the pc - well just log out completely - that would close any other instances of you editing the file if that's whats going on. [?]

the thing is, every time i tied to save the changes, it would block on 'recording' so i had to do 'quit session' - wich automatically created a temporary modules.conf file. now i can't delete it...
btw - that was the message AFTER i rebooted the system...
should i reinstall mdk for the third time?!?
why wouldn't it save? modules.conf, i mean.