SUMMARY-sort of (Trouble with modem dial-in part2)

From: ask6367@pica.army.mil
Date: Wed Aug 10 1994 - 05:43:16 CDT


----------
X-Sun-Data-Type: text
X-Sun-Data-Description: text
X-Sun-Data-Name: text
X-Sun-Content-Lines: 197

Hello again Sun-Managers;

First I'd like to thanks the respondants for their generousity with their time.
Credits at the end.
Apologies for being Late with the SUMMARY,
but I Still haven't found a solution, however, it looks like I'm getting closer.
Read my original post at the end of this email before going on.
Attachement1 is a summary of the responses that I got.

My ttytab looks like this now
console "/usr/etc/getty cons8" sun on local
ttya "/usr/etc/getty std.19200" dialup on remote

My gettytab looks like this.
std.19200|19200-baud:\
        :sp#19200:p8:pd:ab:

I've also tried :ms=-ixon,hupcl,-clocal,crtscts,-tabs:\
                 :tt=dialup

Originally, I was getting garbage when I dialed into my modem.
Now I'm getting the login prompt but characters are missing; such as:

OK
atdt 43980
CONNECT 14400/ARQ/V32/MNP/MNP5

 e o lo i : 636
                      P wor :

What this is suppose to be is:
genom login : ask6367
                      Password:

So as you see it is eating up characters, and shifting subsequent lines as if
not recognizing the carriage return.

---------------------------------------------------------

an interesting phenomenon,
when I copy and paste what appeared at the login prompt, I got:
eoloi:636
                Pwor:

which again stands for "genom login: ask6367" and "Password:"
Soemone tells me that this is the equivalent in 8 bit character set.

---------------------------------------------------------

Most responses suggested locking the DTE rate at 19200 or 38400, however they didn't mention how.
I thought the combination of ttytab and gettytab (as above) does that.

Someone suggested tipping into the modem at 19200bps, then saving the active profile,
exiting the tip, then calling in.
What this is suppose to do is lock the DTE to the 19200bps.
When I did that, I got "xxxx xxx xx xxxx" at the login prompt, and no input was accepted.

---------------------------------------------------------

The profile of the modem I'm originating the call from has the following profile:
USRobotics Courier V.32 Settings...

   B0 C1 E1 F1 Q0 V1 X7
   BAUD=19200 PARITY=N WORDLEN=8
   DIAL=HUNT ON HOOK TIMER

   &A3 &B1 &C0 &D2 &G0 &H1 &I0 &K1 &L0
   &M4 &N0 &P0 &R2 &S0 &T4 &X0 &Y1 %R0

   S00=000 S01=000 S02=043 S03=013 S04=010
   S05=008 S06=002 S07=060 S08=002 S09=006
   S10=014 S11=070 S12=050 S13=032 S14=000
   S15=000 S16=000 S17=000 S18=000 S19=030
   S20=000 S21=010 S22=017 S23=019 S24=150
   S25=000 S26=001 S27=000 S28=008 S29=020
   S30=000 S31=000 S32=001 S33=000 S34=000
   S35=000 S36=000 S37=000 S38=000
---------------------------------------------------------
The active profile of my Hayes Optime 288 modem is:

ACTIVE PROFILE: B0 B16 B76 E1 L1 M1 N1 P Q0 V1 W1 X4 Y0 &A0 &C1 &D2 &G0 &K3 &Q8
&R0 &S0 &T4 &U0 &X2 &Y0 S00:001 S02:043 S03:013 S04:010 S05:008 S06:002 S07:120
S08:002 S09:006 S10:050 S11:095 S12:050 S25:005 S26:001 S36:007 S37:000 S38:020
S46:002 S48:007 S49:064 S50:192 S108:001 S109:4094 S110:002

******************************************************************************************

Original Post:

Hello Sun-managers;

I have been trying to set up a modem on my machine for almost
a week without success; I've tried everything I'm aware of
and I'm almost giving up, this group is my last hope.

Goal:
setup cslip to allow users access from their PCs at home.

Setup:
Hayes OPTIMA 288, V.FC+FAX
Sparc2, running 4.1.3

I've read earlier Summaries, the ZyXEL PS paper, and the sys admin
manual.

My problem is the following:

I'm able to dial out fine.

But when Dialing in:
I'm able to connect, but instead of the login prompt, I get
garbage; something like:

OK
atdt xxx-xxxx
CONNECT 14400/ARQ/V32/MNP/MNP5
...garbage is sent here......

I'm using a vt100 when I call, not a cmdtool.

---------------------------------------------------------------------------------

Here is what I've done so far to avoid wasting your time
with responses I'm already aware of:

connected modem with a good 25 pin modem cable to ttya

applied patch 100513 (to fix tty bugs)

eeprom ttya-ignore-cd=false
eeprom ttya-rts-dtr-off=true
 
halted machine, reset, reboot (so the eeprom changes take eefect)
 
set /etc/ttytab as:
ttya "/usr/etc/getty std.19200" dialup on remote
cua0 "/usr/etc/getty std.19200" unknown off remote

set /etc/gettytab as:
std.19200|19200-baud:\
        :sp#19200:p8: (p8 allows 8 bit processing)

