I have one victim, who has tried a prerelease of the freifunk firmware on his 2Mb WAP. Everything is working well so far, but firstboot seems to run with no effect - the device obviously stays in failsafe.
Unfortunately that bloke is no techie, so I'am looking for a more versatile victim right now. Here are some debug outputs:
(Made with Sveasoft/Freya before flashing FFF)
# cat /proc/mtd
dev: size erasesize name
mtd0: 00040000 00010000 "pmon"
mtd1: 001b0000 00010000 "linux"
mtd2: 0011473c 00010000 "rootfs"
mtd3: 00010000 00010000 "nvram"
(Unsuccessful firstboot session)
[telnet 192.168.1.1]
@Linksys WAP54G:/# set
HOME='/'
IFS='
'
OPTIND='1'
PATH='/bin:/sbin:/usr/bin:/usr/sbin'
PPID='426'
PS1='u@h:w$ '
PS2='> '
PS4='+ '
PWD='/'
SHELL='/bin/sh'
TERM='vt102'
TZ='MET-1MEST-2,M3.3.0,M10.5.0'
USER='root'
_='md'
@Linksys WAP54G:/# umount /jffs/
@Linksys WAP54G:/# firstboot
Creating jffs2 partition... done
creating directories... done
setting up symlinks... done
setting up dropbear (takes a while)...Connection closed by foreign host.
Eliza:~ karsten$
(Note that Freifunk Firmware set boot_wait within /etc/preinit and also tries to init dropbear as part of the process. To overcome the 8MB Ram Limit, I do not load the wl.o driver in Failsafe right now)
For this reason, I'am asking for some background info on this topic.
TIA, Sven-Ola