From owner-freebsd-alpha Mon Oct 16 12:14:51 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.cafes.net (mail.cafes.net [207.65.182.25]) by hub.freebsd.org (Postfix) with ESMTP id E563237B502 for ; Mon, 16 Oct 2000 12:14:48 -0700 (PDT) Received: from mail.cafes.net (mail.cafes.net [207.65.182.25]) by mail.cafes.net (8.9.3/8.9.3) with ESMTP id OAA06723 for ; Mon, 16 Oct 2000 14:14:41 -0500 Date: Mon, 16 Oct 2000 14:14:41 -0500 (CDT) From: Mike Eldridge To: freebsd-alpha@freebsd.org Subject: alpha multia axp (aka noname) boot problems 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 Hi, I have an Alpha Multia AXP 166mhz box that I've been running Linux on for a couple of years and decided I'd try FreeBSD. I created the two 1.44MB floppies needed and booted with them. I kept getting the soft errors as described in some of the FreeBSD documentation. During kernel boot, it spit out "dec_axppci_33_intr_map: bad interrupt pin 192" about 80 times and then the kernel failed with a memory management fault. Now, the documentation said booting from floppy with this type of alpha was broken, so I burned a cd and was going to boot from the cd. I got a couple of soft errors to the effect of "device dka2: sense error", but the kernel started to boot. It failed again at the same places, spitting out loads of garbage about bad interrupt pins. I've also read that you can't use FreeBSD on the console with Multias because of some issue with the video card. I'm not quite sure I understand why this is, I ran Linux on the console just fine (I even got it to run X!, although only at 640x480). Any insight would be appreciated. Thanks, Mike ----------------------------------------------------- Save the whales. Feed the hungry. Free the mallocs. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message