Re: Current build of netbsd for rpi is unable to boot

[Joachim Thiemann <joachim.thiemann%gmail.com@localhost>]

Hi Nick, I did.  (Thanks for the heads-up again.)  For a few days,
building current, for some reason GNU as didn't get built, so nothing
could get compiled on the Pi, but I crossbuilt a distribution
yesterday and that appears to work fine after a clean install.

I'm also just passing root=sd0a on the command line.  Since I never
have another USB drive on during boot anyways, that works fine.

On 12 April 2014 10:42, Nick Hudson <skrll%netbsd.org@localhost> wrote:
> On 04/07/14 14:25, Joachim Thiemann wrote:
>
>> FYI, right now this happens:
>>
>> [...]
>> root file system type: ffs
>> vchiq: local ver 6 (min 3), remote ver 6.
>> vcaudio0 at vchiq0: AUDS
>> WARNING: no TOD clock present
>> WARNING: using filesystem time
>> WARNING: CHECK AND RESET THE DATE!
>> audio0 at vcaudio0: half duplex, playback, capture, independent
>> warning: no /dev/console
>> init: copying out path `/sbin/init' 11
>> mounting sd0a on /mnt
>> setting sysctl
>> init.root: / -> /mnt
>> Tue Dec  3 18:08:37 CET 2013
>> Starting root file system check:
>> fsck_ffs: Please implement DIOCGWEDGEINFO or DIOCGDINFO for disk
>> device /dev/rsd0a: Inappropriate ioctl for device
>> Unknown error 1; help!
>> ERROR: ABORTING BOOT (sending SIGTERM to parent)!
>> [1]   Terminated              (stty status "^T...
>> init: /etc/pwd.db: No such file or directory
>> Enter pathname of shell or RETURN for /rescue/sh:
>> #
>>
>>
>
> Please send-pr this one so it doesn't get lost. I can't remember the reason
> behind this, but I know someone who does.
>
> The easiest way around it is to upgrade your userland to match your kernel,
> iirc.
>
> Nick



-- 
Joachim Thiemann :: http://jthiem.bitbucket.org ::
http://signalsprocessed.blogspot.com