From owner-freebsd-sparc64@FreeBSD.ORG Mon Dec 22 16:20:21 2003 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B702916A4CE for ; Mon, 22 Dec 2003 16:20:21 -0800 (PST) Received: from ahmler5.mail.eds.com (ahmler5.mail.eds.com [192.85.154.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id C45E343D31 for ; Mon, 22 Dec 2003 16:20:19 -0800 (PST) (envelope-from jim.small@eds.com) Received: from ahmlir5.mail.eds.com (ahmlir5-2.mail.eds.com [192.85.154.135]) by ahmler5.mail.eds.com (8.12.10/8.12.9) with ESMTP id hBN0KGYk001869; Mon, 22 Dec 2003 19:20:16 -0500 Received: from ahmlir5.mail.eds.com (localhost [127.0.0.1]) by ahmlir5.mail.eds.com (8.11.6p3/8.11.6) with ESMTP id hBN0KGm02197; Mon, 22 Dec 2003 19:20:16 -0500 Received: from usahm102.exmi01.exch.eds.com (usahm102.exmi01.exch.eds.com [207.37.138.190]) by ahmlir5.mail.eds.com (8.11.6p3/8.11.6) with ESMTP id hBN0KGI02191; Mon, 22 Dec 2003 19:20:16 -0500 Received: by usahm102.exmi01.exch.eds.com with Internet Mail Service (5.5.2657.72) id ; Mon, 22 Dec 2003 19:20:17 -0500 Message-ID: <8AA870658244D4119AF600508BDF0A361C70878A@usahm014.exmi01.exch.eds.com> From: "Small, Jim" To: richardcoleman@mindspring.com, "Phillips, Paul" Date: Mon, 22 Dec 2003 19:20:10 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain cc: freebsd-sparc64@freebsd.org Subject: RE: Serial port flaky when using vi - Netra 1 T 105 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Dec 2003 00:20:21 -0000 I've seen this too. Besides setting the terminal correctly, I've found that if I set the columns and rows correctly it seems to fix the problem. For example: I use an xterm on a UNIX host and then connect via serial connection (tip). Once the O/S is up and running I use ssh. Either way though it's similar: Assuming default of csh: setenv TERM xterm stty rows 48 columns 132 Once I do this, vi/more/less seem to work correctly. You just need to enter the correct row and column size. On the UNIX host you're connecting from, you can do an stty -a to get these parameters. HTH, <> Jim > -----Original Message----- > From: Richard Coleman [mailto:richardcoleman@mindspring.com] > Sent: Monday, December 22, 2003 3:22 PM > To: Phillips, Paul > Cc: freebsd-sparc64@freebsd.org > Subject: Re: Serial port flaky when using vi - Netra 1 T 105 > > Phillips, Paul wrote: > > > I have been installing FreeBSD 5.2 beta on a Netra T1 105. This is a > > headless server, and I am using a Mac Powerbook running Zterm as a > > VT100 terminal emulator. The settings on Zterm are 8-N-1. > > > > In the past, I have used Zterm on this Netra to install Solaris with > > no troubles. > > > > The actual booting up and install works fine. However, post install, > > when I am running the console through the serial port, and attempt to > > use vi as an editor, it becomes very flaky. The h, j, k, and l keys > > do not work to move the cursor. The down and up arrow keys do work, > > but only if I move them VERY slowly. When I use the left and right > > arrow keys, it starts to write over the line that I am moving over > > with different text from somewhere else in the file. > > > > Very strange. This makes editing from the serial port virtually > > impossible. Luckily, I can get it installed, then ssh in and do the > > edits. > > > > Anyone have any ideas? Thanks Paul Phillips > > > I also have a Netra T1 105. I install over serial using minicom (from a > laptop running NetBSD). Minicom has a default terminal type of vt102. > > After I've installed the new kernel and rebooted into single user mode, > the first thing I do is "TERM=vt102; export TERM". This cleans up some > of the problems. I'm able to use vim at this point. > > But when mergemaster runs the pager on a big diff, the terminal still > gets really screwed up. It makes it difficult to see what I'm doing. > So to counteract this, I also type the command "PAGER=/bin/cat; export > PAGER" before running mergemaster. Although I can't page through big > diffs any longer, I can still read the screen enough to finish my install. > > I always thought it was a minicom problem, so I never said anything. > But it sounds like something else is broken. > > Richard Coleman > richardcoleman@mindspring.com > > > _______________________________________________ > freebsd-sparc64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64 > To unsubscribe, send any mail to "freebsd-sparc64-unsubscribe@freebsd.org"