Date: Tue, 9 Aug 2016 21:14:19 +0200 From: =?UTF-8?Q?Ren=c3=a9_Ladan?= <rene@freebsd.org> To: Tim Kientzle <tim@kientzle.com> Cc: ticso@cicely.de, freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: Raspberry Pi B stuck during boot? Message-ID: <1091be19-3675-a11c-872e-d37e722ec550@freebsd.org> In-Reply-To: <CADL2u4jQW%2BdEzLN17ZRBB26Uig342dt5qobXvV8XaAK41ufaTA@mail.gmail.com> References: <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> <20160807115751.GA34368@cicely7.cicely.de> <1242bfd2-420c-cc33-736c-8ec63e510046@freebsd.org> <1BDD6F6A-A420-4F65-AD93-B45069906621@kientzle.com> <CADL2u4jQW%2BdEzLN17ZRBB26Uig342dt5qobXvV8XaAK41ufaTA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 08-08-16 17:38, René Ladan wrote: > 2016-08-07 22:27 GMT+02:00 Tim Kientzle <tim@kientzle.com>: >> >>> On Aug 7, 2016, at 3:04 PM, René Ladan <rene@FreeBSD.org> wrote: >>> >>> On 07-08-16 13:57, Bernd Walter wrote: >>>> 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. >>> Yeah, I'll see if I can construct something using the GPIO pins. >>> >>> I also tried adding autoboot_delay=-1 to /boot/loader.conf and pulling >>> my DCF77 receiver from the GPIO pins (ground, +3.3V, signal wire) but >>> that didn't help either. >>> >>> So with USB power, HDMI cable to TV, and a USB keyboard it hangs >> >> Anyone doing “interesting” work with RPi should have at least one of these on hand: >> >> http://adafru.it/954 >> > Guess I was lucky enough until now to not need one. I ordered one, it > should arrive tomorrow. > I figured it out (with the Adafruit cable): I had an outdated NFS entry in /etc/fstab which now pointed to nothing, and it is automatically mounted so it runs before the login prompt and sshd. So that pretty much disabled non-serial logins if I had the network cable connected. The serial console gave enough information to fix the problem and to restore /etc/ttys to the original settings. Thanks, René
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1091be19-3675-a11c-872e-d37e722ec550>