with version 20210623-00?
20210626-01
r17060+5-88114f617a Snapshot just built - working.
1 Like
Hi All,
I'm trying to migrate my 1900acs over from Davidc502's build and keep hitting a wall when I try to do a sysupgrade.
Every time I upload the relevant firmware I get "Device linksys,shelby not supported by this image Supported devices: linksys,wrt1900acs armada-385-linksys-shelby linksys,shelby - Image version mismatch: image 1.1, device 1.0. Please wipe config during upgrade (force required) or reinstall. Reason: Config cannot be migrated from swconfig to DSA Image check failed."
from what I can tell, modifying the /etc/config/system file in partition 1 will affect the running David build as well (and probably break it)
is there a way to have partition 1 boot in david's last working build and have partition 2 as the new DCS divested build?
..or this is because the DSA change is now an all or nothing modification?
or am I just an idiot and have missed something really simple out?
No. You can boot back to Davidâs build without issue.
Yes. Flashing the divested build will put it on your alternate partition. Only one partition can be active - there is no interaction between the two.
DSA isnât going away. Thereâs a Mini Tutorial linked here about a month ago for a very good reference. FWIW, if your network isnât complicated the change to DSA is pretty trivial.
I managed a workaround kind-of..Flashing the linksys stock firmware back into partition 1, but now am I going to be stuck with having to overwrite the david build on partition 2 in order to install divested? (installing divested via the linksys firmware will put me in this position)
so it would seem the way to go is to scp the divested factory build image over to /tmp in the david partition, and then run a forced update from ssh..is that correct?
LuCI Advanced Reboot and boot back in to Davidâs build.
Now just LuCI Backup/Flash Firmware and force the Divested sysupgrade.bin. This will put the Divested build on whatever the alternate partition happens to be. Davidâs build will still exist so you can easily boot back to it if you need to. Think of each partition as active/dormant. The flash doesnât care about partition 1 or partition 2, it just flashes to whichever is currently dormant.
the sysupgrade? not the factory?
You only need the factory.img if youâre flashing from Linksys stock. If you flash the Divested factory.img from OEM you will overwrite Davidâs image.
so it will be the factory img then, I will be flashing from the david image with ssh so I can keep that image on part 2 and have divested on part 1.
(there's a backstory to this, I have to route all outgoing traffic through a VPN so having an already working image that does this is advantageous in case something goes awry with the new build)
No. Use the sysupgrade.bin. You will get the incompatible image message like before - just donât save settings and force flash.
even though it's overwriting the linksys image?
Yes.
The first time you ever flashed Openwrt you started with the Linksys OEM firmware. The Linksys firmware needs the factory.img to initially load the Openwrt firmware.
So, if you upgrade from Linksys firmware use factory.img. If you upgrade from Openwrt firmware (either ssh or LuCI) always use the sysupgrade.bin
I'm confused...I'm in the david build and I am going to use the divested factory img to install over the top of the linksys image on the other partition.
is that correct? (cos you keep referring to me overwriting the david build with the sysupgrade img, which I am not planning to do.)
Sorry, red herring, your comment about putting OEM back on and a reference to factory.img meant you were flashing from stock - I thought.
If youâre flashing via ssh then youâre already in an Openwrt partition and would always use a sysupgrade.bin for any subsequent Openwrt upgrade.
The sysupgrade.bin will install over the top of the Linksys image on the other partition.
1 Like
Thanks for the claification.
@phinn Thanks for this list of packages. Using this list I was able to migrate my WRT32x1 to rc3 recently from David' build.
Just curious: were you able to install these packages on this build? If not, have you tried to build an image with the necessary dependent kernel modules?
TIA.
I use those packages on the 21.02-snapshot, not on Divested. I can't speak for the packages you might want to add for Divested as I haven't gone through his included tweaks/packages, with but would think it's similar.
I was recently having issues where it would take an inordinate amount of time for two devices on my LAN to communicate with each other.
Setting the following on each wifi-iface did the trick:
option multicast_to_unicast '0'
option isolate '0'
as per the thread here Clients in same WLAN can't reach each other - #72 by jow
3 Likes
Hey folks, I switched to Divested from David's builds earlier this week to fix some annoying issues. Since then, my network has been really unstable. Both my wired and wireless connections will randomly lag out, and it's been driving me crazy. I'm on a WRT1900ACSv2. Has anyone else had issues like this? I'm on the latest build, and I did follow the extra steps in the readme (enabling irqbalance and devcrypto). I haven't been able to check the log when this happens, but I'm going to keep trying.
1 Like