From owner-freebsd-stable  Mon May 25 19:13:48 1998
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id TAA25936
          for freebsd-stable-outgoing; Mon, 25 May 1998 19:13:48 -0700 (PDT)
          (envelope-from owner-freebsd-stable@FreeBSD.ORG)
Received: from mail.kersur.net (root@mail.kersur.net [199.79.199.3])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA25928
          for <freebsd-stable@FreeBSD.ORG>; Mon, 25 May 1998 19:13:43 -0700 (PDT)
          (envelope-from dswartz@druber.com)
Received: from manticore (manticore.druber.com [207.180.95.108])
	by mail.kersur.net (8.8.8/8.8.8) with SMTP id WAA15723;
	Mon, 25 May 1998 22:13:32 -0400 (EDT)
Message-Id: <3.0.5.32.19980525221330.0092b610@mail.kersur.net>
X-Sender: druber@mail.kersur.net
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32)
Date: Mon, 25 May 1998 22:13:30 -0400
To: Mike Smith <mike@smith.net.au>
From: Dan Swartzendruber <dswartz@druber.com>
Subject: Re: Upgrading from BSDI 2.1 -> FreeBSD 2.2.6 
Cc: "Morgan Davis" <mdavis@cts.com>, freebsd-stable@FreeBSD.ORG
In-Reply-To: <199805252352.QAA14532@antipodes.cdrom.com>
References: <Your message of "Sun, 24 May 1998 23:44:09 PDT."             <000c01bd87a8$84e7ef50$24ae44c6@iopc.cts.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk

At 04:52 PM 5/25/98 -0700, Mike Smith wrote:
>> I inherited the duty of upgrading a working BSDI 2.1 system to FreeBSD
>> 2.2.6, but am having trouble getting sysinstall to come up properly.
First,
>> here's the BSDI 2.1 dmesg output:
>...
>> bha0: warning, interrupts not working, using polling
>
>This is fatal; we require interrupts to work for the Buslogic 
>controller.  Check the controller configuration, and also check the 
>FreeBSD verbose boot probe output (boot with -v).  You can scroll back 
>to see this once sysinstall comes up - hit Scroll Lock and use the 
>cursor keys...
>
>The controller may be faulty, or you may have disabled PCI interrupts 
>for the slot it's in (depending on the system in question).

Check your motherboard also.  I've been burned by a motherboard where
not all of the PCI slots supported busmastering, and saw this same
problem (albeit with Linux, not FreeBSD, but the basic outcome was the
same anyway...)




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message