i'll give you some credit neil1... there are alot of peeps that throw heavy packets at their rpi4...
but not many are driving theirs so hard in terms of multi-use
to be honest... the last ~7(back-to-around: 3.2.61-30_r17073ish after the sysupgrade bugs were fixed) major revisions are largely free of quirks and don't really need upgrading... the last 3.1's are also mostly ok
actually that build mostly just has that hardcoded enable SQM fix... (nothing much)
upgraded to rpi-4_snapshot_3.2.130-7_r17311_NO-https-dns-proxy.
flawless, on the first try. everything is fine and working out of the box instantly without any problems for me and my usecase.
sweet now that the bugs are sorted-ish I put the statix imagebuilder back up for anyone who wanted to experiment with it... also slimmed it down from 900M to 203M to 115M
details
experienced users only
remove too many packages or FILES you'll probably break the build... (specifically disk/http-ping/network tools)
but for anyone who's wanted to make your own image with less or more packages...
there is an experimental imagebuilder(s):
just run (or change) (assumes you have used imagebuilder before and have prerequisites)
###################### tar -xJf ib-r17311.tar.xz; cd ib-r17311/
./regen.sh
and you should get the same as a normal build
disclaimer: haven't tested this much yet... and probably not an ongoing thing/needs alot of devel to polish... but always wanted to make the build more versatile
technically with this you can do things like;
PACKAGE MODS
remove unwanted kmods
add procd-seccomp and procd-ujail
pre-install https-dns-proxy/docker or whatever
CONFIG MODS
add a template /etc/config/network for a second device on firstboot so it has an alternate LANIP
also disable dnsmasq and odhcpd for the above if needed with DISABLED_SERVICES
IMAGE MODS
generate with specific disk PARTUUID
generate with specific rootfs size
NON COMMUNITY
if you want to remove/delete all ./files to make a non-community build this should work... but after you install please change your cmdline.txt from PARTUUID back to root=/dev/mmcblk0p2 for the next upgrade to work
etc. etc.
NOTE:
as I removed my build-key you may have to use -F or remove the package 'ucert-full' for your OS to accept a (sysupgrade-only) image as it wont be signed by a known key
if upgrading to alternate partition sizes you probably will need the -p parameter
changing from my value will nullify the rootfsexpand feature
it's missing buildversion fixups so it will report whatever version is in files when created (it's derived from files/etc/custom/buildinfo.txt > localversion) in case you wanted to manually edit that... setting it so some large subrevision will fool the updatecheck feature into thinking it's newer i.e. localversion="3.2.130-700"
up to you... only difference is a conditional in that https-dns-proxy hotplug file that checks if its enabled before trying to reload so I don't have to build two images... (-6_wproxy -7_woproxy -9_backtonormal)
otherwise identical to what you have...
(i'm running it and seems ok)
I was getting unknown error on my WAN interface. Tried rebooting couple of times still same issue. Then I logged into my modem and saw it is started with g.dmt instead of VDSL, rebooted modem and internet started working again.
I thought maybe some issue with the latest build, turned out it was my modem.
some good news for users of this device (and sdcard/x64 etc)... proper image filesystem type detection was recently added (is being added) to attended sysupgrade... this means that it may actually work soon for us (i.e. official builds... not related to these custom builds).
so theoretically in the near future you can build your own images with nic drivers... then upgrade and keep them...
which probably only leaves partition sizes as the last important remaining thing outstanding...
after the latest update packages were not installed automatically, I used these commands you mentioned earlier.
opkg remove --force-removal-of-dependent-packages adblock luci-app-adblock
Removing package luci-app-adblock from root...
Removing package adblock from root...
Not deleting modified conffile /etc/config/adblock.
Collected errors:
* opkg_remove_cmd: Package luci-app-adblock is not installed.
[root@network /]# opkg remove --force-removal-of-dependent-packages adblock luci-app-adblock
No packages removed.
[root@network /]# opkg install igmpproxy samba4-server vsftpd luci-app-samba4 ca-certificates simple-adblock luci-app-s
imple-adblock
Installing igmpproxy (0.3-1) to root...
Downloading http://downloads.cdn.openwrt.org/snapshots/packages/aarch64_cortex-a72/packages/igmpproxy_0.3-1_aarch64_cortex-a72.ipk
Installing samba4-server (4.14.5-1) to root...
Downloading http://downloads.cdn.openwrt.org/snapshots/packages/aarch64_cortex-a72/packages/samba4-server_4.14.5-1_aarch64_cortex-a72.ipk
Installing libtasn1 (4.16.0-1) to root...
Downloading http://downloads.cdn.openwrt.org/snapshots/packages/aarch64_cortex-a72/packages/libtasn1_4.16.0-1_aarch64_cortex-a72.ipk
Installing liburing (2.0-1) to root...
Downloading http://downloads.cdn.openwrt.org/snapshots/packages/aarch64_cortex-a72/packages/liburing_2.0-1_aarch64_cortex-a72.ipk
Installing libpam (1.5.1-1) to root...
Downloading http://downloads.cdn.openwrt.org/snapshots/packages/aarch64_cortex-a72/packages/libpam_1.5.1-1_aarch64_cortex-a72.ipk
Installing attr (2.5.1-1) to root...
Downloading http://downloads.cdn.openwrt.org/snapshots/packages/aarch64_cortex-a72/packages/attr_2.5.1-1_aarch64_cortex-a72.ipk
Installing libavahi-dbus-support (0.8-7) to root...
Downloading http://downloads.cdn.openwrt.org/snapshots/packages/aarch64_cortex-a72/packages/libavahi-dbus-support_0.8-7_aarch64_cortex-a72.ipk
Installing libdaemon (0.14-5) to root...
Downloading http://downloads.cdn.openwrt.org/snapshots/packages/aarch64_cortex-a72/packages/libdaemon_0.14-5_aarch64_cortex-a72.ipk
Installing avahi-dbus-daemon (0.8-7) to root...
Downloading http://downloads.cdn.openwrt.org/snapshots/packages/aarch64_cortex-a72/packages/avahi-dbus-daemon_0.8-7_aarch64_cortex-a72.ipk
Installing libavahi-client (0.8-7) to root...
Downloading http://downloads.cdn.openwrt.org/snapshots/packages/aarch64_cortex-a72/packages/libavahi-client_0.8-7_aarch64_cortex-a72.ipk
Installing samba4-libs (4.14.5-1) to root...
Downloading http://downloads.cdn.openwrt.org/snapshots/packages/aarch64_cortex-a72/packages/samba4-libs_4.14.5-1_aarch64_cortex-a72.ipk
Installing vsftpd (3.0.4-1) to root...
Downloading http://downloads.cdn.openwrt.org/snapshots/packages/aarch64_cortex-a72/packages/vsftpd_3.0.4-1_aarch64_cortex-a72.ipk
Installing luci-app-samba4 (git-21.151.33954-c4cdfcb) to root...
Downloading https://github.com/wulfy23/rpi4-opkg/raw/master/r17311-7057e05485/luci/luci-app-samba4_git-21.151.33954-c4cdfcb_all.ipk
Package ca-certificates (20210119-1) installed in root is up to date.
Package simple-adblock (1.8.7-6) installed in root is up to date.
Package luci-app-simple-adblock (1.8.7-3) installed in root is up to date.
Configuring libpam.
Configuring libavahi-dbus-support.
Configuring libdaemon.
Configuring avahi-dbus-daemon.
Configuring libtasn1.
Configuring libavahi-client.
Configuring attr.
Configuring liburing.
Configuring samba4-libs.
Configuring samba4-server.
Configuring luci-app-samba4.
Configuring igmpproxy.
Configuring vsftpd.
Collected errors:
* resolve_conffiles: Existing conffile /etc/config/igmpproxy is different from the conffile in the new package. The new conffile will be placed at /etc/config/igmpproxy-opkg.
* resolve_conffiles: Existing conffile /etc/config/samba4 is different from the conffile in the new package. The new conffile will be placed at /etc/config/samba4-opkg.
since the move to the hosting provider... i've noticed some opkg update fails on package restore attempts...
just use /etc/packagesinstall.txt and /etc/packagesremove.txt (one package per line) or what you've been doing for a few builds while I have time to investigate...
thanks for the feedback...
( actually looks like some of the other changes I made too... that autorestore.sh file used to always be created )
edit: just tested this and it worked for me... so I think your issue is again back to **firstboot internet connectivity issues**
auto-restore-logs
actually... I think way back when I tried to fix/debug your firstboot internet problems last time... i've added an early exit before /autorestore.sh is created... (and internet is down )... I will try to maybe fix that if i'm ever in that area...
but I'm guessing packagesinstall.txt and packagesremove.txt will also fail for you if it's a connectivity problem...
fwiw... the actions were stalled in your case here;
tail -n20 /tmp/installed_packages.txt
(should show the restore actions that were carried from the last install before you reboot)
one more issue my ftp and samba users were not working and from 8/10 to 8/13 files are missing for my camera and there are some files for 8/14 but not like the normal I don't know why.