From owner-freebsd-current Sun Sep 19 23:28: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id EE84514CAC for ; Sun, 19 Sep 1999 23:27:58 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA01638; Mon, 20 Sep 1999 08:27:55 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199909200627.IAA01638@freebsd.dk> Subject: Re: ata drivers In-Reply-To: from Gary Hampton at "Sep 19, 1999 11:56:16 pm" To: garyh@mail.win.bright.net (Gary Hampton) Date: Mon, 20 Sep 1999 08:27:55 +0200 (CEST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Gary Hampton wrote: > I have been trying to get the ata drivers to work on my system for a > a while now but can't seem to mount my cdrom drives. This is what I get on > boot up: > atapi: DMA transfer mode set > acd0: CDROM drive at ata0 as master I'll bet that your CDROM doesn't do DMA right. I was optimistic when I added the ATAPI DMA code, but it seems LOTS, and I mean LOTS of ATAPI devices doesn't work in DMA mode even if they tell you so :( You can disable DMA on atapi devices by commecnting out the code block with the ata_dmainit call in it. I have a new version of the ATA driver very close to being committed, and it might solve some of this. The real solution might be to have a positive list of ATAPI devices known to work in DMA mode. -Soren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message