From owner-freebsd-current Mon Feb 3 11:47:28 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7F92E37B401 for ; Mon, 3 Feb 2003 11:47:26 -0800 (PST) Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id F02D243F43 for ; Mon, 3 Feb 2003 11:47:25 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0144.cvx21-bradley.dialup.earthlink.net ([209.179.192.144] helo=mindspring.com) by heron.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 18fmYk-0002dB-00; Mon, 03 Feb 2003 11:47:15 -0800 Message-ID: <3E3EC6EE.DE9C34F1@mindspring.com> Date: Mon, 03 Feb 2003 11:45:50 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Don Bowman Cc: Attila Nagy , Lucky Green , freebsd-current@FreeBSD.ORG Subject: Re: L440gx+ serial BIOS needs text mode References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4da094c3bcabea50f90c7dfeef4859d88666fa475841a1c7a350badd9bab72f9c350badd9bab72f9c Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Don Bowman wrote: > > Anyway, it was a particular problem with the SuperMicro motherboards > > with the AMI BIOS that's been the subject of the rest of this > > discussion (i.e. the ones that kick out the escape sequence at the > > end, for no good reason, except to screw up non-monochrome VTxxx > > emulators, and make it hard to use a UNIX box as the serial console). > > FYI, I've found that running under 'screen' fixes the problem > with the odd escape sequences. > One type of system we have puts out an escape sequence that > is escape followed by 12 [. Not sure what that is :) > The other works just great, except it switches to black on > black just as it switches to the OS :) I guess we don't get to escape from the gory details... 8-). The 12 ['s are compressed into a single [, for fully ANSI compliant state machines, because they are in the wrong column of the old DEC-published ASCII chart to terminate an escape sequence, so the real question is "what comes after the last [?". If you are seeing the 12 ['s, then your ANSI 3.64 state machine is not compliant. 8-). Back to the color change... The issue is support for the ISO ESC "[" "3" n "m" and the ISO ESC "[" "4" n "m" set foreground/set background color sequences. Windows Telnet doesn't support these, and neither does the terminal program that comes with Windows by default, but UNIX consoles do, and so does xterm, so running a dumb tty pipe like "tip" or "cu" on one of these passes them through. Running "screen" like you are, the emulation is a dumb VT100, and the escape sequences are interpreted by the "screen" program, instead of by the terminal window in which "screen" is running ("screen" is a terminal emulator that runs in a virtual terminal window, as an implementation detail for it being able to maintain multiple instances of display memory). The xterm didn't use to do this, by default, actually, and if you run your xterm with the "-cm -dc" options, or put: xterm.colorMode=false xterm.dynamicColors=false in your .Xdefaults file. I imagine this change is a result of some idiot wanting "colorls" to work by default, just as the BIOS spitting out the sequence was added at the request of some idiot to give people "one more reason not to use UNIX". 8-). If it really bothers you, you can disassemble, modify, reassemble, and then re-flash your BIOS to get rid of it (it bothered me, but not enough to do that, just enough to make me make an icon that started xterm with the color disabling arguments, which ran telnet to the terminal server connected to the serial consoles in the server room as it's "-e" argument). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message