From owner-freebsd-questions Tue Jun 18 23:27:43 2002 Delivered-To: freebsd-questions@freebsd.org Received: from cpimssmtpu05.email.msn.com (cpimssmtpu05.email.msn.com [207.46.181.81]) by hub.freebsd.org (Postfix) with ESMTP id 6337A37B40B for ; Tue, 18 Jun 2002 23:27:38 -0700 (PDT) Received: from thebe ([67.24.227.209]) by cpimssmtpu05.email.msn.com with Microsoft SMTPSVC(5.0.2195.4905); Tue, 18 Jun 2002 23:26:50 -0700 From: "Aaron Burke" To: "FreeBSD-Questions" , Subject: RE: Serial console issues Date: Tue, 18 Jun 2002 23:26:45 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-reply-to: <20020618235524270.AAA595@empty1.ekahuna.com@pc02.ekahuna.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-OriginalArrivalTime: 19 Jun 2002 06:26:50.0860 (UTC) FILETIME=[4BF46AC0:01C2175A] Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > djf2 wrote: > > > On Tue, 18 Jun 2002, Aaron Burke wrote: > > > > You should be able to use "dmesg | grep sio" to determine what kind > > > of hardware you are running. > > > > I'm fairly certain it isn't the hardware, at least in my case. > > I've used several different machines that were at least > relatively recent > > hardware (at least past the point where they wouldn't have had a 16550 > > uart) and the serial console exhibited the same behavior each time. > > > In my case I'm not able to get the serial console working at all. > All I get on my display is some periodic commas and D characters. > I have it set for Xon/Xoff flow control. I believe that unless your box does not have a keyboard attached the box does not turn on COM1 unless you have specified that you want a login on /dev/cuaa1. You will want to check /etc/ttys for this value. I dont remember if its turned on by default, but I always turn it on myself. Also, unless you make changes to the boot loader, the system will default to the primary graphics adapter. But your suggestion of -Dh may fix the problem. I used to have that configured, but not any more, so your guess is better than mine right now. > > Current FBSD versions appear to enable console operations by default > on sio0, (with the "flags 0x10" argument in the kernal config file) > so in theory all I should have to do is connect a null-modem cable, > run a comm program at 9600,N,8,1 - create a boot.config file with a > "-D" or "-h" or "-Dh" in it (or specify it to the boot loader at boot > time) and get something. I don't get any output. > > I'm going to try it on another box and see if it's hardware related. Ok but also check that /etc/ttys is configured the same way as the terminal that your gonna attach. > > (aside: the Intel L440GX+ server board I'm testing this on has a > bunch of embedded serial management features, most of which work on > COM2. Among other things, it has a "console redirection" feature > which does basically the same thing those $300 boards from > www.realweasel.com do - and which Rod Smith so helpfully mentioned in > the previous thread. Too bad the Intel implementation is buggy.. :-) Well, that sucks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message