ALSA problems with ES1869
 

Hi, I recently downloaded ALSA with the most up to date drivers. I have an ES1869 and have been unable to find a driver for it, so I decided to give ALSA a try. My card isn't specially given a listing on the page, but ES18xx is, so I'm assuming that means it can support my ES1869. Here is a link to the instructions I was given.
http://www.alsa-project.org/alsa-doc...&module=es18xx

Everything worked perfectly until I reached the modprobe part. Then I recieved this error:

[root@localhost calimer]# modprobe snd-es18xx;modprobe snd-pcm-oss;modprobe snd-mixer-oss;modprobe snd-seq-oss
/lib/modules/2.4.20-8/kernel/sound/acore/snd.o: unresolved symbol schedule_work
/lib/modules/2.4.20-8/kernel/sound/acore/snd.o: insmod /lib/modules/2.4.20-8/kernel/sound/acore/snd.o failed
/lib/modules/2.4.20-8/kernel/sound/acore/snd.o: insmod snd-es18xx failed
/lib/modules/2.4.20-8/kernel/sound/acore/snd.o: unresolved symbol schedule_work
/lib/modules/2.4.20-8/kernel/sound/acore/snd.o: insmod /lib/modules/2.4.20-8/kernel/sound/acore/snd.o failed
/lib/modules/2.4.20-8/kernel/sound/acore/snd.o: insmod snd-pcm-oss failed
/lib/modules/2.4.20-8/kernel/sound/acore/snd.o: unresolved symbol schedule_work
/lib/modules/2.4.20-8/kernel/sound/acore/snd.o: insmod /lib/modules/2.4.20-8/kernel/sound/acore/snd.o failed
/lib/modules/2.4.20-8/kernel/sound/acore/snd.o: insmod snd-mixer-oss failed
/lib/modules/2.4.20-8/kernel/sound/acore/snd.o: unresolved symbol schedule_work
/lib/modules/2.4.20-8/kernel/sound/acore/snd.o: insmod /lib/modules/2.4.20-8/kernel/sound/acore/snd.o failed
/lib/modules/2.4.20-8/kernel/sound/acore/snd.o: insmod snd-seq-oss failed

I have no idea what any of that means, so if anyone can help me out I would really appreciate it. Thank you for your time.
-calimer

i've had trouble like that all the time compiling alsa
seperately. i think sometimes if you have similar
modules compiled in your kernel, the alsa ones won't
work.
you could get a patch like Con Kolivas's low latency
kernel patch, which also has alsa support. that way
you could compile alsa directly partched into the kernel,
and it works better that way.
you'll still need the alsa tools and stuff though.

I was searching the web during class and I came across this link.
http://sourceforge.net/mailarchive/f...&forum_id=1751
Figured you might be interested in it, haven't tried it yet though. What exactly does the "low latency" mean in the low latency kernal patch, as in, how does the "low latency" affect it? Thank you for your time.
-calimer

a low latency kernel is supposed to make a desktop
system much more responsive, and just hurts a little
bit in overall system thruput. The system is more
to programs that wait for user input, and programs
that use sound and video are much less likely to skip.
That Con Kolivas patch or set of patches just happens
to include alsa.

Okay, thanks, I'm going to try to install the kernel patch. I tried some of the things that page I linked you with said, but I couldn't get them to work. I downloaded that one update rpm but didn't know how to get the
"apt-get update
apt-get install alsa-lib alsa-lib-devel alsa-utils alsa-driver
gnome-alsamixer"

lines to work because when I ran it in the terminal it didn't work, and the "run command" couldn't run them either, hmm. I am a little unsure though how exactly I'm supposed to install that kernel patch. I assume that I have to unzip it, but after that I'm not sure exactly what command to run. If you have the time and can point in the right direction I would really appreciate it, but if not don't worry about it. Thank you so much for the time you've already spent helping me out. Take care.
-calimer

usually you patch something like this
gzip -cd filename.gz | patch -d directorytopatch -p1

Thank you so much for all the help you've given me, I really appreciate it. I'm assuming I would want to patch to the /usr/src/2.4.20-8 directory. I think that's the directory anyway. I'm on windows (unfortunately) right now, until I get my modem working as well, so I can't check the exact folder. Take care.
-calimer

