Emanuele Who is your Internet provider at 0802201400 ?? Note that if your call passes through a switchboard as opposed to going direct to an IP insert a pause with a , as in Phone = 0,802201400 RE: [Dialer Defaults] Init1 = ATZ Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 X3 Modem Type = Analog Modem Baud = 460800 New PPPD = yes Modem = /dev/ttySL0 ISDN = 0 Carrier Check = no Stupid Mode = yes Phone = 0802201400 Password = ******************************* Username = ******************************* Try, without stupid mode per below [Dialer Defaults] Init1 = ATZ Init2 = ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=34 Modem Type = Analog Modem Baud = 460800 New PPPD = yes Modem = /dev/ttySL0 ISDN = 0 Carrier Check = no # Stupid Mode = yes Phone = 0802201400 Password = ******************************* Username = ******************************* MarvS On Jan 20, 2008 7:12 PM, Emanuele Pagone <epagone@xxxxxxxxxxxxx> wrote: > Hello, > > several days are passed from my last message and I haven't received any > answer. I tried two other solutions to my problem, but they were > useless. I'll report them here because they might be of any use for you: > > 1. I have also an ethernet card in my computer so to avoid > incompatibility problems with the dial-up modem, I disconnected the > RJ-45 cable and I gave this command in the console: > > $ sudo ifconfig eth0 down > > At this point I verified that eth0 was down typing: > > $ ifconfig > > It was correctly down, but this changed nothing. > > > 2. I tried these other Init string commands : +MS=33, +MS=56, +MS=90, > +MS=K56, S10=100 (in place of S0=0) and ATM1L1 (in place of ATQ0). > > Sometimes I get "Bad init string" and sometimes I have the usual problem > (yet described) starting with "Timed out while dialing. Trying again." > > I tried also to change the Baud value overwriting the standard value > with this: "Baud = 115200". Nothing changed :( . > > > Sorry, but I don't understand your silence: am I lacking some requests? > Is my modem not supported (if so, can you say it, please?)? What should > I do? > > Sorry again for my insistence, but I'm quite confused... > > Regards. > > > Emanuele > > Emanuele Pagone ha scritto: > > > Thank you Jacques! > > > > As I said in my first message, I'm very happy to send you my > > ModemData.txt file. I'll paste it after my signature. > > > > If can be useful, I'll say you my procedure to install the modem drivers: > > > > 1. With Synaptic package manager (Ubuntu 7.10), I've installed the > > ''sl-modem-daemon'' package. > > > > 2. I edited /etc/default/sl-modem-daemon to have > > SLMODEMD_COUNTRY=ITALY > > and > > SLMODEMD_DEVICE=slamr0 > > > > 3. Console commands: > > $wget > > http://linmodems.technion.ac.il/packages/smartlink/Ubuntu/slamr-`uname > > -r`.tar.gz > > $tar -xzvf slamr-`uname -r`.tar.gz > > $sudo mkdir /lib/modules/`uname -r`/extra > > $sudo cp slamr-`uname -r`/*.ko /lib/modules/`uname -r`/extra/ > > $sudo depmod -a > > $sudo /etc/init.d/sl-modem-daemon restart > > > > 4. Console command: > > $sudo wvdialconf /etc/wvdial.conf > > > > Bye. > > > > > > Emanuele > > > > PS. I'm sorry: just now I read that the mail object must be in > > ''YourName, YourCountry kernel 2.6.22-14-generic'' format, so I'm > > adjusting the mail object accordingly. Please excuse me. > > > > ModemData.txt: > > -------------------------- System information ---------------------------- > > CPU=i686, > > Linux version 2.6.22-14-generic (buildd@terranova) (gcc version 4.1.3 > > 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)) #1 SMP Tue Dec 18 > > 08:02:57 UTC 2007 > > scanModem update of: 2008_06_01 > > > > > > There are no blacklisted modem drivers in /etc/modprobe* files > > > > The Advanced Linux Sound Architecture (ALSA) packages providing audio > > support, > > also includes drivers for some modems. The ALSA diagnostics are written > > during > > bootup to /proc/asound/ folders. > > > > > > The /proc/asound/pcm file reports: > > ----------------------- > > 00-04: Intel ICH - IEC958 : Intel ICH5 - IEC958 : playback 1 > > 00-03: Intel ICH - ADC2 : Intel ICH5 - ADC2 : capture 1 > > 00-02: Intel ICH - MIC2 ADC : Intel ICH5 - MIC2 ADC : capture 1 > > 00-01: Intel ICH - MIC ADC : Intel ICH5 - MIC ADC : capture 1 > > 00-00: Intel ICH : Intel ICH5 : playback 1 : capture 1 > > > > about /proc/asound/cards: > > ------------------------ > > 0 [ICH5 ]: ICH4 - Intel ICH5 > > Intel ICH5 with AD1985 at irq 22 > > 1 [UART ]: MPU-401 UART - MPU-401 UART > > MPU-401 UART at 0x300, irq 10 > > > > USB modem not detected by lsusb > > > > For candidate card in slot 02:0c.0, firmware information and bootup > > diagnostics are: > > PCI slot PCI ID SubsystemID Name > > ---------- --------- --------- -------------- > > 02:0c.0 10b9:5459 10a5:5459 Modem: ALi Corporation SmartLink > > SmartPCI561 56K Modem > > > > Modem interrupt assignment and sharing: > > --- Bootup diagnostics for card in PCI slot 02:0c.0 ---- > > [ 14.069898] ACPI: PCI Interrupt 0000:02:0c.0[A] -> GSI 20 (level, > > low) -> IRQ 16 > > [ 14.071125] 0000:02:0c.0: ttyS2 at I/O 0xd428 (irq = 16) is a 8250 > > [ 14.071762] 0000:02:0c.0: ttyS3 at I/O 0xd440 (irq = 16) is a 8250 > > [ 14.071874] Couldn't register serial port 0000:02:0c.0: -28 > > > > > > === Finished modem firmware and bootup diagnostics section. === > > === Next deducing cogent software === > > > > > > > > For candidate modem in PCI bus: 02:0c.0 > > Class 0703: 10b9:5459 Modem: ALi Corporation SmartLink SmartPCI561 > > 56K Modem > > Primary PCI_id 10b9:5459 > > Support type needed or chipset: slamr > > > > > > ----------------end Softmodem section -------------- > > The modem is supported by the Smartlink slamr driver > > plus the slmodemd helper utility. Read the > > Smartlink.txt and Modem/YourSystem.txt for follow through guidance. > > > > > > For 2.6.22-14-generic compiling drivers is necessary. As of October 2007 > > the current packages at > > http://linmodems.technion.ac.il/packages/smartlink/ are the > > ungrab-winmodem-20070505.tar.gz and slmodem-2.9.11-20070813.tar.gz > > > > Writing Smartlink.txt > > ============ end Smartlink section ===================== > > > > Completed candidate modem analyses. > > > > The base of the UDEV device file system is: /dev/.udev > > > > Versions adequately match for the compiler installed: 4.1.3 > > and the compiler used in kernel assembly: 4.1.3 > > > > > > > > Minimal compiling resources appear complete: > > make utility - /usr/bin/make > > Compiler version 4.1 > > linuc_headers base folder /lib/modules/2.6.22-14-generic/build > > > > However some compilations and executable functions may need additional > > files, > > in the FileNames.h (so called kernel "h"eaders) collection installed > > in /usr/include/ . > > For martian_modem, additional required packages are libc6-dev (and for > > Debian/Ubuntu, linux-libc-dev). The also required headers of package > > libc6 are commonly installed by default. > > > > > > > > If a driver compilation fails, with message including some lack of some > > FileName.h (stdio.h for example), then > > Some additional kernel-header files need installation to /usr/include. > > The minimal additional packages are libc6-dev > > and any of its dependents, under Ubuntu linux-libc-dev > > > > If an alternate ethernet connection is available, > > $ apt-get update > > $ apt-get -s install linux-kernel-devel > > will install needed package > > For Debian/Ubuntu related distributions, run the following command to > > display the needed package list: > > > > Otherwise packages have to be found through http://packages.ubuntu.com > > Once downloaded and transferred into a Linux partition, > > they can be installed alltogether with: > > $ sudo dpkg -i *.deb > > > > > > Checking pppd properties: > > -rwsr-xr-- 1 root dip 269256 2007-10-04 20:57 /usr/sbin/pppd > > > > In case of an "error 17" "serial loopback" problem, see: > > http://phep2.technion.ac.il/linmodems/archive-sixth/msg02637.html > > > > To enable dialout without Root permission do: > > $ su - root (not for Ubuntu) > > sudo chmod a+x /usr/sbin/pppd > > or under Ubuntu related Linuxes > > sudo chmod a+x /usr/sbin/pppd > > > > Checking settings of: /etc/ppp/options > > asyncmap 0 > > noauth > > crtscts > > lock > > hide-password > > modem > > proxyarp > > lcp-echo-interval 30 > > lcp-echo-failure 4 > > noipx > > > > In case of a message like: > > Warning: Could not modify /etc/ppp/pap-secrets: Permission denied > > see http://linmodems.technion.ac.il/bigarch/archive-sixth/msg04656.html > > > > Read Modem/YourSystem.txt concerning other COMM channels: eth0 > > Which can interfere with Browser naviagation. > > > > Don't worry about the following, it is for the experts > > should trouble shooting be necessary. > > ========================================================== > > > > Checking for modem support lines: > > -------------------------------------- > > /device/modem symbolic link: > > slmodemd created symbolic link /dev/ttySL0: > > Within /etc/udev/ files: > > > > Within /etc/modprobe.conf files: > > /etc/modprobe.d/alsa-base:options snd-atiixp-modem index=-2 > > /etc/modprobe.d/alsa-base:options snd-via82xx-modem index=-2 > > /etc/modprobe.d/blacklist-modem:# Uncomment these entries in order to > > blacklist unwanted modem drivers > > /etc/modprobe.d/blacklist-modem:# blacklist snd-atiixp-modem > > /etc/modprobe.d/blacklist-modem:# blacklist snd-via82xx-modem > > Within any ancient /etc/devfs files: > > > > Within ancient kernel 2.4.n /etc/module.conf files: > > > > --------- end modem support lines -------- > > > > > > Jacques Goldberg ha scritto: > >> You have to understand that these soft modems may seem to work (and > >> yiu hear the noise, but how since the SmartLink driver does not > >> support sound ?) but what you send to the modem goes into vacuum if > >> you do not have the right driver. > >> > >> So, to know exactly what your modem has in its guts, and then help > >> you, we need the report ModemData.txt prepared by scanModem: > >> http://linmodems.technion.ac.il/#scanModem > >> > >> Jacques > >> > >> Emanuele Pagone wrote: > >>> Hello, > >>> > >>> I've installed with no problems my Smartlink compatible PCI modem > >>> Netodragon MDV92XP (ScanModem identifies it as 10b9:5459) on my > >>> Ubuntu 7.10 machine following the instructions given in the Ubuntu wiki. > >>> > >>> Now I'm having problems with the connection using wvdial because the > >>> modem can't ''catch'' the server answer. In fact, this is what I get: > >>> > >>> emanuele@emanuele-desktop:~$ wvdial > >>> WvDial: WvDial: Internet dialer version 1.56 > >>> WvModem: Cannot get information for serial port. > >>> WvDial: Initializing modem. > >>> WvDial: Sending: ATZ > >>> WvDial Modem: ATZ > >>> WvDial Modem: OK > >>> WvDial: Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 X3 > >>> WvDial Modem: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 X3 > >>> WvDial Modem: OK > >>> WvDial: Modem initialized. > >>> WvDial: Sending: ATDT0802201400 > >>> WvDial: Waiting for carrier. > >>> WvDial Modem: ATDT0802201400 > >>> > >>> at this step, about 45 seconds after the server answer (that I can > >>> hear without problems), I get on the console: > >>> > >>> WvDial: Timed out while dialing. Trying again. > >>> WvDial: Sending: ATDT0802201400 > >>> WvDial: Waiting for carrier. > >>> WvDial Modem: NO CARRIER > >>> WvDial Modem: ATDT0802201400 > >>> WvDial: No Carrier! Trying again. > >>> WvDial: Sending: ATDT0802201400 > >>> WvDial: Waiting for carrier. > >>> WvDial Modem: NO CARRIER > >>> WvDial Modem: ATDT0802201400 > >>> WvDial: No Carrier! Trying again. > >>> > >>> Here starts an endless loop, as you can guess, and I must stop it > >>> with Ctrl-c. > >>> > >>> My wvdial.conf is: > >>> > >>> [Dialer Defaults] > >>> Init1 = ATZ > >>> Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 X3 > >>> Modem Type = Analog Modem > >>> Baud = 460800 > >>> New PPPD = yes > >>> Modem = /dev/ttySL0 > >>> ISDN = 0 > >>> Carrier Check = no > >>> Stupid Mode = yes > >>> Phone = 0802201400 > >>> Password = ******************************* > >>> Username = ******************************* > >>> > >>> the provider is Infinito, but I've tested also another one, Libero, > >>> (always using a local POP 080) getting the same results. > >>> > >>> I've tried a lot of different strings for 'Init2': adding +MS=34 or > >>> +MS=90, substituting &D0 with &D2, erasing &C1, &D2 and/or +FCLASS=0 > >>> (in every combination), using ATS11=40 or, finally, copying the > >>> 'Init' string inside the '.inf' file of my Windows drivers that make > >>> the modem working now. That string is: AT &F E0 X3 V1 &A3 &D2 &C1 S0=0. > >>> > >>> All these attempts failed in the same way just described. I'm able to > >>> send you ScanModem output, if needed. > >>> > >>> Can you help me? > >>> > >>> Thank you for reading, and sorry for my bad English. > >>> > >>> > >>> Emanuele > >
