From owner-freebsd-questions@FreeBSD.ORG Wed Mar 24 19:02:59 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 986CA106566C for ; Wed, 24 Mar 2010 19:02:59 +0000 (UTC) (envelope-from cjk32@cam.ac.uk) Received: from ppsw-1.csi.cam.ac.uk (ppsw-1.csi.cam.ac.uk [131.111.8.131]) by mx1.freebsd.org (Postfix) with ESMTP id 5F9398FC14 for ; Wed, 24 Mar 2010 19:02:59 +0000 (UTC) X-Cam-AntiVirus: no malware found X-Cam-SpamDetails: not scanned X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from nat0.cjkey.org.uk ([88.97.163.219]:46883 helo=[192.168.2.59]) by ppsw-1.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.151]:465) with esmtpsa (PLAIN:cjk32) (TLSv1:DHE-RSA-AES256-SHA:256) id 1NuVr0-0001yF-3g (Exim 4.70) for freebsd-questions@freebsd.org (return-path ); Wed, 24 Mar 2010 19:02:58 +0000 Message-ID: <4BAA61E1.4090501@cam.ac.uk> Date: Wed, 24 Mar 2010 19:02:57 +0000 From: Christopher Key User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <4BA78BF3.2090102@cam.ac.uk> <4BAA4CE5.7030104@cam.ac.uk> In-Reply-To: <4BAA4CE5.7030104@cam.ac.uk> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: Unable to boot FreeBSD 8.0 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Mar 2010 19:02:59 -0000 Christopher Key wrote: > Christopher Key wrote: > >> Hello, >> >> I'm using FreeBSD 7.2, and am attempting to update to 8.0. >> >> >> I've been through the standard, >> >> make buildworld >> make buildkernel >> make installkernel >> >> but cannot get the newly installed kernel to boot. The system freezes >> as soon as the loader tries to boot the kernel. It doesn't even get as >> far as the copyright message: >> >> Type '?' for a list of commands, 'help' for more detailed help. >> OK boot -Dd >> \ >> >> >> > Problem solved. Hopefully the answer might be of use to others, as it > doesn't seem too uncommon a situation. > > Had I read /usr/src/UPDATING more carefully however, I might have spotted, 20080713: The sio(4) driver has been removed from the i386 and amd64 kernel configuration files. This means uart(4) is now the default serial port driver on those platforms as well. To prevent collisions with the sio(4) driver, the uart(4) driver uses different names for its device nodes. This means the onboard serial port will now most likely be called "ttyu0" instead of "ttyd0". You may need to reconfigure applications to use the new device names. When using the serial port as a boot console, be sure to update /boot/device.hints and /etc/ttys before booting the new kernel. If you forget to do so, you can still manually specify the hints at the loader prompt: set hint.uart.0.at="isa" set hint.uart.0.port="0x3F8" set hint.uart.0.flags="0x10" set hint.uart.0.irq="4" boot -s which is probably why noone else has suffered from this problem. Christopher Key