From owner-freebsd-current@FreeBSD.ORG  Thu Apr 10 02:02:17 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 6E82937B401
	for <current@FreeBSD.ORG>; Thu, 10 Apr 2003 02:02:17 -0700 (PDT)
Received: from spider.deepcore.dk
	(cpe.atm2-0-56339.0x50c6aa0a.abnxx2.customer.tele.dk [80.198.170.10])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8E96143F75
	for <current@FreeBSD.ORG>; Thu, 10 Apr 2003 02:02:15 -0700 (PDT)
	(envelope-from sos@spider.deepcore.dk)
Received: (from sos@localhost)
	by spider.deepcore.dk (8.12.8p1/8.12.8) id h3A927sf059653;
	Thu, 10 Apr 2003 11:02:07 +0200 (CEST)
	(envelope-from sos)
From: Soeren Schmidt <sos@spider.deepcore.dk>
Message-Id: <200304100902.h3A927sf059653@spider.deepcore.dk>
In-Reply-To: <BABB6569.455F%diskiller@diskiller.net>
To: Martin Minkus <diskiller@diskiller.net>
Date: Thu, 10 Apr 2003 11:02:07 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL98b (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=ISO-8859-1
cc: current@FreeBSD.ORG
cc: Matthew Lukaszewicz <matt@lukaszewicz.org>
Subject: Re: No DMA?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Apr 2003 09:02:17 -0000

It seems Martin Minkus wrote:

> pci0: <mass storage, ATA> at device 1.1 (no driver attached)

That is the problem, somehow your controller is not identified..
I have no idea why actually, but could you do a pciconf -l and
mail me the result ?
Other than that you could instrument the probe code in ata-pci.c
and ata-chipset.c and see where/if it fails...

-Søren