Using the following:
# mount
rootfs on / type rootfs (rw)
/dev/root on / type squashfs (ro)
none on /dev type devfs (rw)
proc on /proc type proc (rw)
ramfs on /tmp type ramfs (rw)
none on /proc/bus/usb type usbdevfs (rw)
/dev/sda1 on /tmp/mnt/usb0/part1 type vfat (rw)
# cat /dev/mtd/0 > /tmp/mnt/usb0/part1/cfe.bin
I was able to put a 256KB file that I named cfe.bin on my attached USB stick.
I think that may indeed be the CFE. It is 256KB in size, padded with 0 (FF) at the end, and I was able to extract some things from it that pertain to when the device boots:
My assumption is that this router will require a few things established first.
1. NEWD or NEWD2?
2. K2.4 or K2.6?
3. Multi-flash for first use?
4. Special builds?
5. Is the necessary code even in the trunk?
1. Probably NEWD2 if we want dual-radio support, but NEWD would be fine if we just want 2.4GHz.
2. Not sure which kernel, but probably K2.6.
3. Multi-flash would be ok for first use, just to make sure. There is no gigabit switch, so flashing a Micro build would not be a problem.
4.
5. No idea.
My assumption is that this router will require a few things established first.
1. NEWD or NEWD2?
2. K2.4 or K2.6?
3. Multi-flash for first use?
4. Special builds?
5. Is the necessary code even in the trunk?
1. NEWDX (latest Broadcom wifi driver, the radio is already used in other dd-wrt supported routers)
2. K26
3. Yes
4. Yes, nv64 build like the WNDR4000 for Netgear routers with 64KByte nvram.
5. Yes
Can you please extract mtd/1, mtd/16, mtd/17 and upload them here or include them in a pm to me.
I don't think Eko ever got a donated router (he usually acknowledge that in a forum post) but it looks like it is possible to add dd-wrt support for the router now without a physical router on his table. _________________ Kernel panic: Aiee, killing interrupt handler!