From owner-freebsd-arm@FreeBSD.ORG Mon Jul 1 08:34:31 2013 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 7BC8489D for ; Mon, 1 Jul 2013 08:34:31 +0000 (UTC) (envelope-from gonzo@id.bluezbox.com) Received: from id.bluezbox.com (id.bluezbox.com [88.198.91.248]) by mx1.freebsd.org (Postfix) with ESMTP id 33C4A17BB for ; Mon, 1 Jul 2013 08:34:31 +0000 (UTC) Received: from [207.6.254.8] (helo=[192.168.1.65]) by id.bluezbox.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from ) id 1UtZYv-0002ai-VR; Mon, 01 Jul 2013 01:34:19 -0700 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Subject: Re: Raspberry pi not ready to self-host yet? From: Oleksandr Tymoshenko In-Reply-To: <463D25BB-88D6-4B2E-A7F2-05A8B0525571@gmail.com> Date: Mon, 1 Jul 2013 01:33:59 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <489E95FC-AF71-483C-BA08-81276B850B7F@bluezbox.com> References: <800732D1-B06A-40AE-AE69-F6170662B2AA@turbofuzz.com> <20130626235542.27844683@ivory.wynn.com> <79CFABCE-156A-44B5-B989-A3607C47B2AF@mail.turbofuzz.com> <20130627013142.5fdb2544@ivory.wynn.com> <20130627111623.137ad2ca@ivory.wynn.com> <20130627215424.GA2441@night.db.net> <463D25BB-88D6-4B2E-A7F2-05A8B0525571@gmail.com> To: Jordan Hubbard X-Mailer: Apple Mail (2.1503) Sender: gonzo@id.bluezbox.com X-Spam-Level: -- X-Spam-Report: Spam detection software, running on the system "id.bluezbox.com", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: On 2013-07-01, at 1:14 AM, Jordan Hubbard wrote: > Well, I managed to build and install an RPI-B kernel on the PI itself last night using gcc as the compiler, but it doesn't boot. I get the dreaded "kernel boot args: (null)" and then a hang before even getting into the device probes. [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Jul 2013 08:34:31 -0000 On 2013-07-01, at 1:14 AM, Jordan Hubbard = wrote: > Well, I managed to build and install an RPI-B kernel on the PI itself = last night using gcc as the compiler, but it doesn't boot. I get the = dreaded "kernel boot args: (null)" and then a hang before even getting = into the device probes. It crashes due to INVARIANTS options in kernel config. I'm going to look into this problem some time next week unless someone beats me to = it.=20 Just disable them for now.=20 The issue with empty console is that if there is "device sc" in kernel config syscons becomes default console. And if crash happens before frame buffer driver is initialize no output from kernel appears anywhere. Add set boot_multicons=3D"YES" to /boot/loader.rc or remove syscons-related stuff from kernel config.=20