From owner-freebsd-current@FreeBSD.ORG Sun Jun 12 11:37:44 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A4DEF16A41C for ; Sun, 12 Jun 2005 11:37:44 +0000 (GMT) (envelope-from paul.richards@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A44243D55 for ; Sun, 12 Jun 2005 11:37:44 +0000 (GMT) (envelope-from paul.richards@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so885648wri for ; Sun, 12 Jun 2005 04:37:43 -0700 (PDT) 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:content-disposition; b=I9Sb0THFB4eiGahR5IYt0xwLzXmDqR00m0C2deRULYPZrUSRkOfUn98nSVQ5b/RiWhdCw4LnSm7uNda5IElwgpBLfeVu2OejG2hH1u2ASfQB9O3cZxzeUx+7R+RIiYsN2PBE+xeRuHr+ni0Yxd0QfXCblCEWHMw4ry6gnbE9V0E= Received: by 10.54.2.61 with SMTP id 61mr873233wrb; Sun, 12 Jun 2005 04:37:43 -0700 (PDT) Received: by 10.54.97.7 with HTTP; Sun, 12 Jun 2005 04:37:43 -0700 (PDT) Message-ID: Date: Sun, 12 Jun 2005 12:37:43 +0100 From: Paul Richards To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: Immediate reboots on amd64 after upgrading to current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Paul Richards List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Jun 2005 11:37:44 -0000 Hi, I was running 5.4 (amd64) but was looking to get my nForce4 nic working. I heard about the nve driver in current and so I upgraded to current. I followed the handbook instructions of essentially make buildworld, buildkernel, installkernel etc.. When I rebooted however I found that the new kernel immediately reboots after selecting any of the options on the boot menu (safe mode, normal, single user, etc). I've restored my system to 5.4 (it didn't have anything important anyway) but I was wondering what actually went wrong.. Is the 6-current broken at the moment? (unlikely as it seems like quite a severe break) Did I miss something to do with reconfiguring the boot process? What should I look out for when I try again..? --=20 Paul Richards