Date: Sun, 7 Aug 2016 10:46:36 -0400 From: Paul Mather <paul@gromit.dlib.vt.edu> To: =?windows-1252?Q?Ren=E9_Ladan?= <rene@freebsd.org> Cc: ticso@cicely.de, freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: Raspberry Pi B stuck during boot? Message-ID: <772B7B99-9C6E-4AA6-86F7-4FECF85B8A15@gromit.dlib.vt.edu> In-Reply-To: <ceb1d17b-cf01-9d7e-a11b-2d5fb0e26538@freebsd.org> References: <CADL2u4jjVuxVkcG06z_7pJWX72YGWGm9P08Rsuwo-Q6u_rbTMQ@mail.gmail.com> <CADL2u4iS=PCXMRr7TxkS8KZJj7wKDKvqCMg71s_iOg3tFTETdw@mail.gmail.com> <CADL2u4jiGMoC0C-rPU7vqyurpUtozy2u0d2XcMq%2BPuBGULZ3Rw@mail.gmail.com> <CADL2u4jqfpH1dsyFfpgR8LR8f6sMZRZVAQOaZNH_OqAXiKMbqA@mail.gmail.com> <CADL2u4h5iP=eVQSYUpMGRj-Awtu4yKT_w7jdv1ZYmb-sXwSUNQ@mail.gmail.com> <CADL2u4iX5yrbwAGmFVc1p8gAT-xQrxPETDazBXgzGJK9PpipdQ@mail.gmail.com> <CADL2u4gsQX9sYcqTLK0xqW1tnP1R_%2B0X4L%2Bg0%2B-Lcy1juCMRFA@mail.gmail.com> <CADL2u4gzxANGUEfCw5Dn5otX7H53J-eA2UjQbTWo%2BqR_OAy_zQ@mail.gmail.com> <CADL2u4j0mx5W=rkdTpnZb1KFsc4y3N0_fq80OZK=eNrw8eFg=w@mail.gmail.com> <CADL2u4hANGUQSLe-JWfB4FQoRMPx5jm0u6oU1K1pg%2BK=Xy-SEw@mail.gmail.com> <20160806142322.GB31491@cicely7.cicely.de> <ceb1d17b-cf01-9d7e-a11b-2d5fb0e26538@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Aug 7, 2016, at 6:09 AM, Ren=E9 Ladan <rene@freebsd.org> wrote: >=20 > On 06-08-16 16:23, Bernd Walter wrote: >> On Sat, Aug 06, 2016 at 03:06:20PM +0200, Ren=E9 Ladan wrote: >>> Hi, >>>=20 >>> 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): >>>=20 >>> % make buildworld TARGET=3Darm TARGET_ARCH=3Darmv6 >>> % make buildkernel KERNCONF=3DRPI-B TARGET=3Darm TARGET_ARCH=3Darmv6 >>> # make installworld TARGET=3Darm TARGET_ARCH=3Darmv6 DESTDIR=3D/mnt >>> # make installkernel TARGET=3Darm TARGET_ARCH=3Darmv6 DESTDIR=3D/mnt >>> KERNCONF=3DRPI-B >>> # make delete-old TARGET=3Darm TARGET_ARCH=3Darmv6 DESTDIR=3D/mnt >>> # make delete-old-libs TARGET=3Darm TARGET_ARCH=3Darmv6 DESTDIR=3D/mnt= >>> # mergemaster -A armv6 -D /mnt -p >>> # mergemaster -A armv6 -D /mnt -U -i >>>=20 >>> See https://rene-ladan.nl/IMG_20160804_193031.jpg for a phone = picture of >>> the TV screen where it gets stuck. >>>=20 >>> Any ideas if what could be wrong? >> It might be hanging in single user mode prompt on serial console. >>=20 > So if I would disable serial console in /etc/ttys it should be fine? The phone picture of the screen showed a "WARNING: / was not properly = dismounted" line in the boot messages. It could be that the system has = dropped into single-user mode because of this (i.e., fsck -p failed and = thus so did multi-user boot). > It still hangs with only the "console" and "ttyv0" entries "on" in > /etc/ttys, the rest is "off", but it used to work fine. I suggest you fsck your SD card file systems so they are clean before = troubleshooting further. Cheers, Paul.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?772B7B99-9C6E-4AA6-86F7-4FECF85B8A15>