No wvdial disn't succeed to dialout. On 2/20/08, Jacques Goldberg <Jacques.Goldberg@xxxxxxx> wrote: > As far as I remember, but I may be wrong, the SmartLink driver does not > recognize incoming calls. > Sasha, am I right? > > > Marvin Stodolsky wrote: > > BY, > > > > Would you please relate whether the modem succeeds in a simple dialout > > using wvdial, > > as we have not yet had a firm evaluation in dialout mode with the > >>> NAME="Modem: SILICON Laboratories > >>> PCIDEV=1543:3052 > >>> SUBSYS=1543:3000 > > chipset. > > > > Jacques is much more knowledgeable than I on server applications > > and may be able to help you further. > > > > MarvS > > > > On Feb 19, 2008 3:15 PM, B. Younes <behloul.maliste@xxxxxxxxx> wrote: > >> Hi Marvin, > >> > >> Thank you for the recommandations. I've followed them but the problem > >> is still here. > >> > >> I wan't to use my linmodem as a dial-in server, to remotly connect to > >> the server. > >> > >> I still have the problem when trying to dial (even with wvdial) or > >> answer a call with the AT Hayes command "ATA", the modem doesn't log > >> any message when recieving a call, and when I send the command "ATA" > >> to the modem, it hangs !! > >> The modem answer al these commands: > >> > >> > >> #minicom > >> AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0 > >> OK > >> ATI > >> SmartLink Soft Modem > >> OK > >> ATI2 > >> SmartLink Soft Modem, 2.9.11 > >> Smart Link Ltd. > >> OK > >> ATI3 > >> /dev/slamr0 > >> modemap driver > >> OK > >> ATI4 > >> s00=000 s01=000 s02=043 s03=013 s04=010 s05=008 s06=002 s07=045 > >> s08=002 s09=006 s10=007 s11=100 s12=050 s13=001 s14=000 s15=001 > >> s16=001 s17=000 s18=000 s19=000 s20=000 s21=000 s22=000 s23=000 > >> > >> OK > >> ATI5 > >> Stored Profile 0: > >> OK > >> ATI6 > >> Stored Profile 1: > >> OK > >> ATI7 > >> Country: ALGERIA > >> OK > >> ATI8 > >> ERROR > >> > >> ATD 050024222 > >> (HANG) > >> > >> > >> Hope this helps to clarify the problem. > >> > >> > >> On Feb 19, 2008 3:07 PM, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> wrote: > >>> BY > >>> > >>> For > >>> > >>> CLASS="Class 0703: 1543:3052" > >>> NAME="Modem: SILICON Laboratories Intel 537 [Winmodem] " > >>> PCIDEV=1543:3052 > >>> SUBSYS=1543:3000 > >>> SUBven=1543 > >>> IRQ=7 > >>> IDENT=INTEL537_on_1543:3052 > >>> > >>> Support through the slamr driver is CORRECT to try, but support is > >>> provisional with your > >>> ---- > >>> root@ankara:/usr/src/slmodem-2.9.11-20080126/modem# ./slmodemd -c > >>> ALGERIA /dev/slamr0 > >>> SmartLink Soft Modem: version 2.9.11 Feb 19 2008 12:18:12 > >>> symbolic link `/dev/ttySL0' -> `/dev/pts/4' created. > >>> modem `slamr0' created. TTY is `/dev/pts/4' > >>> ---- > >>> GOOD starting news. > >>> Try to improve the System through the following steps: > >>> 1) Complete uninstall any hsfmodem software: > >>> # hsfconfig --uninstall > >>> as it may be competing for resources > >>> 2) The sl-modem-daemon package installed an older version 2.9.9 > >>> slmodemd, which cannot serve. So > >>> # mv /usr/sbin/slmodemd /usr/sbin/slmodemd.2.9.9. > >>> # cp -a /usr/src/slmodem-2.9.11-20080126/modem/slmodemd /usr/sbin/slmodemd > >>> Then > >>> # slmodemd --version > >>> should report 2.9.11 > >>> > >>> Replace the default USA with ALGERIA through > >>> # sudo gedit /etc/default/sl-modem-daemon > >>> Reboot. The sl-modem-daemon should now do the modem activation > >>> automatically through > >>> the step: > >>> # slmodemd -c ALGERIA /dev/slamr0 > >>> > >>> Minicom is not an ideal testing tool for softmodems. See in the modem > >>> is found through > >>> # wvdialconf /etc/wvdial.conf > >>> Edit in your dialout info with > >>> # sudo gedit /etc/wvdial.conf > >>> adding the line > >>> Carrier Check = no > >>> and removing the symbols ; < > > >>> > >>> Save. > >>> Try a dialout with > >>> # wvdial. > >>> > >>> Please report back!!! > >>> > >>> MarvS > >>> scanModem maintainer > >>> > >>> > >>> > >>> On Feb 19, 2008 7:05 AM, B. Younes <behloul.maliste@xxxxxxxxx> wrote: > >>>> subsubject "Linmodem, Intex chipset Silicon Labs, driver slmodem can't > >>>> answer "ATA"" > >>>> > >>>> Hello, > >>>> > >>>> I've read and followed Linmodem Howto. it helped me to find the > >>>> correct Linux driver, but I still have a small problem: > >>>> It's about a PCI Modem card, made by Intex (China), I downloaded a > >>>> installed the last slmodem > >>>> > >>>> 1) Loading slmodem driver > >>>> (slmodem-2.9.11-20080126), the driver regognise the Modem and print this (dmesg) > >>>> ----------- start dmesg log ---- > >>>> slamr: SmartLink AMRMO modem. > >>>> slamr: probe 1543:3052 SL2800 card... > >>>> ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKE] -> GSI 7 (level, > >>>> low) -> IRQ 7 > >>>> slamr: amrmo_pci_probe: 0 amrmo is c3fe0000. data d3328a40, io a000, 0. > >>>> slamr: slamr0 is SL2800 card. > >>>> ------------ end dmesg log ----- > >>>> > >>>> 2) starting slmodemd deamon > >>>> root@ankara:/usr/src/slmodem-2.9.11-20080126/modem# ./slmodemd -c > >>>> ALGERIA /dev/slamr0 > >>>> SmartLink Soft Modem: version 2.9.11 Feb 19 2008 12:18:12 > >>>> symbolic link `/dev/ttySL0' -> `/dev/pts/4' created. > >>>> modem `slamr0' created. TTY is `/dev/pts/4' > >>>> Use `/dev/ttySL0' as modem device, Ctrl+C for termination. > >>>> > >>>> 3) starting minicom > >>>> AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0 > >>>> OK > >>>> at > >>>> OK > >>>> ath1 > >>>> OK > >>>> ath0 > >>>> OK > >>>> ata > >>>> (HUNG !!!) > >>>> > >>>> I've also loaded the driver in debug mode, no message is logged when a > >>>> dial-in call arrives. > >>>> > >>>> Next is the ModemData.txt: > >>>> > >>>> Thanks in advance. > >>>> ############ START MODEMDATA.TXT ########### > >>>> Only plain text email is forwarded by the Discuss@xxxxxxxxxxxxx List Server, > >>>> as HTML can contain viruses. Use as the email Subject Line: > >>>> YourName, YourCountry Debian GNU/Linux 4.0 kernel 2.6.22.15 > >>>> With this Subject Line cogent experts will be alerted, and useful > >>>> case names left in the Archive. > >>>> YourCountry will enable Country specific guidance. Your contry's > >>>> local Linux experts > >>>> can be found through: http://www.linux.org/groups/index.html. > >>>> They will know your Country's modem code, which may be essential for > >>>> dialup service. > >>>> Responses from Discuss@xxxxxxxxxxxxx are sometimes blocked by an > >>>> Internet Provider mail filters. > >>>> So in a day, also check the Archived responses at http://www.linmodems.org > >>>> -------------------------- System information ---------------------------- > >>>> CPU=i686, Debian GNU/Linux 4.0 > >>>> Linux version 2.6.22.15 (root@ankara) (gcc version 3.4.6 (Debian > >>>> 3.4.6-5)) #3 Wed Feb 13 09:15:32 CET 2008 > >>>> scanModem update of: 2008_02_10 > >>>> The modem symbolic link is /dev/modem -> ttySL0 > >>>> > >>>> There are no blacklisted modem drivers in /etc/modprobe* files > >>>> PCI slot 00:1b.0 has a High Definition Audio Card > >>>> > >>>> 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. > >>>> > >>>> USB modem not detected by lsusb > >>>> For candidate card in slot 01:00.0, firmware information and bootup > >>>> diagnostics are: > >>>> PCI slot PCI ID SubsystemID Name > >>>> ---------- --------- --------- -------------- > >>>> 01:00.0 1543:3052 1543:3000 Modem: SILICON Laboratories Intel 537 [Winmodem] > >>>> > >>>> Modem interrupt assignment and sharing: > >>>> --- Bootup diagnostics for card in PCI slot 01:00.0 ---- > >>>> ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKE] -> GSI 7 (level, > >>>> low) -> IRQ 7 > >>>> Couldn't register serial port 0000:01:00.0: -28 > >>>> > >>>> For candidate card in slot 00:1b.0, firmware information and bootup > >>>> diagnostics are: > >>>> PCI slot PCI ID SubsystemID Name > >>>> ---------- --------- --------- -------------- > >>>> 00:1b.0 8086:27d8 1458:a002 Audio device: Intel Corporation 82801G > >>>> > >>>> Modem interrupt assignment and sharing: > >>>> 5: 0 XT-PIC-XT uhci_hcd:usb5 > >>>> --- Bootup diagnostics for card in PCI slot 00:1b.0 ---- > >>>> > >>>> > >>>> === Finished modem firmware and bootup diagnostics section. === > >>>> === Next deducing cogent software === > >>>> > >>>> > >>>> > >>>> > >>>> Predictive diagnostics for card in PCI bus 01:00.0: > >>>> Modem chipset not detected on > >>>> CLASS="Class 0703: 1543:3052" > >>>> NAME="Modem: SILICON Laboratories Intel 537 [Winmodem] " > >>>> PCIDEV=1543:3052 > >>>> SUBSYS=1543:3000 > >>>> SUBven=1543 > >>>> IRQ=7 > >>>> IDENT=INTEL537_on_1543:3052 > >>>> > >>>> For candidate modem in PCI bus: 01:00.0 > >>>> Class 0703: 1543:3052 Modem: SILICON Laboratories Intel 537 [Winmodem] > >>>> Primary PCI_id 1543:3052 > >>>> Support type needed or chipset: INTEL537_on_1543:3052 > >>>> > >>>> > >>>> ----------------end Softmodem section -------------- > >>>> > >>>> > >>>> Predictive diagnostics for card in PCI bus 00:1b.0: > >>>> Modem chipset not detected on > >>>> CLASS="Class 0403: 8086:27d8" > >>>> NAME="Audio device: Intel Corporation 82801G " > >>>> PCIDEV=8086:27d8 > >>>> SUBSYS=1458:a002 > >>>> SUBven=1458 > >>>> IRQ=5 > >>>> HDA=8086:27d8 > >>>> SOFT=8086:27d8.HDA > >>>> > >>>> > >>>> High Definition Audio (HDA) cards MAY host a modem chip in their Subsystem, > >>>> and many are supported by the ALSA audio+modem driver snd-hda-intel > >>>> A modem was not detected on HDA card 8086:27d8. > >>>> If another modem card is present, then most likely 8086:27d8 does not > >>>> host a modem. > >>>> If another modem card has not been detected, then possibilities are: > >>>> 1) A Conexant modem chip is present on 8086:27d8, as Conexant chips > >>>> are frequently not detectable by ALSA diagnostics > >>>> 2) The modem may be of the older non-PCI Controller Chipset (hardware) type. > >>>> Try detection with Root permission: > >>>> wvdialconf /etc/wvdial.conf > >>>> > >>>> For candidate modem in PCI bus: 00:1b.0 > >>>> Class 0403: 8086:27d8 Audio device: Intel Corporation 82801G > >>>> Primary PCI_id 8086:27d8 > >>>> Subsystem PCI_id 1458:a002 > >>>> Softmodem codec or chipset from diagnostics: > >>>> from Archives: > >>>> > >>>> > >>>> > >>>> Lacking a dsp (digital signal processing) chip, the modem is a software > >>>> intensive or "softmodem" type. Its primary controller manages the traffic > >>>> with the CPU. But the software needed is specified in the Subsystem. > >>>> ----------------------------------------- > >>>> Support type needed or chipset: > >>>> > >>>> Support can likely be achieved through two mutually exclusive alternatives: > >>>> 1) The hsfmodem software for Conexant chipset modems: Read Conexant.txt > >>>> The following ALSA alternative CANNOT work with Conexant modems. > >>>> > >>>> 2) An ALSA modem driver plus slmodemd. Read Smartlink.txt for details, and > >>>> to test get the package SLMODEMD.gcc3.4.tar.gz from: > >>>> http://linmodems.technion.ac.il/packages/smartlink/ > >>>> > >>>> ----------------end Softmodem section -------------- > >>>> > >>>> Completed candidate modem analyses. > >>>> > >>>> The base of the UDEV device file system is: /dev/.udev > >>>> > >>>> Versions adequately match for the compiler installed: 3.4.6 > >>>> and the compiler used in kernel assembly: 3.4.6 > >>>> > >>>> > >>>> > >>>> Minimal compiling resources appear complete: > >>>> make utility - /usr/bin/make > >>>> Compiler version 3.4 > >>>> linuc_headers base folder /lib/modules/2.6.22.15/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. > >>>> > >>>> Compressed files at: /usr/src/linux-2.6.20.4.tar.bz2 > >>>> /usr/src/sl-modem.tar.bz2 /usr/src/squashfs.tar.bz2 > >>>> > >>>> For Debian and some related distributions, a package > >>>> kernel-kbuild-2.6-22 may be needed to support driver compiling > >>>> > >>>> > >>>> 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 265880 2006-06-04 04:58 /usr/sbin/pppd > >>>> > >>>> In case of an "error 17" "serial loopback" problem, see: > >>>> http://linmodems.technion.ac.il/linmodems/archive-sixth/msg02637.html > >>>> > >>>> To enable dialout without Root permission do: > >>>> $ su - root (not for Ubuntu) > >>>> chmod a+x /usr/sbin/pppd > >>>> or under Ubuntu related Linuxes > >>>> chmod a+x /usr/sbin/pppd > >>>> > >>>> Checking settings of: /etc/ppp/options > >>>> asyncmap 0 > >>>> auth > >>>> 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. > >>>> ========================================================== > >>>> > >>>> # start/stop the daemon when the USB modem is connected > >>>> KERNEL=="slusb[0-9]*", GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon" > >>>> Checking for modem support lines: > >>>> -------------------------------------- > >>>> /device/modem symbolic link: lrwxrwxrwx 1 root root 6 > >>>> 2008-02-19 11:43 /dev/modem -> ttySL0 > >>>> slmodemd created symbolic link /dev/ttySL0: > >>>> Within /etc/udev/ files: > >>>> /etc/udev/rules.d/030_sl-modem-daemon.rules:# start/stop the daemon > >>>> when the USB modem is connected > >>>> /etc/udev/rules.d/030_sl-modem-daemon.rules:KERNEL=="slusb[0-9]*", > >>>> GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon" > >>>> /etc/udev/sl-modem-daemon.rules:# start/stop the daemon when the USB > >>>> modem is connected > >>>> /etc/udev/sl-modem-daemon.rules:KERNEL=="slusb[0-9]*", > >>>> GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon" > >>>> 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/sl-modem-daemon.modutils:install slamr modprobe > >>>> --ignore-install ungrab-winmodem ; modprobe --ignore-install slamr; > >>>> test -e /dev/slamr0 || (/bin/mknod -m 660 /dev/slamr0 c 242 0 > >>>> 2>/dev/null && chgrp dialout /dev/slamr0) > >>>> /etc/modprobe.d/alsa-base-blacklist:# Uncomment these entries in order > >>>> to blacklist unwanted modem drivers > >>>> /etc/modprobe.d/alsa-base-blacklist:# blacklist snd-atiixp-modem > >>>> /etc/modprobe.d/alsa-base-blacklist:# blacklist snd-via82xx-modem > >>>> Within any ancient /etc/devfs files: > >>>> > >>>> Within ancient kernel 2.4.n /etc/module.conf files: > >>>> /etc/modules.conf:options snd-atiixp-modem index=-2 > >>>> /etc/modules.conf:options snd-via82xx-modem index=-2 > >>>> /etc/modules.conf:# Uncomment these entries in order to blacklist > >>>> unwanted modem drivers > >>>> /etc/modules.conf:# alias snd-atiixp-modem off > >>>> /etc/modules.conf:# alias snd-via82xx-modem off > >>>> /etc/modules.conf:### update-modules: start processing > >>>> /etc/modutils/sl-modem-daemon.modutils > >>>> /etc/modules.conf:### update-modules: end processing > >>>> /etc/modutils/sl-modem-daemon.modutils > >>>> /etc/modules.conf.old:options snd-atiixp-modem index=-2 > >>>> /etc/modules.conf.old:options snd-via82xx-modem index=-2 > >>>> /etc/modules.conf.old:# Uncomment these entries in order to blacklist > >>>> unwanted modem drivers > >>>> /etc/modules.conf.old:# alias snd-atiixp-modem off > >>>> /etc/modules.conf.old:# alias snd-via82xx-modem off > >>>> /etc/modules.conf.old:alias /dev/modem /dev/ttySHSF > >>>> /etc/modules.conf.old:### update-modules: start processing > >>>> /etc/modutils/sl-modem-daemon.modutils > >>>> /etc/modules.conf.old:### update-modules: end processing > >>>> /etc/modutils/sl-modem-daemon.modutils > >>>> --------- end modem support lines -------- > >>>> >
