From owner-freebsd-amd64@FreeBSD.ORG Tue Jun 21 13:55:06 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D67C516A41F for ; Tue, 21 Jun 2005 13:55:06 +0000 (GMT) (envelope-from gallatin@cs.duke.edu) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96F4643D48 for ; Tue, 21 Jun 2005 13:55:06 +0000 (GMT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.13.4/8.13.4) with ESMTP id j5LDt53U006780 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 21 Jun 2005 09:55:05 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id j5LDt0wC060029; Tue, 21 Jun 2005 09:55:00 -0400 (EDT) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17080.7220.311013.499442@grasshopper.cs.duke.edu> Date: Tue, 21 Jun 2005 09:55:00 -0400 (EDT) To: "O. Hartmann" In-Reply-To: <42B2D638.8090501@mail.uni-mainz.de> References: <42B2D638.8090501@mail.uni-mainz.de> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Cc: freebsd-amd64@freebsd.org Subject: Re: 6.0-CURRENT (SNAP004) on AMD64 fails, alternatives? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jun 2005 13:55:07 -0000 O. Hartmann writes: > Hello. > I try to boot 6.0-Current from the most recent June2005 snap built and > kernel fails due to detaching and ataching hard drives connected to the > nForce4 SATA controller (ASUS A8N-SLI Deluxe with Maxtor 6MO200B and > Samsung 2004C drives). > > I read about problems with SATA/ATA in this list so I don't want to do a > error report. I would like to know whether there is an alternative way > to get a maybe fixed boot image of 6.0-CURRENT? What I did was to build a -current kernel on another machine, and netboot that via PXE (my motherboard calls it the "Nvidia Boot Agent") Make sure that you copy the mfsroot.gz from the CDROM into your diskless boot area, and put this into the loader.conf in your diskless boot area: mfsroot_load="YES" mfsroot_type="mfs_root" mfsroot_name="/boot/mfsroot" vfs.root.mountfrom="ufs:/dev/md0c" Make sure to go to the shell prompt and copy the good kernel onto the machine after the installation, but before rebooting. To do this, you'll need a network. I had problems with the nve0 adapter (though PXE worked great), and ended up switching to the sk0 adapter. This is annoying, because linux & solaris hate the sk0 adapter and like the nforce ethernet better.. Good luck! Drew