Date: Sat, 3 Nov 2001 13:21:10 -0500 (EST) From: Andrei Popov <ceesaxp@m-net.arbornet.org> To: current@freebsd.org Cc: nnd@mail.nsk.ru Subject: Re: ouch -- the second controller on Promise-66 is not detected! Message-ID: <200111031821.fA3ILAh34857@m-net.arbornet.org>
next in thread | raw e-mail | index | archive | help
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 <IBM-DTLA-307020> [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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200111031821.fA3ILAh34857>