Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!ihnp4.ucsd.edu!nntp.ucsb.edu!library.ucla.edu!agate!usenet.ins.cwru.edu!magnus.acs.ohio-state.edu!math.ohio-state.edu!jussieu.fr!univ-lyon1.fr!swidir.switch.ch!newsfeed.ACO.net!Austria.EU.net!EU.net!Germany.EU.net!mips.arb-phys.uni-dortmund.de!arb-phys.uni-dortmund.de!not-for-mail From: wb@arb-phys.uni-dortmund.de (Wilhelm B. Kloke) Newsgroups: comp.os.386bsd.bugs Subject: FreeBSD-1.1.5R probable bug in terminal driver, when using SLIP Date: 4 Aug 1994 11:02:54 +0200 Organization: Inst f Arbeitsphysiologie Dortmund Lines: 17 Message-ID: <31qash$ssj@gisli.arb-phys.uni-dortmund.de> NNTP-Posting-Host: gisli.arb-phys.uni-dortmund.de As the behaviour of the terminal driver changed from FreeBSD-1.1 to 1.1.5 changed, I tried some debugging on slattach/chat. ( In 1.1, I used slattach -h -r 'chat "" ATDP258 CONNECT "" ogin:-\\r-ogin: dial ssword: *secret* </dev/tty00 1>/dev/tty00' -s 57600 /dev/tty00 to drive a SLIP dialout port successfully. Now the opening by the redirect seems to reset the baud rate to 9600. It works if I change 57600 to 9600.) So I changed slattach to start chat with the modem port open on file descs 0 and 1, and baud rate set to 57600. I now use slattach -h -r 'chat -v "" AT OK-AT-OK dATDP258 CONNECT-ATDP258-CONNECT "" ogin:-\\r-ogin: dial ssword: *secret*' -s 57600 /dev/cua00 and it works *once*. When the line looses carrier afterwards, any further attempt to chat fail with I/O errors. This seems to indicate a bug in the behaviour of the terminal driver. -- Dipl.-Math. Wilhelm Bernhard Kloke Institut fuer Arbeitsphysiologie an der Universitaet Dortmund Ardeystrasse 67, D-44139 Dortmund, Tel. 0231-1084-257