Antonio, RE: The device /dev/ttySL0 --> /dev/pts/1 stays the same when using wvdial and kppp is more flexible and I disconnect and reconnect again, and the new /dev/ttySL0 --> /dev/pts/2, ..., /dev/ttySL0 --> /dev/pts/3, --------- After a session using wvdial, terminated by Ctrl-C, check the ports with: ln -s /dev/ttyS0 /dev/pts/* Manually remove the symbolic link: # rm /dev/ttySL0 Do the slmodemd restart & check the ports again: ln -s /dev/ttyS0 /dev/pts/* and try the dialout. I suspect that it is the retained /dev/ttySL0 that has been causing the problem, and that you will find a different /dev/pts/N usage, as you haved reported with KPPP usage. If this proves to be the only problem, a scriplet can always be added to delete the old /dev/ttySL0 under modem shutdown. MarvS On Sat, May 2, 2009 at 12:43 PM, Antonio Olivares <olivares14031@xxxxxxxxx> wrote: > Ahmed, > > I think I have found out why. Take a look below: > > This is when I am using wvdiial: > > [root@localhost ~]# wvdial > --> WvDial: Internet dialer version 1.60 > --> Cannot get information for serial port. > --> Initializing modem. > --> Sending: ATZ > ATZ > OK > --> Sending: ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 > ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 > OK > --> Modem initialized. > --> Sending: ATDT7072000 > --> Waiting for carrier. > ATDT7072000 > CONNECT 42667 > --> Carrier detected. Starting PPP immediately. > --> Starting pppd at Sat May 2 11:20:14 2009 > --> Pid of pppd: 3119 > --> Using interface ppp0 > --> pppd: �;[08]H�;[08] > --> pppd: �;[08]H�;[08] > --> pppd: �;[08]H�;[08] > --> local IP address 66.201.8.196 > --> pppd: �;[08]H�;[08] > --> remote IP address 66.201.8.6 > --> pppd: �;[08]H�;[08] > --> primary DNS address 66.201.0.203 > --> pppd: �;[08]H�;[08] > --> secondary DNS address 66.94.120.9 > --> pppd: �;[08]H�;[08] > ^CCaught signal 2: Attempting to exit gracefully... > --> Terminating on signal 15 > --> pppd: �;[08]H�;[08] > --> Connect time 12.1 minutes. > --> pppd: �;[08]H�;[08] > --> pppd: �;[08]H�;[08] > --> Disconnecting at Sat May 2 11:32:17 2009 > [root@localhost ~]# wvdial > --> WvDial: Internet dialer version 1.60 > --> Cannot get information for serial port. > --> Initializing modem. > --> Sending: ATZ > --> Sending: ATQ0 > --> Re-Sending: ATZ > --> Modem not responding. > [root@localhost ~]# service slmodemd stop > [root@localhost ~]# service slmodemd start > Starting SmartLink Modem driver for slamr0: [ OK ] > [root@localhost ~]# wvdial > --> WvDial: Internet dialer version 1.60 > --> Cannot get information for serial port. > --> Initializing modem. > --> Sending: ATZ > ATZ > OK > --> Sending: ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 > ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 > OK > --> Modem initialized. > --> Sending: ATDT7072000 > --> Waiting for carrier. > ATDT7072000 > CONNECT 49333 > --> Carrier detected. Starting PPP immediately. > --> Starting pppd at Sat May 2 11:34:29 2009 > --> Pid of pppd: 4225 > --> Using interface ppp0 > --> pppd: ��[08]H��[08] > --> pppd: ��[08]H��[08] > --> pppd: ��[08]H��[08] > --> local IP address 66.201.8.212 > --> pppd: ��[08]H��[08] > --> remote IP address 66.201.8.6 > --> pppd: ��[08]H��[08] > --> primary DNS address 66.201.0.203 > --> pppd: ��[08]H��[08] > --> secondary DNS address 66.94.120.9 > --> pppd: ��[08]H��[08] > > [olivares@localhost ~]$ su - > Password: > [root@localhost ~]# ls /dev/slamr0 -l > crw-rw---- 1 root uucp 242, 0 2009-05-02 11:16 /dev/slamr0 > [root@localhost ~]# ls /dev/ttySL0 -l > lrwxrwxrwx 1 root root 10 2009-05-02 11:16 /dev/ttySL0 -> /dev/pts/1 > [root@localhost ~]# ls /dev/ttySL0 -l > lrwxrwxrwx 1 root root 10 2009-05-02 11:16 /dev/ttySL0 -> /dev/pts/1 > [root@localhost ~]# ls /dev/slamr0 -l > crw-rw---- 1 root uucp 242, 0 2009-05-02 11:16 /dev/slamr0 > [root@localhost ~]# ls /dev/ttySL0 -l > lrwxrwxrwx 1 root root 10 2009-05-02 11:16 /dev/ttySL0 -> /dev/pts/1 > [root@localhost ~]# ls /dev/slamr0 -l > crw-rw---- 1 root uucp 242, 0 2009-05-02 11:16 /dev/slamr0 > [root@localhost ~]# ls /dev/ttySL0 -l > lrwxrwxrwx 1 root root 10 2009-05-02 11:16 /dev/ttySL0 -> /dev/pts/1 > [root@localhost ~]# ls /dev/slamr0 -l > crw-rw---- 1 root uucp 242, 0 2009-05-02 11:16 /dev/slamr0 > [root@localhost ~]# ls /dev/ttySL0 -l > lrwxrwxrwx 1 root root 10 2009-05-02 11:33 /dev/ttySL0 -> /dev/pts/1 > > > The device /dev/ttySL0 --> /dev/pts/1 stays the same when using wvdial > and kppp is more flexible and I disconnect and reconnect again, and > the new /dev/ttySL0 --> /dev/pts/2, ..., /dev/ttySL0 --> /dev/pts/3, > .... and so on where /dev/ttySL0 --> /dev/pts/N but in wvdial the > modem does not respond and hence we have to restart slmodemd service > and the device /dev/ttySL0 ---> /dev/pts/1 again. Take a look above. > It is strange and it had not happened before :(, I wonder what > change(s) are causing this? > > Regards, > > Antonio > > > > > On Sat, May 2, 2009 at 1:23 AM, أحمد المحمودي > <aelmahmoudy@xxxxxxxxxxxxxxxxxxxxx> wrote: >> On Sat, May 02, 2009 at 02:30:55AM +0000, Antonio Olivares wrote: >>> The connection works again. So I scratch my head here, why is kppp >>> connecting whereas wvdial does not and one has to restart slmodemd?? >>> >>> This is just an observation and it makes me wonder why this is is >>> happening. Why doesn't the modem respond with wvdial and it does with >>> kppp? Very strange observation ? >> ---end quoted text--- >> >> I don't really know, I never used kppp. But allow me to say my guess, >> probably kppp disconnects in a "clean" way. While pressing Ctrl+C in >> wvdial doesn't make it disconnect in a clean way. Maybe some option >> needs to be added to wvdial ? Just guesses. >> >> -- >> أحمد المحمودي (Ahmed El-Mahmoudy) >> Digital design engineer >> GPG KeyID: 0x9DCA0B27 (@ subkeys.pgp.net) >> GPG Fingerprint: 087D 3767 8CAC 65B1 8F6C 156E D325 C3C8 9DCA 0B27 >> > > <div><br></div> >
