From owner-freebsd-stable Mon May 25 17:58:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA14523 for freebsd-stable-outgoing; Mon, 25 May 1998 17:58:19 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles201.castles.com [208.214.165.201]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA14342 for ; Mon, 25 May 1998 17:56:17 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id QAA14532; Mon, 25 May 1998 16:52:12 -0700 (PDT) Message-Id: <199805252352.QAA14532@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Morgan Davis" cc: freebsd-stable@FreeBSD.ORG Subject: Re: Upgrading from BSDI 2.1 -> FreeBSD 2.2.6 In-reply-to: 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 Date: Mon, 25 May 1998 16:52:11 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > 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). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message