i wouldn't be suprised if that patch wouldn't apply
cleanly to to the redhat source. you might have to
have clean kernel source from a www.kernel.org
mirror. i looked at the con kolivas page and i couldn't
tell if alsa was included in hte 2.4.20 kernel patch.
alsa may also be in the alan cox series kernels too,
but i can't remember for sure.

Yeah, I wasn't sure if ALSA was in the patch either, but it seems like it is because the bottom of the .19 section of downloads it says what was used to help create the .20/.19 patches, and ALSA was one of the links given. Due to my extreme newb nature I think I will probably fool around with a "clean" kernel as a last resort. I'm too worried about losing features that came with the redhat kernel and stuff like that. I really need to learn all this stuff but well, I've only had linux on here for a few days so I can't learn all this stuff at once. Thank you so much for all the help that you've given me already, it's so helpful. Have a good night.
-calimer
PS I'm going to try to see if I can do something with those rpms at "freshrpms" or whatever it is, they seem to have helped others so maybe they help me as well.

Trying to load ALSA from rpms didn't seem to work. Although this may be because I have to uninstall the original alsa stuff that I had installed? Not sure exactly how to even do that. Also I tried to install the rpms by double clicking on them, and they said they were updating my system, but I still don't have sound. Any help would be greatly appreciated.
-calimer
PS there are the exact rpms I tried to install
alsa-kernel-0.9.2-fr2_2.4.20_8.i586.rpm
alsa-driver-0.9.2-fr2.i386.rpm
alsa-lib-0.9.2-fr2.i386.rpm
alsa-utils-0.9.2-fr2.i386.rpm
xmms-mp3-1.2.7-21.p.i386.rpm

what is the fr in the alsa name for?
french?
you wouldn't just have sound automatically.
you would have to modeprobe the right
modules for your card, and with alsa, when it
does start working, it leaves all the mixer settings
muted, so you have to use a mixer to turn the
sound up.

follow the modprobe instructions you had from your
first post.

Don't know what the fr stands for, that's just what it said in the file names. I didn't have language options though, just architecture and version options. I tried to do another modprobe like you said, but I think the previously installed tar files were what was attempted to be loaded, and that's not what I want. I don't know how to uninstall those tar files though or what I can do about that. Also, I'm not exactly sure how to unmute my mixer. I'm using KDE and I loaded the mixer in the control panel but it doesn't give me unmute options. I do shift the volume on aurun or whatever that media player is, but not sure if that unmuting it or not. Also, I added in the /ect/module.conf what I was asked to in the installation page, but still no luck. I'm thinking that I really need to get rid of the tar stuff and maybe even try to reinstall the rpms. Any advice would be great. Thank you for your time.
-calimer

by muted, i just meant the volume all the way down.

Ahh, okay. I did see that ALSA says by default they are muted but I wasn't sure if you needed to "unmute" something, or if rasing the volume would take care of that, hmm. Well, it seems like I ALMOST have it in gear except the loading it into the kernel deal. Would deleting the folders that I created for the tar files help? I don't know how to cleanly uninstall a tar file, hmm. Another thing i don't get is why don't linux OS already come with ALSA, especially at how many sound cards it supports? Seems strange to me, especially since it seems like such an incredible useful resource.
-calimer

It's Linus' choice. I guess it wouldn't be called alsa
if it was the default. alsa ( alternative sound something).
The more stuff in the default kernel, the more stuff Linus
has to test himself.
You could probably download the stock kernel, and an
alsa patch, and save your current kernel config. It's in the
top of your kernel source directory, called .config, then
load the config into the new source and compile.
A tar file may or may not have an install. It's just really
some "zipped up" files anyway. More often than not,
you can run make uninstall in the directory and it will
uninstall. It just depends on the package. In Linux
uninstall just means deletes the files it installed. If
running the program creates settings files in your
home directory, those will not be deleted. One thing
I love about linux software, is that if you want it to act
like it was just installed, you just delete the config files
in your home directory. In windows, you uninstall, then
reinstall, and hope that fixes the problem.
Anyway, you don't have to uninstall your redhat kernel,
or the source to install another. You can keep the source
in a different directory, and the kernel modules will install
in a different directory too. Just change your old kernel
to a new name, and change the name of the link in
your bootloader, lilo or grub, then add an entry for your
new stuff. That way you will not mess up your working
kernel, and you can spend some spare time trying to
get your new kernel working