From owner-freebsd-alpha Fri Apr 9 15:26:57 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 4E99315B6E for ; Fri, 9 Apr 1999 15:25:19 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id KAA13164; Fri, 9 Apr 1999 10:01:29 -0700 Date: Fri, 9 Apr 1999 10:01:29 -0700 (PWT) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: "Gooderum, Mark" Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: FreeBSD on Alpha Multia ( In-Reply-To: <50C732FEDE87D211954300A024786203A69A@archeron.good.com> 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 There is no TGA driver so at the point in time that a switch to real as oppsed to PROM drivers happens, console input/output goes away. Use a serial line for a console. On Fri, 9 Apr 1999, Gooderum, Mark wrote: > I've got a DEC Multia up reasonably well minus a few problems. I'm > generally running a the late March SNAPSHOT with a 3.1 Release userland. > > Issue 1 - 4.x Kernel (any snapshot from February through 3/26 and CURRENT) > doesn't read the keyboard. 3.1-RELEASE/GENERIC kernel does. The console > isn't locked because output to /dev/console works. Obviously the getty is > on /dev/console and not /dev/ttyvN on the Multia. Any pointers for Keyboard > parameters to play with? I've tried doing a diff of 3.1-RELEASE versus 4.x > but the keyboard code has changed a lot. Note that NumLock/CapsLock toggle > on and off, just no input. Other wierdnesses are that the load program sees > KB input, upper and lower case, but ? comes through as / and some other > similar wierdness. > > Issue 2 - Random crashes. With 3.1-RELEASE the system will randomly just > restart without any messages from the kernel or a core dump. It's pretty > consistently related to lots of disk activity especially with more than one > process. With the latest 4.x SNAPSHOT things are much more stable and it's > only done that once. > > Issue 3 - Are kernel coredumps supposed to work on the Alpha port yet? I've > never had one occur on a crash. > -- > Mark Gooderum > mark@jumpweb.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message