If you use the squashfs image.
You could also do something like this Sysupgrade help for x86_64 - #14 by frollic.
It's doable with squashfs too, but it's harder to resize after doing the dd.
…and as I know that tapper will build from source anyways, these settings can easily be customized at build-time as well, e.g.:
CONFIG_TARGET_KERNEL_PARTSIZE=32
CONFIG_TARGET_ROOTFS_PARTSIZE=920
(it does not make sense to make that rootfs/ overlay toooo large, as it gets re-written during each sysupgrade (may take long, with a large rootfs and slow storage) - just use the rest for another (unrelated) partition).
I believe even with the image builder it's possible to increase the size of the root partition for the image it generates.
Anyways, you may want to expand you search for any Sophos SG/XG 1X5/2X5 products and if it's something like 125w it would also have a wireless card on board.
My SG-135wr2 came with the Qualcomm Atheros QCA9880 wireless card.
OK I got me a Sophos XG 85 for £40 Not the best one I could of got, but It will do me for now. I will get it in about 4 or 5 days. At that price if it is not to my liking I can just put it up on ebay again. Thanks for all the grate advice people.
1 Like
You could also try HW flow offloading experimental build for r7800 or rpi 4b or something . Both should be capable. Pick your poison 
One of the things with the r7800 is that in the jump to Kernel 5.15 there is a bug that makes the router reboot when the CPU clocks up or down to save power. This is even a problem with the NNS builds from the forums. I hope it gets fixt soon. It is being worked on, but it is being a bit of a pane to track down. Thanks for the pointer tho mate.
I had that bug on 19.x.x.
Try this:
echo ondemand > /sys/devices/system/cpu/cpufreq/policy0/scaling_governor
echo ondemand > /sys/devices/system/cpu/cpufreq/policy1/scaling_governor
echo 800000 > /sys/devices/system/cpu/cpufreq/policy0/scaling_min_freq
echo 800000 > /sys/devices/system/cpu/cpufreq/policy1/scaling_min_freq
echo 25 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold
echo 10 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_down_factor
echo 800000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 800000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq
exit 0
That fixed it for me. I havent had random reboots since. Your milage may vary though (my guess its related to too low clock which causes memory corruption, so could be related to the actual CPU or memory banks on your unit). Note you are not alone, these settings helped other poeple (see https://forum.openwrt.org/t/openwrt-22-03-0-first-stable-release/136252/192?u=ramon
and https://forum.openwrt.org/t/openwrt-22-03-0-first-stable-release/136252/205?u=ramon)
2 Likes
I used those settings too, on my Archer C2600s, but they are running as APs.
Reached some 400+ days of uptime.
1 Like
Hi tryed this settings thanks. Will see how we go.
Fingers crossed!
if it helps put it in the startup script
I also needed to adjust similar settings to make a ThinClient keep running without sporadic resets: Using Thin Client Wortmann Terra Rangee Thinclient 5210, Intel(R) Celeron(R) CPU N3160 @ 1.60GHz
I lost a fair bit of performance/powersaving options in my setup, but now it is really solid and reliable.
So I got my xg85 and have installed openwrt to it. I like it it's fast and is doing 250 down and 25 up SQM with out braking a swet.
One thing tho on the wiki for it it says to use the efi file to flash it, but it would not boot so I used the squashfs-combined.img.gz and it booted up just fine. Any one know why this is and what's going on? Should I be using the efi file or is it ok to stick with it how it is now?
it's a BIOS thing, could be different revision, or outdated on the one you got.
I haven't used EFI file on neither SG-105 nor SG-135. You may also want to extend the root partition on your XG-85 to all of the internal SSD.
1 Like
Hi I am not going to extend the root partition. Not yet anyway. I don't want to mess up sysupgrading and I don't install that many packages anyway. Thanks for letting me know about efi. There is not mutch on google on just what it is and why you would want to use it. Just things about old bios or uefi. I was digging because it says to use the efi file for flashing on the wiki.
I don't have the cable to find out what bios I have on my xg85 yet. I am going try and pick one up in a week or 2. Then If it's a verry old bios I mite flash back to the latest stock SW and then update the FW package. Then flash back to OpenWrt. I do know that there is at leste 3 bioses out there for the rev1 which I have.
Does it really matter...?
To me yes. I want to know all the things about my new box. That's just the way I role!
New(er) BIOSes could make your CPU run slower, due to the intel bugs discovered a couple of years ago.
Not really, if you get intel-microcode via a kernel upgrade or opkg doesn't really make a difference (and it's needed either way). The meltdown/ spectre and friends mitigations do cause significant slowdowns though, especially (but not limited to) interactive 'snappiness'.
that's what I was referring to ... 5 - 30% performance hit, depending on what the CPU's doing.