From owner-freebsd-current Mon Oct 5 01:30:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA01503 for freebsd-current-outgoing; Mon, 5 Oct 1998 01:30:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA01484 for ; Mon, 5 Oct 1998 01:30:46 -0700 (PDT) (envelope-from kpielorz@caladan.tdx.co.uk) Received: from localhost (kpielorz@localhost) by caladan.tdx.co.uk (8.9.1a/8.9.1) with ESMTP id JAA07355 for ; Mon, 5 Oct 1998 09:30:21 +0100 (BST) Date: Mon, 5 Oct 1998 09:30:21 +0100 (BST) From: Karl Pielorz To: current@FreeBSD.ORG Subject: Serial Console - at above 9600 baud? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi All, I've finally got my serial console working (thanks to all that helped) - the sio flags being set to '0x30' (as opposed to the 0x20 I was using) finally got it working... I can't seem to get it to run above 9600 baud though... If I use: options CONSPEED=57600 In my kernel config (with our without "'s around it) it boots, starts the serial console at 9600 - then I get a _lot_ of corruption, it almost looks as if some parts of the console IO are happening at 9600 baud, and others at 57k6... If I leave the above line out - it all works, but only at 9600 baud... Has anyone else seen this? Also once the system is booted - the console is left 'dead' - am I safe to run up a getty on this? (i.e. I presume the getty will die and ddb will take over in case of a panic?) Regards, Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message