Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mira.net.au!yarrina.connect.com.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!paladin.american.edu!gatech!newsfeed.internetmci.com!info.ucla.edu!library.ucla.edu!news.bc.net!rover.ucs.ualberta.ca!george From: george@ee.ualberta.ca (Jason George) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Crazy remote login problem Date: 9 Mar 1996 07:04:46 GMT Organization: University of Alberta Electrical Engineering Department Lines: 53 Message-ID: <4hraie$pfc@pulp.ucs.ualberta.ca> NNTP-Posting-Host: nyquist.ee.ualberta.ca X-Newsreader: TIN [version 1.2 PL2] Ok...I'll try to make this description as painless at possible! :-) I have an old 9600 baud modem off the back of a FreeBSD box I set up at work. I have the modem setup to answer the phone and give a login prompt. This was no problem. I can dial in and get the prompt everytime. The problem arises _after_ I hit the 'enter' key, following the password. I get a few characters of the login message (copyrights, etc) then my screen goes to pot. I am making an educated guess that there is a parity flip occurring on the line from the time I hit enter after the password to the time the actual login is processed. Whatever I type at the remote end is echoed back cleanly and is executed properly but the 'text' coming back down the line is complete garbage. I have tried dialing in with _every_ conceivable and supported bit scheme. I would post my gettytab and ttys entries, but I'd have to drive a fair distance to login at the console...;-) In any instance, the ttys entry should be fine set as 'dialup', and my std.9600 entry is the stock, generic entry. I am highly certain that it is set to NO PARITY. I am beginning to pull my hair out. My uucp connection can't even resolve a "Shere" when logging in. Hardware of interest: ATI 9600 modem, Soyo P5-75 PCI integrated mainboard (IDE, serial, etc) I originally suspected a flaky UART but then I remembered that I had used that same port earlier in the week with another device and had no problems. At any rate, I need to get this working ASAP and I have completely exhausted my local resources. I suspect I'm rambling now. Mental exhaustion can do that to you. :-) Any help is greatly appreciated! --Jason george@ee.ualberta.ca Contract admin. and bitsmith, frantically trying to graduate! Addendum: the system works flawlessly otherwise...it's just that dang modem connection!f