From owner-freebsd-current@FreeBSD.ORG Wed Mar 16 16:49:24 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 94C2F106564A for ; Wed, 16 Mar 2011 16:49:24 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id 53C208FC15 for ; Wed, 16 Mar 2011 16:49:24 +0000 (UTC) Received: by yxl31 with SMTP id 31so834034yxl.13 for ; Wed, 16 Mar 2011 09:49:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=EWaWzmsLo8vktrTXXIpVOH3i+FJgE/ZaQGAXJ9N/OiE=; b=blNAStqXlxhYBxs9ngiEJCu+otrZ0U2cio+Og+YZD5gZrCPi818Ot3Z5h9xMkr0EX2 GgIIXJ09/tc6ceAHRnIQ9xRVoA48KvPu6veXvHSqT78KHUfP10pWlaTmgnBjcVhUWPim nWvzNyk9wHldLDcoei8tdhFVdxmO7nhXBBN5k= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=iTMRETrj1K5AO72cTpmkgqNvZwG8q8xvjmH6FFY5LvMXZxxb2K1z5bzUfhZhfUk62Q lS9F9d9+Hhh8Cy97BiC8h4nFqkEJTIBgPYhpdyQGu2s8t6o7Cw94ZznFd8zlIKihVuMM 3g7EPqdOIXquzZDaT2yMnsgbNcRazMMvTNcSc= MIME-Version: 1.0 Received: by 10.91.79.12 with SMTP id g12mr281535agl.168.1300294163415; Wed, 16 Mar 2011 09:49:23 -0700 (PDT) Received: by 10.90.83.18 with HTTP; Wed, 16 Mar 2011 09:49:23 -0700 (PDT) Date: Wed, 16 Mar 2011 09:49:23 -0700 Message-ID: From: Freddie Cash To: FreeBSD-Current Content-Type: text/plain; charset=UTF-8 Subject: How does one get a working serial console with gptboot? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Mar 2011 16:49:24 -0000 I feel like an idiot right now because I can just not figure out how to make $subject work on a -CURRENT system. :( I've read through the Handbook chapter on this. I've done the process I've used with 8.x systems. But once the kernel loads, the serial console stops working. I'm obviously missing a step somewhere. Here's what I've done. Please point out my error(s): /boot/loader.conf: hint.uart.0.disabled="0" hint.uart.0.flags="0x30" console="comconsole vidconsole" comconsole_speed="115200" boot_multicons="yes" /etc/make.conf: BOOT_COMCONSOLE_PORT=0x3F8 BOOT_COMCONSOLE_SPEED=115200 /etc/ttys: ttyu0 "/usr/libexec/getty std.115200" vt100 on secure Then I rebuilt the boot code via: cd /usr/src/sys/boot make cleandepend; make depend; make; make install And I loaded the new boot code into the GPT via: gpart bootcode -p /boot/gptboot -i 1 ada0 This motherboard (SuperMicro H8DGi-F) includes an IPMI-enabled serial-over-LAN setup, including a KVM-over-LAN. The KVM-over-LAN uses a virtual onscreen keyboard, though, so it's a pain to use, which is why I'm trying to get the serial console stuff working. The BIOS is configured to use COM3 for the remote access setup. The kernel detects this as uart0, and dmesg shows it as being detect and set as "uart0: console (115200,n,8,12). The serial console works at the boot loader screens and I can drop to a loader prompt, type away, etc. As soon as I type "boot" and the kernel loads ... the serial console dies. Any suggestions? -- Freddie Cash fjwcash@gmail.com