From owner-freebsd-questions@FreeBSD.ORG Sat Nov 6 23:58:48 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 785EB16A4CE for ; Sat, 6 Nov 2004 23:58:48 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 26EEE43D4C for ; Sat, 6 Nov 2004 23:58:48 +0000 (GMT) (envelope-from nick.holley@gmail.com) Received: by rproxy.gmail.com with SMTP id a36so194597rnf for ; Sat, 06 Nov 2004 15:58:45 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=U5A4nOJfRSq0eV6mKU/cJmSoNGN4okalek/48zZ48bZ7893Dfmk8jBDEueT5s2Rk6m6FbMmafWVUuKH/why1MIbVZeK6GSl4ojWZFbwj9r3LF8XV+ln1R2i1SBJuVn6GjrCOFI91a2tOPezeF6Lhgu+2O5cILQQ/5pocptjFst0= Received: by 10.38.66.19 with SMTP id o19mr1179584rna; Sat, 06 Nov 2004 15:58:45 -0800 (PST) Received: by 10.38.15.43 with HTTP; Sat, 6 Nov 2004 15:58:45 -0800 (PST) Message-ID: <40200b1704110615582694410d@mail.gmail.com> Date: Sat, 6 Nov 2004 16:58:45 -0700 From: nick holley To: freebsd-questions@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: issues booting 5.3 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: nick holley List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Nov 2004 23:58:48 -0000 I downloaded the 5.3 bootonly disc this morning and was unable to boot. I had the same problem that I experienced with the 5.3-RC2 and also when I did a buildworld from 5.2.1. The kernel appears to be booting fine until it gets to a certain point where it will stop. The boot process stops right after listing my hdds or, if my orinoco card is in, after failing to initialize my wireless nic (which happens right after the hdd listing). The system is not locked as I still receive a message about not being ready to suspend from the acpi module when I push the power button on my tower. Also, it doesn't matter which boot option I use; the boot stops at the same place every time. Can anybody give me any pointers on how to go about diagnosing the problem here? Thanks, Nick