From owner-freebsd-stable Tue Mar 13 6:21: 9 2001 Delivered-To: freebsd-stable@freebsd.org Received: from c353425-b.htfds1.ct.home.com (c353425-b.htfds1.ct.home.com [24.2.169.205]) by hub.freebsd.org (Postfix) with ESMTP id BF86437B71D for ; Tue, 13 Mar 2001 06:21:06 -0800 (PST) (envelope-from tsikora@home.com) Received: from home.com (localhost.htfds1.ct.home.com [127.0.0.1]) by c353425-b.htfds1.ct.home.com (8.11.3/8.11.2) with ESMTP id f2DEFYd00396 for ; Tue, 13 Mar 2001 09:15:34 -0500 (EST) (envelope-from tsikora@home.com) Message-ID: <3AAE2B86.4C1354EF@home.com> Date: Tue, 13 Mar 2001 09:15:34 -0500 From: "T.Sikora" Reply-To: tsikora@powerusersbbs.com Organization: Jtl Development Group X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "freebsd-stable@FreeBSD.ORG" Subject: cdrom mount errors Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Beta 4.3 I'm using an EPoX KTA2 with VIA KT133 chipset. I have the cdrom installed as primary slave with a Maxtor hd as master. on the primary ide. It takes a long long time .. gives the messages then finally mounts. I have a second hd on the secondary ide as master. Putting the hardrives on one cable and the cd on another? Would this cure it? Shouldn't matter I would think. Mar 13 09:02:28 c353425-b /kernel: ata0-master: DMA limited to UDMA33, non-ATA66 compliant cable Mar 13 09:02:28 c353425-b /kernel: ad0: 14655MB [29777/16/63] at ata0-master UDMA33 Mar 13 09:02:28 c353425-b /kernel: ad2: 14655MB [29777/16/63] at ata1-master UDMA66 Mar 13 09:02:28 c353425-b /kernel: acd0: CDROM at ata0-slave using UDMA33 Mar 13 09:02:28 c353425-b /kernel: Mounting root from ufs:/dev/ad0s2a Mar 13 09:02:28 c353425-b /kernel: dc0: failed to force tx and rx to idle state Mar 13 09:02:28 c353425-b last message repeated 2 times Mar 13 09:03:30 c353425-b login: ROOT LOGIN (root) ON ttyv0 Mar 13 09:05:00 c353425-b /kernel: acd0: READ_BIG command timeout - resetting Mar 13 09:05:59 c353425-b /kernel: ata0: resetting devices .. ata0-master: DMA limited to UDMA33, non-ATA66 compliant cable Mar 13 09:06:34 c353425-b /kernel: done Mar 13 09:06:34 c353425-b /kernel: acd0: READ_BIG command timeout - resetting Mar 13 09:06:34 c353425-b /kernel: ata0: resetting devices .. ata0-master: DMA limited to UDMA33, non-ATA66 compliant cable Mar 13 09:06:34 c353425-b /kernel: done Mar 13 09:06:34 c353425-b /kernel: acd0: READ_BIG command timeout - resetting Mar 13 09:06:34 c353425-b /kernel: ata0: resetting devices .. ata0-master: DMA limited to UDMA33, non-ATA66 compliant cable Mar 13 09:06:34 c353425-b /kernel: done Mar 13 09:06:34 c353425-b /kernel: acd0: READ_BIG command timeout - resetting Mar 13 09:06:34 c353425-b /kernel: ata0-slave: timeout waiting to give command=ef s=d0 e=00 Mar 13 09:06:34 c353425-b /kernel: acd0: trying fallback to PIO mode Mar 13 09:06:34 c353425-b /kernel: ata0: resetting devices .. ata0-master: DMA limited to UDMA33, non-ATA66 compliant cable Mar 13 09:06:34 c353425-b /kernel: done Mar 13 09:06:34 c353425-b /kernel: cd9660: Joliet Extension (Level 3) -- Ted Sikora Jtl Development Group tsikora@powerusersbbs.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message