From owner-freebsd-current@FreeBSD.ORG Mon Aug 23 03:31:08 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 3041E16A4CE for ; Mon, 23 Aug 2004 03:31:08 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA4F943D53 for ; Mon, 23 Aug 2004 03:31:07 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.11/8.12.11) with ESMTP id i7N3Ut9m058730; Sun, 22 Aug 2004 21:30:55 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sun, 22 Aug 2004 21:31:12 -0600 (MDT) Message-Id: <20040822.213112.116247523.imp@bsdimp.com> To: dwhite@gumbysoft.com From: "M. Warner Losh" In-Reply-To: <20040822194550.L94593@carver.gumbysoft.com> References: <20040822062942.jdgc48ksoo8c8kk0@mail.encontacto.net> <20040822194550.L94593@carver.gumbysoft.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: Re: Problems with fdc0 w/Athlon and via chipset. Floppy isn't recognized. 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: Mon, 23 Aug 2004 03:31:08 -0000 In message: <20040822194550.L94593@carver.gumbysoft.com> Doug White writes: : On Sun, 22 Aug 2004, Edwin Culp wrote: : : > I've been seeing this problem for some time. I've seen other : > folks comment about it also. I'm wondering if it is operator : > error or if there really is a problem. : > : > fdc0: port : > 0x3f7,0x3f4-0x3f5,0x3f2-0x3f3 irq 6 drq 2 on acpi0 : > fdc0: I/O to control range incorrect : > device_attach: fdc0 attach returned 6 : > : > I see this on all my athlon/via machines. I'm running current as : > yesterday. : : Your BIOS writer is on crack. I think Nate was working on a hack to glue : the ranges together to work around this. Actually, Nate's hack doesn't glue things together like this. I have a preliminary patch ready for this problem before phk committed the rewrite of fdc, which I need to merge into the current fdc. Warner