Date: Sat, 16 Mar 2013 20:29:44 +0100 From: =?ISO-8859-1?Q?Lo=EFc?= BLOT <loic.blot@unix-experience.fr> To: Tim Kientzle <tim@kientzle.com> Cc: freebsd-arm@freebsd.org Subject: Re: Custom kernel under RPI Message-ID: <1363462184.15561.26.camel@Nerz-PC.home> In-Reply-To: <A674439E-3592-4107-94CF-5E5223DA6F91@kientzle.com> References: <1363433673.5871.2.camel@Nerz-PC.home> <20130316173850.68e8cc1e.ray@freebsd.org> <1363448928.2403.4.camel@Nerz-PC.home> <20130316180556.a12c6927.ray@freebsd.org> <1363453851.2403.5.camel@Nerz-PC.home> <D5C4D8AE-757B-42E1-9BDF-51D7B84CAD78@kientzle.com> <1363455598.2403.11.camel@Nerz-PC.home> <1363456493.1157.67.camel@revolution.hippie.lan> <A674439E-3592-4107-94CF-5E5223DA6F91@kientzle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-xjT6naND+Sef+KUL5V6R Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi tim, it's a freebsd image from raspberrypi.org website (last month), but i would have some custom kernel drivers, then i get freebsd -current and compile all kernel sources. I have three partitions 1 MSDOS and two bsdlabels with two slices. --=20 Best regards, Lo=C3=AFc BLOT,=20 UNIX systems, security and network expert http://www.unix-experience.fr Le samedi 16 mars 2013 =C3=A0 12:21 -0700, Tim Kientzle a =C3=A9crit : > On Mar 16, 2013, at 10:54 AM, Ian Lepore wrote: >=20 > > On Sat, 2013-03-16 at 18:39 +0100, Lo=C3=AFc BLOT wrote: > >> Ok, cross compile is done, i have a modular kernel, but same error > >> appears when i boot. Kernel is blocked at those lines: > >>=20 > >> Kernel entry at 0x100100 .. > >> Kernel args: (null) > >>=20 > >>=20 > >=20 > > If it doesn't say anything about what FDT it is using before it says > > Kernel Entry, then you aren't using the latest ubldr code. =20 >=20 > Lo=C3=AFc: How did you set up the MSDOS partition? >=20 > The details of how we boot FreeBSD have changed some > over the last couple of months; if you used some old > instructions to set that up, you may not have the right > boot loader configuration to correctly boot the current kernel. >=20 >=20 > > If it doesn't have the device tree data, it will lock up exactly as > > you're experiencing (without the device data the kernel doesn't have > > enough info to even print an error message). > >=20 > > A quick way to see if that's the problem is to add to the kernel config= : > >=20 > > options FDT_DTB_STATIC > > makeoptions FDT_DTS_FILE=3Dbcm2835-rpi-b.dts >=20 >=20 > Keep in mind that Ian's advice here (to compile the FDT > into the kernel) should only be used for debugging. >=20 > On RPi, the boot loaders edit the FDT before > handing it to the kernel. A compiled-in FDT won't > properly reflect a few details that the boot loaders > know about. >=20 > If the boot chain is all working properly, a compiled-in > FDT is not needed and not recommended. >=20 > Tim >=20 --=-xjT6naND+Sef+KUL5V6R Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iF4EABEIAAYFAlFEyCgACgkQh290DZyz8ub3bAEAtaymhcOWS1z+i5+4iGGk2JnB rGvnplLQ5UB/t8RbmZABAKMCywU1ZoVpkXKqMWO7ZHyswXQyJQmFELwbLpg252Mp =QEoL -----END PGP SIGNATURE----- --=-xjT6naND+Sef+KUL5V6R--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1363462184.15561.26.camel>