mknod cua0 c 12 128
chmod 666 cua0
ls -alg /dev/cu*
crw-rw-rw- 1 root staff 12, 128 Jun 28 13:26 /dev/cua0

set /etc/remote to dial out ( works good )

------------------------------------------------------------------------------------
Modem setup:

set modem to auto-answer on 2nd rings (which it does)
set modem max DCE speed to 14,400
Set modem to return result code when originating a call but not when answering
        to avoid confusing getty (login)

I see of no way to set the DTE (modem to terminal spped from the "at" command)
but I believe that's already set from the ttytab entry for the ttya port.

I couldn't do ttysoftcar -n /dev/ttya
        (when I tried, nothing happens; it just sits there forever)
        (same response when I try to display current mode with ttysoftcar /dev/ttya)

Is setting the eeprom mode important? does it affect communication in any way.
I'm under the impression that all these parameters are setup during handshaking.
I have it as:
ttya-mode=9600,8,n,1,-
------------------------------------------------------------------------------------

Thanks a million to all who responded, and I hope to hear from you more solutions so I can
get my modem to work.

Paul Hostrup-Jessen <phj06@bk.dk>
Steven Grevemeyer <grevemes@vtc.tacom.army.mil>
Buddy Mecca <bmecca@ralph.wea.com>
Ed Romascan <ed@magma.com>
Jim Hendrickson <jhendric@spock.resd.honeywell.com>
Brett Lynch <brett@iia.org>
Ed Romascan <ed@magma.com>
Kevin Cosgrove <sd.com!solomon!kevinc@PICA.ARMY.MIL>
"Jairo A. Medina" <jairo%pantaleon.cesma.usb.ve@PICA.ARMY.MIL>
Lee Fook Heng <fhlee@csam.my>
Richard Skelton <rich@brake.demon.co.uk>
George H. McBlane" <gmcblane@reality-tech.com
Scott Buzby <buzbys@netcom.com>

aiman
----------
X-Sun-Data-Type: default
X-Sun-Data-Description: default
X-Sun-Data-Name: modem_replies
X-Sun-Content-Lines: 81

I have experienced these problems, too, and in most cases it is the modem
being unable to syncronize either between the Baud rate or the bits. Modern
modems such as the Hayes you are using try to automatically detect these
parameters. Try to force the modems at each end (either software conrolled or
hardware controlled by internal jumpers) to select one particular Baud rate
and let's say 8 bits/one stop bit/no parity just for the sake of the test.
@----------------------------------------------------------------------------
Use PPP V2.1.2. It is a modloadable module for the Sparc. No
kernel work needed.
Compression/Error Correction problems or bits/sec rate.
Set the sun to fixed 38400 bps
Turn off DTE speed adjust. Lock the modem to 38400 (The highest
speed the sun supports)
If you lock the DTE rates (sun<->modem) at 38400 all of the speed
correction is handled by the modem and most of these problems go away.
@----------------------------------------------------------------------------
I turnerd off soft carrier on ttyd0. In /etc/rc I set
    /usr/etc/ttysoftcar -n ttyd0 > /dev/null 2>&1

pd is set in gettytab, ie

        :p8:pd:

it means parity disable. You need this or otherwise
getty tries to operate with 8 bits with parity.

and your vt100 should be set to 8-bit no parity.

@----------------------------------------------------------------------------

What is missing is a fixed baud rate between the modem (DCE) and the
computer (DTE). The default action for the modem is to send the data
to the computer at the same baud rate as it sets up for the incoming
connection. This won't work in your configuration at all (computer at
19.2K and modem max at 14400.

I don't have a manual for your modem, but what you need to do is set
up the modem for "speed-buffering", "fixed DTE-DCE baud rate" or
some related term
@----------------------------------------------------------------------------
        a. at&f&w(cr)
        b. at&c1&d2&s2&k4&w(cr)
        c. ats0=(#rings)s36=7&w(cr)
        d. ate0q1&w(cr
@----------------------------------------------------------------------------
you don't appear to have set hw flow control.

My gettytab entry is;

h|std.38400|38400-baud:\
        :ms=-ixon,crtscts,-tabs:\
        :tt=dialup:\
        :sp#38400:ht:p8:
@----------------------------------------------------------------------------
                Change 19200 to 14400 in everywhere.
@----------------------------------------------------------------------------
I fixed it by setting E0 and V0 .
My /etc/gettytab is also different :-

zoom.38400|38400-baud:\
        :ms=hupcl,-clocal:lc:to#30:sp#38400:
@----------------------------------------------------------------------------
The modem uses the DTE speed the profile was written with as it's
default DTE speed. So when a call comes into the modem and it
connects to the Sun, which is expecting speed of 19200, it uses what
ever speed you used to write the profile which was probably not 19200.

To solve my problem I used tip (not cu) to save my profile. When I
did stty on my serial port when connected with cu I got a input baudrate
of 9600 and a output baudrate of 38400, using tip the baudrate was
38400.

So put an entry in /etc/remote for your serial port at your desired
baud rate (19200 or 38400), connect to you modem and re-write the
current profile.

I've been using 38400 and I've only seen zs0 silo overflows during
uucp transfers while the system was very busy (runing sundiag).
@----------------------------------------------------------------------------



This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:09:07 CDT