Date: Fri, 15 Mar 2013 11:37:34 -0600 From: Ian Lepore <ian@FreeBSD.org> To: loic.blot@unix-experience.fr Cc: FreeBSD Hackers <freebsd-hackers@FreeBSD.org>, freebsd-arm <freebsd-arm@FreeBSD.org> Subject: Re: Custom kernel under RPI Message-ID: <1363369054.1157.46.camel@revolution.hippie.lan> In-Reply-To: <1363368112.22589.3.camel@Nerz-PC.home> References: <1363368112.22589.3.camel@Nerz-PC.home>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 2013-03-15 at 18:21 +0100, Lo=EFc BLOT wrote: > Hi all, > I don't know if it's the good list, but hackers for RPI, i think it's a > good thing :D >=20 > I have a little problem with custom kernel with RPI. I have modified > RPI-B config file to include run/runfw driver, compiled the kernel and > install it (make buildkernel KERNCONF=3DRPI-B && make installkernel > KERNCONF=3DRPI-B, from the RPI). The problem is at reboot. I can't boot= on > the RPI, because the kernel is frozen after those lines: >=20 > Kernel entry at 0x100100 .. > Kernel args: (null) >=20 > Nothing after. > Can someone tell me if i do something wrong ? > Thanks for advance For arm-specific questions, the freebsd-arm list might be better (I've added it to the CC). The problem may be that it has no device-tree info. You can add "fdt addr 0x100" to the /boot/loader.rc file to fix that. You can also enter it by hand at the loader prompt first to see if that helps... just hit a character (other than return) while it's loading the kernel, enter that command, then enter 'boot'. -- Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1363369054.1157.46.camel>