Messages in this thread | | | Date | Sat, 14 Mar 1998 21:26:17 +0100 (MET) | From | Nicola Bernardelli <> | Subject | Sound: possible aweWithModularizedSoundSupport-miniHOWTO.cat |
| |
Maybe some lines with the essential information on how to pass parameters to the sound modules have already been added to the docs coming with the kernel source tree by now, maybe not yet. I was clueless before I got help from AWE owners who in turn must have collected infos here on linux-kernel, Hoang Ngo <hoang@hal.com> and Jim Bray <jb@as220.org> (he was also pointing to a patch he prepared for 2.1.87 to be able to compile the sound modules with default parameters). If it hasn't been done yet, maybe something similar to the lines I attach (or to a part of them) can be put in the Documentation directory (maybe included in an existent suitable file).
Nicola Bernardelli <nbern@mail.protos.it> --------------------------------------------------------------------------- Please use <n.bern@mail.protos.it> for messages from any kind of robot, such as mailing lists. --------------------------------------------------------------------------- In order to load SB-AWE related drivers on recent kernels (tested with 2.1.86 and 2.1.88) with modularized sound support these lines can be issued (of course with the suitable values for the parameters) after PNP setup:
insmod sound.o insmod uart401.o insmod sb.o io=0x220 irq=5 dma=1 dma16=5 mpu_io=0x330 insmod awe_wave.o
Alternatively, in order to also have automatic load on demand (not of the awe support, which would anyway most likely also require a call to sfxload), these lines can be added to /etc/conf.modules, of course with the suitable values for the parameters):
alias char-major-14 sb post-install sb modprobe "-k" "adlib_card" options sb io=0x220 irq=5 dma=1 dma16=5 mpu_io=0x330 options adlib_card io=0x388 # FM synthetiser
and then these two commands can be issued:
modprobe sb insmod awe_wave
------------------------------------------------------------------------------
After picking up the second approach, you may want to put these lines on an ossfreeOn script:
----- #!/bin/sh
modprobe sb insmod awe_wave
# A call to 'aumix -L' (attention to what the home dir is at boot # time, you may put a link /.aumixrc -> /home/<sounduser>/.aumixrc) to # restore mixer device levels and a call to 'sfxload <path to # soundfont bank>' may be added in a customized ossfreeSetup script:
if [ -x /usr/local/sbin/ossfreeSetup ] ; then /usr/local/sbin/ossfreeSetup fi -----
And these lines in an ossfreeOff script:
----- #!/bin/sh
# NOT set -e, maybe not all of them are currently loaded.
rmmod awe_wave rmmod adlib_card rmmod opl3 rmmod sb rmmod uart401 rmmod sound -----
------------------------------------------------------------------------------
| |