From owner-freebsd-current@FreeBSD.ORG Tue Jul 27 00:10:11 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 391D116A4CE; Tue, 27 Jul 2004 00:10:11 +0000 (GMT) Received: from ns1.xcllnt.net (209-128-86-226.BAYAREA.NET [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id BCFC743D45; Tue, 27 Jul 2004 00:10:10 +0000 (GMT) (envelope-from marcel@xcllnt.net) Received: from dhcp50.pn.xcllnt.net (dhcp50.pn.xcllnt.net [192.168.4.250]) by ns1.xcllnt.net (8.12.11/8.12.11) with ESMTP id i6R0AAmL058161; Mon, 26 Jul 2004 17:10:10 -0700 (PDT) (envelope-from marcel@piii.pn.xcllnt.net) Received: from dhcp50.pn.xcllnt.net (localhost [127.0.0.1]) i6R0AAfh000696; Mon, 26 Jul 2004 17:10:10 -0700 (PDT) (envelope-from marcel@dhcp50.pn.xcllnt.net) Received: (from marcel@localhost) by dhcp50.pn.xcllnt.net (8.12.11/8.12.11/Submit) id i6R0AAmF000695; Mon, 26 Jul 2004 17:10:10 -0700 (PDT) (envelope-from marcel) Date: Mon, 26 Jul 2004 17:10:10 -0700 From: Marcel Moolenaar To: Nate Lawson Message-ID: <20040727001010.GA670@dhcp50.pn.xcllnt.net> References: <20040726021326.GA23697@cat.robbins.dropbear.id.au> <20040726095929.GA30092@cat.robbins.dropbear.id.au> <410583B3.4000104@root.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <410583B3.4000104@root.org> User-Agent: Mutt/1.4.2.1i cc: current@freebsd.org cc: Tim Robbins Subject: Re: Floppy disk drive no longer detected X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 27 Jul 2004 00:10:11 -0000 On Mon, Jul 26, 2004 at 03:20:35PM -0700, Nate Lawson wrote: > > Ok, below is a patch to address this. There are two things this fixes. > The first, which I think Marcel's laptop had from the dmesg I saw, is that > _FDI is not required so a system may have child devices of FDC that lack an > _FDI method. Yup. That seems to be resolved: fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 However, no fd0. Hence no /dev/fd0. With FDC_DEBUG I get: : [0x3->FDDATA][0xdf->FDDATA][0x2->FDDATA][0x10->FDDATA][FDDATA->0x90] : [fdc0 IDLE] : And that's it... -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net