redhat 8 rear speaker issues
 

I realize this is a slightly old topic, but I'm really very new to linux (that is, I've had it installed for only a couple days) and had trouble following the other threads. Anyways, I recently set up Red Hat 8 in a dual-boot environment. I have a Soundblaster Live! and 4.1 speakers. Linux detected the SB Live without any trouble, but it does not output to the rear speakers. So if somebody could tell me, from the beginning, how to go about correcting this, it would be much appreciated. I looked at the ALSA page but didn't quite understand how it worked. And please, nothing about how I should install Mandrake 9, because I had it installed before RH8, and it froze up on boot about 80% of the time, and when it actually managed to boot, it always froze on shutdown :) But anyways, any help us very much appreciated.

-another Jason

Do a sourceforge search for emutools. This is a little script/app that adds functionality and configurability to the emu10k1 driver (the one that runs the SB Live!)

Ok, I downloaded the emu tools and unpacked the .tgz file. the problem now is that the directions given simply aren't working. This is what it tells me to do:

untar this package, enter the directory and make. i.e. :

tar zxfv emu-tools-XXX.tar.gz
cd emu-tools-XXX.tar.gz
make

It then says to log in as root and type "make install."

So first of all, the second line doesn't work because there is no directory that fits (I realize that XXX are the appropriate numbers). It created three directories in the one where I unpacked it, called "usr" "install" and "etc-incoming." So my question is where do I go for the first "make" command, and where should I be for the "make install" command? A little while down it talks about the "emu-dspmgr" and "emu-config" executable files, which did show up on my hard drive but are not executable. So yeah, I'm rather lost :(

-Jason

The directory to cd into should just be emu-tools-XXX, no tar.gz, and it should be where you extracted the gz file...

For instance:
Of course the numbers are not right, I just made em up...but you get the idea.

some progress
 

ok well I figured out partially what I was doing wrong. The file I had was a .tgz instead of a .tar.gz. So I went and downloaded the correct one, which made the new directory as it was supposed to. I went into the directory, only now when I enter the "make" command I get this:

[root@cc8a5c1b60 emu-tools-0.9.4]# make
cd as10k1 && make
make[1]: Entering directory `/home/Jason/emu-tools-0.9.4/as10k1'
cc -M *.c -W -Wall > .depend
/bin/sh: line 1: cc: command not found
make[1]: *** [dep] Error 127
make[1]: Leaving directory `/home/Jason/emu-tools-0.9.4/as10k1'
make: *** [As10k1] Error 2

Entering "make install" gives me the exact same thing.

-Jason

Do you have gcc installed? Do a "rpm -q gcc" if it says "package gcc not installed" then you have a long night ahead of you...you need a compiler to compile stuff ;)

Perhaps you just need to link cc to gcc, but I think that's usually done automatically.

gcc is not installed - any idea where it would be in the package menu thingy?

-Jason

In development. The thing is, to install gcc you are going to need a bunch of other things like automake, bison, libraries and all that...

Hopefully it will take care of everything you need but...

That's why I said you have a long night ahead of you. If you have the disk space I would install ALL of the development packages, it might save you some grief

Might be easier if you can find an rpm for emutools, try out www.rpmfind.net as you might get lucky

well see, I did in fact find an RPM and ran it. However, it doesn't tell me where the files went, and furthermore, when I search for the files, nothing comes up. If I try running it again, it just says the package has already been installed.

-Jason