From owner-freebsd-current Mon Oct 5 16:37:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA02118 for freebsd-current-outgoing; Mon, 5 Oct 1998 16:37:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA02103 for ; Mon, 5 Oct 1998 16:37:14 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA00720; Mon, 5 Oct 1998 16:42:34 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810052342.QAA00720@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Viren R. Shah" cc: freebsd-current@FreeBSD.ORG Subject: Re: boot loader problems.. In-reply-to: Your message of "Mon, 05 Oct 1998 17:35:58 EDT." <199810052135.RAA01302@jabberwock.rstcorp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 05 Oct 1998 16:42:34 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > [Let me preface this by saying that this is very probably my fault -- > I probably missed doing something] No, it's a known problem. > The loader can't figure out where it was loaded from -- thus it > defaults to disk0 (floppy drive). I can change the currdev setting to > disk1s3 and it boots up fine. There's a problem where the boot arguments are being scrubbed off the stack in some cases. I have systems where they come in fine, and some where they don't. We're still looking at this one. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message