MarvS, thank you very much for writing - sorry for not replying earlier. I'd be happy to help with Italian transalations, when needed. As far as I could see, both compiled and packaged versions of slmodemd 2.9.11 work, provided Alsa-driver and Alsa-lib are right. Here are my experiences with some distributions: Knoppix 5.1.1. (2007). My first success with slmodemd. Kernel 2.6.19.1, Alsa-driver and Alsa-lib both version 1.0.13, gcc 4.1.2. slmodemd was not included in the distribution, but both packaged and compiled 2.9.11 work. Essentially the same results with the following distributions: Sidux 2007: Kernel 2.6.21.3, Alsa-driver 1.0.14rc3, Alsa-lib 1.0.13, gcc 4.1.3. DreamLinux 3.2, Kernel 2.6.23, Alsa-driver 1.0.14, Alsa-lib 1.0.15 Puppy NOP 4.0, Kernel 2.6.21.3, Alsa-driver 1.0.15rc2, Alsa-lib 1.0.14 In 2008, first problems noticed: Knoppix 5.3.1., Kernel 2.6.24.4, Alsa-driver 1.0.15, Alsa-lib 1.0.16, gcc 4.2.3. The modem connects, but at a slow speed and disconnects again after a short while. Solution: used libasound.so.2.0.0 version 1.0.15, and the modem works perfectly. Sidux 2008-01: closely resembles Knoppix 5.3.1, with same Kernel, Alsa-driver, Alsa-lib and gcc versions. Same problem and same solution. Then, the problems become even worse: Puppy NOP 4.1.2. and 4.1.3.: Kernel 2.6.25.16, Alsa-driver and Alsa-lib 1.0.16rc2. With this one, the only way to connect consisted in recompiling the sound modules, using files taken from Alsa-driver 1.0.15 (control.c, pcm.c, pcm_lib.c, pcm_native.c, asound.h and pcm.h), with minimal modifications to ensure compilation. Alsa-lib 1.0.15 needed for successful connect. Essentially, same experience with the following distributions: Puppy NOP 4.3.1, Kernel 2.6.30.5, Alsa-driver and Alsa-lib 1.0.20 TinyCore, Kernel 2.6.29.1; tried this one also with self-compiled Vanilla kernels 2.6.26, 2.6.27.1, 2.6.28, 2.6.29, 2.6.30 and 2.6.31. Pink On 11/17/09, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> wrote: > Pink, > > Your information on: >> I only need to keep the following source files from ALSA 1.0.15: >> control.c, pcm.c, pcm_lib.c, pcm_native.c, asound.h and pcm.h. > is very useful as it may be applicable to drivers other than the ali5451 > > What is your Linux distro? > Which slmodemd are using? While the Smartlink release 2.9.11 is > certainly appropriate, > If might help to compile slmodemd on your own system, to get the > optimal match of alsa resources and gcc compiler. > > Within the folder slmodem-2.9.11-20090222/modem/ folder, the compile > can be done as below, > though I suspect you have compiled your own. > > Would you please gzip your slmodemd and send it to "Antonio Olivares" > <olivares14031@xxxxxxxxx> > He has success with a slmodemd+slamr driver under 2.6.30, but not 2.6.31 > > MarvS > ------------- > slmodem-2.9.11-20090222/modem$ make SUPPORT_ALSA=1 > rebuild profile... > gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o > modem_main.o -c modem_main.c > modem_main.c: In function ‘setup_stream’: > modem_main.c:429: warning: ‘snd_pcm_sw_params_set_xfer_align’ is > deprecated (declared at /usr/include/alsa/pcm.h:1114) > gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o > modem_cmdline.o -c modem_cmdline.c > gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o modem.o > -c modem.c > gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o > modem_datafile.o -c modem_datafile.c > gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o > modem_at.o -c modem_at.c > gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o > modem_timer.o -c modem_timer.c > gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o > modem_pack.o -c modem_pack.c > gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o > modem_ec.o -c modem_ec.c > gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o > modem_comp.o -c modem_comp.c > gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o > modem_param.o -c modem_param.c > gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o > modem_debug.o -c modem_debug.c > gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o > homolog_data.o -c homolog_data.c > gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o > dp_sinus.o -c dp_sinus.c > gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o > dp_dummy.o -c dp_dummy.c > gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o > sysdep_common.o -c sysdep_common.c > gcc -o slmodemd modem_main.o modem_cmdline.o modem.o modem_datafile.o > modem_at.o modem_timer.o modem_pack.o modem_ec.o modem_comp.o > modem_param.o modem_debug.o homolog_data.o dp_sinus.o dp_dummy.o > dsplibs.o sysdep_common.o /usr/lib/libasound.so > gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o > modem_test.o -c modem_test.c > modem_test.c: In function ‘modem_test_start’: > modem_test.c:110: warning: ignoring return value of ‘write’, declared > with attribute warn_unused_result > gcc -o modem_test modem_test.o modem_cmdline.o modem.o > modem_datafile.o modem_at.o modem_timer.o modem_pack.o modem_ec.o > modem_comp.o modem_param.o modem_debug.o homolog_data.o dp_sinus.o > dp_dummy.o dsplibs.o sysdep_common.o /usr/lib/libasound.so > > slmodem-2.9.11-20090222/modem$ ls -lh slmodemd > -rwxr-xr-x 1 marv marv 1.3M 2009-11-17 17:51 slmodemd > > > > On Tue, Nov 17, 2009 at 11:39 AM, Pink SoftBunny > <pinksoftbunny@xxxxxxxxxxxxxx> wrote: >> Dear Readers, >> >> my ALi 5451 modem used to work perfectly with ALSA driver version >> 1.0.15, ALSA library 1.0.15 and slmodemd 2.9.11. >> >> Since newer Linux Kernels also brought newer ALSA drivers with them, I >> have not been able to get a "CONNECT" with this modem. >> I did a number of tests with different distributions and dialling >> software. >> >> As a workaround, I compiled ALSA driver 1.0.15 for the more recent >> Linux kernels, up to 2.6.31, the current release at the time of this >> writing. The modem works perfectly with this workaround. >> I only need to keep the following source files from ALSA 1.0.15: >> control.c, pcm.c, pcm_lib.c, pcm_native.c, asound.h and pcm.h. >> >> However, I lack the necessary insight to determine whether the >> problem is due to the ALSA driver, the ALSA library, slmodemd or other >> components. >> This problem has been submitted to ALSA as issue #0004601. >> >> Thank you for your assistance! >> >
