From owner-freebsd-alpha Wed Jun 28 19:28:41 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id E292537BAD1 for ; Wed, 28 Jun 2000 19:28:37 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from gale.cs.duke.edu (gale.cs.duke.edu [152.3.145.6]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id WAA02345; Wed, 28 Jun 2000 22:28:36 -0400 (EDT) Received: (gallatin@localhost) by gale.cs.duke.edu (8.8.4/8.6.9) id WAA11582; Wed, 28 Jun 2000 22:28:35 -0400 (EDT) Date: Wed, 28 Jun 2000 22:28:35 -0400 (EDT) Message-Id: <200006290228.WAA11582@gale.cs.duke.edu> From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Peter Wemm Cc: alpha@FreeBSD.ORG Subject: Re: fdc driver problem on the Alpha (PC164SX) - anyone else? In-Reply-To: <20000629002616.BDAA41CDF@overcee.netplex.com.au> References: <20000629002616.BDAA41CDF@overcee.netplex.com.au> X-Mailer: VM 6.32 under 19.15 XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Peter Wemm writes: > @@ -105,6 +106,7 @@ > * Reset the DMA hardware. > */ > outb(DMA1_RESET, 0); > + outb((IO_DMA1 + 1*14), 0); > outb(DMA2_RESET, 0); > isa_dmacascade(4); > > I'm wondering if this could be related somehow. The driver seems to be > hanging in a way that might be consistant with a dma initialization > problem. Gack! Pass me the pointy hat. That never should have snuck in. I was desparately trying to wake up the floppy drive on my up1000 & that was left from a failed attempt. It didn't seem to affect my xp1000 or my up1000 which is why I forgot to remove it before committing. At any rate, I just removed it. Please let me know if that fixes your problem. Sorry, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message