From owner-freebsd-arm@freebsd.org Sun Aug 7 11:58:26 2016 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 5183EBAEDA9 for ; Sun, 7 Aug 2016 11:58:26 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "raven.bwct.de", Issuer "BWCT" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E37891876; Sun, 7 Aug 2016 11:58:24 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id u77Bw2aL098563 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 7 Aug 2016 13:58:08 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id u77BvstI009701 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 7 Aug 2016 13:57:55 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTP id u77BvqTX034406; Sun, 7 Aug 2016 13:57:52 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id u77Bvpbs034405; Sun, 7 Aug 2016 13:57:51 +0200 (CEST) (envelope-from ticso) Date: Sun, 7 Aug 2016 13:57:51 +0200 From: Bernd Walter To: =?iso-8859-1?Q?Ren=E9?= Ladan Cc: ticso@cicely.de, freebsd-arm Subject: Re: Raspberry Pi B stuck during boot? Message-ID: <20160807115751.GA34368@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <20160806142322.GB31491@cicely7.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Operating-System: FreeBSD cicely7.cicely.de 10.2-RELEASE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Aug 2016 11:58:26 -0000 On Sun, Aug 07, 2016 at 12:09:08PM +0200, René Ladan wrote: > On 06-08-16 16:23, Bernd Walter wrote: > > On Sat, Aug 06, 2016 at 03:06:20PM +0200, René Ladan wrote: > >> Hi, > >> > >> With recent versions of 11 (alpha3 and beta3) my raspberry b gets stuck > >> near the end of the boot. I checked the SD card and updated it to 11-beta3 > >> using these commands (if I remember correctly, but nothing unusual): > >> > >> % make buildworld TARGET=arm TARGET_ARCH=armv6 > >> % make buildkernel KERNCONF=RPI-B TARGET=arm TARGET_ARCH=armv6 > >> # make installworld TARGET=arm TARGET_ARCH=armv6 DESTDIR=/mnt > >> # make installkernel TARGET=arm TARGET_ARCH=armv6 DESTDIR=/mnt > >> KERNCONF=RPI-B > >> # make delete-old TARGET=arm TARGET_ARCH=armv6 DESTDIR=/mnt > >> # make delete-old-libs TARGET=arm TARGET_ARCH=armv6 DESTDIR=/mnt > >> # mergemaster -A armv6 -D /mnt -p > >> # mergemaster -A armv6 -D /mnt -U -i > >> > >> See https://rene-ladan.nl/IMG_20160804_193031.jpg for a phone picture of > >> the TV screen where it gets stuck. > >> > >> Any ideas if what could be wrong? > > It might be hanging in single user mode prompt on serial console. > > > So if I would disable serial console in /etc/ttys it should be fine? No - that is just for the login prompt after the OS has been booted into multiuser mode. Unfortunately I have no idea where the loader on an RPi gets that information from, since so far I've always used serial consoles. The kernel itself can do double output, but the rc-scripts, including the single user mode prompt, are limited to one. It would be easiest if you have the option to wire up the serial console. > It still hangs with only the "console" and "ttyv0" entries "on" in > /etc/ttys, the rest is "off", but it used to work fine. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.