From owner-freebsd-current@FreeBSD.ORG Thu Jun 3 12:41:44 2004 Return-Path: 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 7FEEB16A4CE for ; Thu, 3 Jun 2004 12:41:44 -0700 (PDT) Received: from lakermmtao03.cox.net (lakermmtao03.cox.net [68.230.240.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0248143D48 for ; Thu, 3 Jun 2004 12:41:44 -0700 (PDT) (envelope-from conrads@cox.net) Received: from ip68-11-70-23.no.no.cox.net ([68.11.70.23]) by lakermmtao03.cox.netESMTP <20040603194143.WIBS21849.lakermmtao03.cox.net@ip68-11-70-23.no.no.cox.net>; Thu, 3 Jun 2004 15:41:43 -0400 Received: from ip68-11-70-23.no.no.cox.net (localhost.no.no.cox.net [127.0.0.1])i53Jfdxj000915; Thu, 3 Jun 2004 14:41:39 -0500 (CDT) (envelope-from conrads@ip68-11-70-23.no.no.cox.net) Received: (from conrads@localhost)i53JfUFf000914; Thu, 3 Jun 2004 14:41:30 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Thu, 03 Jun 2004 14:41:30 -0500 (CDT) From: Conrad Sabatier To: freebsd-current@freebsd.org cc: =?ISO-8859-1?Q?S=F8ren_Schmidt?= Subject: Another followup on atapi issues (progress!) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: conrads@cox.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jun 2004 19:41:44 -0000 Well, I'm pleased to report that things are looking better today re: my atapi problems. I still have a broken CD burner on acd1, it looks like, but at least things are looking more normal now at boot time . Both atapi devices are being properly recognized once again and assigned to their correct positions, and the acd0 device is functioning properly (which it wasn't for a while). It seems that part of the problem was that I was trying to force DMA on in /boot/loader.conf. After upgrading the world today, I was still encountering pretty much the same problems as before, until I changed hw.ata.atapi_dma to 0. Then the system finally came up normally. I do intend to replace the broken drive Real Soon Now. After I do, I'll post another followup report. Thanks for your interest, Soren; I do appreciate it. Sorry for not following up sooner; I got sidetracked with a few other things the last couple of days. :-) -- Conrad Sabatier - "In Unix veritas"