From owner-freebsd-alpha Fri Apr 9 5:20:37 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from archeron.good.com (mgooderum1.dsl.uswest.net [209.180.19.145]) by hub.freebsd.org (Postfix) with ESMTP id 422BE14FEB for ; Fri, 9 Apr 1999 05:20:35 -0700 (PDT) (envelope-from mark@jumpweb.com) Received: by archeron.good.com with Internet Mail Service (5.5.2448.0) id <2SW368AR>; Fri, 9 Apr 1999 07:17:07 -0500 Message-ID: <50C732FEDE87D211954300A024786203A69A@archeron.good.com> From: "Gooderum, Mark" To: freebsd-alpha@FreeBSD.ORG Subject: FreeBSD on Alpha Multia ( Date: Fri, 9 Apr 1999 07:16:50 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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