From owner-freebsd-questions  Sun Feb  9 18: 5:33 2003
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id AD5FB37B401
	for <questions@FreeBSD.ORG>; Sun,  9 Feb 2003 18:05:32 -0800 (PST)
Received: from mailhost.det2.ameritech.net (mailhost1-sfldmi.sfldmi.ameritech.net [206.141.193.105])
	by mx1.FreeBSD.org (Postfix) with ESMTP id C731F43F85
	for <questions@FreeBSD.ORG>; Sun,  9 Feb 2003 18:05:31 -0800 (PST)
	(envelope-from dbailey27@ameritech.net)
Received: from ameritech.net ([67.38.16.140])
          by mailhost.det2.ameritech.net
          (InterMail vM.4.01.02.17 201-229-119) with ESMTP
          id <20030210020514.OLGO26543.mailhost.det2.ameritech.net@ameritech.net>;
          Sun, 9 Feb 2003 21:05:14 -0500
Message-ID: <3E4708C6.7080406@ameritech.net>
Date: Sun, 09 Feb 2003 21:04:54 -0500
From: northern snowfall <dbailey27@ameritech.net>
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:0.9.4.1) Gecko/20020518 Netscape6/6.2.3
X-Accept-Language: en-us
MIME-Version: 1.0
To: jfm@blueyonder.co.uk
Cc: questions@FreeBSD.ORG
Subject: Re: 5.0-release install problem
References: <1044835204.30687.56.camel@daneel> <3u1e4vs4ahgsc6b48o4atru87abg0d98th@4ax.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-questions.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-questions>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-questions>
X-Loop: FreeBSD.ORG

>
>
>drivers.flp is your friend :) It happened to me, and I'm no fool!
>
Well, thats kind of the point of the problem. Drivers.flp isn't needed.
Sysinstall loads the 8139 driver from its base. The ATA drivers are
in the base, as well (of course), so the question is: why does the bug in
the 8139 driver manifest in a mishandling of the mounted file system?
This leads me to believe that the bug isn't 8139-dependant, but, something
rooted in the design of the interrupt code itself.
Don

"i want to be.. as deep... as the ocean"

>


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