From owner-freebsd-sparc64@FreeBSD.ORG Wed Oct 6 15:50:11 2004 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6A6CD16A4CE for ; Wed, 6 Oct 2004 15:50:11 +0000 (GMT) Received: from bender.flyingweasel.com (102Net-240.sou.edu [140.211.102.240]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1AD4843D41 for ; Wed, 6 Oct 2004 15:50:11 +0000 (GMT) (envelope-from jason@flyingweasel.com) Received: from mail.flyingweasel.com (localhost [127.0.0.1]) i96FnrsI028123; Wed, 6 Oct 2004 08:49:54 -0700 (PDT) (envelope-from jason@flyingweasel.com) Received: from 66.241.92.176 (SquirrelMail authenticated user jason) by mail.flyingweasel.com with HTTP; Wed, 6 Oct 2004 08:49:54 -0700 (PDT) Message-ID: <2617.66.241.92.176.1097077794.squirrel@mail.flyingweasel.com> In-Reply-To: References: <25D03B22-175F-11D9-9B47-000502D39E8D@flyingweasel.com><4163D00B.7010904@orel.ru> Date: Wed, 6 Oct 2004 08:49:54 -0700 (PDT) From: "Jason Moreland" To: Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= User-Agent: SquirrelMail/1.4.2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal X-Spam-Status: No, hits=0.8 required=4.0 tests=PRIORITY_NO_NAME autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on bender.flyingweasel.com X-Virus-Scanned: clamd / ClamAV version devel-20040522, clamav-milter version 0.71 X-Virus-Status: Clean cc: freebsd-sparc64@freebsd.org Subject: Re: X.org on Ultra 60 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Oct 2004 15:50:11 -0000 > Andrew Belashov writes: >> Jason Moreland wrote: >> > I built X.org on my Ultra 60 running 5.3-BETA7, but realized that I >> > had not included syscon support in the kernel, therefore X would >> > not start. When I try to compile sc in the kernel however, I >> > receive an error. >> Try to uncomment uart and puc device in kernel config: > > Uh, no, that has nothing to do with it. The OP just forgot to include > a keyboard driver in his config. The linker is complaining that it > can't find the kbddriver_set linker set which normally contains a list > of compiled-in keyboard drivers. > How is this rectified then? Is it something stupid on my part? -Jason