From owner-freebsd-current@FreeBSD.ORG Tue Aug 18 14:15:00 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CBC33106568E for ; Tue, 18 Aug 2009 14:15:00 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (muon.cran.org.uk [66.246.138.153]) by mx1.freebsd.org (Postfix) with ESMTP id 9F0968FC16 for ; Tue, 18 Aug 2009 14:15:00 +0000 (UTC) Received: from unknown (87-194-158-129.bethere.co.uk [87.194.158.129]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA id 999FA851A; Tue, 18 Aug 2009 14:14:59 +0000 (UTC) Date: Tue, 18 Aug 2009 15:14:59 +0100 From: Bruce Cran To: John Baldwin Message-ID: <20090818151459.00004e1c@unknown> In-Reply-To: <200908180830.58904.jhb@freebsd.org> References: <20090818122453.0000301a@unknown> <200908180830.58904.jhb@freebsd.org> X-Mailer: Claws Mail 3.7.1 (GTK+ 2.16.0; i586-pc-mingw32msvc) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: fdc(4) regression: fdc0 fails to probe X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Aug 2009 14:15:00 -0000 On Tue, 18 Aug 2009 08:30:58 -0400 John Baldwin wrote: > On Tuesday 18 August 2009 7:24:53 am Bruce Cran wrote: > > There appears to be a regression between 7.2 and 8.0-BETA2 with > > fdc(4): it used to find and attach fdc0, but now it fails to probe > > fdc0 but appears to initially find a nonexistant fdc1: > > > > fdc0: No FDOUT register! > > fdc0 failed to probe at port 0x3f0 irq 6 drq 2 on isa0 > > > I think fdc0 will work if you remove the fdc0 hints. Removing /boot/device.hints made fdc0 probe again, but /dev/fd0 didn't appear because during boot after the probe it timed out on input/output for fdc0 this time. I'll investigate some more later. -- Bruce Cran