Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!metro!sequoia!ultima!kralizec.zeta.org.au!godzilla.zeta.org.au!not-for-mail From: bde@kralizec.zeta.org.au (Bruce Evans) Newsgroups: comp.os.386bsd.questions Subject: Re: FreeBSD multiport serial troubles... Date: 23 Nov 1993 16:34:12 +1100 Organization: Kralizec Dialup Unix Sydney - +61-2-837-1183, v.32bis and v.42bis Lines: 25 Message-ID: <2cs7clINN2b5@godzilla.zeta.org.au> References: <CGorE5.23K@swi.psy.uva.nl> <2cglg6$hm@wzv.win.tue.nl> <CGsMxF.3L5@swi.psy.uva.nl> <1993Nov22.031429.27227@mcshub.dcss.mcmaster.ca> NNTP-Posting-Host: godzilla.zeta.org.au In article <1993Nov22.031429.27227@mcshub.dcss.mcmaster.ca>, Todd Pfaff <todd@flex.eng.mcmaster.ca> wrote: > >I have a similar problem with dialup logins under FreeBSD-1.0R but on >a standard serial port (not multiport) using sio drivers. > >The modem answers, getty responds and starts login, and login seems to >change the tty to cs7 so the remote, which is set for 8-bit data, sees >garbage. You may be experiencing the same problem. During a modem login >attempt, try 'stty -f /dev/serial-device' and check for cflags: cs7. Old versions of getty only use the settings specified in /etc/gettytab while getty is running. They throw away these settings and replace them with the fixed settings (cs7) in /usr/include/sys/ttydefaults.h when getty execs login. >Is it login that sets the tty to 7-bit? If so, why? If not, then what's >the culprit? Is there a simple solution? getty sets the tty to 7-bit so that login doesn't have to know about tty stuff. For a quick fix, change <sys/ttydefaults.h> to cs8 and recompile getty. The next version of FreeBSD should have a better solution. -- Bruce Evans bde@kralizec.zeta.org.au