Just noticed this commit in nbd's git where he disables packet steering by default since: "mt76 now spreads the load over multiple CPUs more smoothly, processing
ethernet packets should be faster running on one core"
With the script you set the irq affinities manually and thus you shouldn't need irqbalance anymore.
That being said, irqbalance is a one-size-fits-all solution, the script is more tailored. However, for your situation there might be more optimal irq affinities. So, put the scripts through it's paces but don't be afraid to change stuff around and see how that works.
r14284 installed through LuCI forcing the update and without keeping settings.
Reconfigured all by hand, but at the first reboot the settings are gone
I will try to flash from d-link recovery, but it seems that we still have the same problem of all previous 5.4 kernel builds...
just updated with sysupgrade from ssh, but at every reboot I am continuing to lose all settings.
below the command I used for the upgrade:
root@OpenWrt:/tmp# sysupgrade -v -n -F /tmp/openwrt-ramips-mt7621-dlink_dir-860l
-b1-squashfs-sysupgrade..bin
Device dlink,dir-860l-b1 not supported by this image
Supported devices: dlink,dir-860l-b1 dir-860l-b1 - 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 (early adopters with DSA already set up may just force-flash keeping existing config)
Image check failed but --force given - will update anyway!
Commencing upgrade. Closing all shell sessions.
Connection to 192.168.1.1 closed by remote host.
Connection to 192.168.1.1 closed.
I am upgrading from r12255, will try without -n option but I am not confident it will make any difference. PS: just for fun I tried also to upgrade from recovery with factory bin file, but it is the same (no settings kept after reboot)
Might be because I have stripped out debug info. Needs more testing
You can use the script but you have to modify the board names. Newer build that I am on has a few fixes, uptime is over 2 days and I only have:
ERR: 352
Usage: /sbin/sysupgrade [<upgrade-option>...] <image file or URL>
/sbin/sysupgrade [-q] [-i] [-c] [-u] [-o] [-k] <backup-command> <file>
upgrade-option:
-f <config> restore configuration from .tar.gz (file or url)
-i interactive mode
-c attempt to preserve all changed files in /etc/
-o attempt to preserve all changed files in /, except those
from packages but including changed confs.
-u skip from backup files that are equal to those in /rom
>> -n do not save configuration over reflash
-p do not attempt to restore the partition table after flash.
-k include in backup a list of current installed packages at
/etc/backup/installed_packages.txt
-T | --test
Verify image and config .tar.gz but do not actually flash.
-F | --force
Flash image even if image checks fail, this is dangerous!
-q less verbose
-v more verbose
-h | --help display this help
backup-command:
-b | --create-backup <file>
create .tar.gz of files specified in sysupgrade.conf
then exit. Does not flash an image. If file is '-',
i.e. stdout, verbosity is set to 0 (i.e. quiet).
-r | --restore-backup <file>
restore a .tar.gz created with sysupgrade -b
then exit. Does not flash an image. If file is '-',
the archive is read from stdin.
-l | --list-backup
list the files that would be backed up when calling
sysupgrade -b. Does not create a backup file.
-n is kind of a weird flag. From the description is not entirely clear to me what it exactly does. Do other builds flash just fine, master and/or 19.07?
I tried numerous flashing methods, including going back to stock and to openwrt from there (oddly enough going back to stock some previous stock settings such as SSID names had been retained).
I've been reading up but can't seem to find a definitive cause for this...
Could anyone more "enlightened" share their thoughts on this?
I just happened to be catching up on this thread...
I have the same issue on ath79 and haven't found any mentions of it. On a freshly built image I see log entries saying it failed to mount /overlay and something about it using ramdisk instead (hence no configs are retained over a reboot).
Did you find anything since you wrote this?
@Bartvz you asked a question further back that indicates you might also have the issue, any idea where this was introduced? I haven't had time to work back and find the commit
I don't follow this thread that close as I don't have 860l anymore, however there is this in the 19.07.4 changelog:
Device support: images for some device became too big to support a persistent overlay, causing such devices to lose configuration after a reboot. If you experience this problem, please report the affected device in the forum and consider downgrading to OpenWrt 18.06 or using the Image Builder to pack a smaller custom image
Thanks for the heads up, however I believe that 16Mb flash at this point in time should be sufficient, also it might be worth noting that dev/root has actually decreased from 8.8Mb in 12255 to 8.3 in the latest optimized build, whilst dev/mtdblock8 (overlays) has remained the same size - 5.1Mb.
Could it be a JFFS2 configuration issue? (its odd that on first boot overlays get mounted fine, but in subsequent boots it defaults to ramdisk)
Just installed 19.07.4 over snapshot r12255 (bart's build) directly from Luci.
The setting backup didn't work, but once configured the settings by hand, they were kept after reboot.