Mario SmartLink Soft Modem: version 2.9.9e-pre1 is too old. Likely it was installed from the older sl-modem-daemon package It doesn't have the fix for error: period size 48 is not supported by playback (64) >From http://phep2.technion.ac.il/linmodems/packages/smartlink/ get the SLMODEMD.gcc4.1.tar.gz and replace the one at /usr/sbin/slmodemd Leaving early in the AM MarvS On Jan 11, 2008 12:59 PM, Mario Ferreira <ztrange@xxxxxxxxx> wrote: > Thanks Daniel, I added those options at the end of my wvdial.conf but > I got exactloy the same errors. > > Any help would be appreciated > > Thanks > > > On Jan 11, 2008 11:37 AM, Daniel Victoria <daniel.victoria@xxxxxxxxx> wrote: > > I had a similar problem. I added to my wvdial.conf the options > > > > Carrier Check = no > > Stupid mode = on > > > > Also, I have to try at least 5 times before I get a connection. That's > > probably the internet provider fault. > > > > Another thing to try is to put on the Phone line a number that you > > know, just to see if your modem is dialing. I put my cell phone > > number. > > > > As for the error on the slmodemd terminal, I have no idea what that is > > > > Cheers > > Daniel > > > > > > On Jan 11, 2008 3:27 PM, Mario Ferreira <ztrange@xxxxxxxxx> wrote: > > > Hi all, > > > > > > Im from mexico, This far I have received a great support from Marvin > > > Stoldosky, but he told me that he'll rarely be online in the next 10 > > > days, so I'm witing to you because in spite of I've been able, with > > > the great guidance of Marvin, to advance some steps, my modem still is > > > not working, here is what i've done this far: > > > > > > $ sudo slmodemd -c MEXICO --alsa hw:0,6 > > > [sudo] password for mario: > > > SmartLink Soft Modem: version 2.9.9e-pre1 Sep 30 2007 00:07:03 > > > symbolic link `/dev/ttySL0' -> `/dev/pts/1' created. > > > modem `hw:0,6' created. TTY is `/dev/pts/1' > > > Use `/dev/ttySL0' as modem device, Ctrl+C for termination. > > > > > > In another terminal: > > > $ sudo wvdialconf /etc/wvdial.conf > > > Editing `/etc/wvdial.conf'. > > > > > > Scanning your serial ports for a modem. > > > > > > Modem Port Scan<*1>: S0 S1 S2 S3 > > > WvModem<*1>: Cannot get information for serial port. > > > ttySL0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud > > > ttySL0<*1>: ATQ0 V1 E1 -- A > > > ttySL0<*1>: failed with 9600 baud, next try: 115200 baud > > > ttySL0<*1>: ATQ0 V1 E1 -- OK > > > ttySL0<*1>: ATQ0 V1 E1 Z -- OK > > > ttySL0<*1>: ATQ0 V1 E1 S0=0 -- OK > > > ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK > > > ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK > > > ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK > > > ttySL0<*1>: Modem Identifier: ATI -- SmartLink Soft Modem > > > ttySL0<*1>: Speed 230400: AT -- OK > > > ttySL0<*1>: Speed 460800: AT -- OK > > > ttySL0<*1>: Max speed is 460800; that should be safe. > > > ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK > > > > > > Found a modem on /dev/ttySL0. > > > Modem configuration written to /etc/wvdial.conf. > > > ttySL0<Info>: Speed 460800; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0" > > > > > > $ sudo gedit /etc/wvdial.conf > > > > > > Here I added my tel/login/pass > > > > > > This one I tested it with and withot sudo: > > > > > > $ sudo wvdial > > > WvDial<*1>: WvDial: Internet dialer version 1.56 > > > WvModem<*1>: Cannot get information for serial port. > > > WvDial<*1>: Initializing modem. > > > WvDial<*1>: Sending: ATZ > > > WvDial Modem<*1>: ATZ > > > WvDial Modem<*1>: OK > > > WvDial<*1>: Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 > > > WvDial Modem<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 > > > WvDial Modem<*1>: OK > > > WvDial<*1>: Modem initialized. > > > WvDial<*1>: Sending: ATDT53289928 > > > WvDial<*1>: Waiting for carrier. > > > WvDial Modem<*1>: ATDT53289928 > > > WvDial Modem<*1>: NO CARRIER > > > WvDial Modem<*1>: ERROR > > > WvDial<Warn>: No Carrier! Trying again. > > > WvDial<*1>: Sending: ATDT53289928 > > > WvDial<*1>: Waiting for carrier. > > > WvDial Modem<*1>: ATDT53289928 > > > WvDial Modem<*1>: NO CARRIER > > > WvDial Modem<*1>: ERROR > > > WvDial<Warn>: No Carrier! Trying again. > > > And so on.... > > > > > > Meanwhile, in the termilar runing slmodem, it said: > > > > > > error: period size 48 is not supported by playback (64). > > > error: period size 48 is not supported by playback (64). > > > error: period size 48 is not supported by playback (64). > > > error: period size 48 is not supported by playback (64). > > > error: period size 48 is not supported by playback (64). > > > And so on... > > > > > > > > > I'll really appreciate the last step of help to make this modem work, > > > > > > Thanks. > > > > > > > > > On Jan 10, 2008 8:50 PM, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> wrote: > > > > Mario > > > > > > > > COMM functions require Adm permissions. So prefix with sudo > > > > $ sudo wvdialconf /etc/wvdial.conf > > > > Then edit with: > > > > $ sudo gedit /etc/wvdial.conf to a format like below. > > > > Then leaving slmodemd running > > > > $ sudo wvdial > > > > should get you online. Please send to the List hereafter. I'll rarely > > > > be online for 10 days > > > > > > > > MarvS > > > > -------------- > > > > [Dialer Defaults] > > > > Init1 = ATZ > > > > Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 > > > > Modem Type = Analog Modem > > > > Baud = 460800 > > > > New PPPD = yes > > > > Modem = /dev/ttySL0 > > > > ISDN = 0 > > > > Phone = 3015560020 > > > > Password = YourPassWord > > > > Username = LoginName@xxxxxxxxxxxxxxxx > > > > # needed for /dev/pts/N ports > > > > Carrier Check = no > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Jan 10, 2008 7:56 PM, Mario Ferreira <ztrange@xxxxxxxxx> wrote: > > > > > Ok, now it found my modem and I think that it's now working but now I > > > > > don't know how to ensure myself, and how to make a test with a dial-up > > > > > connection. Here is the oputput this far: > > > > > > > > > > mario@beula:~$ sudo slmodemd -c MEXICO --alsa hw:0,6 > > > > > [sudo] password for mario: > > > > > Sorry, try again. > > > > > [sudo] password for mario: > > > > > SmartLink Soft Modem: version 2.9.9e-pre1 Sep 30 2007 00:07:03 > > > > > symbolic link `/dev/ttySL0' -> `/dev/pts/2' created. > > > > > modem `hw:0,6' created. TTY is `/dev/pts/2' > > > > > Use `/dev/ttySL0' as modem device, Ctrl+C for termination. > > > > > > > > > > > > > > > In other terminal: > > > > > > > > > > mario@beula:~$ wvdialconf /etc/wvdial.conf > > > > > Editing `/etc/wvdial.conf'. > > > > > > > > > > Scanning your serial ports for a modem. > > > > > > > > > > Modem Port Scan<*1>: S0 S1 S2 S3 > > > > > WvModem<*1>: Cannot get information for serial port. > > > > > ttySL0<*1>: ATQ0 V1 E1 -- OK > > > > > ttySL0<*1>: ATQ0 V1 E1 Z -- OK > > > > > ttySL0<*1>: ATQ0 V1 E1 S0=0 -- OK > > > > > ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK > > > > > ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK > > > > > ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK > > > > > ttySL0<*1>: Modem Identifier: ATI -- SmartLink Soft Modem > > > > > ttySL0<*1>: Speed 4800: AT -- OK > > > > > ttySL0<*1>: Speed 9600: AT -- OK > > > > > ttySL0<*1>: Speed 19200: AT -- OK > > > > > ttySL0<*1>: Speed 38400: AT -- OK > > > > > ttySL0<*1>: Speed 57600: AT -- OK > > > > > ttySL0<*1>: Speed 115200: AT -- OK > > > > > ttySL0<*1>: Speed 230400: AT -- OK > > > > > ttySL0<*1>: Speed 460800: AT -- OK > > > > > ttySL0<*1>: Max speed is 460800; that should be safe. > > > > > ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK > > > > > > > > > > Found a modem on /dev/ttySL0. > > > > > Modem configuration written to /etc/wvdial.conf. > > > > > /etc/wvdial.conf<Warn>: Can't write '/etc/wvdial.conf.tmp6215': > > > > > Permission denied > > > > > /etc/wvdial.conf<Warn>: Can't write '/etc/wvdial.conf' > > > > > ('/etc/wvdial.conf'): Bad file descriptor > > > > > ttySL0<Info>: Speed 460800; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0" > > > > > > > > > > I don't know why it says can't write to /etc/wvdial.conf I'm working > > > > > with sudo. By the way, I still cant find the ALSA tgz > > > > > > > > > > Thanks for your help. > > > > > > > > > > > > > > > On Jan 9, 2008 7:00 PM, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> wrote: > > > > > > RE: > edited that 0 to 1 to avoid boot load > > > > > > COrrect!! > > > > > > > > > > > > > finally > > > > > > > sudo wvdialconf /etc/wvdial.conf > > > > > > > > > > > > > $ sudo slmodemd -c MEXICO --alsa hw:0,6 > > > > > > > this told me that i could use the modem from /tty/something > > > > > > Good > > > > > > > > > > > > > and it told me that no modem was found. > > > > > > Make sure you open a 2nd console and leave slmodemd running during this test. > > > > > > > > > > > > MarvS > > > > > > > > > > > > > > > > > > > > > > > > On Jan 9, 2008 6:25 PM, Mario Ferreira <ztrange@xxxxxxxxx> wrote: > > > > > > > Marvin, firs of all, thanks for your help this far. > > > > > > > > > > > > > > I did what you told me but my modem didn't show up > > > > > > > > > > > > > > $ sudo gedit /etc/default/sl-modem-daemon > > > > > > > edited that 0 to 1 to avoid boot load > > > > > > > > > > > > > > $ sudo slmodemd -c MEXICO --alsa hw:0,6 > > > > > > > this told me that i could use the modem from /tty/something I cant't > > > > > > > remember this vervy well and now I'm on an Internet coffe > > > > > > > > > > > > > > finally > > > > > > > sudo wvdialconf /etc/wvdial.conf > > > > > > > > > > > > > > and it told me that no modem was found. > > > > > > > > > > > > > > Does that means that it won't work at all? > > > > > > > > > > > > > > > > > > > > > > > > > > > > On 1/9/08, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> wrote: > > > > > > > > Daniel > > > > > > > > > > > > > > > > RE: Analysing card in PCI bus 00:04.0, > > > > > > > > writing to scanout. 00:04.0 > > > > > > > > ./scanModem: line 1070: 1: ambiguous redirect > > > > > > > > ------- > > > > > > > > THanks the problem is an unwanted space in > > > > > > > > scanout. 00:04.0 > > > > > > > > Should be > > > > > > > > scanout.00:04.0 > > > > > > > > > > > > > > > > WIll fix easily now. > > > > > > > > > > > > > > > > MarvS > > > > > > > > > > > > > > > > On Jan 9, 2008 11:32 AM, Daniel Victoria <daniel.victoria@xxxxxxxxx> wrote: > > > > > > > > > OK, using the updated version of scanModem sent by Jacques I get the > > > > > > > > > following ModelData.txt (attached). > > > > > > > > > > > > > > > > > > I see that it now recognizes the ALI modem and also suggests the > > > > > > > > > slmodemd driver. It also outputs a file called Smartlink.txt which it > > > > > > > > > did not do before. > > > > > > > > > > > > > > > > > > On the other hand, some errors appear. First I see a bunch of > > > > > > > > > ambiguous redirect error and then a file named 00:04.0 gets writen, > > > > > > > > > along with a file Modem/scanout. > > > > > > > > > > > > > > > > > > I'm also attaching the screen dump of the scanModem run (stderr and > > > > > > > > > stdout - DV.tx) > > > > > > > > > > > > > > > > > > Cheers > > > > > > > > > Daniel > > > > > > > > > > > > > > > > > > PS - Bessides that the modem seems to be working fine. I can call my > > > > > > > > > cell phone. Just have not been able to get the ISP to work > > > > > > > > > > > > > > > > > > > > > > > > > > > On Jan 9, 2008 2:05 PM, Jacques Goldberg <Jacques.Goldberg@xxxxxxx> wrote: > > > > > > > > > > Folks, > > > > > > > > > > Attached an URGENT update of scanModem for immediate use > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Marvin Stodolsky wrote: > > > > > > > > > > > Daniel and Mario, > > > > > > > > > > > > > > > > > > > > > > Please send me your ALSA*.tgz files. > > > > > > > > > > > > > > > > > > > > > > Mario, > > > > > > > > > > > Use > > > > > > > > > > > $ sudo gedit /etc/default/sl-modem-daemon > > > > > > > > > > > to shut down the bootup actions of sl-modem-daemon > > > > > > > > > > > as it may not work properly for Sysetems using the snd-hda-intel driver. > > > > > > > > > > > Then reboot and do the modem setup with > > > > > > > > > > > $ sudo slmodemd -c MEXICO --alsa hw:0,6 > > > > > > > > > > > > > > > > > > > > > > Then open a 2nd console and the modem should be found by > > > > > > > > > > > sudo wvdialconf /etc/wvdial.conf > > > > > > > > > > > > > > > > > > > > > > Daniel, > > > > > > > > > > > Run > > > > > > > > > > > $ bash -x ./scanModem | tee -a DV2.txt > > > > > > > > > > > and send me the DV2.txt > > > > > > > > > > > The setup command > > > > > > > > > > > slmodemd -c BRAZIL --alsa -s hw:0,1 > > > > > > > > > > > should be used with your ALI5451 hardware. > > > > > > > > > > > Just go forward with the rest of the testing. > > > > > > > > > > > > > > > > > > > > > > Marv > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Jan 9, 2008 6:10 AM, Daniel Victoria <daniel.victoria@xxxxxxxxx> wrote: > > > > > > > > > > >> Hi all, > > > > > > > > > > >> > > > > > > > > > > >> This version is either significantly slower or it's not working in my > > > > > > > > > > >> laptop. It hangs right after the message > > > > > > > > > > >> > > > > > > > > > > >> A copy of /proc/asound had been copied to Modem/ALSAroot.tgz > > > > > > > > > > >> > > > > > > > > > > >> By the way, I'm running it as root. Is that necessary? > > > > > > > > > > >> > > > > > > > > > > >> Daniel > > > > > > > > > > >> > > > > > > > > > > >> > > > > > > > > > > >> On Jan 8, 2008 11:41 PM, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> wrote: > > > > > > > > > > >>> Attached is another scanModem update. > > > > > > > > > > >>> Should do better for ALI5451 test. > > > > > > > > > > >>> Send me back the ModemData.txt and scanout.* file > > > > > > > > > > >>> > > > > > > > > > > >>> MarvS > > > > > > > > > > >>> > > > > > > > > > > >>> > > > > > > > > > > >>> On Jan 8, 2008 8:13 AM, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> wrote: > > > > > > > > > > >>>> RE: mentions a snd-hda-intel > > > > > > > > > > >>>> This shows that there is still some residual bug. > > > > > > > > > > >>>> Will work on it tonight. > > > > > > > > > > >>>> > > > > > > > > > > >>>> MarvS > > > > > > > > > > >>>> > > > > > > > > > > >>>> > > > > > > > > > > >>>> On Jan 8, 2008 6:51 AM, Daniel Victoria <daniel.victoria@xxxxxxxxx> wrote: > > > > > > > > > > >>>>> MarvS, > > > > > > > > > > >>>>> > > > > > > > > > > >>>>> I only saw this message after I replied to the first one. I ran the > > > > > > > > > > >>>>> new scanModem tool and attached is the ModemData.txt and the > > > > > > > > > > >>>>> /proc/asound files. > > > > > > > > > > >>>>> > > > > > > > > > > >>>>> Apperently the difference is that it now mentions a snd-hda-intel > > > > > > > > > > >>>>> module, which does not seams to be loaded but, laptop sound is working > > > > > > > > > > >>>>> so the sound modules are loaded > > > > > > > > > > >>>>> > > > > > > > > > > >>>>> Thanks > > > > > > > > > > >>>>> Daniel > > > > > > > > > > >>>>> > > > > > > > > > > >>>>> > > > > > > > > > > >>>>> On Jan 8, 2008 1:02 AM, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> wrote: > > > > > > > > > > >>>>>> OK, found the problem. Just run the scanModem update attached > > > > > > > > > > >>>>>> and send me the /proc/asound copy along with the ModemData.txt > > > > > > > > > > >>>>>> > > > > > > > > > > >>>>>> MarvS > > > > > > > > > > >>>>>> > > > > > > > > > > >>>>>> > > > > > > > > > > >>>>>> On Jan 7, 2008 9:21 PM, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> wrote: > > > > > > > > > > >>>>>>> Mario & Daniel > > > > > > > > > > >>>>>>> > > > > > > > > > > >>>>>>> With the attached recurse2,gz > > > > > > > > > > >>>>>>> $ gunzip recurse2.gz > > > > > > > > > > >>>>>>> $ chmod +x recurse2 > > > > > > > > > > >>>>>>> you can browse the script recurse2 > > > > > > > > > > >>>>>>> It just makes a copy of the /proc/asound/ structure. > > > > > > > > > > >>>>>>> > > > > > > > > > > >>>>>>> Run > > > > > > > > > > >>>>>>> $ ./recurse2 > > > > > > > > > > >>>>>>> and send me the output file. > > > > > > > > > > >>>>>>> > > > > > > > > > > >>>>>>> scanModem should do this automatically > > > > > > > > > > >>>>>>> but there is a bug I haven't found yet. > > > > > > > > > > >>>>>>> > > > > > > > > > > >>>>>>> MarvS > > > > > > > > > > >>>>>>> > > > > > > > > > > >>>>>>> > > > > > > > > > > >>>>>>> > > > > > > > > > > >>>>>>> On Jan 7, 2008 7:33 PM, Mario Ferreira <ztrange@xxxxxxxxx> wrote: > > > > > > > > > > >>>>>>>> Hi I'm from Mexico and trying to install my modem into my new ubuntu > > > > > > > > > > >>>>>>>> xp dual boot. Im attaching the ModemData.txt resulting from the > > > > > > > > > > >>>>>>>> scanModem run. > > > > > > > > > > >>>>>>>> > > > > > > > > > > >>>>>>>> Any help on the next step to take will be appreciated. > > > > > > > > > > >>>>>>>> > > > > > > > > > > >>>>>>>> Thanks, > > > > > > > > > > >>>>>>>> Mario > > > > > > > > > > >>>>>>>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
