From owner-freebsd-alpha Wed Dec 9 06:24:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA19498 for freebsd-alpha-outgoing; Wed, 9 Dec 1998 06:24:02 -0800 (PST) (envelope-from owner-freebsd-alpha@FreeBSD.ORG) Received: from davinci.isds.duke.edu (davinci.isds.duke.edu [152.3.22.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA19491 for ; Wed, 9 Dec 1998 06:24:00 -0800 (PST) (envelope-from sto@stat.Duke.EDU) Received: from cayenne.isds.duke.edu (cayenne.isds.duke.edu [152.3.22.11]) by davinci.isds.duke.edu (8.8.8/8.8.8) with ESMTP id JAA25437 for ; Wed, 9 Dec 1998 09:23:53 -0500 (EST) Received: (from sto@localhost) by cayenne.isds.duke.edu (8.8.8/8.8.8) id JAA13558 for freebsd-alpha@FreeBSD.ORG; Wed, 9 Dec 1998 09:23:53 -0500 (EST) Message-ID: <19981209092353.L27@isds.duke.edu> Date: Wed, 9 Dec 1998 09:23:53 -0500 From: "Sean O'Connell" To: FreeBSD alpha Subject: Up and running Reply-To: "Sean O'Connell" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2 X-Organization: Institute of Statistics and Decision Sciences Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi All- I wanted to let the list know that I was up and running. It was a struggle, but I have FreeBSD/Alpha on an AlphaStation 200 4/166. To install the machine, I used the kern.flp image from the 3.0-19981206-SNAP and the mfsroot.gz from the 3.0-19981127-SNAP (from the mirror site) which I copied over the mfsroot.gz (after renaming fs-image.gz) from the Dec SNAP. The mfsroot.gz from the later SNAP freezes up in sysinstall on the serial terminal (kermit + null modem from an x86 box). I had a devil of a time getting the scsi to talk to any drive (admittedly, I believe the first, a Seagate Hawk, may be shot, but the old RZ25M failed over too). It wasn't until I used a Seagate Barracuda that I was able to successfully get the disks probed. Could the tagged queueing that seems to be enabled be causing problems with the older drives? It seemed to enable it even on some very old disks. Not sure if this is a proverbial red herring or not. Secondly, it wasn't obvious to me that the installation was not going to install boot blocks on the drive. So, thanks to Curtis (ufkartfm@pacific.net) who pointed me toward the booting off of the floppy and then using disklabel. I think the following steps are what I would liked to have seen somewhere (did I miss something, somewhere?). 1) boot machine from kernel image floppy 2) when it prompts for mfsroot, hit enter and let it find your hard drive 3) mount -u /dev/da0a / {to get root mounted writeable since the fstab is borked up} 4) change all of da0s1[a-h] entries in fstab to da0[a-h] 5) mount the rest of the partitions 6) disklabel -B -b /usr/mdec/boot1 /dev/da0c 7) while you have machine up change, /dev/ttyd0 entry in /etc/ttys, so you can actually log in on the serial console :) ttyd0 "/usr/libexec/getty std.9600" dialup off secure to ttyd0 "/usr/libexec/getty std.9600" vt100 on secure This box has a Mach64 in it, so the next trick will be getting syscons/X working. Maybe it'll replace the DU box on my desk :) Thanks, S -- ------------------------------------------------------------------------- Sean O'Connell Email: sean@stat.Duke.EDU Institute of Statistics and Decision Sciences Phone: (919) 684-5419 Duke University Fax: (919) 684-8594 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message