From owner-freebsd-stable Sat Apr 15 0:50:33 2000 Delivered-To: freebsd-stable@freebsd.org Received: from isabase.philol.msu.ru (isabase.philol.msu.ru [195.208.217.73]) by hub.freebsd.org (Postfix) with ESMTP id DC3BA37B8AE for ; Sat, 15 Apr 2000 00:50:28 -0700 (PDT) (envelope-from grg@isabase.philol.msu.ru) Received: (from grg@localhost) by isabase.philol.msu.ru (8.9.3/8.9.2) id LAA08210; Sat, 15 Apr 2000 11:50:14 +0400 (MSD) (envelope-from grg) Date: Sat, 15 Apr 2000 11:50:14 +0400 From: Grigoriy Strokin To: fingers Cc: freebsd-stable@FreeBSD.ORG Subject: Re: problem with ata/ad0 in 4.0 Message-ID: <20000415115014.A993@isabase.philol.msu.ru> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from fingers@fingers.co.za on Fri, Apr 14, 2000 at 03:16:57PM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 14, 2000 at 03:16:57PM +0200, fingers wrote: > Hi > > I decided to fresh-install a machine that's currently running 3.4. > > I'm having the following problem though: > > I can boot, and it loads both disks with kern and mfsroot images (but > doesn't pick up my hard drive (3 gig IDE Quantum fireball)). It loads > sysinstall, and if I press ALT F2, I see: > > ad0 - READ command timeout > ata0 - resetting devices - done > > The read timeout I take it is the kernel not being able to read my hard > disk. There's only 1 drive in the machine, no cdrom or anything else > installed. > > Why would it be that it's not seing it? The drive and controller are > working perfectly, as it's got a working installation of bsd on it atm. > > I checked release notes and couldn't find any mention of problems with > this drive. Are there known problems with the controllers under 4.0? This is sort of well-known problem (to the members of the list :>), which is not in any way documented, though. Also, Kris Kennaway wrote: " Perhaps you should drop back to 3.4 until the bug is fixed. These things " aren't easy to spot and fix.. There is a work-around if you are installing FreeBSD 4.0 stable onto an existing system: add /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio to the beginning (just after #!/bin/sh) of /etc/rc and also /root/.login (for csh) and /root/profile (for sh). I would think that it is somehow possible to do the trick when booting from the installation disk, but don't know how. -- === Grigoriy Strokin, Lomonosov University (MGU), Moscow === === contact info: http://isabase.philol.msu.ru/~grg/ === To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message