From owner-freebsd-questions@FreeBSD.ORG Wed Sep 17 08:39:38 2003 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 65F0416A4B3 for ; Wed, 17 Sep 2003 08:39:38 -0700 (PDT) Received: from remt21.cluster1.charter.net (remt21.cluster1.charter.net [209.225.8.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 756DE43FBD for ; Wed, 17 Sep 2003 08:39:37 -0700 (PDT) (envelope-from chowse@charter.net) Received: from [66.168.145.25] (HELO moe) by remt21.cluster1.charter.net (CommuniGate Pro SMTP 4.0.6) with ESMTP id 160883847; Wed, 17 Sep 2003 11:39:36 -0400 From: "Charles Howse" To: "'Ekrem'" Date: Wed, 17 Sep 2003 10:39:27 -0500 Message-ID: <003801c37d31$e12b0bb0$04fea8c0@moe> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 In-Reply-To: <003701c37d2f$6e266210$04fea8c0@moe> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal cc: 'freebsd-questions' Subject: RE: Boot timeout? - SOLVED X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Sep 2003 15:39:38 -0000 > > On Wed, 2003-09-17 at 05:47, Charles Howse wrote: > > > > > Now the system hangs for about 20 seconds at the BIOS drive=20 > > > > detection, > > > > > and at the FBSD atapi controller detection. > > > >=20 > > > > Are you using ATAPICAM? If so, it's probably the SCSI settling. > > > > That's adjustable in the kernel configuration. > > >=20 > > > The string 'atapicam' does not appear in my > > > /usr/src/sys/i386/conf/CUSTOM customized kernel config=20 > > file. Is that > > > what you meant? I did find that string in LINT, but I'm=20 > > not using it. > > >=20 > > > I may have misled you in my post. What I should have said is, the > > > system hangs for about 20 seconds at the BIOS drive=20 > > detection, and then > > > there is another 20 second delay when FBSD is detecting=20 > > devices, *after* > > > it displays the line about finding the atapi controller. =20 > > It displays > > > that line concerning the atapi controller, issues 2 cr/lf=20 > > and pauses for > > > that 20 seconds. It then continues to load without error,=20 > > all devices > > > are detected properly and I can read and write to them. > > >=20 > > > I really think this delay may be more related to hardware=20 > > than software. > > > I just booted the system to an MS-DOS diskette, and the=20 > > delay is still > > > there. I have no special settings in BIOS. > > >=20 > > > BTW: I've also posted this to alt.comp.hardware. No joy yet. > >=20 > > Hi, > >=20 > > I also think the delay is hardware related. The most common=20 > > reason would > > be if a drive was jumpered incorrectly, eg. if the drive is=20 > > set as slave > > but there is no master drive, or the master drive is set with slave > > drive present when there is no slave drive. > >=20 > > So the BIOS waits for a response from an unavailable drive or=20 > > until the > > time-out period is reached. > >=20 > > In your original post you mentioned the 2Gb was set as=20 > > master, then you > > connected it as secondary-slave. You would need to change jumper > > settings to reflect this. >=20 > Yes, I changed the jumper. > I will check the Western Digital (I HATE them) web site for up-to-date > info on jumper settings for that drive, and try different settings > myself, but I think I have it correct to begin with. OK, this was another 'dumb-ass' issue on my part. After checking the WDC web site, I realized that since the WDC drive was the *only* drive on the primary channel, it should *NOT* be jumpered at all. I had it jumpered for 'dual master' Thanks to all who responded.