usb isdn modem need help
have a US Robotics ISDN TA modem connected to the USB port. Yast2 recognizes it, put in all of the ISP info, but when I dial with kinternet, I get the following: Selection of new interface/provider "ppp3"/"sonic.net" succeeded. Starting connection. (2002-08-03 13:59:45 PDT) pppd: Plugin passwordfd.so loaded. pppd: Perms of /dev/ttyACM0 are ok, no 'mesg n' neccesary. pppd: --> WvDial: Internet dialer version 1.42 pppd: --> Initializing modem. pppd: --> Sending: ATM1 pppd: OK pppd: --> Modem initialized. pppd: --> Sending: ATDT17075221001 pppd: --> Waiting for carrier. pppd: NO CARRIER pppd: --> No Carrier! Trying again. pppd: --> Sending: ATDT17075221001 pppd: --> Waiting for carrier. pppd: NO CARRIER pppd: --> No Carrier! Trying again. pppd: --> Sending: ATDT17075221001 pppd: --> Waiting for carrier. pppd: NO CARRIER pppd: --> No Carrier! Trying again. pppd: --> Sending: ATDT17075221001 pppd: --> Waiting for carrier. pppd: NO CARRIER pppd: --> No Carrier! Trying again. pppd: --> Sending: ATDT17075221001 pppd: --> Waiting for carrier. pppd: NO CARRIER pppd: --> No Carrier! Trying again. pppd: --> Sending: ATDT17075221001 pppd: --> Waiting for carrier. Stopping connection. (2002-08-03 14:05:26 PDT) pppd: Terminating on signal 15. pppd: Connect script failed We are disconnected. (2002-08-03 14:05:27 PDT) I know there is a carrier as I can dial in Win2k and get it to work. If I use KPPP, I get a Selection of interface/provider "ppp3"/"sonic.net" succeeded. Starting connection. (2002-08-03 13:09:24 PDT) pppd: Plugin passwordfd.so loaded. pppd: Perms of /dev/ttyACM0 are ok, no 'mesg n' neccesary. pppd: --> WvDial: Internet dialer version 1.42 pppd: --> Initializing modem. pppd: --> Sending: ATM1 pppd: --> Sending: ATQ0 pppd: OK pppd: --> Re-Sending: ATM1 pppd: OK pppd: --> stdin not read/write and $MODEM not set pppd: Connect script failed pppd died: Connect script failed (exit code 8) What is the line "pppd: --> stdin not read/write and $MODEM not set" mean? Art
Art Fore wrote:
have a US Robotics ISDN TA modem connected to the USB port. Yast2 recognizes it, put in all of the ISP info, but when I dial with kinternet, I get the following:
Three suggestions: 1. Since you have a Windows partition, look for the script that windows uses to connect. There may be some extra commands you need. For example, it is usual to send something like ATZ before ATM1. 2. Have a look at your modem manual (if you have one) or the manufacturer's site for their AT command set. It often gives clues to what you need. 3. Test the commands in minicom, which should be available on one of your disks. JDL -- Non enim propter gloriam, diuicias aut honores pugnamus set propter libertatem solummodo quam Nemo bonus nisi simul cum vita amittit.
Have you got your log running tail -f /var/log/messages ? What happens when you do isdnctrl dial ippp0 ? Brian Marr On Sunday 04 August 2002 17:52, John Lamb wrote:
Art Fore wrote:
have a US Robotics ISDN TA modem connected to the USB port. Yast2 recognizes it, put in all of the ISP info, but when I dial with kinternet, I get the following:
Three suggestions:
1. Since you have a Windows partition, look for the script that windows uses to connect. There may be some extra commands you need. For example, it is usual to send something like ATZ before ATM1.
2. Have a look at your modem manual (if you have one) or the manufacturer's site for their AT command set. It often gives clues to what you need.
3. Test the commands in minicom, which should be available on one of your disks.
JDL
Got the problem solved in KiI unchecked the sound and wait for dial tone in the ppp1 dialog in Yast 2 and that got it to working. (Still does not make sense) It was connecting at only 64kb, but changed the AT&PPP=1 that was suggested in the article on the suse website to AT&PPP=4. Now it connects at 128k. Thanks for the help Art On Sun, 2002-08-04 at 03:30, Brian Marr wrote:
Have you got your log running tail -f /var/log/messages ? What happens when you do isdnctrl dial ippp0 ? Brian Marr
On Sunday 04 August 2002 17:52, John Lamb wrote:
Art Fore wrote:
have a US Robotics ISDN TA modem connected to the USB port. Yast2 recognizes it, put in all of the ISP info, but when I dial with kinternet, I get the following:
Three suggestions:
1. Since you have a Windows partition, look for the script that windows uses to connect. There may be some extra commands you need. For example, it is usual to send something like ATZ before ATM1.
2. Have a look at your modem manual (if you have one) or the manufacturer's site for their AT command set. It often gives clues to what you need.
3. Test the commands in minicom, which should be available on one of your disks.
JDL
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the archives at http://lists.suse.com
Isdnctrl does not work since this is setup like a regular modem and not an internal ISDN modem. In Windows, using the same modem and ISP I get a connect is just a few seconds and it does not loose DNS. I copied the initialization commands from Windows. They are as follows. Init1=AT&F1 Init2=ATE0Q0V1&A3&C1&D2S0=0 Init3=ATS7=60S19=0&H1&R2&I0X4 Init4=AT*PPP=0S67=0 Put these in wvdial.conf and in /etc/sysconfig/ifcfg-ppp1. When I dial, kinternet does not output anyone of the init values except Init1 and ATQ0 which I do not even have. I get the old stdin not read/write and $MODEM not set. If I have Init1=ATZ Init2=AT&F*PPP=4 I then get ATQ0 AND ATM0 added and it does work to a certain extent. Takes about 5 minutes to connect and it looses the dns all of the time even putting the nameserver in resolv.conf and setting auto DNS to no in the providers file. Try to use KPPP, it is still looking for /dev/usb/ttyACM0 instead of /dev/ttyACM0 which is in the wvdial.conf. Wished I know how to change this. Tried link /dev/usb/ttyACM0 > /dev/ttyACM0. Comes up command not found and I could not find it with Konqueror although the manual file is there when you do man link. Anyone have any other suggestions? Could this maybe be handled with a script and if so, does someone have a sample script they could send me? Also, have no /dev/modem, have a /dev/modems which contains nothing. Here is the log from Windows. 08-04-2002 20:00:26.425 - Initializing modem. 08-04-2002 20:00:26.435 - Send: AT&F1<cr> 08-04-2002 20:00:26.615 - Recv: <cr><lf>OK<cr><lf> 08-04-2002 20:00:26.615 - Interpreted response: OK 08-04-2002 20:00:26.626 - Send: ATE0Q0V1&A3&C1&D2S0=0<cr> 08-04-2002 20:00:26.626 - Recv: ATE0Q0V1&A3&C1&D2S0=0<cr> 08-04-2002 20:00:26.626 - Command Echo 08-04-2002 20:00:26.796 - Recv: <cr><lf>OK<cr><lf> 08-04-2002 20:00:26.796 - Interpreted response: OK 08-04-2002 20:00:26.806 - Send: ATS7=60S19=0&H1&R2&I0X4<cr> 08-04-2002 20:00:26.976 - Recv: <cr><lf>OK<cr><lf> 08-04-2002 20:00:26.976 - Interpreted response: OK 08-04-2002 20:00:26.976 - Setting Digital Link Protocol 08-04-2002 20:00:26.986 - Send: AT*PPP=0S67=0<cr> 08-04-2002 20:00:27.146 - Recv: <cr><lf>OK<cr><lf> 08-04-2002 20:00:27.146 - Interpreted response: OK 08-04-2002 20:00:27.146 - Dialing. 08-04-2002 20:00:27.156 - Send: ATDT###########<cr> 08-04-2002 20:00:28.198 - Recv: <cr><lf>CONNECT 128000<cr><lf> 08-04-2002 20:00:28.198 - Interpreted response: Connect 08-04-2002 20:00:28.198 - Receive Connect but CD was low, Waiting for signal to go high 08-04-2002 20:00:28.218 - After waiting 20ms CD is still low. 08-04-2002 20:00:28.238 - CD has been raised 08-04-2002 20:00:28.238 - Connection established at 128000bps. On Sun, 2002-08-04 at 03:30, Brian Marr wrote:
Have you got your log running tail -f /var/log/messages ? What happens when you do isdnctrl dial ippp0 ? Brian Marr
On Sunday 04 August 2002 17:52, John Lamb wrote:
Art Fore wrote:
have a US Robotics ISDN TA modem connected to the USB port. Yast2 recognizes it, put in all of the ISP info, but when I dial with kinternet, I get the following:
Three suggestions:
1. Since you have a Windows partition, look for the script that windows uses to connect. There may be some extra commands you need. For example, it is usual to send something like ATZ before ATM1.
2. Have a look at your modem manual (if you have one) or the manufacturer's site for their AT command set. It often gives clues to what you need.
3. Test the commands in minicom, which should be available on one of your disks.
JDL
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the archives at http://lists.suse.com
participants (3)
-
Art Fore -
Brian Marr -
John Lamb