From owner-freebsd-questions@FreeBSD.ORG Thu Apr 7 15:15:59 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6745A16A4CE for ; Thu, 7 Apr 2005 15:15:59 +0000 (GMT) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8465B43D53 for ; Thu, 7 Apr 2005 15:15:58 +0000 (GMT) (envelope-from mike.daemon@gmail.com) Received: by zproxy.gmail.com with SMTP id 40so318600nzk for ; Thu, 07 Apr 2005 08:15:57 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=YibsasKhJ6iOlcfgBXUlbOgM0vAZiHZSrLeBIkRVzhJmPxbTeKszveie+q2gTrFOuWYPQr0t37ohcPjeXMYclPvtMod9Ie73Vza/UXVPfjLtlh3H6fA3ZZ62Dsoo5qegOiVI2FKNEfpOsmQzAPUdWjClnjz40ZkTcLylqVtK/mw= Received: by 10.36.96.8 with SMTP id t8mr61938nzb; Thu, 07 Apr 2005 08:15:57 -0700 (PDT) Received: by 10.36.39.7 with HTTP; Thu, 7 Apr 2005 08:15:57 -0700 (PDT) Message-ID: <3db6da6d0504070815624c7a03@mail.gmail.com> Date: Thu, 7 Apr 2005 17:15:57 +0200 From: Mike Daemon To: FreeBSD Questions In-Reply-To: <3db6da6d05032713476ac966d4@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable References: <3db6da6d05032713157dac8a14@mail.gmail.com> <006701c53314$834b7490$4300a8c0@home.lan> <3db6da6d05032713476ac966d4@mail.gmail.com> Subject: Re: more problems with 5.3 and "TIMEOUT - WRITE_DMA" [SOLOTION] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Mike Daemon List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Apr 2005 15:15:59 -0000 On Mar 27, 2005 11:47 PM, Mike Daemon wrote: > On Sun, 27 Mar 2005 13:32:43 -0800, Thomas Foster w= rote: > > I had this same issue >=20 > I=B4ll have seen some more posts on the list with about the same problem > therefore, I hope some bright one will take alook at the code.. and > post something smart.. I=B4m very much stuck, hopeing any new snapshot > will work.. >=20 > on an older AMD Nforce board. 5.2.1 seemed to install > > and run.. but moving to 5.3 gave me issues. I tinkered with the DMA > > settings in the BIOS.. to no avail. The Geometry seemed to be off on t= he > > drive I noticed (IBM deskstar) when I newfs'd it.. so I changed out dri= ves.. > > but never got it working.. I eventually just dropped Gentoo on it. > > > > What chipset, drive controller hard drive are you using on this system? >=20 > http://www.freebsd.org/cgi/man.cgi?query=3Data&sektion=3D4&manpath=3DFree= BSD+5.3-RELEASE >=20 > I=B4ll notised that my idecontroller IS supported by the ata-driver, > witch makes it even stranger.. (I think I will check on my cabling > once more, even if it=B4s a newly installed _rounded_ 32 pin cable..) >=20 > My atacontroller: SiS 5513 > My HDD: Seagate 200 GB >=20 >=20 > > > > T > > > > ----- Original Message ----- > > From: "Mike Daemon" > > To: "FreeBSD Questions" > > Sent: Sunday, March 27, 2005 1:15 PM > > Subject: more problems with 5.3 and "TIMEOUT - WRITE_DMA" > > > > I got this annoying problem when upgradeing to 5.3, the miniinst iso > > blurps out "TIMEOUT - WRITE_DMA" when it starts writing base to my > > disk. And when I tried to first install 5.2.1 and upgrade (cvsup, make > > buildworld etc.. ) to 5.3 that way everything seems fine until I > > reboot to single-user-mode, as soon as Im starting to write anything > > to the disk it=B4s blurping out those errors.. I have diagnosticed my > > disk, checked my cabling and fixed my PSU (installed a brand new one). > > No difference. I noticed that my ide-controller was supported in 4.11, > > but not? in 5.3, is that realy true? seems very strange... > > > > Sence I duel boot with Wintendo/Lunix and don=B4t see this problem with > > those oses I=B4m very confused of what to do next.. > > > > I=B4ll tried some snapshots to but no luck... > > > > / Mike > > > > ps My dmesg goes in the attachment, in hope for a patch/solution to > > this problem. ds > > > > -----------------------------------------------------------------------= --------- > > > > > _______________________________________________ > > > freebsd-questions@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > > To unsubscribe, send any mail to > > > "freebsd-questions-unsubscribe@freebsd.org" > > > > > I (with a little help from a good friend ) figured out an solution to the problem, in switching my brand new ata133 ide-cable to an "old school" ata33 ide-cable FreeBSD sets my drives to UDMA3 and boots up alright.. key commands here: atacontrol list and atacontrol mode ( my buddy had come across some message telling about how SiS had created an new "SiS 5513" chipset with the same tag.. unfortunal he didn't remember where that message were. But it would make sense why FreeBSD tryies to use UDMA5 on my UDMA3 only atachipset.. )