@hnyman was thinking of implementing some type of module or status to display the presence of pstore directly in luci.
Would be an interesting feature to add...
Something like
Give user notification if a pstore is present (aka system has crashed here is the log)
Advise to publish it and provide a download button
What do you think? Do you have suggestion / opinion on this feature?
First 22.03 build that I have uploaded for downloading. This is still pretty much the same code as the master was last week (when 22.03 was branched off master).
The buildbot for 22.03 has been created today, so there will be opkg installable packages in the next few days, hopefully. Right now there aren't, yet.
I made a test build with kernel 5.15, as Ansuel's implementation of the basic support for it for ipq806x got merged yesterday. That 5.15 will likely be a step on the path toward DSA with ipq806x.
FYI I'm getting "pkg_hash_check_unresolved: cannot find dependency kernel" when installing the mainline driver ipk. No issues when installing the mainline firmware ipk. Let me know if anyone needs to see the error messages.
I run your build on one of my R7800 and on the other I use your scripts to make mine. I have a question, from your scripts, if I change something in menuconfig (.config) do I need to add it in main.patch to have the changing at the end when the new build in ready, I mean in config.init, main.patch, packages.patch etc, in bin folder..etc
Also, do you have those kind of errors these days?
..make defconfig...
tmp/.config-package.in:102110:error: recursive dependency detected!
tmp/.config-package.in:102110: symbol PACKAGE_iptables-legacy is selected by PACKAGE_iptables-nft
tmp/.config-package.in:102917: symbol PACKAGE_iptables-nft is selected by PACKAGE_opennds
tmp/.config-package.in:101140: symbol PACKAGE_opennds depends on PACKAGE_iptables-legacy
For a resolution refer to Documentation/kbuild/kconfig-language.rst
subsection "Kconfig recursive dependency limitations"
Depends on your workflow.
You can use menuconfig to edit the current .config, but if you then replace it again with the .config.init recipe (like I do), you need to manually replicate the necessary minimal changes to .config.init
You only need main.patch etc. when you initially create the buildroot.
The recursive config errors are caused by the opennds package. Also seen by the buildbot. Not related to you.
That will work, now, but as it contains all dependencies, it may cause unnecessary packages to be included later if dependencies change.
I suggest that you prune it manually and only leave the top selections that you have actually made.
And I see you 've put your selection in .config.init in categories ;
# Include package list in build
CONFIG_INCLUDE_CONFIG=y
# Longer waiting for failsafe button push
CONFIG_IMAGEOPT=y
CONFIG_PREINITOPT=y
CONFIG_TARGET_PREINIT_TIMEOUT=5
# Busybox tweaks
CONFIG_BUSYBOX_CUSTOM=y
#CONFIG_BUSYBOX_CONFIG_DIFF=y
CONFIG_BUSYBOX_CONFIG_FEATURE_EDITING_SAVEHISTORY=y
CONFIG_BUSYBOX_CONFIG_FEATURE_EDITING_SAVE_ON_EXIT=y
CONFIG_BUSYBOX_CONFIG_FEATURE_LESS_FLAGS=y
CONFIG_BUSYBOX_CONFIG_FEATURE_LESS_REGEXP=y
CONFIG_BUSYBOX_CONFIG_FEATURE_LESS_WINCH=y
### Build also ath10k mainline .ipk
### (disable this if you use the below section to fully switch to mainline)
CONFIG_PACKAGE_kmod-ath10k=m
## # Mainline ath10k wifi firmware and driver instead of -ct
## CONFIG_PACKAGE_ath10k-firmware-qca9984=y
## # CONFIG_PACKAGE_ath10k-firmware-qca9984-ct is not set
## CONFIG_PACKAGE_kmod-ath10k=y
## # CONFIG_PACKAGE_kmod-ath10k-ct is not set
# Add-on programs
CONFIG_PACKAGE_ccrypt=y
CONFIG_PACKAGE_curl=y
CONFIG_LIBCURL_OPENSSL=y
CONFIG_PACKAGE_diffutils=y
CONFIG_DROPBEAR_ECC=y
CONFIG_PACKAGE_htop=y
CONFIG_PACKAGE_irqbalance=y
CONFIG_PACKAGE_mtr-nojson=y
CONFIG_PACKAGE_nano-full=y
CONFIG_PACKAGE_patch=y
CONFIG_PACKAGE_tcpdump-mini=y
CONFIG_PACKAGE_tree=y
CONFIG_PACKAGE_wget-ssl=y
Do I need to do that if I add some packages? I'm not sure where to add them