Date: Tue, 30 Sep 2003 09:07:07 -0400 From: Chris Pepper <pepper@reppep.com> To: Peter Pentchev <roam@ringlet.net> Cc: qa@freebsd.org Subject: Re: FreeBSD 4.9 RC1 (i386) now available Message-ID: <p06100304bb9f2fd554b3@[66.92.104.201]> In-Reply-To: <20030930112341.GK551@straylight.oblivion.bg> References: <20030929151905.GD3743@freebsdmall.com> <p06100304bb9e9e078823@[66.92.104.201]> <20030930110311.GA7634@rot13.obsecurity.org> <20030930112341.GK551@straylight.oblivion.bg>
next in thread | previous in thread | raw e-mail | index | archive | help
At 2:23 PM +0300 2003/09/30, Peter Pentchev wrote: >On Tue, Sep 30, 2003 at 04:03:11AM -0700, Kris Kennaway wrote: >> On Mon, Sep 29, 2003 at 11:38:05PM -0400, Chris Pepper wrote: >> >> > When I choose vt100 (option #2), the display is scrambled >> > (lines wrap, option titles shift up and down when using the arrows, >> > and get out of sync with the descriptions on the right side). With >> > ANSI (option #1), I couldn't move into the main options area -- all 4 >> > arrows, as well as tab, ask me if I really wanted to abort, and >> > there's no visible way to do anything but exit. >> >> Sounds like both of these are the wrong terminal type. > >Chris (the original poster ;), what terminal emulator are you using >on the other side of the serial cable? What terminal type is it set to >emulate? I'm using Mac OS X 10.2.8's Terminal.app, which claims to be vt100, through minicom. The bad display is probably Terminal.app's fault -- I'll try through an (Apple) xterm next -- but I was very surprised that arrow keys wouldn't work in ANSI mode. FWIW, I mentioned that primarily as an indication that I might not have hit BootMgr, since I couldn't see what I was doing well. The more serious problems are package conflicts and nonworking boot code... Thanks, Chris Pepper -- Chris Pepper: <http://www.reppep.com/~pepper/>; Rockefeller University: <http://www.rockefeller.edu/>;
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p06100304bb9f2fd554b3>