LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)
-   -   ALSA install (https://www.linuxquestions.org/questions/linux-software-2/alsa-install-43596/)

The Burninator 01-31-2003 08:52 PM

ALSA install - NEW problem autoloading snd-seq-oss
 
ALSA is installed, but the module snd-seq-oss won't load on login. The other necessary modules do. Just not that. Here's my modules.conf file:

alias parport_lowlevel parport_pc
alias eth0 3c59x
alias sound-slot-0 snd-cs46xx
#post-install sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -L >/dev/null 2>&1 || :
#pre-remove sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -S >/dev/null 2>&1 || :

post-install sound-slot-0 /usr/sbin/alsactl restore >/dev/null 2>&1 || :
pre-remove sound-slot-0 /usr/sbin/alsactl store >/dev/null 2>&1 || :


alias usb-controller usb-uhci


#alias char-major-195 nvidia


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

alias char-major-195 NVdriver

After login, I have no problems loading the module and playing sounds.

Also, I'm still getting the 'unresolved symbols' error (see below), which is likely related. And I don't think the alsamixer restore script is working.

This is weird.


-------------------------------------------------------------------

I'm using RedHat 8.0, and my sound has a tendency to "hiccup." So I decided to try and install ALSA. I went to www.freshrpms.net and downloaded the following files:

alsa-driver-0.9.0-fr0rc6.2.i386.rpm
alsa-kernel-0.9.0-fr0rc6.2_2.4.18_19.8.0.athlon.rpm
alsa-xmms-0.9.7-fr1.i386.rpm
alsa-lib-0.9.0-fr0rc6.1.i386.rpm
alsa-utils-0.9.0-fr0rc6.1.src.rpm

I installed them by double-clicking on them in GNOME. Then, when I ran XMMS and selected the ALSA output plugin, I got this message:

ALSA error
error opening alsa device: No such file or directory

What's wrong??


P.S. I then downloaded alsaplayer, which I installed the same way. It seemed completely functionless, so I tried to uninstall it through the terminal. The uninstall wasn't completely effective; it seems to technically be installed, but the link it the GNOME menu is gone. Any ideas? I'm quite a newbie. Thanks.

The Burninator 02-01-2003 03:00 PM

Anybody?

rnturn 02-01-2003 05:23 PM

Re: ALSA install
 
Quote:

Originally posted by The Burninator
I'm using RedHat 8.0, and my sound has a tendency to "hiccup." So I decided to try and install ALSA. I went to www.freshrpms.net and downloaded the following files:

alsa-driver-0.9.0-fr0rc6.2.i386.rpm
alsa-kernel-0.9.0-fr0rc6.2_2.4.18_19.8.0.athlon.rpm
alsa-xmms-0.9.7-fr1.i386.rpm
alsa-lib-0.9.0-fr0rc6.1.i386.rpm
alsa-utils-0.9.0-fr0rc6.1.src.rpm

I installed them by double-clicking on them in GNOME. Then, when I ran XMMS and selected the ALSA output plugin, I got this message:

ALSA error
error opening alsa device: No such file or directory


What's in modules.conf?

What do you see in /proc? You should see a subdirectory `asound' and under that you should see an entry `version'. What does that contain?
What do you see under /proc/modules?

The Burninator 02-01-2003 06:03 PM

There's no directory asound. Being a linux newbie, i don't know exactly what you mean by "modules.conf".
Here are the contents of proc/modules

sr_mod 18136 0 (autoclean)
cs46xx 62960 2 (autoclean)
ac97_codec 13384 0 (autoclean) [cs46xx]
soundcore 6500 3 (autoclean) [cs46xx]
autofs 13348 0 (autoclean) (unused)
3c59x 30608 1
ipt_REJECT 3736 6 (autoclean)
iptable_filter 2412 1 (autoclean)
ip_tables 14840 2 [ipt_REJECT iptable_filter]
usb-storage 62000 0
ide-scsi 10512 0
scsi_mod 107176 3 [sr_mod usb-storage ide-scsi]
ide-cd 33608 0
cdrom 33696 0 [sr_mod ide-cd]
nls_iso8859-1 3516 1 (autoclean)
nls_cp437 5116 1 (autoclean)
vfat 13084 1 (autoclean)
fat 38744 0 (autoclean) [vfat]
mousedev 5524 1
keybdev 2976 0 (unused)
hid 22244 0 (unused)
input 5888 0 [mousedev keybdev hid]
usb-uhci 26188 0 (unused)
usbcore 77056 1 [usb-storage hid usb-uhci]
ext3 70400 2
jbd 52212 2 [ext3]


Upon closer look, i found "modules.conf" in /etc, and the contents are....

alias parport_lowlevel parport_pc
alias eth0 3c59x
alias sound-slot-0 cs46xx
post-install sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -L >/dev/null 2>&1 || :
pre-remove sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -S >/dev/null 2>&1 || :
alias usb-controller usb-uhci


My instincts would tell me that there's no evidence of ALSA anywhere here, but in XMMS, the output plugin is listed. I'm really, really confused. Thanks for any help you can give me.

MasterC 02-01-2003 06:12 PM

Yeah, you'd wanna checkup on a page over at alsa about how to setup modules.conf for your soundcard, here's the page to locate your soundcard:
http://www.alsa-project.org/alsa-doc/

Read the one for your card, if you have questions, ask :)

