From owner-freebsd-stable Sun Apr 23 14: 6:10 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id 8F0A337B9AB for ; Sun, 23 Apr 2000 14:06:06 -0700 (PDT) (envelope-from dgilbert@office.tor.velocet.net) Received: from office.tor.velocet.net (trooper.velocet.net [204.138.57.194]) by sabre.velocet.net (Postfix) with ESMTP id D5D3013807E for ; Sun, 23 Apr 2000 17:06:02 -0400 (EDT) Received: (from dgilbert@localhost) by office.tor.velocet.net (8.9.3/8.9.3) id RAA04060; Sun, 23 Apr 2000 17:06:02 -0400 (EDT) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14595.26042.23891.386879@trooper.velocet.net> Date: Sun, 23 Apr 2000 17:06:02 -0400 (EDT) To: stable@freebsd.org Subject: ATA datapoint. X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just as a datapoint, because I see people recomending sysctl -w hw.atamodes=pio,pio,pio,pio, I have a configuration which resists anything being read or written from/to the primary master disk. For the time being, I have put wdc back in my kernel, and this is what it says: wdc0 at port 0x1f0-0x1f7 irq 14 drq 0 flags 0x80ff80ff on isa0 wdc0: unit 0 (wd0): , 32-bit, multi-block-16 wd0: 2441MB (4999680 sectors), 4960 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): , 32-bit, multi-block-16 wd1: 6187MB (12672450 sectors), 13410 cyls, 15 heads, 63 S/T, 512 B/S wdc0: driver is using old-style compatability shims isa_compat: didn't get drq for wdc wdc1 at port 0x170-0x177 irq 15 drq 0 flags 0x80ff80ff on isa0 isa_compat: didn't get drq for wdc wdc1: unit 0 (wd2): , 32-bit, multi-block-16 wd2: 6208MB (12715920 sectors), 13456 cyls, 15 heads, 63 S/T, 512 B/S wdc1: driver is using old-style compatability shims Now... the Fujitsu 3064 is a fairly common drive (I know there's 5 or six of them kicking around our small shop) and the controller is on the motherboard of a fairly plain K6-2 motherboard. When booting with the ata driver, it spits out 'ad0: READ command timeout - resetting' multiple times, but never spits out the done message. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message