From owner-freebsd-questions@FreeBSD.ORG Mon May 10 16:28:53 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A7A7916A4CE for ; Mon, 10 May 2004 16:28:53 -0700 (PDT) Received: from relay02.roc.ny.frontiernet.net (relay02.roc.ny.frontiernet.net [66.133.131.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id C938F43D2F for ; Mon, 10 May 2004 16:28:52 -0700 (PDT) (envelope-from drew@mykitchentable.net) Received: (qmail 460 invoked from network); 10 May 2004 23:28:51 -0000 Received: from 67-51-156-100.dsl1.elk.ca.frontiernet.net (HELO blacklamb.mykitchentable.net) ([67.51.156.100]) (envelope-sender )SMTP for ; 10 May 2004 23:28:51 -0000 Received: from [165.107.42.233] (unknown [165.107.42.233]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by blacklamb.mykitchentable.net (Postfix) with ESMTP id 63E6F3BF489; Mon, 10 May 2004 16:28:50 -0700 (PDT) Message-ID: <40A01036.3050604@mykitchentable.net> Date: Mon, 10 May 2004 16:28:54 -0700 From: Drew Tomlinson User-Agent: Mozilla Thunderbird 0.6 (Windows/20040502) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Stijn Hoop References: <409B0973.7030205@solisix.com> <409B4259.9040300@users.sourceforge.net> <20040507081053.GA861@pcwin002.win.tue.nl> <409B6DBD.1080704@users.sourceforge.net> <20040507114247.GB861@pcwin002.win.tue.nl> In-Reply-To: <20040507114247.GB861@pcwin002.win.tue.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: Rob cc: freebsd-questions@freebsd.org Subject: Re: Connecting to a Headless machine, after install X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 May 2004 23:28:53 -0000 On 5/7/2004 4:42 AM Stijn Hoop wrote: >On Fri, May 07, 2004 at 08:06:37PM +0900, Rob wrote: > > >>Stijn Hoop wrote: >> >> >>>On Fri, May 07, 2004 at 05:01:29PM +0900, Rob wrote: >>> >>> >>>>Funny, that I'm struggling with opposite problem: I do not get the >>>>boot messages over the serial cable, but do get the login prompt, >>>>which I do not understand :(. >>>> >>>> >>>You probably need to tell the kernel to use the serial console: >>> >>># echo '-h' > /boot.config >>> >>> >>Ah, thanks. I don't have a /boot.config yet. Are you sure this file goes >>in the top-root directory? Or in /boot/... ? >> >> > >Yes, top-root /. Check the handbook, section 17.6: > >http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/serialconsole-setup.html > > > >>You made me research a little more on this. I do have a file >>/boot/loader.conf. >>How about having in here the line >> >> console="comconsole" >> >>(to divert it from the default: console="vidconsole") ? >> >>Or will that not do the same? >> >> > >Having -h in /boot.config will also allow the boot blocks to output to >your serial console. I suspect console="comconsole" would help the loader >+ kernel. It certainly couldn't hurt I guess :) > If I understand the process correctly, settings in /boot/loader.conf override settings in /boot.config as the boot loader happens after the boot blocks. Thus by setting "comconsole" will negate any settings in /boot.config. Setting in both places is redundant and may cause problems for you when troubleshooting. For my serial console, I set my kernel flag to 0x10 so I have console options without recompiling. Then I do my serial console settings in /boot.config as it happens earlier in the boot stage and thus, I get my serial console a little sooner. HTH, Drew -- Visit The Alchemist's Warehouse Magic Tricks, DVDs, Videos, Books, & More! http://www.alchemistswarehouse.com