From owner-freebsd-sparc64@FreeBSD.ORG Sun Dec 20 15:00:13 2009 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C425A106566B for ; Sun, 20 Dec 2009 15:00:13 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214]) by mx1.freebsd.org (Postfix) with ESMTP id 29FC98FC0A for ; Sun, 20 Dec 2009 15:00:12 +0000 (UTC) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.14.3/8.14.3/ALCHEMY.FRANKEN.DE) with ESMTP id nBKF05mQ078672; Sun, 20 Dec 2009 16:00:05 +0100 (CET) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.3/8.14.3/Submit) id nBKF051V078671; Sun, 20 Dec 2009 16:00:05 +0100 (CET) (envelope-from marius) Date: Sun, 20 Dec 2009 16:00:05 +0100 From: Marius Strobl To: Anton Shterenlikht Message-ID: <20091220150005.GA74529@alchemy.franken.de> References: <20091202192134.GA6562@alchemy.franken.de> <20091203131609.GA86854@mech-cluster241.men.bris.ac.uk> <20091203141711.GA43641@mech-cluster241.men.bris.ac.uk> <20091206161815.GA70140@mech-cluster241.men.bris.ac.uk> <20091207155713.GF6562@alchemy.franken.de> <20091218133634.GA89155@mech-cluster241.men.bris.ac.uk> <20091219125614.GV74529@alchemy.franken.de> <20091219182004.GA80336@mech-cluster241.men.bris.ac.uk> <20091219200730.GW74529@alchemy.franken.de> <20091219214803.GA10306@mech-cluster241.men.bris.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091219214803.GA10306@mech-cluster241.men.bris.ac.uk> User-Agent: Mutt/1.4.2.3i Cc: freebsd-sparc64@freebsd.org Subject: Re: Solved: Re: trouble installing to sun blade 1500 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Dec 2009 15:00:13 -0000 On Sat, Dec 19, 2009 at 09:48:03PM +0000, Anton Shterenlikht wrote: > On Sat, Dec 19, 2009 at 09:07:30PM +0100, Marius Strobl wrote: > > On Sat, Dec 19, 2009 at 06:20:04PM +0000, Anton Shterenlikht wrote: > > > On Sat, Dec 19, 2009 at 01:56:14PM +0100, Marius Strobl wrote: > > > > On Fri, Dec 18, 2009 at 01:36:34PM +0000, Anton Shterenlikht wrote: > > > > > On Mon, Dec 07, 2009 at 04:57:13PM +0100, Marius Strobl wrote: > > > > > > > > > > > > > > If I can get nowhere with this card, any advice for > > > > > > > a card I could buy for Sun Blade 1500 (red or silver)? > > > > > > > > > > > > Sun PGX64 would be a good choice as they even allow to > > > > > > use accelerated X with decent resolution (which is > > > > > > unlikely to ever work with most of the XVR cards as > > > > > > Sun didn't open source their drivers nor release the > > > > > > necessary documentation). > > > > > > > > > > Marius, thank you. I bought on of those (15 pounds, ebay) > > > > > and it seems to work ok in the text mode. > > > > > I haven't yet built X successfully, still some errors > > > > > in devel/gobject-intospection > > > > > > > > You'll likely want to use a more lightweight window manager > > > > than GNOME like for example windowmaker on a Blade 1500 > > > > anyway. > > > > > > sure. I don't use gnome anyway. But gobject-introspection is > > > required by hal, which, in turn, is necessary for X. > > > > Ah, ok, I missed that gobject-introspection now also is a > > dependency of hal. You should avoid using hal by building > > xorg-server with WITHOUT_HAL defined anyway though; last > > time I looked at its code it didn't seem like it would > > work on sparc64 and given that it doesn't exactly work on > > amd64/i386 either I didn't bother trying to fix it. > > I've built X without hal, but get this error on X -configure: > Actually when running `X -configure` or when trying to use the resulting /root/xorg.conf.new? This looks more like an error in the configuration file and the results returned by google for this failure message suggest that this can be due to the server not being able to load a configured module. Anyway, I'd try to use the resulting xorg.conf.new and if that fails manually checking its contents and removing unnecessary and unavailable stuff like DRI for example. Marius