From owner-freebsd-stable Tue Jun 13 8:40:36 2000 Delivered-To: freebsd-stable@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id 9BA2637B552 for ; Tue, 13 Jun 2000 08:40:33 -0700 (PDT) (envelope-from larse@ISI.EDU) Received: from [128.9.176.137] (ras37.isi.edu [128.9.176.137]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id IAA20398 for ; Tue, 13 Jun 2000 08:40:31 -0700 (PDT) User-Agent: Microsoft-Outlook-Express-Macintosh-Edition/5.02.2022 Date: Tue, 13 Jun 2000 08:40:30 -0700 Subject: Promise Ultra66 install problem From: Lars Eggert To: Message-ID: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I'm having a strange problem booting after installing 4.0-RELEASE onto a Maxtor 7200rpm ATA66 drive attached to a Promise Ultra66 controller. Installation went by without problems, but booting off the drive fails at varying points during boot0 or the BTX boot loader. Sometimes I see a message about "elf_loadexec: archsw.readin failed", sometimes not even that. If I move the drive on the onboard (standard) IDE controller, I can boot fine (until the time comes to mount things, because the fstab is wrong, but that is to be expected.) The system also has an onboard SCSI controller with drives attached and 3.4-RELEASE installed, could that be part of the problem? (Disabling it didn't make a difference.) I checked the archive, and the recommended fix for the "archsw.readin" problem seems to be to reinstall boot blocks. I can't do this, however, since I can't boot from the drive. I've redone the installation, would that have the same effect? But wouldn't the boot blocks be okay anyway, since I can boot if the drive is connected to a standard IDE controller? -- Lars Eggert Information Sciences Institute http://www.isi.edu/~larse/ University of Southern California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message