Date: Wed, 26 Dec 2012 08:17:04 -0700 From: Ian Lepore <freebsd@damnhippie.dyndns.org> To: Oleksandr Tymoshenko <gonzo@bluezbox.com> Cc: Tim Kientzle <tim@kientzle.com>, freebsd-arm@freebsd.org Subject: Re: Raspberry Pi questions Message-ID: <1356535024.1144.46.camel@revolution.hippie.lan> In-Reply-To: <2E70584E-598E-4D3A-9B2B-6E5FB19A506C@bluezbox.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> <2E70584E-598E-4D3A-9B2B-6E5FB19A506C@bluezbox.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2012-12-25 at 22:07 -0800, Oleksandr Tymoshenko wrote: > 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: > >>>> > >>>> This is so close to working. > > > > I know what you mean…. > > > > I've almost got my scripts building bootable RPi images now using > > the new boot sequence that Oleksandr's been working on. > > > > There's clearly been a huge amount of progress: memory config > > now works, the HDMI video console works. > > > > But I am still having a few inexplicable issues: > > > > 1) Building U-Boot. > > > > 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. > > > > > 2) Random failure to mount root. > > > > 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 > mountroot? > > > > > 3) Doesn't quite make it to multi-user. > > > > 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 > freeze. I'm planning on merging this patch soon. Oh that's interesting. I guess I haven't seen it because I only have a serial console, no keyboard and screen. I did notice however that timekeeping seems a bit marginal... I left a compile and portsnap fetch running overnight, and this morning my ssh sessions had closed on a broken pipe, but the RPi had not rebooted. I always use "ServerAliveInterval 60" in my ssh sessions, so they shouldn't normally timeout for inactivity. In syslog I found: Dec 26 04:55:29 rpi ntpd[9534]: ntpd 4.2.4p5-a (1) Dec 26 07:20:31 rpi sshd[689]: fatal: Write failed: Broken pipe Dec 26 07:20:31 rpi sshd[590]: fatal: Write failed: Broken pipe Dec 26 09:03:45 rpi ntpd[9535]: time reset +4294.767396 s The first ntpd line was when the machine last rebooted yesterday. In case you're wondering, the difference between the broken pipe messages and the clock step is 6194 seconds. It would be just too neat and tidy for it to be 4294. (On the other hand, the difference between 6194 and 4294 is exactly 31 minutes. I hate round-number coincidences.) -- Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1356535024.1144.46.camel>