From owner-freebsd-current  Sun May 28 19: 4:15 2000
Delivered-To: freebsd-current@freebsd.org
Received: from postal.linkfast.net (postal.linkfast.net [208.160.105.2])
	by hub.freebsd.org (Postfix) with ESMTP
	id BFDF437B9ED; Sun, 28 May 2000 19:04:08 -0700 (PDT)
	(envelope-from grasshacker@linkfast.net)
Received: from leviathan (gh.ws.linkfast.net [208.160.105.41])
	by postal.linkfast.net (Postfix) with SMTP
	id 14BB29B0A; Sun, 28 May 2000 21:04:07 -0500 (CDT)
Message-ID: <002601bfc912$2cc36360$2969a0d0@leviathan>
From: "gh" <grasshacker@linkfast.net>
To: "Mike Smith" <msmith@freebsd.org>, <current@freebsd.org>
References: <200005130706.AAA01390@mass.cdrom.com>
Subject: Re: unknown: <PNP...> 
Date: Sun, 28 May 2000 19:39:35 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
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 apologize for being currently un-helpful, but I will try to help if you
still need so.

Dan




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message