"pppd[0]: --> Don't know what to do!"

Ok, lets take the shotgun approach. What is the result of the following command from konsole?

ls -l /dev/ttyLT0

Originally posted by harryc@Apr 26 2005, 01:03 PM
Ok, lets take the shotgun approach. What is the result of the following command from konsole?

ls -l /dev/ttyLT0

[snapback]77446[/snapback]

crw-rw-rw- 1 root dialout 62, 64 2005-04-26 14:06 /dev/ttyLT0

And the /dev/ttyLT0 part is highlited

Your permissions look fine. Did this modem ever work? Can you run kinternet as root to see if that makes a difference?. Have you tried another OS, like knoppix to test it? Can you try a hardware modem? I am reaching here. Maybe somebody else has an idea for you. Good luck.

i have been following this thread. it seems to me that the modprobe would be of little help since the modem is connecting. it also seems to me its doing the handshake but then disconnecting. the error code is the key here, so i did some searches. http://plug.org.in/pipermail/plug-mail/200...ber/013026.html

http://www.google.com/search?q=pppd[0]:%20Terminating%20on%20signal%2015.&ie=UTF-8&oe=UTF-8

based on what the searches reveal, it seems to be a password issue.

the ubuntu forums also shed a bit of light on this http://ubuntuforums.org/archive/index.php/t-3486.html

reading the ppp man page says

lcp-echo-failure n
* * * * * * * If this option is given, pppd will presume the peer to* be* dead
* * * * * * * if* n* LCP* echo-requests are sent without receiving a valid LCP
* * * * * * * echo-reply.* If this happens, pppd will* terminate* the* connec-
* * * * * * * tion.* Use of this option requires a non-zero value for the lcp-
* * * * * * * echo-interval parameter.* This option can be used to enable pppd
* * * * * * * to* terminate* after* the* physical* connection* has been broken
* * * * * * * (e.g., the modem has hung up) in situations* where* no* hardware
* * * * * * * modem control lines are available.

http://unixhelp.ed.ac.uk/CGI/man-cgi?pppd+8

the signal 15 is an echo request error. which is why i posted this.


both of your logs end with signal 15. this is where we need to focus our attention. http://www.google.com/search?hl=en&lr=&q=E...ts.&btnG=Search

Just thought of one more thing to try. Disable susefirewall in YaST to see if that makes a difference.

@linux_learner: Thats probably it - but i can't really tell much from the results - the manuals explain it poorly, and most of the threads on it never get finished.

Oh, well - i might just have to get broadband. Hmmm.. if i had broadband i could download 9.3 Pro - the modem might be better supported in 9.3 Pro.

Thanks anyway!

Didn't want to see you close the thread without trying to make up for the bum steer on the driver name. I wasn't paying attention to much of anything that day. :blink: Hope the links help.

Your drivers are loaded, and your modem is dialing, but it disconnects about the time that it wants to link modem0 <--> /dev/ttyLT0. My notes indicate that the "Waiting for prompt" notice was associated with an authentication problem when I first started to test my configuration. On the last line of the /etc/ppp/pap-secrets file enter your login name, a tab, an asterisk, a tab, and finally your password. Most dialup servers use what is called PAP/CHAP authentication, and your isp may require it. Also, double check the three "alias" lines to make sure that they were entered properly. I hope you get it working.