Re: [Alsa-user] I cannot get ALSA to work!

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

On 29 Oct 2002 17:14:51 -0500
Hazen Valliant-Saunders <ha...@gu...> wrote:

> Ok, 
> 	Mabye this is just me but here's my dillema.
> 	I have RedHat 8.0 
> 	
> [root@hal hazen]#uname -a
> Linux hal.guru.homelinux.com 2.4.18-17.8.0smp #1 SMP Tue Oct 8 10:52:32
> EDT 2002 i686 athlon i386 GNU/Linux
> [root@hal hazen]#
> 
> Ok, 
> 	now over at www.freshrpms.net they have the following rpms for alsa,
> I've checked my dependencies and I'm good. 
> -----------------------------------------------------------------------
> alsa-driver-0.9.0rc5-fr1.i386.rpm
> alsa-kernel-smp-0.9.0rc5-fr1_2.4.18_17.8.0.athlon.rpm
> alsa-lib-0.9.0rc5-fr1.i386.rpm
> alsa-lib-devel-0.9.0rc5-fr1.i386.rpm
> alsaplayer-0.99.72-fr2.i386.rpm
> alsa-utils-0.9.0rc5-fr1.i386.rpm
> -----------------------------------------------------------------------
> 
> 	After installing them via good ol' rpm I get the following error when
> trying to run alsamixer.
> ------------------------------------------------------------------------
> alsamixer
> 
> alsamixer: function snd_ctl_open failed for default: No such file or
> directory
> ------------------------------------------------------------------------
> 
> Here's the output of my /proc/modules
> ------------------------------------------------------------------------
> snd-pcm-oss            43876   0 (unused)
> snd-pcm                86720   0 [snd-pcm-oss]
> snd-timer              16392   0 [snd-pcm]
> snd-mixer-oss          15736   0 [snd-pcm-oss]
> snd                    42412   0 [snd-pcm-oss snd-pcm snd-timer
> snd-mixer-oss]
> sr_mod                 18200   0 (autoclean)
> emu10k1                73032   1 (autoclean)
> sound                  77708   0 (autoclean) [emu10k1]
> ac97_codec             13512   0 (autoclean) [emu10k1]

The above three modules are OSS modules. I think RH set up your system
for OSS sound. You have to remove these modules and the entries in
/etc/modules.conf which cause them to load. Only then can the ALSA
modules be loaded.

> soundcore               7108   7 (autoclean) [snd emu10k1 sound]
> autofs                 13668   0 (autoclean) (unused)
> 3c59x                  31344   1
> iptable_filter          2412   0 (autoclean) (unused)
> ip_tables              15672   1 [iptable_filter]
> ide-scsi               10640   0
> ide-cd                 33640   0
> cdrom                  34176   0 [sr_mod ide-cd]
> st                     31440   0 (unused)
> nls_iso8859-1           3516   3 (autoclean)
> nls_cp437               5148   3 (autoclean)
> vfat                   13276   3 (autoclean)
> fat                    40056   0 (autoclean) [vfat]
> mousedev                5688   1
> keybdev                 2976   0 (unused)
> hid                    22404   0 (unused)
> input                   6240   0 [mousedev keybdev hid]
> usb-ohci               22056   0 (unused)
> usbcore                80512   1 [hid usb-ohci]
> ext3                   72992   4
> jbd                    56688   4 [ext3]
> aic7xxx               138356   0 (unused)
> qla2200               269348   0
> sd_mod                 13552   0
> scsi_mod              110376   6 [sr_mod ide-scsi st aic7xxx qla2200
> sd_mod]
> [root@hal hazen]#
> -------------------------------------------------------------------------------
> 
> Now, I've run the ./sndevices script and I've tried to use modprobe to
> install the modules however I get an error there too (Perhaps they are
> already loaded?).
> -------------------------------------------------------------------------------
>  modprobe snd-emu10k1
> /lib/modules/2.4.18-17.8.0smp/kernel/sound/pci/emu10k1/snd-emu10k1.o:
> init_module: No such device
> Hint: insmod errors can be caused by incorrect module parameters,
> including invalid IO or IRQ parameters.
>       You may find more information in syslog or the output from dmesg
> /lib/modules/2.4.18-17.8.0smp/kernel/sound/pci/emu10k1/snd-emu10k1.o:
> insmod
> /lib/modules/2.4.18-17.8.0smp/kernel/sound/pci/emu10k1/snd-emu10k1.o
> failed
> /lib/modules/2.4.18-17.8.0smp/kernel/sound/pci/emu10k1/snd-emu10k1.o:
> insmod snd-emu10k1 failed
> ------------------------------------------------------------------------------
> 
> Here is my silly / stupid rant.  All of the ALSA documentation is for
> Linux-2.2.x now why hasen't anyone changed it to be 2.4.x compliant?
> Char-Major/Minor devices are anitquated and no longer used to my
> knoledge anyway (correct me if I'm wrong please!). I've read all the
> documentation, I've tried everything I can think of and thats why I'm
> posting to this list, as I hope there is someone out there whom can show
> me the error's of my ways (yes I chmod'ed the entries in the dev
> directory to ensure correct permissions were set on /dev/mixer, 
> /dev/midi /dev/...) So if some one has any idea ?
> 
> Oh here's another oddity that may help. When I install alsa-xmms I get
> the following error on startup and xmms will not start. 
> 
> ----------------------------------------------------------------------------
> 
> [root@hal hazen]# rpm -Uvh alsa-xmms-0.9.5-fr1.i386.rpm
> warning: alsa-xmms-0.9.5-fr1.i386.rpm: V3 DSA signature: NOKEY, key ID
> e42d547b
> Preparing...                ###########################################
> [100%]
>    1:alsa-xmms              ###########################################
> [100%]
> [root@hal hazen]# xmms
> 
> ** WARNING **: snd_mixer_attach: No such file or directory
> [root@hal hazen]#  f
> ------------------------------------------------------------------------------
> 
> So I know I'm missing something I just cant wrap my head around the
> issue.  the entries are there (and according to the documentation) are
> correct (those in /dev) the module cannot load.
> 
> In the interim I'm trying on linux-2.5.43 for size as alsa is
> "Compiled-in" with the kernel. However I would like to resolve this with
> my stock installation. 
> 
> Sincerely,
> Hazen Vallaint-Saunders
> ~Sig goes here.

HTH,

    -Frans