Date: Tue, 25 Dec 2012 22:07:28 -0800 From: Oleksandr Tymoshenko <gonzo@bluezbox.com> To: Tim Kientzle <tim@kientzle.com> Cc: freebsd-arm@freebsd.org Subject: Re: Raspberry Pi questions Message-ID: <2E70584E-598E-4D3A-9B2B-6E5FB19A506C@bluezbox.com> In-Reply-To: <B46B53E3-F555-4AE9-A5B4-FE2C33756C62@kientzle.com> References: <1356466883.1144.8.camel@revolution.hippie.lan> <08125E73-C46A-4DDF-BFD8-59D5B86136B8@bluezbox.com> <1356476778.1144.20.camel@revolution.hippie.lan> <0F630E03-7A0C-4D56-A580-C7A9ABD2CB0C@bluezbox.com> <1356479705.1144.23.camel@revolution.hippie.lan> <B46B53E3-F555-4AE9-A5B4-FE2C33756C62@kientzle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2012-12-25, at 9:57 PM, Tim Kientzle <tim@kientzle.com> wrote: > On Dec 25, 2012, at 3:55 PM, Ian Lepore wrote: >>>>=20 >>>> This is so close to working. >=20 > I know what you mean=85. >=20 > I've almost got my scripts building bootable RPi images now using > the new boot sequence that Oleksandr's been working on. >=20 > There's clearly been a huge amount of progress: memory config > now works, the HDMI video console works. >=20 > But I am still having a few inexplicable issues: >=20 > 1) Building U-Boot. >=20 > I'm trying to build U-Boot from the sources at > github.com/gonzoua/u-boot-pi.git > They build but the result won't boot. Can anyone > point me to the U-Boot sources that do work? For > now, I'm using the binary blob that Oleksandr built. u-boot.bin should be post-processed by this tool: https://github.com/raspberrypi/tools/tree/master/mkimage The rest file is proper binary to be booted by Raspberry Pi firmware. >=20 > 2) Random failure to mount root. >=20 > This is weird. If I insert the SD card into my Mac and open > the MSDOS partition, then eject, the card will boot (sort of, > see below). Otherwise, the kernel can't mount root. I'm > entirely baffled. Never heard of it before :( could you provide full dmesg for failed=20= mountroot? >=20 > 3) Doesn't quite make it to multi-user. >=20 > When root does mount, it goes through the init > scripts (generates SSH keys, etc), then prints the > date and time and stops. I know the kernel is running > since I get insert/removal messages if I plug/unplug a > keyboard, but getty never seems to launch on either > HDMI or serial console. Daisuke Aoyama posted patch that I believe should fix this problem. The = root cause for it is that timer setup is interrupted and as a result - timer = never gets fired. So system stuck waiting for interrupt. If you boot with serial = console - pressing any key will generate UART interrupt and system will go out of=20= freeze. I'm planning on merging this patch soon.=20=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2E70584E-598E-4D3A-9B2B-6E5FB19A506C>