Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msunews!agate!howland.reston.ans.net!math.ohio-state.edu!jussieu.fr!univ-lyon1.fr!swidir.switch.ch!scsing.switch.ch!news.belwue.de!news.uni-ulm.de!rz.uni-karlsruhe.de!darum.uni-mannheim.de!andrew From: andrew@wipux2.wifo.uni-mannheim.de (Andrew Wheadon) Newsgroups: comp.os.386bsd.bugs Subject: Re: Anyone having tty00 access problems in NetBSD-.0 Date: 9 Jan 1995 13:41:50 GMT Organization: Rechenzentrum Uni-Mannheim Lines: 24 Distribution: usa Message-ID: <3ereeu$geh@darum.uni-mannheim.de> References: <3ei8ap$25v@ebony.woods.com> NNTP-Posting-Host: wipux2.wifo.uni-mannheim.de In article <3ei8ap$25v@ebony.woods.com>, J. T. Holmes <jtholmes@ebony.woods.com> wrote: >I cannot access /dev/tty00 or /dev/tty01 via tip or cu (or with anything >else it appears) under NetBSD-1.0 Have you tried kermit >I have both NetBSD-1.0 and NetBSD-0.9 and DOS on the same 486/33 machine >and only NetBSD-1.0 is unable to talk to the modem on /dev/tty00. com0 at isa0 port 0x3f8-0x3ff irq 4: ns82450 or ns16450, no fifo com1 at isa0 port 0x2f8-0x2ff irq 3: ns82450 or ns16450, no fifo Does dmesg list the above ? if not recompile kernel with support for com? Are you running ttyflags -a Have you set the flags in ttys (man ttys) you might try (this is guessing): tty00 "/usr/libexec/getty std.9600" dailup on rtscts (if you have rts/cts handshaking which you should) try setting flags for tty00 with 'stty' Cheerio -- The cost of living hasn't affected it's popularity. (unknown) current release=doc host=wipux2.wifo.uni-mannheim.de \ "NetBSD-current mirror" hostbase=/mit/ftp/pub/NetBSD base=/usr prefix=/usr backup delete use-rel-suffix