From owner-freebsd-sparc64@FreeBSD.ORG Wed Jun 26 07:42:56 2013 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C4F5E367 for ; Wed, 26 Jun 2013 07:42:56 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from eu1sys200aog116.obsmtp.com (eu1sys200aog116.obsmtp.com [207.126.144.141]) by mx1.freebsd.org (Postfix) with ESMTP id 23761135D for ; Wed, 26 Jun 2013 07:42:55 +0000 (UTC) Received: from mail-wg0-f46.google.com ([74.125.82.46]) (using TLSv1) by eu1sys200aob116.postini.com ([207.126.147.11]) with SMTP ID DSNKUcqbasHNX9IGiEBvehMcbP9nNVLiqIbi@postini.com; Wed, 26 Jun 2013 07:42:56 UTC Received: by mail-wg0-f46.google.com with SMTP id c11so10027239wgh.25 for ; Wed, 26 Jun 2013 00:42:34 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:date:from:message-id:to:subject:cc:reply-to:in-reply-to :x-gm-message-state; bh=sLJ68hUCKTiXoonkD241no28fRra17BDAAsvjcnY8bA=; b=h1MO3Vg3Qx3R/afPeqnlc0dJV7wREF85zFQ9vruvQCtEvbCfL80NtP5SV0x6WDQ51x SyLxKn/3xRGApWpsv9KfVqLom9ll4djEHK9DO03C1pnL9A+5oJUIG9sXRUOsql810IhR BSwTXKp/9SP0hn0iJoO/j1qCeQsshOZPv6Y84Zyph3mDexu3+UbzBJyT9xJ+aMxokF8a 5RlmhUIESi1NQEzDcQdL+lUJYFiJpqBEqbnMPU3Fr30elDiPUpWqGklEfsVtKBuk+/WO CsrZJnX+6KxjxbcpJn0RBttAmMSrqb3i7t8b7nV5E7TuP/8/6TSiVx7qxNCbs3dpZLoy ww9g== X-Received: by 10.180.36.107 with SMTP id p11mr1708793wij.31.1372232554807; Wed, 26 Jun 2013 00:42:34 -0700 (PDT) X-Received: by 10.180.36.107 with SMTP id p11mr1708789wij.31.1372232554746; Wed, 26 Jun 2013 00:42:34 -0700 (PDT) Received: from mech-cluster241.men.bris.ac.uk (mech-cluster241.men.bris.ac.uk. [137.222.187.241]) by mx.google.com with ESMTPSA id m3sm8949670wij.5.2013.06.26.00.42.32 for (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 26 Jun 2013 00:42:33 -0700 (PDT) Sender: Anton Shterenlikht Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6) with ESMTP id r5Q7gVQx067876 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 26 Jun 2013 08:42:31 +0100 (BST) (envelope-from mexas@mech-cluster241.men.bris.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6/Submit) id r5Q7gVu2067875; Wed, 26 Jun 2013 08:42:31 +0100 (BST) (envelope-from mexas) Date: Wed, 26 Jun 2013 08:42:31 +0100 (BST) From: Anton Shterenlikht Message-Id: <201306260742.r5Q7gVu2067875@mech-cluster241.men.bris.ac.uk> To: marius@alchemy.franken.de, mexas@bristol.ac.uk Subject: Re: sparc64 machfb: (EE) Unable to map mmio aperture. Invalid argument (22) In-Reply-To: <20130625212559.GA3904@alchemy.franken.de> X-Gm-Message-State: ALoCoQnuXlvlP2wxxl5DoQ4076v1ewv4Ampim+TzaDEl0KpeTm3a0uwJYSeVis3WANn//QCan2ziDVGh5/LrBpcjk/KxEsLWwCjCmqG2FBXpsRCR0iNFje0m7/V9KOchUEVDrSllRU+jR35huU46f27SK67auNZIwvfIQFl5aWQU0etmueuBvX8= Cc: freebsd-sparc64@freebsd.org X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: mexas@bristol.ac.uk List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jun 2013 07:42:56 -0000 From marius@alchemy.franken.de Tue Jun 25 23:52:19 2013 On Thu, Jun 13, 2013 at 11:14:30AM +0100, Anton Shterenlikht wrote: > I've just updated my Sun Blade 1500 silver > to 10.0-CURRENT #11 r251648. The graphics broke. > I get: > > (EE) Unable to map mmio aperture. Invalid argument (22) > FYI, I have a fix for that. Unfortunately, while the Xorg ports people were fast on nuking sparc64 support from libpciaccess, they are now extra-cautious on adding it back ... Marius oh, great! I was getting nowhere with rolling the ports back to before the latest Xorg updates. It is surprisingly hard to move the tree back and have a consistent set of installed ports. Some will have been marked vulnerable, others (e.g. pkg) refuse to go back altogether. So, many thanks for your help. Finally, I gather from what I read in ports@ in the last couple of weeks that the new Xorg is unlikely to work on sparc64 ever and the old (current) will no longer be supported after a while, so future, say 2-3 years ahead of X on sparc64 looks bleak, right? Thanks Anton