From owner-freebsd-hardware Thu Sep 23 19:14:37 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.rdc1.az.home.com (ha1.rdc1.az.home.com [24.1.240.66]) by hub.freebsd.org (Postfix) with ESMTP id C8D3B14E97 for ; Thu, 23 Sep 1999 19:14:35 -0700 (PDT) (envelope-from elgreen@iname.com) Received: from ehome.local.net ([24.9.114.169]) by mail.rdc1.az.home.com (InterMail v4.01.01.00 201-229-111) with SMTP id <19990924021401.FCWM27294.mail.rdc1.az.home.com@ehome.local.net>; Thu, 23 Sep 1999 19:14:01 -0700 From: Eric Lee Green Organization: Myself @ Home To: Dann Lunsford , Lance Costanzo , hardware@FreeBSD.ORG Subject: Re: Secondary IDE-PCI interface invisible Date: Thu, 23 Sep 1999 19:10:25 -0700 X-Mailer: KMail [version 1.0.21] Content-Type: text/plain References: <37E82A40.95DF5966@greycat.com> MIME-Version: 1.0 Message-Id: <99092319133302.00682@ehome.local.net> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 21 Sep 1999, Dann Lunsford wrote: > Good idea. Bad news, though: DOS sees the drive fine. > FreeBSD can't even find the controller, let alone the drive. > Something tells me this one is one for the books... FreeBSD is detecting the controller. The FreeBSD 3.x IDE driver has a bug in it where, if it cannot properly handshake with a drive connected to the controller (because it is not abiding strictly by the EIDE standard), it reports that it cannot detect the controller. I verified this during my own EIDE problem by putting debugging statements all over the place, starting with where the error message was printed and working backwards. What I found was that the controller was being detected just fine, but that the EIDE initialization routine was getting confused when it sent out an EIDE 'init' command and got back what it considered to be gibberish. -- Eric Lee Green http://members.tripod.com/e_l_green mail: e_l_green@hotmail.com There Is No Conspiracy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message