From owner-freebsd-questions Sun Sep 17 11:52:16 2000 Delivered-To: freebsd-questions@freebsd.org Received: from one.net-noise.com (ansible.nwark.net [208.136.254.190]) by hub.freebsd.org (Postfix) with ESMTP id 331DE37B423 for ; Sun, 17 Sep 2000 11:52:11 -0700 (PDT) Received: from guinevere (guinevere.net-noise.com [192.168.1.14]) by one.net-noise.com (8.9.3/8.9.3) with SMTP id NAA20331 for ; Sun, 17 Sep 2000 13:52:06 -0500 Message-ID: <000e01c020d8$7b8396a0$0e01a8c0@guinevere> Reply-To: "J. Seth Henry" From: "J. Seth Henry" To: Subject: Serial TTY problems Date: Sun, 17 Sep 2000 13:52:51 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000B_01C020AE.9257F490" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_000B_01C020AE.9257F490 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I have a VT220 terminal I would like to use with my BSD machine. The = terminal and serial cable both work; I tested it on a Windows PC with = TeraTerm and I can type both ways. The problem is, FreeBSD doesn't seem = to like it. I turned on COM1 for getty in /etc/ttys and restarted the = init daemon. Sure enough, I get the login prompt on the terminal - but I = can't type anything. It's as though the getty process isn't receiving = anything. I've tested both the serial ports, and they work, so I don't = know where the problem is. I know the serial port parameters are = correct, because the text on the terminal is correct.=20 Particulars: I'm running FreeBSD 4.1 on an Intel based system. (P233MMX on a Tyan = mainboard). Both serial ports were known to be working before installing = BSD on the system. I am not running a generic kernel, I stripped out a = lot of "unnecessary" drivers, and added sound system support - so it may = be a kernel issue. I'm stumped. Any ideas? Thanks, Seth Henry jshenry@net-noise.com ------=_NextPart_000_000B_01C020AE.9257F490 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

I have a VT220 terminal I would like to = use with my=20 BSD machine. The terminal and serial cable both work; I tested it = on a=20 Windows PC with TeraTerm and I can type both ways. The problem is, = FreeBSD=20 doesn't seem to like it. I turned on COM1 for getty in /etc/ttys and = restarted=20 the init daemon. Sure enough, I get the login prompt on the terminal - = but I=20 can't type anything. It's as though the getty process isn't = receiving=20 anything. I've tested both the serial ports, and they work, so I don't = know=20 where the problem is. I know the serial port parameters are correct, = because the=20 text on the terminal is correct.

Particulars:

I'm running FreeBSD 4.1 on = an Intel based=20 system. (P233MMX on a Tyan mainboard). Both serial ports were known to = be=20 working before installing BSD on the system. I am not running a generic = kernel,=20 I stripped out a lot of "unnecessary" drivers, and added sound system = support -=20 so it may be a kernel issue.

I'm stumped. Any ideas?

Thanks,

Seth Henry

jshenry@net-noise.com ------=_NextPart_000_000B_01C020AE.9257F490-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message