From owner-freebsd-arm@FreeBSD.ORG Wed Jan 22 03:50:57 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BF16A631 for ; Wed, 22 Jan 2014 03:50:57 +0000 (UTC) Received: from mail-pd0-f170.google.com (mail-pd0-f170.google.com [209.85.192.170]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8BD2718D8 for ; Wed, 22 Jan 2014 03:50:57 +0000 (UTC) Received: by mail-pd0-f170.google.com with SMTP id p10so4841899pdj.1 for ; Tue, 21 Jan 2014 19:50:56 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=DpSIfHPIKUomgVl2Lh09B261HcUG1Ta9RAPoZcDmfv0=; b=i7nGYkqcUd8EbVtAqgp5/31FS818t1YeDRPURm6uPcrVQnr2MrFuBMJ/1M/5u0Wqj+ gtZqqFAdJPtlduNWfXfHXT+DtVrhAnJxjANyXBOYz0jI3eqLAq975RXCFY66JS7tr+qR RUN585FEFB43E7h63smNsZ+BAi5ZJt9GQ5wpeh9iyd2LAdvurbjZZirj3AR1qSuf2Pye 9vSydrq1oi4BUxSJxrqYcUba+KCDLIPfd4go3XUtPS18+9TVJ63d9vTqg2R3VYsc+qkX /Wka1PSoVQqpXkJVF99yf9sjJNGLp3AQGIJrZQx50G9TrZSzPxcLzOZdAKWukHvo/nw1 8AXg== X-Gm-Message-State: ALoCoQmTZBoINHF84fyalsuDq56CMB60kfVlU2xguClSngHKbfiuWzGFN9RTjgXIaftcUdP5OtXn X-Received: by 10.68.134.98 with SMTP id pj2mr28868794pbb.110.1390362656531; Tue, 21 Jan 2014 19:50:56 -0800 (PST) Received: from [192.168.1.2] (c-24-6-182-22.hsd1.ca.comcast.net. [24.6.182.22]) by mx.google.com with ESMTPSA id yd4sm17475910pbc.13.2014.01.21.19.50.54 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 21 Jan 2014 19:50:55 -0800 (PST) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) Subject: Re: Raspberry Pi Binary Snapshot of 10.0? From: Tim Kientzle In-Reply-To: Date: Tue, 21 Jan 2014 19:50:42 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <7E354C58-96C5-4497-8F29-197BE3BA1619@kientzle.com> References: <20140121054346.GA61932@glenbarber.us> <20140121060912.GB61932@glenbarber.us> <20140122004915.GL35180@glenbarber.us> To: Jordan Starcher X-Mailer: Apple Mail (2.1827) Cc: Glen Barber , "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jan 2014 03:50:57 -0000 On Jan 21, 2014, at 5:21 PM, Jordan Starcher = wrote: > I gave the 10.0-RELEASE build a shot and it gets stuck early on in the = boot > kernel section. Can you provide more details? > This is the same behavior I saw when I created a build > using Crochet with the 10.0-RELEASE source. It's odd because it = doesn't > even make it far enough to hit the mounting error 19. I reflashed your > 10.0-PRERELEASE and booted up perfectly. Also worth noting, the > autosize_enable does work after the second boot. This is a pretty well-known bug at this point. Autosizing requires resizing two partitions: one is inside the other. For some reason, FreeBSD=92s =91geom resize=92 will successfully grow the outer partition but the new size isn=92t being fully honored until after a reboot. So two resize operations requires two boots. Does anyone have any ideas why geom isn=92t picking up the new size correctly after a resize? > On Tue, Jan 21, 2014 at 7:49 PM, Glen Barber wrote: >=20 >> Great to hear. >>=20 >> FWIW, I've moved the location of the images, so they are all in one >> directory (and checksums are included): >>=20 >> http://people.freebsd.org/~gjb/RPI/ >>=20 >> There is also an (untested by me yet, and *NOT* official) = 10.0-RELEASE >> image there. >>=20 >> I'm working on integrating this into the release build process, so it = is >> very much "work in progress, may eat your cookies" kind of stuff. It = is >> a wrapper around Crochet to do clean-room builds within a chroot. >>=20 >> The in-progress stuff is located here: >>=20 >> svn.freebsd.org/base/user/gjb/hacking/release-embedded >>=20 >> Glen >>=20 >> On Tue, Jan 21, 2014 at 07:41:14PM -0500, Jordan Starcher wrote: >>> Hi Glen, >>>=20 >>> I tested with the 11.0-CURRENT image and had the same error: = Mounting >>> failed with error 19. >>>=20 >>> I bought a new SD Card today and flashed your 10.0 image and it = worked >>> perfectly the first time! I guess these SD Cards are a bit finicky. >>>=20 >>> Thank you very much for the help, your image seems to be working = like a >>> champ. I'll pickup another SD Card to test your 11.0 image as well. = May I >>> ask what build procedures you used? >>>=20 >>> Best, >>> Jordan >>>=20 >>>=20 >>> On Tue, Jan 21, 2014 at 1:09 AM, Glen Barber = wrote: >>>=20 >>>> I should have noted I have not personally tested the = 10.0-PRERELEASE >>>> build. >>>>=20 >>>> I have seen your issue in the past, however. I'm not clear on the >>>> cause. >>>>=20 >>>> For experimentation purpose, can you try this build? >>>>=20 >>>> http://people.freebsd.org/~gjb/FreeBSD-11.0-CURRENT-RPI-B.img.bz2 >>>>=20 >>>> I'm mostly curious if the behavior is the same (i.e., if may be = related >>>> to the SD card itself). >>>>=20 >>>> SHA256 (FreeBSD-11.0-CURRENT-RPI-B.img.bz2) =3D >>>> a7722ef975a04a8a7c651b616c802a7d7adf3811f768db65697b5a8e50c8300b >>>>=20 >>>> Glen >>>>=20 >>>> On Tue, Jan 21, 2014 at 01:00:44AM -0500, Jordan Starcher wrote: >>>>> Hi Glen, >>>>>=20 >>>>> I seem to be running into the same error with your build. I = checked >> the >>>>> sha256 hash and had the correct binary. See attached error. >>>>>=20 >>>>> Thanks, >>>>> Jordan >>>>>=20 >>>>> On Tuesday, January 21, 2014, Glen Barber wrote: >>>>>=20 >>>>>> On Tue, Jan 21, 2014 at 12:38:15AM -0500, Jordan Starcher wrote: >>>>>>> Hi, >>>>>>>=20 >>>>>>> I've been trying to build a Raspberry Pi Model B binary image of >>>> FreeBSD >>>>>>> 10.0 using a 10.0 host and the crochet-freebsd script but have >> been >>>>>>> failing. I can get built image to POST, but it gets stuck when >>>> attempting >>>>>>> to initialize the kernel. >>>>>>>=20 >>>>>>> Does anyone have a 10.0 image I can use? >>>>>>>=20 >>>>>>=20 >>>>>> I have had some build failures with my release/10.0.0/ builds for >> RPI. >>>>>>=20 >>>>>> Can you try this image, built from stable/10/ ? >>>>>>=20 >>>>>>=20 >> http://people.freebsd.org/~gjb/FreeBSD-10.0-PRERELEASE-RPI-B.img.bz2 >>>>>>=20 >>>>>> SHA256 (FreeBSD-10.0-PRERELEASE-RPI-B.img.bz2) =3D >>>>>> aec511f434d551c95a53c979add5b9b84d2618bbd2e2e012db9364e1985f5de3 >>>>>>=20 >>>>>> Glen >>>>>>=20 >>>>>>=20 >>>>=20 >>>>=20 >>>>=20 >>=20 > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"