time@oxtrap.aa.ox.com (Tim Endres) (11/30/89)
I have recently placed two Telebit modems off my A/UX machine for a sophisticated retrieval system. I have noticed, though, that even though I set gettydefs to handle the 19200 rate, and have the inittab respawn pointing to the 19200 gettydefs entry, I can not connect at 19200. I always have to autobaud to 9600, where it appears the port is "stuck" in terms of baud rate. Someone told me that there exists a default baud rate for each tty in the kernel, and it is tricky to get the port to handle different bauds. Something like the port had to be opened *originally* at the desired rate, and held open at that rate. This did not sound right to me. I also remember some discussion here a while back about exactly this problem. Could some kind soul enlighten me. I have a T2500 doing 9600 baud :(
pst@anise.acc.com (Paul Traina) (11/30/89)
I have blazer's on my A/UX machine set at 19.2k without any problem. Here is my /etc/gettydefs entry for a 19.2k blazer: 19200# EXTA # EXTA HUPCL SANE2 TAB3 # MODEM ~DTR ~FLOW #\r\nlogin: #19200 Here are the modem parameters after an ATZ: E1 F1 M0 Q0 T V1 X3 Version BA4.00 S00=000 S01=000 S02=043 S03=013 S04=010 S05=008 S06=002 S07=060 S08=002 S09=006 S10=007 S11=070 S12=050 S45=255 S47=032 S48=000 S49=000 S50=000 S51=005 S52=002 S53=004 S54=003 S55=000 S56=017 S57=019 S58=000 S59=000 S60=000 S61=030 S62=003 S63=001 S64=000 S65=000 S66=001 S67=000 S68=255 S90=000 S91=000 S92=000 S95=000 S100=000 S101=000 S102=000 S104=000 S110=255 S111=255 S112=001 S121=000 I made a special cable to detect hangup transitions -- this cable uses DSR (which I have programed to drop for 2 seconds after a hangup) instead of DCD as the carrier detect function. Then, I have a special getty program which does some additional programming. It will send down: ATE0 AT&EE0X1V0S2=128S58=0 Contact me if you want my blazer intelligent getty. -- Ooh, I just know that something good is going to happen And I don't know when But just saying it could even make it happen, -- Kate Bush
ksand@appleoz.oz.au (Kent Sandvik) (12/08/89)
time@oxtrap.aa.ox.com (Tim Endres) writes in article <1989Nov29.163459.23051@oxtrap.aa.ox.com>:
Someone told me that there exists a default baud rate for each
tty in the kernel, and it is tricky to get the port to handle
different bauds. Something like the port had to be opened *originally*
at the desired rate, and held open at that rate. This did not sound right
to me. I also remember some discussion here a while back about exactly
this problem.
This is a typical UNIX case for outgoing modem lines with *no* getty that
programs the port settings (as with ingoing lines and getty spawned).
That's the case where you need to override the default setting with
a program that opens the port, does ioctl on the port settings and keeps
the port open until doomsday.
/Kent
--
Kent Sandvik -- ksand@appleoz.oz.AU | Apple Australia DTS Ph: +61 2 452 82 93
{uunet,mcvax}!munnari!appleoz.oz!ksand | AppleLink: AUSTAUX, Discl: All comments mine
-- CyberSpace, the Final Frontier --