From owner-freebsd-current Wed Mar 27 01:36:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA11388 for current-outgoing; Wed, 27 Mar 1996 01:36:30 -0800 (PST) Received: from cyberport.com (root@puma.cyberport.com [204.134.75.6]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id BAA11367 for ; Wed, 27 Mar 1996 01:36:21 -0800 (PST) Received: from hippo.cyberport.com (kevin@hippo.cyberport.com [204.134.75.2]) by cyberport.com (8.7.5/8.7.3) with SMTP id CAA05594 for ; Wed, 27 Mar 1996 02:36:19 -0700 (MST) Date: Wed, 27 Mar 1996 02:36:18 -0700 (MST) From: Kevin Rosenberg To: freebsd-current@freebsd.org Subject: Hang on "changing root device to sd0" Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I just upgraded from 2.1-RELEASE to current and I ran into a problem. The kernel compiles fine, but the boot process hangs with "changing root device to sd0". I've read the handbook and have disabled everything that probes 0x300 except for ep0. I have a buslogic 946C with 4 SCSI disks. The disks are all found fine during booting, but I get the messages "bt: unit number (1) too high" "bt0: not found" Later, I get the hang mentioned above. I did change /sys/compile/LOCAL/bt.h to set NBT equal to 2. Then I no longer get the "bt: unit number (1) too high" message. After bt0 drives are found, the boot process "finds" bt1 and lists it's IO port, irq, and drives as exactly the same as bt0. Other Hardware 3COM 509B Intel Neptune MB with P90/64MB I'd be grateful if someone had some suggestions! TIA. ----------------------------------------------------------------------- Kevin Rosenberg | The Four Corner's Finest Internet Access System Administrator | kevin@cyberport.com CyberPort Station | http://www.cyberport.com