I'm a enthusiastic Compilerman for the newest "stable" ALSA-driver which is now Version 0.9.3c. It compiles absolutly without any warnings - but - Oh shit, the new driver can't be loaded !
1. My Hardware: P2 233MHz, PIIX-Board, SB AWE 64 Gold Soundcard.
2. My Software: SuSE 8.1 Distribution with Updates and the following
Versions: 2.4.20 kernel with SYSTRACE patch (non SuSE - it's
from ftp.kernel.org), make 3.79.1, gcc 3.2,
ld-2.2.5.so, module-init-tools 0.9.12.3. the command line for the configure script and the results at the end of the config.log:
"$ ./configure --with-moddir=/lib/modules/2.4.20/kernel/sound
--with-cards=sbawe --with-debug=detect --with-isapnp=yes
--with-sequencer=yes --with-oss=yes ## ----------------- ##
## Cache variables. ##
## ----------------- ## ac_cv_c_compiler_gnu=yes
ac_cv_c_const=yes
ac_cv_c_inline=inline
ac_cv_env_CC_set=
ac_cv_env_CC_value=
ac_cv_env_CFLAGS_set=
ac_cv_env_CFLAGS_value=
ac_cv_env_CPPFLAGS_set=
ac_cv_env_CPPFLAGS_value=
ac_cv_env_CPP_set=
ac_cv_env_CPP_value=
ac_cv_env_LDFLAGS_set=
ac_cv_env_LDFLAGS_value=
ac_cv_env_build_alias_set=
ac_cv_env_build_alias_value=
ac_cv_env_host_alias_set=
ac_cv_env_host_alias_value=
ac_cv_env_target_alias_set=
ac_cv_env_target_alias_value=
ac_cv_header_stdc=yes
ac_cv_header_time=yes
ac_cv_objext=o
ac_cv_path_install='/usr/bin/install -c'
ac_cv_prog_CPP='gcc -E'
ac_cv_prog_ac_ct_CC=gcc
ac_cv_prog_ac_ct_RANLIB=ranlib
ac_cv_prog_cc_g=yes
ac_cv_prog_cc_stdc=
ac_cv_prog_gcc_traditional=no ## ------------ ##
## confdefs.h. ##
## ------------ ## #define STDC_HEADERS 1
#define TIME_WITH_SYS_TIME 1
#define CONFIG_SND_KERNELDIR "/lib/modules/2.4.20/build"
#define CONFIG_SND_VERBOSE_PRINTK 1
#define CONFIG_SND_DEBUG 1
#define CONFIG_SND_DEBUG_MEMORY 1
#define CONFIG_SND_DEBUG_FULL 1
#define CONFIG_SND_DEBUG_DETECT 1
#define CONFIG_SND_ISA 1
#define CONFIG_ISAPNP_KERNEL 1
#define CONFIG_ISAPNP 1
#define CONFIG_PNP 1
#define CONFIG_HAVE_VMALLOC_TO_PAGE 1
#define CONFIG_SND_VERSION "0.9.3c"
#define CONFIG_SND_DATE ""
#define CONFIG_SND_SEQUENCER 1
#define CONFIG_SND_SEQ_DUMMY_MODULE 1
#define CONFIG_SND_OSSEMUL 1
#define CONFIG_SND_MIXER_OSS 1
#define CONFIG_SND_PCM_OSS 1
#define CONFIG_SND_SEQUENCER_OSS 1
#define CONFIG_SND_SBAWE_MODULE 1configure: exit 0 "
4. after a make I ran the 'snddevices' script as describe in 'INSTALL'
5. the Sound related lines in my modules.conf are:
"# Alsa sound support.
# Warning: please don't modify comments over aliases
# 'snd-card-#'
alias char-major-116 snd
options snd-sbawe enable=1 index=0 isapnp=1 mic_agc=1
options snd cards_limit=1 major=116 # QQNm.Z8+dKbUnHfF:Creative SB AWE64 Gold
alias snd-card-0 snd-sbawe # YaST2: sound system dependent part
#
alias sound-slot-0 snd-card-0
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-11 snd-mixer-oss
alias sound-service-0-12 snd-pcm-oss alias sound-slot-1 off
alias sound-slot-2 off
alias sound-slot-3 off "6. a 'modprobe snd-sbawe' tells me this m.....f.....g ERROR:
"/lib/modules/2.4.20/kernel/sound/snd-sbawe.o: init_module: No such device /lib/modules/2.4.20/kernel/sound/snd-sbawe.o: insmod /lib/modules/2.4.20/kernel/sound/snd-sbawe.o failed /lib/modules/2.4.20/kernel/sound/snd-sbawe.o: insmod snd-sbawe failed 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"
..and these are the lines in /var/log/messages:
"kernel: ALSA ../../alsa-kernel/isa/sb/sb16.c:313: pnp SB16: port=0x220, mpu port=0x330, fm port=0x388 kernel: ALSA ../../alsa-kernel/isa/sb/sb16.c:315: pnp SB16: dma1=1, dma2=5, irq=5 kernel: ALSA ../../alsa-kernel/isa/sb/sb16.c:336: pnp SB16: wavetable port=0x620 kernel: ALSA ../../alsa-kernel/isa/sb/sb_common.c:133: SB [0x220]: DSP chip found, version = 4.16 kernel: ALSA ../../alsa-kernel/isa/sb/sb16.c:505: sbawe: fatal error - EMU-8000 synthesizer not detected at 0x620 kernel: ALSA ../../alsa-kernel/isa/sb/sb16.c:638: Sound Blaster 16 soundcard not found or device busy kernel: ALSA ../../alsa-kernel/isa/sb/sb16.c:640: In case, if you have non-AWE card, try snd-sb16 module kernel: ALSA ../../alsa-kernel/isa/sb/sb16.c:302: sbawe: AUDIO pnp configure failure kernel: ALSA ../../alsa-kernel/isa/sb/sb16.c:638: Sound Blaster 16 soundcard not found or device busy kernel: ALSA ../../alsa-kernel/isa/sb/sb16.c:640: In case, if you have non-AWE card, try snd-sb16 module"
7. Yes, that's fine. I also compile a driver-Version 0.9.3a and after I try to load 'snd-sbawe' a very interesting message appear on the screen:
"Warning: loading /lib/modules/2.4.20/kernel/sound/snd-pnp.o will
taint the kernel: no license
See http://www.tux.org/lkml/#export-tainted for information about
tainted modules .. Module snd-pnp loaded, with warnings
/lib/modules/2.4.20/kernel/sound/snd-sbawe.o: init_module:
No such device ...etc.." , like above (6.) ..was there Steven Balmer's hands on code ? Well, at this time I was
total tainted and return back to the 'well-functioning-driver'
0.9.0rc8 before I try the Release 0.9.3c. Again, I'm back to
0.9.0cr8 for the stable Kernel 2.4.20 !8. the driver modules (0.9.2) in the newest experimental Kernel 2.5.70 works "half" with my (historic ?) Hardware and the warnings in /var /log/messages are at medium stage (the emu8000-synth don't work??):
" kernel: pnp: the driver 'sb16' has been registered
kernel: pnp: match found with the PnP device '01:01.00' and the
driver 'sb16'
kernel: pnp: match found with the PnP device '01:01.02' and the
driver 'sb16'
kernel: pnp: res: The resources requested do not match those set
kernel: ALSA sound/isa/sb/sb16.c:311: pnp SB16: port=0x220, mpu
port=0x330, fm port=0x388
kernel: ALSA sound/isa/sb/sb16.c:313: pnp SB16: dma1=1, dma2=5,
irq=5
kernel: pnp: res: the device '01:01.02' has been activated.
kernel: ALSA sound/isa/sb/sb16.c:334: pnp SB16: wavetable
port=0x620
kernel: ALSA sound/isa/sb/sb_common.c:133: SB [0x220]: DSP chip
found, version = 4.16
kernel: ALSA sound/drivers/opl3/opl3_lib.c:133: OPL3: stat1 = 0xff
kernel: ALSA sound/drivers/opl3/opl3_lib.c:451: OPL2/3 chip not
detected at 0x388/0x38a
kernel: ALSA sound/isa/sb/sb16.c:464: sbawe: no OPL device at
0x388-0x38a
kernel: ALSA sound/isa/sb/emu8000.c:178: EMU8000 [0x620]: Synth
chip found
modprobe: FATAL: Module snd_sbawe already in kernel.
modprobe: FATAL: Module snd_seq_oss already in kernel. "There are also problems with the alsa-lib-0.9.3, but I'm not shure about my own mistakes I've make. As You see I'm NOT a Developer and I can't speek C, C++, ..or any programming language - but my last Microsoft-OS was Windows 98 'first release'. Now I say: Only Linux please... :)
------------------------------------------------------- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