And you've got the ALSA plugin in XMMS because you installed the RPM for it ;)

Cool

The Burninator 02-01-2003 08:07 PM

Well, I entered the lines of code there, and i also downloaded and installed the alsa-utils package, which had previously been wrong, but now i get this error upon login:

couldn't open mixer device /dev/sound/mixer

in addition, not even the OSS output plugin works now... I've made things worse!

What could be wrong?

MasterC 02-01-2003 08:13 PM

First check if /dev/sound/mixer exists. If it does, is it a device or symlink. To check out all this:
ls -l /dev/sound/mixer

If it shows up as a symlink, look at where it's linked to. If it's an actual device what are the permissions on it? Post up what comes up when you type:
ls -l /dev/sound/mixer

You probably will be able to get away with simple chmodding. Something like:
chmod 666 /dev/sound/mixer (as root).

But first off, let's see what shows up with the above command.

Cool

The Burninator 02-01-2003 08:32 PM

no such file or directory

MasterC 02-01-2003 08:37 PM

Ok, sounds like maybe instead of the RPM's you may wanna go tarballs (or bzipped tarballs). Get the newest alsa files from their website, then follow the directions exactly as they are written on the webpage for your soundcard. You maybe have missed the create devices scripts. ./snddevices or something along those lines, been a while since I've worked with alsa. Anyway, here's a link to their latest files:
www.alsa-project.org
Get the latest unstable files (0.90 rc7).
Cool

The Burninator 02-01-2003 09:15 PM

The installation instructions require that i use a command called "modprobe," which doesn't appear to be valid for me. What to do?

The Burninator 02-01-2003 10:24 PM

Nev.... I managed to find it, but now I get an error during startup (before login) that says:

Feb 1 22:58:19 localhost depmod: depmod: *** Unresolved symbols in /lib/modules/2.4.18-14/kernel/sound/isa/gus/snd-gus-synth.o
Feb 1 22:58:19 localhost depmod: depmod: *** Unresolved symbols in /lib/modules/2.4.18-14/kernel/sound/isa/sb/snd-emu8000-synth.o
Feb 1 22:58:19 localhost depmod: depmod: *** Unresolved symbols in /lib/modules/2.4.18-14/kernel/sound/pci/emu10k1/snd-emu10k1-synth.o
Feb 1 22:58:19 localhost depmod: depmod: *** Unresolved symbols in /lib/modules/2.4.18-14/kernel/sound/pci/trident/snd-trident-synth.o
Feb 1 22:58:19 localhost depmod: depmod: *** Unresolved symbols in /lib/modules/2.4.18-14/kernel/sound/synth/emux/snd-emux-synth.o

(this is from /var/log/boot.log)

mad_ady 02-02-2003 01:10 AM

The problems you get at startup are caused probably by a faulty configuration of you /etc/modules.conf...
Check the file again and see if modprobe (or the install script) has made any changes to it... If it did, please post them...

Good luck!

MasterC 02-02-2003 04:59 AM

Can you post the following:
uname -r
modprobe sound (if it returns any errors, if not, can you post up 'lsmod' (LSMOD lowercase)
and your /etc/modules.conf
?

Cool

The Burninator 02-02-2003 01:57 PM

Ok, it's working.... there's a very well-hidden alsamixer setting that was muting my external amplifier. However, my modules.conf doesn't contain any of the lines ALSA's website tells me to insert. Perhaps those are for autoloading the modules??

Thanks for all the help.

rnturn 02-02-2003 10:31 PM

Quote:

Originally posted by The Burninator
Ok, it's working.... there's a very well-hidden alsamixer setting that was muting my external amplifier.
Aahh... When you build the alsa driver from the sources, there's a big notice at the end of the build alerting you that the sound is muted and to fire up your mixer to set the sound level. Guess the rpm install doesn't provide that little hint. :-)

Quote:

However, my modules.conf doesn't contain any of the lines ALSA's website tells me to insert. Perhaps those are for autoloading the modules??

So, did you add them? (You'll need 'em.)

Have fun...

Rick


All times are GMT -5. The time now is 07:16 AM.