From owner-freebsd-current Sat Nov 3 10:37:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from m-net.arbornet.org (m-net.arbornet.org [209.142.209.161]) by hub.freebsd.org (Postfix) with ESMTP id E1DF337B416 for ; Sat, 3 Nov 2001 10:37:49 -0800 (PST) Received: (from ceesaxp@localhost) by m-net.arbornet.org (8.11.4/8.11.2) id fA3ILAh34857; Sat, 3 Nov 2001 13:21:10 -0500 (EST) (envelope-from ceesaxp) Date: Sat, 3 Nov 2001 13:21:10 -0500 (EST) From: Andrei Popov Message-Id: <200111031821.fA3ILAh34857@m-net.arbornet.org> To: current@freebsd.org Subject: Re: ouch -- the second controller on Promise-66 is not detected! Cc: nnd@mail.nsk.ru Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Oct 31, 2001 at 08:54:35AM +0600, Nickolay Dudorov wrote: > With the following patch I can now use all > the channels on the HPT366 controller in my ABIT's BP6 mobo. Hmmm... Just a thing I was having troyuble with ... Are you saying that you can now use DMA, not PIO mode with it? I tried your patch, but I still have the same problem with BP6/HPT366: [dmesg output] Nov 3 19:07:53 vogon /boot/kernel/kernel: ata2: at 0xd000 on atapci1 Nov 3 19:07:54 vogon /boot/kernel/kernel: ad4: 19623MB [39870 /16/63] at ata2-master UDMA66 ... Nov 3 19:07:54 vogon /boot/kernel/kernel: ad4: READ command timeout tag=0 serv= 0 - resetting Nov 3 19:07:54 vogon /boot/kernel/kernel: ata2: resetting devices .. done However, if I have something like: hw.ata.ata_dma=0 in /boot/loader.conf everything is fine (except that harddrive is used in PIO mode instead of DMA). Maybe it's my IBM drive that is fooling around?... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message