From owner-freebsd-arm@freebsd.org Wed Nov 1 23:26:15 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 864D9E66D19 for ; Wed, 1 Nov 2017 23:26:15 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 564E83254 for ; Wed, 1 Nov 2017 23:26:14 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id vA1NH1ve066082 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 1 Nov 2017 16:17:01 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id vA1NH0tW066081; Wed, 1 Nov 2017 16:17:00 -0700 (PDT) (envelope-from fbsd) Date: Wed, 1 Nov 2017 16:17:00 -0700 From: bob prohaska To: Carl Johnson Cc: freebsd-arm@freebsd.org, bob prohaska Subject: Re: RPi2 snapshot for armv7 won't boot. Message-ID: <20171101231700.GA66048@www.zefox.net> References: <86fu9xmx3u.fsf@elm.localnet> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <86fu9xmx3u.fsf@elm.localnet> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Nov 2017 23:26:15 -0000 On Wed, Nov 01, 2017 at 03:51:17PM -0700, Carl Johnson wrote: > I had previously tried to upgrade my RPi2 12.0-CURRENT system from armv6 > to armv7, but it then refused to boot. Was this done self-hosted, or using crochet? I've been trying for weeks (months?) to make the armv6-armv7 transition on a self-hosted system, without even getting it to finish buildworld, much less boot. If you are self-hosting please describe what you did to make it work as far as it did. > This time I downloaded the > latest snapshot (r325156 from 20171030) and it also refuses to boot for > exactly the same reason. In every case the kernel loads, but then it > reports that init has died, and then panics and drops into kdb. It > gives a stack backtrace, but that doesn't mean anything to me. > > Is this just me, or is anybody else having this problem? If others have > the problem, is there some workaround to get it working? > I'd be curious to know as well. Thanks for reading, bob prohaska > -- > Carl Johnson carlj@peak.org > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"