Date: Wed, 26 Jun 2013 08:42:31 +0100 (BST) From: Anton Shterenlikht <mexas@bris.ac.uk> To: marius@alchemy.franken.de, mexas@bristol.ac.uk Cc: freebsd-sparc64@freebsd.org Subject: Re: sparc64 machfb: (EE) Unable to map mmio aperture. Invalid argument (22) Message-ID: <201306260742.r5Q7gVu2067875@mech-cluster241.men.bris.ac.uk> In-Reply-To: <20130625212559.GA3904@alchemy.franken.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201306260742.r5Q7gVu2067875>