Date: Tue, 14 Dec 1999 07:15:36 -0500 (EST) From: "Christopher J. Michaels" <cjm2@weeble.DynDns.ORG> To: Strange Alex <strange@unicon.ru> Cc: questions@FreeBSD.org Subject: Re: UDMA Message-ID: <Pine.BSF.4.10.9912140713080.3301-100000@cartman.weeble.DynDNS.ORG> In-Reply-To: <8620.991214@unicon.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Yes I did get it solved. It was a compatability issue with the motherboard. What was happening was that the BIOS was recognizing the UDMA/66 capability of the harddrives, even though the chipset is only capable of UDMA/33. I belive when FreeBSD was requesting a DMA transfer the system was trying to use UDMA/66 and failing.[ A BIOS update that limits to UDMA/33 resolved this problem for me. -Chris On Tue, 14 Dec 1999, Strange Alex wrote: > Hello ChrisMic, > > > wd0: UDMA/66 capable 10.2GB Western Digital Harddrive > > wd1: UDMA/66 capable 20.2GB IBM Deskstar. > > > The flags on the controller is 0xa0ffa0ff. > > > When I boot the system with UDMA mode enabled in the BIOS I get the > > following 2 error messages. > > > wd0: reverting to PIO mode reading fsbn 0 (status 51<rdy,seekdone,err> error > > 84<badblk,abort>) > > wd1: reverting to PIO mode reading fsbn 0 (status 51<rdy,seekdone,err> error > > 84<badblk,abort>) > > Did you solve this problem ??? > > > Regards, Aleksey Rusanov > Unicon+ Ltd, Novosibirsk > Unix network administrator > Phones: +7 3832 23-94-06 > +7 3832 10-00-50 > Fax: +7 3832 23-94-06 > ICQ UIN: 8397628 > URL: http://www.unicon.ru/ > http://www.H-ck.ru/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9912140713080.3301-100000>