From owner-freebsd-alpha Sat Nov 7 11:43:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA02731 for freebsd-alpha-outgoing; Sat, 7 Nov 1998 11:43:08 -0800 (PST) (envelope-from owner-freebsd-alpha@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA02724 for ; Sat, 7 Nov 1998 11:43:07 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with SMTP id LAA07687 for ; Sat, 7 Nov 1998 11:42:42 -0800 Date: Sat, 7 Nov 1998 11:42:41 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: freebsd-alpha@FreeBSD.ORG Subject: my experiences so far... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org (as I slowly shift over toward this....still involved in some legal foo)... So far, I haven't had much luck at Feral. I've a AlphaPC164 and a Multia. The Alpha PC164 I usually just have a serial console for- and that seems to be a problem (kernel freezes about at the point it should shift over to a real console). The Multia I have on a monitor (actually this multia has an ARC instance for linux && NT/Alpha and I switch it to SRM for NetBSD/Digital Unix)- but in booting the latest boot.flp it puked all over my shoes with machine checks and unexpected interrupts, yadda yadda yadda- I'm checking that this wasn't a corrupt floppy (this has been known to have occurred before- the floppies are really flakey on the multia) but that may not be the case. Next step is to pop a graphics card into the PC164... drag... Well, I'll try and all make it work... but from what I see of the packaging, way to guy, guys! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message