From owner-freebsd-current Wed May 31 15: 1:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (www.slackware.com [204.216.27.13]) by hub.freebsd.org (Postfix) with ESMTP id 8976C37BA59 for ; Wed, 31 May 2000 15:01:47 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id PAA01594; Wed, 31 May 2000 15:04:31 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200005312204.PAA01594@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "gh" Cc: current@freebsd.org Subject: Re: unknown: In-reply-to: Your message of "Sun, 28 May 2000 19:39:35 CDT." <002601bfc912$2cc36360$2969a0d0@leviathan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 31 May 2000 15:04:31 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > IF and ONLY IF the PNPBIOS code is causing your machine to fail, do the > > following: > > > > - Send me FULL DETAILS; this will need to include the trap messages and, > > if the trap is in the kernel, a DDB traceback. > > > > The described situation actually occured to me tonight (5-28-2000) while > trying to install. > Rather than check the list for a solution, I went back to the 4.0 boot disks > (which worked really well) and changed them to setup a snapshot > (5.0-20000528-CURRENT). > > If you so desire (which presumably is the case), I can just boot up the > current floppies and try to send you the information you request. I can't imagine not being interested in working out what's going wrong, so please, if you could, do so. Let me know what your hardware is as well, please. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message