LinuxSA Mailing list archives

Index: [thread] [date] [subject] [author] [stats]
  From: Andrew Lord <andrewlord@internode.on.net>
  To  : <linuxsa@linuxsa.org.au>
  Date: Fri, 25 Jul 2003 12:57:58 +0930

Re: Sound modules

Thanks for your response Conrad,

On Fri, 25 Jul 2003 08:30 am, you wrote:
> Andrew Lord wrote:
> > Hi all,
> >
> > I've been attempting to get sound running after a system - reinstall
> > (Mandrake 9.1).  It's not a really happenning thing at the moment,
> > however.
> >
> > Here's a printout of the various parameters:
> >
> > ### Which driver does the card use by default ?  lspcidrake -v | fgrep
> > AUDIO
> >
> > es1371          : Ensoniq|ES1371 [AudioPCI-97] [MULTIMEDIA_AUDIO]
> > (vendor:1274 device:1371)
> >
> > ### Which driver does it currently use ?   grep sound-slot
> > /etc/modules.conf alias sound-slot-0 es1371
>
> Are you asking whether the sound modules are loaded? ...they aren't.

No, they're not loading automatically.  So I'm wondering if there is something 
that I can enter in a shell to manually load the modules ? Perhaps there's 
more to it than that ?

> Are you compiling the alsa drivers?   

After my reinstall of Mandrake 9.1 and finding that sound didn't work, I 
re-installed alsa-utils, libalsa-data and libalsa2 rpms (rpm -Uvh --force 
$module_name) and the results obtained were exactly the same as described 
elsewhere in this e-mail.

When sound broke on my earlier install of Mandrake 9.1, I removed those rpm 
modules using the Mandrake control centre and then reinstalled them, but this 
had unexpected & fairly wide ranging repercussions on my system (clock went 
haywire among other things) so I just did another install of M'9.1.  

> There are several modules that are
> used by alsa.  I'm not familiar with Mandrake 9.1 and how it sets up
> sound cards (usually it does it for you).  It used to use the module
> supplied with the current kernel (es1371.o) unless it has started
> including the alsa drivers as it is going to be in the 2.6 kernel.  It
> looks like you are expecting the alsa drivers to be present but only the
> kernel module es1371 is available.  Try modprobe es1370 and see what
> happens.

Mmm.  Nor am I familiar with what modules are used in the alsa collection so 
I've visited alsa-project and found that there is one module, 'alsa-driver', 
that is not present on my CD's . . .. must be there (since I *did* have alsa 
working with my previous install) but perhaps one of the CD's is a bit flakey 
and it no longer is retrievable ?  

A couple of questions for anyone who knows  . . . . . .

1.  Is alsa-driver the module that installs drivers such as es1371 or is it 
simply required to operate such drivers ?

2.  Is there some other package responsible for installation of drivers such 
as es1371?

I'll try downloading the .tar.gz files and installing those.

>
> > ### Is the module (driver) loaded or not ?   /sbin/lsmod
> > Module                  Size  Used by    Not tainted
> > ppp_deflate             4408   0 (autoclean)
> > zlib_deflate           21144   0 (autoclean) [ppp_deflate]
> > bsd_comp                5336   0 (autoclean)
> > isofs                  27988   0 (autoclean)
> > zlib_inflate           21156   0 (autoclean) [ppp_deflate isofs]
> > udf                    90464   0 (autoclean)
> > binfmt_misc             7020   1
> > autofs4                11540   2 (autoclean)
> > lp                      8096   0
> > parport_pc             25096   1
> > parport                34176   1 [lp parport_pc]
> > nfsd                   74256   8 (autoclean)
> > ppp_async               9216   1
> > ppp_generic            24060   3 [ppp_deflate bsd_comp ppp_async]
> > slhc                    6564   1 [ppp_generic]
> > af_packet              14952   0 (autoclean)
> > ip_vs                  83192   0 (autoclean)
> > sr_mod                 16920   0 (autoclean)
> > floppy                 55132   2
> > sis900                 15564   1 (autoclean)
> > nls_iso8859-1           3516   2 (autoclean)
> > nls_cp850               4316   2 (autoclean)
> > vfat                   11820   2 (autoclean)
> > fat                    37944   0 (autoclean) [vfat]
> > supermount             15296   4 (autoclean)
> > ide-cd                 33856   1
> > cdrom                  31648   0 [sr_mod ide-cd]
> > ide-scsi               11280   0
> > scsi_mod              103284   2 [sr_mod ide-scsi]
> > usb-ohci               20584   0 (unused)
> > usbcore                72992   1 [usb-ohci]
> > rtc                     8060   0 (autoclean)
> >
> > ### Are the sound services configured to be run on initlevel3 ?
> > /sbin/chkconfig --list sound
> > sound          	0:off	1:off	2:on	3:on	4:on	5:on	6:off
> >
> > ### Are the alsa services configured to be run on initlevel3 ?
> > /sbin/chkconfig --list alsa
> > alsa           	0:off	1:off	2:off	3:off	4:off	5:off	6:off
> >
> > ### Is the sound volume muted or not ?   aumix -q
> > aumix:  error opening mixer
> >
> > ### Which program uses the soundcard ?   /sbin/fuser -v /dev/dsp
> > /dev/dsp: No such file or directory
> >
> > Also, when I run sndconfig 0.68, I get the following:
> >
> > #######################
> > PCI Probe Results
> >
> > A PCI sound card was found in your system.  The details are:
> >
> > 	Model: Ensoniq|ES1371 [AudioPCI-97]
> > #######################
> >
> >  . . . and then . . . . .
> >
> > #######################
> > Sound Card Test
> >
> > A sound sample will now be played to determine if your sound card has
> > been correctly configured.
> >
> > #######################
> >
> >  . . . and then . . . . .
> >
> > #######################
> > The following error occurred running the modprobe program:
> >
> > /lib/modules/2.4.21-0.13mdk/kernel/drivers/sound/es1371.o.gz:
> > init_module: No such device
> > modprobe: insmod
> > /lib/modules/2.4.21-0.13mdk/kernel/drivers/sound/es1371.o.gz failed
> > modpobe: insmod sound-slot-0 failed
> > #######################
> >
> > This is despite es1371.o.gz being "present and accounted for" at the very
> > same directory that sndconfig says it is absent from.
> >
> > How do I go about getting the sound module to load ?
> >
> > Any suggestions as to whether this is the limit of the problem, or
> > whether the above info indicates another problem, would be much
> > appreciated.

Cheers,

Andrew Lord

-- 
LinuxSA WWW: http://www.linuxsa.org.au/ IRC: #linuxsa on irc.freenode.net
To unsubscribe from the LinuxSA list:
  mail linuxsa-request@linuxsa.org.au with "unsubscribe" as the subject


Index: [thread] [date] [subject] [author] [stats]
Return to the LinuxSA Mailing List Information Page