I've got Suse 6.4 (2.2.14 kernel) installed on my Beige G3. I have SupraFaxModem 33.6 hooked up to the modem port through a serial switch box (it's set to the modem, I just wanted to include it in the description for the sake of being thorough). I went into Yast and configured the modem for COM1 (yeah, wouldn't it be nice if the choices were actually - modem/printer port). I then went to the auto modem detect. I saw the lights flash on the modem, but the auto detect failed. I created a file 'afile' that contained the following lines: ATH0 ATZ ATDT 5551212 I then executed the following line: cat afile > /dev/modem and cat afile > /dev/ttyS0 both produced the same results, the lights on the modem flashed, but I never heard it try to dial. ----------------------------- Robert G. Palmer, Jr. Product Engineer robert.palmer@ipix.com iPIX - The Leader in Dynamic Imaging Phone: (865)-482-3000 http://www.ipix.com
On Fri, Nov 03, Robert G Palmer Jr wrote:
I went into Yast and configured the modem for COM1 (yeah, wouldn't it be nice if the choices were actually - modem/printer port).
yast will display the correct values in 7.0-ppc.
I then went to the auto modem detect. I saw the lights flash on the modem, but the auto detect failed.
Autodetect is in fact a auto-guess. Does that Modem work in MacOS? What modem skript do you use? We can extract that string with a text editor, like BBEdit Lite.
I created a file 'afile' that contained the following lines:
ATH0 ATZ ATDT 5551212
I then executed the following line:
cat afile > /dev/modem and cat afile > /dev/ttyS0
both produced the same results, the lights on the modem flashed, but I never heard it try to dial.
You proably need another init string. Gruss Olaf -- $ man clone BUGS Main feature not yet implemented...
Olaf Hering wrote:
On Fri, Nov 03, Robert G Palmer Jr wrote:
I created a file 'afile' that contained the following lines:
ATH0 ATZ ATDT 5551212
I then executed the following line:
cat afile > /dev/modem and cat afile > /dev/ttyS0
both produced the same results, the lights on the modem flashed, but I never heard it try to dial.
You proably need another init string.
I think so too... provided that you are using the correct cable. For testing purposes, you may try AT&F1E0S0=0X3 (E0 = echo off, S0=0 = don't answer calls, X3 = don't detect dial tone): it works with a lot of modems. Better yet, find a MacOS script for the modem (with OS9, look inside System folder - Extensions - Modem scripts), open it with a text editor and look for the init string (usually below @LABEL 3). good luck nicola
on 11/3/00 11:07 AM, Olaf Hering at olh@suse.de wrote:
I then went to the auto modem detect. I saw the lights flash on the modem, but the auto detect failed.
Autodetect is in fact a auto-guess. Does that Modem work in MacOS? What modem skript do you use? We can extract that string with a text editor, like BBEdit Lite.
Yes, it works fine in MacOS. I use the default init string in RemoteAccess for the SupraFax288 modem.
I created a file 'afile' that contained the following lines:
ATH0 ATZ ATDT 5551212
I then executed the following line:
cat afile > /dev/modem and cat afile > /dev/ttyS0
both produced the same results, the lights on the modem flashed, but I never heard it try to dial.
You proably need another init string.
For testing, I can put the init string in 'afile', but once I get it working, how do I modify the init string that Yast uses for it's auto-guess. Or do I even need to? If not, where do I specify the new, correct, init string. ----------------------------- Robert G. Palmer, Jr. robert.palmer@ipix.com Internet Pictures Corp. Product Engineer Phone: (865)-482-3000 http://www.ipix.com -------- These are my opinions - I don't know what my employer thinks.
On Fri, Nov 03, Robert G Palmer Jr wrote:
on 11/3/00 11:07 AM, Olaf Hering at olh@suse.de wrote:
I then went to the auto modem detect. I saw the lights flash on the modem, but the auto detect failed.
Autodetect is in fact a auto-guess. Does that Modem work in MacOS? What modem skript do you use? We can extract that string with a text editor, like BBEdit Lite.
Yes, it works fine in MacOS. I use the default init string in RemoteAccess for the SupraFax288 modem.
I created a file 'afile' that contained the following lines:
ATH0 ATZ ATDT 5551212
I then executed the following line:
cat afile > /dev/modem and cat afile > /dev/ttyS0
both produced the same results, the lights on the modem flashed, but I never heard it try to dial.
You proably need another init string.
For testing, I can put the init string in 'afile', but once I get it working, how do I modify the init string that Yast uses for it's auto-guess. Or do I even need to? If not, where do I specify the new, correct, init string.
look at /etc/wvdial.conf, the first string should reset the modem, the second one should configure it. Gruss Olaf -- $ man clone BUGS Main feature not yet implemented...
on 11/3/00 2:59 PM, Olaf Hering at olh@suse.de wrote:
I created a file 'afile' that contained the following lines:
ATH0 ATZ ATDT 5551212
I then executed the following line:
cat afile > /dev/modem and cat afile > /dev/ttyS0
both produced the same results, the lights on the modem flashed, but I never heard it try to dial.
You proably need another init string.
For testing, I can put the init string in 'afile', but once I get it working, how do I modify the init string that Yast uses for it's auto-guess. Or do I even need to? If not, where do I specify the new, correct, init string.
look at /etc/wvdial.conf, the first string should reset the modem, the second one should configure it.
Gruss Olaf
I modified the init string and that still didn't work. I played around some more and I'm pretty sure that the problem is that the wrong end-of-line character is being sent. The modem expects a <CR> (0x0D or ctrl-M - all the same thing, just different names) as the end-of-line. I tested this by doing the following: First I executed: cat > /dev/modem I could type in things and when I hit return, nothing would happen. However, if I typed <ENTER> the modem would respond. I could reset it and make it dial and hang up. I went and changed the key map to mac-us instead of mac-102 and tried it again. I could then use the return key to get the modem to respond. I could reset it, make it dial and put it back on hook. Next I put the same commands I had been manually entering, into a file (afile). The commands were: AT&F1(don't remember the rest) ATH0 ATDT 5551212 The key was that I used <CTRL>-M to end each line instead of hitting either return or enter. I then sent this file to the modem using: cat afile > /dev/modem This worked perfectly. So now - how do I tell wvdial to use the correct character when sending an end-of-line, or is there something else wrong? ----------------------------- Robert G. Palmer, Jr. Product Engineer robert.palmer@ipix.com iPIX - The Leader in Dynamic Imaging Phone: (865)-482-3000 http://www.ipix.com
On Tue, Nov 14, Robert G Palmer Jr wrote:
I modified the init string and that still didn't work. I played around some more and I'm pretty sure that the problem is that the wrong end-of-line character is being sent. The modem expects a <CR> (0x0D or ctrl-M - all the same thing, just different names) as the end-of-line. I tested this by doing the following:
You mean the modem wants always a "0x0d" as CR value and the "0x0a" or "0x0d 0x0a" doesnt work? Thats a real bug in the modem.
So now - how do I tell wvdial to use the correct character when sending an end-of-line, or is there something else wrong?
We need a hacked wvdial for that modem bug. The guy who maintain the wvdial package is back from vacation tomorrow. I will ask him to add a workaround. You could try a hexeditor like khexedit to add "0x0d" to the wvdial.conf. But it is possible that wvdial filter that byte. Gruss Olaf -- $ man clone BUGS Main feature not yet implemented...
Olaf is probably right on the money with his suggestion. As a knee-jerk troubleshooting reaction, though, I'd like to recommend that you remove the switchbox from this configuration until you've got the modem working while it's directly connected to the computer. When you're troubleshooting something like this, it helps to remove all the variables possible. Seth Robert G Palmer Jr wrote:
I've got Suse 6.4 (2.2.14 kernel) installed on my Beige G3. I have SupraFaxModem 33.6 hooked up to the modem port through a serial switch box (it's set to the modem, I just wanted to include it in the description for the sake of being thorough).
I went into Yast and configured the modem for COM1 (yeah, wouldn't it be nice if the choices were actually - modem/printer port).
I then went to the auto modem detect. I saw the lights flash on the modem, but the auto detect failed.
I created a file 'afile' that contained the following lines:
ATH0 ATZ ATDT 5551212
I then executed the following line:
cat afile > /dev/modem and cat afile > /dev/ttyS0
both produced the same results, the lights on the modem flashed, but I never heard it try to dial.
----------------------------- Robert G. Palmer, Jr. Product Engineer robert.palmer@ipix.com iPIX - The Leader in Dynamic Imaging Phone: (865)-482-3000 http://www.ipix.com
participants (4)
-
nicola moretti -
Olaf Hering -
Robert G Palmer Jr -
seth johnson