From owner-freebsd-current@FreeBSD.ORG Wed Apr 30 10:08:09 2003 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 90C1E37B401 for ; Wed, 30 Apr 2003 10:08:09 -0700 (PDT) Received: from c001.snv.cp.net (h008.c001.snv.cp.net [209.228.32.122]) by mx1.FreeBSD.org (Postfix) with SMTP id DCEAD43F3F for ; Wed, 30 Apr 2003 10:08:08 -0700 (PDT) (envelope-from jeff@walters.name) Received: (cpmta 24747 invoked from network); 30 Apr 2003 10:08:07 -0700 Received: from 24.216.194.242 (HELO 10.0.1.51) by smtp.register-admin.com (209.228.32.122) with SMTP; 30 Apr 2003 10:08:07 -0700 X-Sent: 30 Apr 2003 17:08:07 GMT From: Jeff Walters To: current@freebsd.org Date: Wed, 30 Apr 2003 13:08:06 -0400 User-Agent: KMail/1.5.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200304301308.06597.jeff@walters.name> Subject: ACPI vs. /dev/fd0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jeff@walters.name List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Apr 2003 17:08:09 -0000 I cannot load the ACPI module in 5.0-current and get a working floppy drive simultaneously. With ACPI loaded the dmesg | grep fdc0 is: fdc0: cmd 3 failed at out byte 1 of 3 fdc0: cmd 3 failed at out byte 1 of 3 fdc0: cannot reserve I/O port range (6 ports) With the ACPI module disabled in /boot/loader.conf, I get: fdc0: at port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 I have the latest BIOS firmware, and I've been told by my M/B vendor's support organization: "ASRock motherboards are all ACPI complaint" and "All our Produsts are fully support and fully tested with Windows 98SE/ME/2000/XP. We won't provide any support to Linux or other OS like FreeBSD." I replied to ask them "why not?", however what can the issue be where they claim compliance on all versions of Windows yet FreeBSD doesn't work? Is this a case where Windows has it's own "standard" that no one else meets, or is FreeBSD support still incomplete? I not sure if this is relevant, but here's a chunk of acpidump output related to the device FDC0: Device(FDC0) { Name(_HID, 0x0007d041) Method(_STA) { If(FDST) { Return(GSTA(LDFD)) } Return(0x0) } Method(_DIS) { DDIS(LDFD) } Method(_CRS) { Return(FCRS) } Method(_PRS) { Return(FPRS) } Method(_SRS, 1) { DENB(LDFD) } } Thanks, Jeff Walters