topic Re: Modem problems in Operating System - HP-UX

Modem problems

Burt Buchen — Tue, 16 Mar 2004 16:31:47 GMT

Hello,

I am attempting to get a dialin modem working.
I have tried a couple different kind of modems and nothing seems to work.
The problem is I get no getty. I have a getty running

/etc/inittab entry is as follows:

a0:3:respawn:/usr/lbin/uucp/uugetty -r -t 60 -h ttyd0p1 9600

I also can connect via kermit -l /dev/ttyd0p1 -b 9600
When I connect via kermit I can see information coming through the modem, so I know the connection is good and the modem can send information back and forth.
I just cannot get a login no matter what I do.
I have used a us robitics modem 56k fax,
also a multitech MT1432BA with the same results.

I have set the us robotics setting every which way currently they are set at 1,3,5,8 down

The current settings are:
U.S. Robotics 56K FAX EXT Settings...

B0 E1 F1 L2 M1 Q0 V1 X4 Y0
BAUD=9600 PARITY=N WORDLEN=8
DIAL=PULSE ON HOOK CID=0

&A1 &B0 &C1 &D2 &H0 &I0 &K1
&M4 &N0 &P2 &R1 &S0 &T5 &U0 &Y1

S00=003 S01=000 S02=043 S03=013 S04=010 S05=008 S06=004
S07=055 S08=003 S09=006 S10=014 S11=070 S12=050 S13=000
S15=000 S16=000 S18=000 S19=000 S21=010 S22=017 S23=019
S25=005 S27=000 S28=008 S29=020 S30=000 S31=128 S32=002
S33=000 S34=000 S35=000 S36=014 S38=000 S39=012 S40=001
S41=004 S42=000

Any ideas?

Re: Modem problems

Steven E. Protter — Tue, 16 Mar 2004 16:42:08 GMT

I'm wondering what if anything comes up on ioscan.

ioscan -fnk

or

ioscan

insf -e

This may do or prove nothing. It might however get your modem recognized and it probably won't hurt anything.

Then try configuring the modem for dialin with sam.

It has a higher chance than my pea brain molecules of getting the settings right.

Re: Modem problems

Burt Buchen — Tue, 16 Mar 2004 17:01:40 GMT

ioscan shows it is claimed.

tty 0 56 mux2 CLAIMED INTERFACE MUX
/dev/cua0p1 /dev/diag/tty0p3 /dev/tty0p13
/dev/cul0p1 /dev/diag/tty0p4 /dev/tty0p14
/dev/diag/mux0 /dev/diag/tty0p5 /dev/tty0p15
/dev/diag/tty0p0 /dev/diag/tty0p6 /dev/tty0p2
/dev/diag/tty0p1 /dev/diag/tty0p7 /dev/tty0p3
/dev/diag/tty0p10 /dev/diag/tty0p8 /dev/tty0p4
/dev/diag/tty0p11 /dev/diag/tty0p9 /dev/tty0p5
/dev/diag/tty0p12 /dev/mux0 /dev/tty0p6
/dev/diag/tty0p13 /dev/tty0p0 /dev/tty0p7
/dev/diag/tty0p14 /dev/tty0p10 /dev/tty0p8
/dev/diag/tty0p15 /dev/tty0p11 /dev/tty0p9
/dev/diag/tty0p2 /dev/tty0p12 /dev/ttyd0p1

Re: Modem problems

A. Clay Stephenson — Tue, 16 Mar 2004 17:22:36 GMT

Since kermit works (I assume using the same device node), your cabling and modem settings should be close. I think you will have better luck using getty rather than uugetty. (e.g. you might have a lock file killing you)
0) chown root:tty /dev/ttyd0p1
1) Edit /etc/inittab and change "respawn" to "off" in the uugetty line. Save the file.
2) init q
3) ps -ef | grep getty and kill any stray processes.
4) cd /var/spool/locks and rm any files found there.
5) Again, edit /etc/inittab and change your uugetty to /usr/sbin/getty -h ttyd0p1 and change "off" to "respawn". Save the file.
6) Power cycle the modem -- just to clear any possible bits.
7) Note that the "9600" gettydefs entry loops around to the "300" entry. You may want to use a custom gettydefs entry that remains at 9600 or uses a fixed 19200. If so edit /etc/gettydefs and use the matching label in place of the "9600" label in your /etc/inittab entry.
8) init q

If the Force is with you, you now have a login.

Re: Modem problems

Burt Buchen — Tue, 16 Mar 2004 18:25:35 GMT

I think I found the problem, although I don't know why?

I found that if I go into kermit and run the following:
set parity even
set stop-bits 1

Then exit kermit the port now will display a login.

This worked for both my test system. But the system I really need to get working will not keep this setting. Everytime I set this and exit the configuration has changed back to 8N1. Any ideas how to keep 7E1?

Re: Modem problems

A. Clay Stephenson — Tue, 16 Mar 2004 18:47:46 GMT

This is controlled by the gettydefs entry you are using. You need one with a PARENB and CS7.

Re: Modem problems

Burt Buchen — Tue, 16 Mar 2004 18:54:04 GMT

Hmmm, got that

9600 # B9600 HUPCL IGNPAR PARENB ICRNL IXON OPOST ONLCR CS7 CREAD
ISIG ICANON ECHO ECHOK PARENB ISTRIP TAB3
# B9600 SANE CS7 PARENB ISTRIP TAB3 HUPCL
#login: #1200

Thanks,

Any other ideas

Re: Modem problems

A. Clay Stephenson — Tue, 16 Mar 2004 18:59:08 GMT

Yes, you probably aren't even using the gettydef you think you are. Note that your current 9600 loops to a 1200 whichh probably loops to a 2400 ... until finally back to 9600. I would change to a fixed entry (one which loops back to itself) until you get this debugged. I also assume that your terminal is configured 71E.

Re: Modem problems

Sanjiv Sharma_1 — Tue, 16 Mar 2004 20:10:58 GMT

Hi Burt,

Please check this earlier posts:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=4537
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=27000

hth.

Re: Modem problems

Ryan McKlveen — Wed, 17 Mar 2004 11:44:46 GMT

assuming that the modem is set to auto answer? What happens when you connect a regular phone (or tester) to the line - can you call in and see if it rings - was the line set up for dial out only?