From owner-freebsd-alpha Thu Sep 24 18:34:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA00272 for freebsd-alpha-outgoing; Thu, 24 Sep 1998 18:34:46 -0700 (PDT) (envelope-from owner-freebsd-alpha@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA00250 for ; Thu, 24 Sep 1998 18:34:34 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id TAA02254; Thu, 24 Sep 1998 19:34:27 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199809250134.TAA02254@panzer.plutotech.com> Subject: installing bootblocks... To: freebsd-alpha@FreeBSD.ORG Date: Thu, 24 Sep 1998 19:34:27 -0600 (MDT) Cc: imp@pluto.plutotech.com, gibbs@pluto.plutotech.com X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I know I'm doing something stupid here, but I'm just not quite sure what. :) I've got a Miata with two disks, and I've pretty much got FreeBSD up and running on the second disk. % uname -a FreeBSD subway.plutotech.com 3.0-BETA FreeBSD 3.0-BETA #1: Thu Sep 24 16:44:04 MDT 1998 root@subway.plutotech.com:/usr/src/sys/compile/subway alpha The problem is, the only way I've been able to boot the thing so far is by netbooting. (there were a number of tricks to figure out, but it does work) I compiled the bootblocks in sys/boot/alpha (had to hack the include paths and such), and installed them in /usr/mdec. Then I did: disklabel -B da1 /boot has the right files, I think: % ls -la /boot total 356 drwxrwxr-x 2 root wheel 512 Sep 24 19:06 . drwxr-xr-x 19 root wheel 512 Sep 24 18:06 .. -r-xr-xr-x 1 root wheel 6512 Sep 24 19:06 boot1 -r-xr-xr-x 1 root wheel 6512 Sep 19 17:08 boot1.old -r-xr-xr-x 1 root wheel 82432 Sep 24 19:11 boot2 -r-xr-xr-x 1 root wheel 82232 Sep 19 17:07 boot2.old I've tried to boot off the disk by typing this at the console prompt: >>> boot -flags 'a' dkc100 And here's what I get: (typed in by hand, excuse any typos) >>>boot -flags 'a' dkc100 (boot dkc100.1.0.1009.0 -flags a) block 0 of dkc100.1.0.1009 is a valid boot block reading 13 blocks from dkc100.1.0.1009.0 bootstrap code read in base = 14e000, image start = 0, image bytes = 1a00 initializing HWRPB at 2000 initializing page table at 140000 initializing machine state setting affinity to the primary CPU jumping to bootstrap code And it just hangs there. Anyone have an idea of what I'm doing wrong? Thanks, Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message