max@maxsun.lgc.com (Max Heffler) (07/15/90)
I finally got around to installing the FAS driver and when I tried to use getty I got the same problems I posted 6 months ago: modem answers but no login prompt. I have been successfully dialing out of this same port with the original driver and the FAS driver. In fact, I am posting this from a successful dialout. I am using a Compaq 386/25 running ISC 386/ix 2.0.2 and the FAS driver with a Telebit Trailblazer Plus modem. /usr/lib/uucp portions of interest: Devices: ACU ttyF01 - 1200 tb1200 \T ACU ttyF01 - 2400 tb2400 \T ACU ttyF01 - 9600 tbfast \T ACU ttyF01 - 19200 tbfast \T ACU tbinit - 19200 tbinit \T Dialers: tb1200 =W-, "" A\pA\pA\pA\pA\pT OK ATx3s0=0s64=1s50=2DT\T NNECT\s1200 tb2400 =W-, "" A\pA\pA\pA\pA\pT OK ATx3s0=0s64=1s50=3DT\T NNECT\s2400 tbfast =W-, "" A\pA\pA\pA\pA\pT OK ATx3s0=0s64=1s50=255DT\T FAST-\c-FAST tbinit =W-, "" A\pA\pA\pA\pA\pT OK ATs51=254 OK Systems (modified): lgc Any ACU 19200 5551212 "" \r "" \r ogin:--ogin:--ogin: uulgcp assword: *** Does anybody have a suggestion on how to get a successful dialin? Thanx in advance (again)... -- Max Heffler internet: max@lgc.com Landmark Graphics Corp. uucp: ..!uunet!lgc!max 333 Cypress Run, Suite 100 phone: (713) 579-4751 Houston, Texas 77094
gemini@geminix.mbx.sub.org (Uwe Doering) (07/17/90)
max@maxsun.lgc.com (Max Heffler) writes: >I finally got around to installing the FAS driver and when I tried to use >getty I got the same problems I posted 6 months ago: modem answers but no >login prompt. I have been successfully dialing out of this same port with >the original driver and the FAS driver. In fact, I am posting this from a >successful dialout. I am using a Compaq 386/25 running ISC 386/ix 2.0.2 >and the FAS driver with a Telebit Trailblazer Plus modem. Unfortunately you didn't tell us which release of FAS you use. I'll assume that it is 2.06 (the latest one). From your dialers file I'd suspect that you have result codes enabled even if getty is on the port. Try to set your EEPROM parameters to disable result codes by default (`ATQ1'). But then you have to enable it wherever you need it (`ATQ0'), in your dialers file for instance. The problem here is that the modem result string may confuse getty. Did you check the gettydefs file? Maybe the port isn't set up with the proper flags. Please tell us when you got it working. Uwe PS: Max, you obviously mixed up the `Followup-To:' with the `Reply-To:' header line. Please use the latter for your e-mail address. My first attempt to post a followup to your article ended in `dead.article'. :-( -- Uwe Doering | Domain : gemini@geminix.mbx.sub.org Berlin |--------------------------------------------------------------- West Germany | Bangpath : ...!uunet!pyramid!tub!tmpmbx!geminix!gemini
det@hawkmoon.MN.ORG (Derek E. Terveer) (07/22/90)
In article <9KMH2R@geminix.mbx.sub.org> gemini@geminix.mbx.sub.org (Uwe Doering) writes: > max@maxsun.lgc.com (Max Heffler) writes: > > From your dialers file I'd suspect that you have result codes enabled > even if getty is on the port. Try to set your EEPROM parameters to disable > result codes by default (`ATQ1'). But then you have to enable it wherever > you need it (`ATQ0'), in your dialers file for instance. The problem here > is that the modem result string may confuse getty. I specify atq5 on my trailblazer plus with satisfactory results -- but i'm also running uugetty on the port. [The atq5 mode is defined as follows: The local modem will not report the RING result codes and it not report NO CARRIER, CONNECT, BUSY or RRING unless the connection was initiated with an ATD or ATA command. (From page 4-9 of rev A of the tb+ manual) -- Derek Terveer det@hawkmoon.MN.ORG