Kam, scanModem does find modem port /dev/ttySL0, all that remains for you to do, if you already did, sorry about adding it several times remove the ";" and add username, password, and ISP phone number, add a line "Carrier Check = no" [Dialer Defaults] Modem = /dev/ttySL0 Baud = 460800 Init1 = ATZ Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 ISDN = 0 Modem Type = Analog Modem ; Phone = <Target Phone Number> ; Username = <Your Login Name> ; Password = <Your Password> After removing ";" and adding correct information, you may add line Carrier Check = no Try to dialout and save the attempt to a file and send it to list. Use the trick in Modem/DOCs/wvdial.txt ## To make a logfile wvdial.out # wvdial 2>&1 | tee wvdial.out send us wvdial.out in case you cannot connect. Also since you used # slmodemd -c 50 /dev/ttyS2 where 50 is the country code or HONG_KONG, it would be wise to edit /etc/rc.d/init.d/slmodemd and as root (su -) change SLMODEMD_COUNTRY=USA or SLMODEMD_COUNTRY=ITALY, to SLMODEMD_COUNTRY=HONG_KONG and try to connect again. $ su - passwd: # gedit /etc/rc.d/init.d/slmodemd make the above change and try to dialout using the wvdial 2>&1 | tee wvdial.out trick, and you may at your option also open up another terminal (su -) and run # tail -f /var/log/messages to see what is going on at the time of connection. Regards, Antonio On 5/3/10, Kam Yan Lo <kamyanlo@xxxxxxxxxxxx> wrote: > is other problem ? > have msg ,but dialing no connection > > [root@localhost ~]# wvdialconf /etc/wvdial.conf > Scanning your serial ports for a 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. > ttySL0<Info>: Speed 460800; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0" > [root@localhost ~]# > > > > > ----- 郵件原件 ---- > 寄件人﹕ Antonio Olivares <olivares14031@xxxxxxxxx> > 收件人﹕ Kam Yan Lo <kamyanlo@xxxxxxxxxxxx> > 傳送日期﹕ 2010/4/30 (五) 8:25:52 PM > 主題： Re: Re： Re： Re： ModemData.txt > > On 4/30/10, Kam Yan Lo <kamyanlo@xxxxxxxxxxxx> wrote: >> # modprobe ungrab-winmodem >> # modprobe slamr >> # slmodemd -c 50 /dev/slamr0 >> > Did you leave the terminal shell running and fire up another terminal? > > If you used CTRL+C you will more than 99.9% of the time see message below :( >> >> [root@localhost ~]# wvdialconf /etc/wvdial.conf >> Scanning your serial ports for a modem. >> Port Scan<*1>: S0 S1 S2 S3 >> >> Sorry, no modem was detected! Is it in use by another program? >> Did you configure it properly with setserial? >> Please read the FAQ at http://open.nit.ca/wvdial/ >> If you still have problems, send mail to wvdial-list@xxxxxxxxxxxxx >> [root@localhost ~]# >> >> > > Leave the shell running slmodemd on and fire up another shell and then > do the above again. Otherwise, I will drop my case and suggest: > > $ su - > passwd: > # cd slmodem-2.9.11-20080126/scripts > # cp slmodemd /etc/rc.d/init.d/ > > Fire up an editor maybe gedit > # gedit /etc/rc.d/init.d/slmodemd > > and after start procedure add > start { > /* somewhere here before slmodemd call */ > > } > # modprobe ungrab-winmodem > # modprobe slamr > save the file then run > # cbkconfig slmodemd --add > # chkconfig slmodemd on > # chkconfig slmodemd --list > > Then reboot and check to see if slmodemd is running: > $ su - > passwd: > # service slmodemd status > > Let me know how this goes. If it does not work for some reason or > another, I will post a link to a page I made for this purpose. > > Regards, > > Antonio > >> >> >> >> >> ----- 郵件原件 ---- >> 寄件人﹕ Antonio Olivares <olivares14031@xxxxxxxxx> >> 收件人﹕ Kam Yan Lo <kamyanlo@xxxxxxxxxxxx> >> 傳送日期﹕ 2010/4/30 (五) 3:58:34 PM >> 主題： Re: Re： Re： ModemData.txt >> >> Kam, >> >> On 4/30/10, Kam Yan Lo <kamyanlo@xxxxxxxxxxxx> wrote: >>> [root@localhost ~]# modprobe ungrab-winmodem >>> [root@localhost ~]# modprobe slamr >>> [root@localhost ~]# slmodemd -c 50 /dev/slamr0 >>> error: mdm setup: cannot stat `/dev/slamr0': No such file or directory >>> error: cannot setup device `/dev/slamr0' >>> [root@localhost ~]# slmodemd -c 50 /dev/ttyS2 >>> SmartLink Soft Modem: version 2.9.11 Apr 29 2010 08:56:04 >>> bad country name `50', using default by code! >>> symbolic link `/dev/ttySL66' -> `/dev/pts/3' created. >>> modem `ttyS2' created. TTY is `/dev/pts/3' >>> Use `/dev/ttySL66' as modem device, Ctrl+C for termination. >> When you get to this point, Dont press CTRL +C, this kills slmodemd >> and thus wvdialconf /etc/wvdial.conf fails. Fire up another >> terminal, and leave this running, then go and do this >>> [root@localhost ~]# wvdialconf /etc/wvdial.conf >>> Scanning your serial ports for a modem. >>> ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud >>> ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud >>> ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. >>> ttyS1<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud >>> ttyS1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud >>> ttyS1<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. >>> Port Scan<*1>: S2 S3 >>> >>> Sorry, no modem was detected! Is it in use by another program? >>> Did you configure it properly with setserial? >>> Please read the FAQ at http://open.nit.ca/wvdial/ >>> If you still have problems, send mail to wvdial-list@xxxxxxxxxxxxx >> >> The modem should be found. After you see that this works, we could >> automate the process so you won't have to go and do a >> # modprobe ungrab-winmodem >> # modprobe slamr >> # slmodemd -c 50 /dev/slamr0 >> >> Hopefully this time it will work so I can tell you how to do it. >> >> Regards, >> >> Antonio >> >>> [root@localhost ~]# >>> >>> lspci -vv >>> >>> 00:13.0 Modem: Motorola SM56 Data Fax Modem (rev 04) (prog-if 00 >>> [Generic]) >>> Subsystem: Motorola Unknown device 3020 >>> Control: I/O- Mem- BusMaster- SpecCycle- MemWINV+ VGASnoop- >>> ParErr- >>> Stepping+ SERR+ FastB2B- >>> Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- >>> <TAbort- <MAbort- >SERR- <PERR- >>> Interrupt: pin A routed to IRQ 9 >>> Region 0: Memory at febfe000 (32-bit, non-prefetchable) [disabled] >>> [size=4K] >>> Region 1: I/O ports at e400 [disabled] [size=256] >>> Capabilities: [80] Power Management version 2 >>> Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA >>> PME(D0+,D1-,D2-,D3hot+,D3cold+) >>> Status: D0 PME-Enable- DSel=0 DScale=0 PME- >>> >>> is Motorola Unknown device 3020? >>> >>> >>> ----- 郵件原件 ---- >>> 寄件人﹕ Antonio Olivares <olivares14031@xxxxxxxxx> >>> 收件人﹕ Kam Yan Lo <kamyanlo@xxxxxxxxxxxx> >>> 副本(CC) discuss@xxxxxxxxxxxxxx >>> 傳送日期﹕ 2010/4/30 (五) 5:53:07 AM >>> 主題： Re: Re： ModemData.txt >>> >>> Kam, >>> >>> On 4/29/10, Kam Yan Lo <kamyanlo@xxxxxxxxxxxx> wrote: >>>> thank you for your help >>>> >>>> i'm installed ungrab-winmodem-20070505.tar.gz and >>>> slmodem-2.9.11-20080126.tar.gz >>>> but not work >>>> >>>> i used minicom setup to slamr0 not connect >>>> >>>> [root@localhost slmodem-2.9.11-20080126]# slmodemd -c YOUR_COUNTRY >>>> /dev/slamr0 >>>> SmartLink Soft Modem: version 2.9.11 Apr 29 2010 08:56:04 >>>> bad country name `YOUR_COUNTRY', using default by code! >>>> symbolic link `/dev/ttySL0' -> `/dev/pts/3' created. >>>> modem `slamr0' created. TTY is `/dev/pts/3' >>>> Use `/dev/ttySL0' as modem device, Ctrl+C for termination. >>>> >>> >>> Leave this command running. You may use CHINA? or HONG_KONG in place >>> of YOUR_COUNTRY. You can see from running slmodemd --countrylist: >>> >>> 26: CHINA >>> or >>> 50: HONG_KONG >>> >>> root@slax:~# slmodemd --countrylist >>> 02: ALGERIA >>> 07: ARGENTINA >>> 09: AUSTRALIA >>> 0a: AUSTRIA >>> 0c: BAHREIN >>> 0f: BELGIUM >>> 16: BRAZIL >>> 1a: BRUNEI >>> 1b: BULGARIA >>> 20: CANADA >>> 25: CHILE >>> 26: CHINA >>> 100: CTR21EUROPE >>> 2d: CYPRUS >>> 2e: CZECH_REPUBLIC >>> 31: DENMARK >>> 36: EGYPT >>> 101: ESTONIA >>> 3c: FINLAND >>> 3d: FRANCE >>> 42: GERMANY >>> 46: GREECE >>> 50: HONG_KONG >>> 51: HUNGARY >>> 52: ICELAND >>> 53: INDIA >>> 54: INDONESIA >>> 57: IRELAND >>> 58: ISRAEL >>> 59: ITALY >>> 00: JAPAN >>> 5e: JORDAN >>> 61: KOREA >>> 62: KUWAIT >>> 103: LATVIA >>> 64: LEBANON >>> 104: LITHUANIA >>> 69: LUXEMBOURG >>> 6c: MALAYSIA >>> 70: MALTA >>> 73: MEXICO >>> 77: MOROCCO >>> 7b: NETHERLANDS >>> 7e: NEW_ZEALAND >>> 82: NORWAY >>> 83: OMAN >>> 84: PAKISTAN >>> 88: PERU >>> 89: PHILIPPINES >>> 8a: POLAND >>> 8b: PORTUGAL >>> 8e: ROMANIA >>> b8: RUSSIA >>> 98: SAUDIARABIA >>> 9c: SINGAPORE >>> c5: SLOVAKIA >>> c6: SLOVENIA >>> 9f: SOUTHAFRICA >>> 107: SOUTHKOREA >>> a0: SPAIN >>> a1: SRILANKA >>> a5: SWEDEN >>> a6: SWITZERLAND >>> 108: TAIWAN >>> a9: THAILAND >>> ad: TUNISIA >>> ae: TURKEY >>> b3: UAE >>> b4: UK >>> b7: URUGUAY >>> b5: USA >>> bc: VIETNAM >>> >>> >>> >>> Then run this one >>> >>>> [root@localhost slmodem-2.9.11-20080126]# wvdialconf /etc/wvdial.conf >>>> Scanning your serial ports for a modem. >>>> ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud >>>> ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud >>>> ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. >>>> ttyS1<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud >>>> ttyS1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud >>>> ttyS1<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. >>>> Port Scan<*1>: S2 S3 >>>> >>>> >>> After doing this wvdialconf /etc/wvdial.conf as root should find the >>> modem. >>> >>> Let us know how it goes. >>> >>> Regards, >>> >>> Antonio >>> >>>> Sorry, no modem was detected! Is it in use by another program? >>>> Did you configure it properly with setserial? >>>> >>>> >>>> 00:13.0 Modem: Motorola SM56 Data Fax Modem (rev 04) (prog-if 00 >>>> [Generic]) >>>> Subsystem: Motorola Unknown device 3020 >>>> Flags: bus master, stepping, medium devsel, latency 64, IRQ 9 >>>> Memory at febfe000 (32-bit, non-prefetchable) [size=4K] >>>> I/O ports at e400 [size=256] >>>> Capabilities: [80] Power Management version 2 >>>> >>>> >>>> >>>> >>>> ----- 郵件原件 ---- >>>> 寄件人﹕ Antonio Olivares <olivares14031@xxxxxxxxx> >>>> 收件人﹕ Kam Yan Lo <kamyanlo@xxxxxxxxxxxx> >>>> 副本(CC) discuss@xxxxxxxxxxxxx >>>> 傳送日期﹕ 2010/4/29 (四) 8:28:52 PM >>>> 主題： Re: ModemData.txt >>>> >>>> Kam, >>>> >>>> scanModem reports that your modem is supported through slmodem-2.9.11 >>>> code: >>>> >>>> Predictive diagnostics for card in bus 00:13.0: >>>> Modem chipset detected on >>>> NAME="Modem: Motorola SM56 Data Fax Modem " >>>> CLASS=0703 >>>> PCIDEV=1057:3052 >>>> SUBSYS=1057:3020 >>>> IRQ=9 >>>> IDENT=slamr >>>> >>>> For candidate modem in: 00:13.0 >>>> 0703 Modem: Motorola SM56 Data Fax Modem >>>> Primary device ID: 1057:3052 >>>> Support type needed or chipset: slamr >>>> >>>> >>>> >>>> 1057:3052 has a Motorola chipset, poorly supported by Motorola itself >>>> However Zello discovered that drivers written to support Smartlink >>>> modems do support the 1057:3052 chipset!! >>>> It sufficed to add 1057:3052 to the list of modem cards recognized by >>>> the Smartlink slamr driver. >>>> There is a ungrab-winmodem driver used in conjunction with slamr, >>>> which must have 1057:3052 >>>> similarly added. See messages from Zello: >>>> http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00846.html >>>> http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00848.html >>>> and Alvaro Aguirre about the ungrab-winmodem fix: >>>> http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00990.html >>>> For general guidance on ungrab-winmodem + slamr usage, read the >>>> DOCs/Smartlink.txt >>>> >>>> The modem is supported by the Smartlink >>>> plus the slmodemd helper utility. Read the >>>> DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for follow through >>>> guidance. >>>> >>>> For kernels 2.6.31 the slamr driver is not (yet) functional, failing >>>> within at the >>>> Carrier Check >>>> function. Thus for service, retain a 2.6.30 or earlier kernel. For >>>> Ubuntu users this >>>> can be done by downloading the kernel from >>>> http://packages.ubuntu.com/jaunty/linux-image-2.6.28-16-generic >>>> and from http://linmodems.technion.ac.il/packages/smartlink/Ubuntu/ >>>> the slamr-2.6.28-16-generic.tar.gz >>>> >>>> >>>> For 2.6.18-164.15.1.el5 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-20080126.tar.gz >>>> >>>> Writing DOCs/Smartlink.txt >>>> >>>> You may read DOCs/Smartlink.txt for more information. >>>> >>>> Do download: >>>> >>>> http://linmodems.technion.ac.il/packages/smartlink/ are the >>>> ungrab-winmodem-20070505.tar.gz and slmodem-2.9.11-20080126.tar.gz >>>> >>>> $ tar -zxvf slmodem-2.9.11-20080126.tar.gz >>>> $ cd slmodem-2.9.11-20080126 >>>> $ make KERNEL_VER=/lib/modules/`uname -r`/build >>>> $ make >>>> $ su -c 'make install' >>>> $ tar -zxvf ungrab-winmodem-20070505.tar.gz >>>> $ su - >>>> passwd: >>>> # cd ungrab-winmodem-20070505 >>>> # make >>>> # make install >>>> >>>> # exit >>>> $ su - >>>> passwd: >>>> # modprobe ungrab-winmodem >>>> # modprobe slamr >>>> # slmodemd -c YOUR_COUNTRY /dev/slamr0 >>>> >>>> then open up another terminal shell >>>> $ su - >>>> passwd: >>>> # wvdialconf /etc/wvdial.conf >>>> will scan and hopefully find /dev/ttySL0 as the modem port all that >>>> remains is edit /etc/wvdial.conf as root user and remove ";" and add >>>> username, password, ISP phone number and a line "Carrier Check = no" >>>> to it. Attempt to dialout and see if you can connect. If you can >>>> connect , but cannot browse add the nameserver to /etc/resolv.conf and >>>> save it. >>>> >>>> You may also download latest packages (don't know if they will compile >>>> with 2.6.18-? kernel). Should you encounter difficulties, let us know >>>> and we'll try to help. >>>> >>>> Regards, >>>> >>>> Antonio >>>> >>>> On 4/29/10, Kam Yan Lo <kamyanlo@xxxxxxxxxxxx> wrote: >>>>> ModemData.txt >>>>> >>>>> >>>>> >>>> >>>> >>>> >>>> >>>> >>>> >>> >>> >>> >>> >>> >>> >> >> >> >> >> >> > > > >
