From owner-freebsd-current@FreeBSD.ORG Mon Aug 23 11:58:37 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 AD83116A4CE for ; Mon, 23 Aug 2004 11:58:37 +0000 (GMT) Received: from encontacto.net (dsl-200-95-35-64.prod-infinitum.com.mx [200.95.35.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id 08DB443D39 for ; Mon, 23 Aug 2004 11:58:37 +0000 (GMT) (envelope-from eculp@encontacto.net) Received: from localhost (localhost [127.0.0.1]) (uid 80) by encontacto.net with local; Mon, 23 Aug 2004 06:58:36 -0500 Received: from dsl-200-95-35-64.prod-infinitum.com.mx (dsl-200-95-35-64.prod-infinitum.com.mx [200.95.35.64]) by mail.encontacto.net (Horde) with HTTP for ; Mon, 23 Aug 2004 06:58:36 -0500 Message-ID: <20040823065836.4ows4o8ck8o8k0cw@mail.encontacto.net> Date: Mon, 23 Aug 2004 06:58:36 -0500 From: Edwin Culp To: Doug White References: <20040822062942.jdgc48ksoo8c8kk0@mail.encontacto.net> <20040822194550.L94593@carver.gumbysoft.com> In-Reply-To: <20040822194550.L94593@carver.gumbysoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) 4.0-cvs X-Originating-IP: 200.95.35.64 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 11:58:37 -0000 Quoting Doug White : > 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'm not surprised. :) They're cheap and seem to work ok in every other way so there are probably more out there than a person might think. > I think Nate was working on a hack to glue > the ranges together to work around this. Is there anything I can do on this end. (Change configuration, test patches, etc?) Thanks, Doug, for confirming my suspicions. ed > > -- > Doug White | FreeBSD: The Power to Serve > dwhite@gumbysoft.com | www.FreeBSD.org >