Re: Unable to boot NetBSD on Linksys NSLU2 (armbe / armv5tel)

[Eddy Petrișor <eddy.petrisor%gmail.com@localhost>]

2015-03-07 20:54 GMT+02:00 Andy Ruhl <acruhl%gmail.com@localhost>:
> On Mar 7, 2015 11:31 AM, "Eddy Petrișor" <eddy.petrisor%gmail.com@localhost> wrote:
>>
>> Trying to go back in history looking for a working version, and after
>> talking to people on #netbsd on Freenode, I built a version from Oct 13,
>> 2013:
>>
>> commit 0a546fdcf7f6382275ac3aacd97163f9d7daaf2e (HEAD, nslu2-test)
>> Author: skrll <skrll>
>> Date:   Wed Oct 16 07:34:20 2013 +0000
>>
>>     Apply patch from PR/48310 - kue(4) cannot receive multicast packets.
>>
>> The result is different with this version, but still the system hasn't
>> reached the login:
>>
>> [..]
>> nfs_boot: my_name=kinder
>> nfs_boot: my_domain=eddyp.homeunix.net
>> nfs_boot: my_addr=192.168.77.251
>> nfs_boot: my_mask=255.255.255.0
>> nfs_boot: gateway=192.168.77.1
>> root on 192.168.77.250:/export/netbsd-nslu2/root
>> root time: 0x54fb349b
>> WARNING: clock lost 5545 days
>> WARNING: using filesystem time
>> WARNING: CHECK AND RESET THE DATE!
>> init: copying out path `/sbin/init' 11
>> exec /sbin/init: error 8
>> init: copying out path `/sbin/oinit' 12
>> exec /sbin/oinit: error 2
>> init: copying out path `/sbin/init.bak' 15
>> exec /sbin/init.bak: error 2
>> init: copying out path `/rescue/init' 13
>> exec /rescue/init: error 8
>> init path (default /sbin/init):
>>
>> And there is no interaction possible via the serial console. Is it
>> normal at this point the serial console not to be enabled at this
>> point, or is it something wrong in my setup/serial adapter?
>
> Did you do "sh MAKEDEV all" in /dev in the client filesystem?

Yes, I am using a script to automate the preparation of the rootfs and
I have this section in it:

mknod=$srcdir/obj/tooldir.$(uname -s)-$(uname -r)-$(uname -m)/bin/nbmknod
cd $NETBSDOUT/root/dev && sh ./MAKEDEV -m $mknod all && cd -

The entire script is visible here:
http://pastebin.com/1XcB8r34

-- 
Eddy Petrișor