From owner-freebsd-current Mon Dec 14 23:58:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA28059 for freebsd-current-outgoing; Mon, 14 Dec 1998 23:58:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ayukawa.aus.org (ayukawa.aus.org [199.166.246.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA28054 for ; Mon, 14 Dec 1998 23:58:21 -0800 (PST) (envelope-from lh@aus.org) Received: from bsd.aus.org (lh@bsd.aus.org [199.166.246.189]) by ayukawa.aus.org (8.8.7/8.7.3) with ESMTP id CAA04078 for ; Tue, 15 Dec 1998 02:39:45 -0500 (EST) Message-Id: <199812150739.CAA04078@ayukawa.aus.org> X-Mailer: XFMail 1.3-beta-042198 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3675F292.31DFF4F5@whistle.com> Date: Tue, 15 Dec 1998 02:58:14 -0500 (EST) Reply-To: lh@aus.org From: Luke To: current@FreeBSD.ORG Subject: Re: ide_pci.c Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I have the same problem, with the 2nd IDE not showing up, so here :) >> I have an Acer Aladdin V chipset, the IDE chip is a 1543C. It also seems to >> have a bizarre UDMA problem (at certain clocksettings , DMA for IDE breaks >> ). I have a list of the PCI clocks , if that would help. >> > > > Can you define "breaks" ? > At many cpu clock settings, with DMA turned on, booting is fine, but as soon as the device detection part is done, and rc I guess is being run, theres a flood of DMA errors like (not 100% on this) wd0: DMA failure DMA status 5 I actually started trying to figure out ide_pci.c but its beyond my ability. I think it is because the PCI clock is different for every cpu clock setting , I have 2 mbs with this chipset, one only works set at 66mhz , one at 75mhz. I could and would be willing to mess with this on my machine, and I have a list of clock settings per cpu settings for this board. The only reason its annoying is because I stuck 100mhz sdram in here and have to have it running at 66mhz. I dont know if having it set to 100mhz would make any difference, its just the fact that I cant do it that bugs me :) --- E-Mail: Luke Sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message