ppp chat script failed
Trying to get a dial-up going on Zenwalk 2.6 (slack based). Ran pppsetup, accepted the default init string. Run ppp-go, exits with "Connection script failed", no other info echoed or in /var/log/syslog. Added a verbose option (chat -e -V) to ppp-go, and something echoed the string "^@^@", whatever that means. Man pages don't seem helpful. Is there some magic incantation I'm missing? What's the next step?
|
From http://www.slackware.com/config/ppp.php :
Quote:
Code:
#!/bin/bash Also, from the same webpage (link above), there are several scripts in /etc/ppp which might be useful to look at. I believe the ^@^@ represent two null ascii characters, i.e. characters whose hex value is zero. But I have no idea what they mean. I hope this can get you started. (I have no idea how much you know about scripts.) Post back with additional questions or info. |
Quote:
Yes, ppp-go is a sh/bash script. I added a -v option that calls chat with more verbosity. Now it's calling "chat -evsV". After a few "abort on ..." lines, the output looks like this: send (AT&FH0^M) expect (OK) ^@^@alarm Failed So I'm guessing the ^@^@ isn't good :( I tried experimenting with the modem speed in /etc/ppp/pppscript, and this output occurred through the whole range, from 9600 to the highest speed mentioned in pppsetup. I found a web page that says to try "cat /dev/ttySN" to test your modem device, where N is the device number. No output means it's there, I/O error means it's not. I set the modem to ttyS0 in pppscript, and "cat /dev/ttyS0" returns no output with no error, whereas "cat /dev/ttyS[1-4]" returns an error. So I think I have the right device file. The modem is a Rockwell RCVDL56ACF/SP R6761-21 COM ID RSS0250, ISAPNP\RSS 0250 That's what I know about the modem. This is a fresh install of the OS as of a day or two ago. The installer didn't say anything about a modem driver, so I don't know whether it found the driver itself or just did nothing. Is there a way to check that? Is the driver's presence implied by "cat /dev/ttyS0"? I'll see if dmesg says anything. btw, is this the best forum to post this question on? Is there another forum that would be good to cross-post it on? The Slack forum? Hardware? Software? Don't want to bug too many people :) Thanx for the help. |
Quote:
Quote:
One more thing. You say your modem is on /dev/ttyS0. On older computers, this would usually be a built in serial line on the motherboard. If your modem is external, all is well. If your modem is internal (a quick google on your model didn't help me determine), make sure it isn't conflicting with a built in serial line. Quote:
Code:
set -x Look into "tagging" your post. Again, post back as needed. Good luck. |
If all went well with your minicom test, you can modify your ppp-go script so it shows you every line as it executes. Use your favorite text editor to add
Code:
set -x Oops!!! I should have set put "set -x" on the second line ... after the #!/bin/[ba]sh line! |
Null Bytes
Sorry for this succession of posts, but I just had an idea what those two null bytes (^@^@) might be. They could be what the script is seeing coming back from the modem in response to AT&FH0 instead of the expected OK. This would suggest a problem communicating with the modem (a conflict between devices?). This would probably best be investigated with minicom, as I suggested above.
|
What about /etc/ppp/options what does it contains?
Add "debug" to see if it is pppd the problem (errors go to /var/log/daemon or /var/log/messages). Also, adding "crtscts" and "modem" can help. |
Quote:
Quote:
Anyway, the minicom man page says the modem is usually on ttyS1, and the setserial man page says ttyS0 should have IRQ 4 and ttyS1 should have IRQ 3. But the Zenwalk installer found a modem on ttyS0, not ttyS1, and setserial -a says "UART: 16550A" for ttyS0, but "UART: unknown" for ttyS1, plus catting ttyS1 returns a device error. So it almost sounds like the modem is on ttyS1/COM2, but the installer somehow didn't figure that out so it didn't setup the modem correctly(?). Isn't there some sort of command-line utility to sort all this out? ppp, chat, and minicom all seem to assume the modem is setup already. |
Quote:
Quote:
|
Quote:
Quote:
Quote:
Code:
Jun 18 22:13:26 Vectra kernel: ttyS00 at 0x03f8 (irq = 4) is a 16550A Your log entries should give you an idea of what your choices are on when you look for your modem. As far a command line tool, all I know is using cat and echo as follows: If you are in a graphical environment you can open up two terminal windows and try to talk to the modem manually. (If not in a GUI, you can use two virtual terminals. But a GUI is better, because if things run away -- and they might -- you can kill things by simply closing the windows.) In both windows use su to become root. In one window, listen like you did before using cat, e.g. cat /dev/ttyS0. In the other window you can send commands, e.g. echo "ATZ" > /dev/ttyS0. You already know about setserial. In this excercise, the stty command can also be relevant. It controls a bunch of higher level functions of the port, including echoing. Software like pppd and minicom handle these settings for you. When you brute force things like I describe above, you are on your own. When I first tried this back when, I had both the modem and port echoing to each other, and as soon as I sent the first command, it went into a perpetual, viscous cycle! Other times I totally hosed things. Never knew how. But worse case scenario, it was nothing a reboot wouldn't fix. I hope this helps you get a little further. |
Quote:
Quote:
Quote:
Code:
zenwalk kernel: serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A Quote:
|
Quote:
(later) With regard to #2 above, I just searched some Linux hardware compatibility lists. If I found the right thing and read the list right, it looked like both PnP and jumpers were checked. So perhaps the address is PnP, or perhaps can be jumpered either PnP or a manual address?:scratch: I hope this is not a "winmodem" or "software modem." See what you can figure out from the jumpers, or lack thereof. Also, feel free to google. |
Progress!
Okay, we're dialing.
Quote:
I learned from the PCI and ISA wikis that the big black slot is an ISA port. The card has three sets of jumpers, including one for the IO address and one for the IRQ. The third set has three jumpers, but the key lists only two options: PNP and COM. The card was set to PNP and the address and IRQ for COM4/ttys3. I changed them to COM and the settings for COM2/ttyS1. ttyS1 is now showing a 16550A UART, and pppd is dialing out. This distribution doesn't seem to have isapnp, so maybe the system wasn't able to configure the ISA card. Quote:
|
Anyway, this is a BIG step forward. :)
I ran pppsetup, which created /etc/ppp/[options && pppscript] with ttyS1 and all the info for my ISP and userid. Now pppd does this: Code:
AT&FH0 Also, this disrtibution doesn't seem to have wvdial either, not even in /sbin or /usr/sbin. |
I am glad you can at least now talk to the modem!!! You probably gathered from my last post that I was beginning to fear the worst.
Quote:
Seriously, you might check /var/log/messages to see if there is anything there. Also, on post #3 you reported ppp-go giving messages like: Code:
send (AT&FH0^M) Quote:
BTW, an ethernet card should not show up as a serial port. I am guessing you have a serial port on your motherboard. |
All times are GMT -5. The time now is 04:40 PM. |