1 Alternative OpenWrt SNAPSHOT r13152-5019a06fc1
2 Current OpenWrt SNAPSHOT r12834-d24e43a7f6
(Currently running on partition 2 ok)
Sat May 2 14:31:37 2020 kern.info kernel: [ 0.000000] Booting Linux on physical CPU 0x0
Sat May 2 14:31:37 2020 kern.notice kernel: [ 0.000000] Linux version 5.4.28 (nick@DESKTOP-XXXXXX) (gcc version 9.3.0 (OpenWrt GCC 9.3.0 r12834-d24e43a7f6)) #0 Sat Apr 4 15:12:43 2020
Sat May 2 14:31:37 2020 kern.info kernel: [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
Sat May 2 14:31:37 2020 kern.info kernel: [ 0.000000] CPU: VIVT data cache, VIVT instruction cache
Sat May 2 14:31:37 2020 kern.info kernel: [ 0.000000] OF: fdt: Machine model: Linksys Viper (E4200v2 / EA4500)
I have done the make distclean; git fetch; git merge
./scripts/feeds update -a
./scripts/feeds install -a
make menuconfig
make -j6
I get a successful successful factory.bin and sysupgrade.bin. I get the normal warnings about not being able to validate this is valid firmware, force the flash and end up with a router that appears to be booted. Lights and such look normal, but no internet or pings.
Trying from SSH using sysupgrade does not produce any different results
Using MTD, I am unable to actually write the image.
root@OpenWrt:/tmp# mtd -n write /tmp/openwrt-kirkwood-linksys_viper-squashfs-factory.bin kernel1
Unlocking kernel1 ...
Writing from /tmp/openwrt-kirkwood-linksys_viper-squashfs-factory.bin to kernel1 ... [w]Error writing image.
root@OpenWrt:/tmp# mtd -e kernel1 -r write /tmp/openwrt-kirkwood-linksys_viper-squashfs-factory.bin linux
Could not open mtd device: linux
Can't open device for writing!
Any suggestions without a soldering a serial cable?
Thanks,
Nick