Build for Netgear R7800

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

No need, that sectioning and comments are just for clarity. Easier to see what has been added and why.

1 Like

Hi, thanks for this build that I'm using, I'm coming from ddwrt, I can understand how OpenWrt work but I understand almost nothing about the builds numbers, updates, etc...

Sorry for the stupid question, now I've installed the OpenWrt SNAPSHOT r19345-72b93b77a5 / LuCI Master git-22.089.43958-7110635 that I don't know if is the latest updated, by the way, the latest update in your dropbox folder should be the master-r19345-72b93b77a5-20220401 ? What are the other builds? and why your builds report 19.xxx when the latest OpenWrt firmware should be 22.xx?

And when you compile a new build, I can simple upgrade from the CLI/LuCI interface the build: master-r19345-xyz-sysupgrade.bin?

I also have removed some software (AdBlock, since I'm using a pihole), but if I update with your build, the deleted software are inside again, right?

There's something also that I have to know before updating? I understand that those are stupid questions but I'm having some trouble to understand the "OpenWrt environment-builds" rather than networking features :slight_smile:

Thanks again.

Well, as I try to explain in the first message, I offer build from the development master branch and the two current stable branches 22.03 and 21.02. The latest builds are listed in message 1.

In the build version I show the branch, Openwrt revision (rXXXXX - commit hash) and the build date:
owrt2203-r19206-6e7bf6ad95-20220403
OpenWrt 22.03 revision r19206-6e7bf6ad95 built on 2022-04-03.

Various branches get bug fix updates, but e.g. in the 21.02 the main OpenWrt code is mainly from 2021 February, while 22.03 is based on March 2022 code. Current branches:

.

you are probably referring to the LuCI GUI revision shown at footer. It shows the Luci main version, but various LuCI components have newer revisions.
Btw, for the master build it shows currently:

If you flash a new firmware image, you naturally get also all the packages included in the image. But note that if you have set adblock as disabled in the adblock config, it remains disabled. Configs are preserved by default in sysupgrade.

4 Likes

Thanks a lot for the reply and all the info, now I'm starting to understand a little more, what a complicated development in OpenWrt :grin:

Well, as I try to explain in the first message, I offer build from the development master branch and the two current stable branches 22.03 and 21.02. The latest builds are listed in message 1.


In the build version I show the branch, Openwrt revision (rXXXXX - commit hash) and the build date:
owrt2203-r19206-6e7bf6ad95-20220403
OpenWrt 22.03 revision r19206-6e7bf6ad95 built on 2022-04-03.

Various branches get bug fix updates, but e.g. in the 21.02 the main OpenWrt code is mainly from 2021 February, while 22.03 is based on March 2022 code. Current branches:

Thanks a lot for the image, do you have a source for it? Maybe there's also a little explanation in the same article.

you are probably referring to the LuCI GUI revision shown at footer. It shows the Luci main version, but various LuCI components have newer revisions.
Btw, for the master build it shows currently:

Yes, my mistake, I have already installed the master/last (22.089)

then there're the stables builds: 22.03 and 21.02, both are currently developed but are not the latest if I correctly understand. Weird but okay, I'm making confusion also because the OpenWrt wiki I think has not been updated:

Stable release:

Old Stable release

https://openwrt.org/releases/start

If you flash a new firmware image, you naturally get also all the packages included in the image. But note that if you have set adblock as disabled in the adblock config, it remains disabled. Configs are preserved by default in sysupgrade.

Yes, surely, but in order to keep only "my" packages I have to make my build or to use sysupgrade -k as reported here:
Use sysupgrade -k or Opkg extras to include user-removed/installed packages in your backup

And in order to keep the latest build I have to install it from this folder if I understand correctly:

(what's the "master-firewall3" folder?)

Thanks again for all the info and the patience, I'll follow the thread and hope to help in the future, when I understand a (lot of) bit more :sweat_smile:

I have done (and updated along the versions) the chart by myself.
It can also be found on the wiki's history page, with the explanations that I have written.

They are "the latest" of their release version branch...
Similarly as there is a fully updated windows 10 while there is already also Windows 11. (Or Ubuntu 18.04, Ubuntu 20.04, Ubuntu 21.10 and soon also 22.04. Each of them have separate updates.)

No.
You have circled r19345 of 2202-04-01 while the directory below is 5 days newer r19368 of 2022-04-06.
You can check from the first message of the thread the newest builds. I build pretty often.

Master with the previous default firewall package version. Iptables based firewall3 was the default until January, while now there is nftables based firewall4 in master and 22.03.

1 Like

I have done (and updated along the versions) the chart by myself.
It can also be found on the wiki's history page, with the explanations that I have written.

Oh great, it's at the bottom, for that I haven't found it, what a stupid!

They are "the latest" of their release version branch...
Similarly as there is a fully updated windows 10 while there is already also Windows 11. (Or Ubuntu 18.04, Ubuntu 20.04, Ubuntu 21.10 and soon also 22.04. Each of them have separate updates.)

Yes, obviously (at least I understand correctly)

No.
You have circled r19345 of 2202-04-01 while the directory below is 5 days newer r19368 of 2022-04-06.
You can check from the first message of the thread the newest builds. I build pretty often.

Ah right, my mistake again, because I had installed it just few days ago and I thought the r19345 was the still the last build, great to know that you're compiling new builds so often, thanks :clap:

So I just updated (my first update :birthday:)

From
r19345-72b93b77a5 / LuCI Master git-22.089.43958-7110635
To
r19368-64f629e207 / LuCI Master git-22.089.43958-7110635

...all perfect but unfortunately I noticed that the DDNS service didn't start automatically because I've installed myself the ddns-scripts-noip (https://openwrt.org/packages/pkgdata/ddns-scripts-noip) package that are not included in your DDNS provider list. For me it's a big trouble because I use (the pretty common) no-ip.com service to get the dynamic ip address for my VPN/wireguard, if I make a remote update and it doesn't start/update my IP, I can't no more connect to my VPN obviously.

Now I need to auto-download it every time I update, is it possible (maybe it's a silly question but I'm new here) to automate it? Or can you please include this 1Kb package in your build? :blush:

You need to install it via opkg after flashing a new firmware.

Hmmm but I can't if I'm upgrading via VPN and the router doesn't send me the new IP because the no-ip ddns service is not available after the update :roll_eyes:

In the end, do you (or anyone else) have a suggestion for another ddns service that's already included in the list?

Thanks

EDIT: never mind, I went for duckdns (btw if you have other suggestions, they're welcome)

Not seeing the new

stable openwrt-21.02 owrt2102-r16545-39bf2aee0e-20220407

in Dropbox. Still the old owrt2102-r16528... thanks @hnyman

Now it is there. I forgot to copy the files.

1 Like

FYI: today my R7800 crashed / rebooted. I cannot find anything usefull in syslog or kernel log. Also pstore dir is empty.

r19345

Can i search somewhere else?

Not really. pstore may catch software caused reboots, but if was something caused by the hardware itself, there would be no trace.

1 Like

Like I mentioned earlier, console pstore logging should catch most errors. It's not enabled.

The crash logging should be currently enabled by default for R7800 (since https://github.com/openwrt/openwrt/commit/549f8694c308761c25690a519de724ea3ad2bd76)

pstore seems to be enabled as there is a pstore directory...

EDIT:
Apparently there is also a continuous(?) kernel console logging into pstore, to which shelterx possibly refers. That is not enabled.

2 Likes

Can you please create new build from 22.03? The kernel has been updated, so the kmod packages are returning some errors:

* pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.109-1-a812bfb2eede414c82d2ebee84f74ebc) for kmod-nf-reject

Thanks!

1 Like

pkg_hash_check_unresolved will always be an issue with community builds, if you need any kernel modules beyond those provided by hnyman, you will have to build the complete firmware from source yourself (enabling and integrating them into your firmware image). Dependencies between kernel and its modules are very strict, in practice they will differ for every build - so even a build done now, wouldn't match with the modules from the official binary package repositories.

yeah, I know it, but mostly the builds are working quite good for a week or more. Normally I will use 21.02 (which works good), but I need to test a package, which is only available in 22.03.

owrt2203-r19235-d0965dc174-20220410

1 Like

I am not sure if I have understood correctly:
If you need any additional modules, you have to build it by yourself -> OK
If you do not need any additional modules and just want to use the community build from hnman (btw: thanks for all your work!), why the hash check differ between the same sysupgrade version and ath10k-mainline-xxxx.ipk.
I checked for all versions that the version is really matching to ech other.

For example I have tried today:
owrt2203-r19235-d0965dc174-20220410
owrt2203-r19206-6e7bf6ad95-20220403
owrt2102-r16545-39bf2aee0e-20220407
All showing this pkg_hash_check_unresolved.

Firmware Version	OpenWrt 22.03-SNAPSHOT r19235-d0965dc174 / LuCI openwrt-22.03 branch git-22.083.69105-af8e91c
root@OpenWrt:~# opkg remove kmod-ath10k-ct
Removing package kmod-ath10k-ct from root...
root@OpenWrt:~# opkg remove ath10k-firmware-qca9984-ct
Removing package ath10k-firmware-qca9984-ct from root...
root@OpenWrt:~# opkg install /tmp/ath10k-mainline-owrt2203-r19235-d0965dc174-202
20410-0934.ipk
Installing kmod-ath10k (5.10.109+5.15.8-1-2) to root...
Configuring kmod-ath10k.
Collected errors:
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.110-1-a812bf                                                                                    b2eede414c82d2ebee84f74ebc) for kmod-cfg80211
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.110-1-a812bf                                                                                    b2eede414c82d2ebee84f74ebc) for kmod-crypto-hash
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.110-1-a812bf                                                                                    b2eede414c82d2ebee84f74ebc) for kmod-crypto-cmac
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.110-1-a812bf                                                                                    b2eede414c82d2ebee84f74ebc) for kmod-crypto-null
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.110-1-a812bf                                                                                    b2eede414c82d2ebee84f74ebc) for kmod-crypto-aead
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.110-1-a812bf                                                                                    b2eede414c82d2ebee84f74ebc) for kmod-crypto-manager
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.110-1-a812bf                                                                                    b2eede414c82d2ebee84f74ebc) for kmod-crypto-hmac
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.110-1-a812bf                                                                                    b2eede414c82d2ebee84f74ebc) for kmod-crypto-sha256
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.110-1-a812bf                                                                                    b2eede414c82d2ebee84f74ebc) for kmod-crypto-rng
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.110-1-a812bf                                                                                    b2eede414c82d2ebee84f74ebc) for kmod-crypto-seqiv
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.110-1-a812bf                                                                                    b2eede414c82d2ebee84f74ebc) for kmod-crypto-ctr
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.110-1-a812bf                                                                                    b2eede414c82d2ebee84f74ebc) for kmod-crypto-ccm
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.110-1-a812bf                                                                                    b2eede414c82d2ebee84f74ebc) for kmod-crypto-gf128
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.110-1-a812bf                                                                                    b2eede414c82d2ebee84f74ebc) for kmod-crypto-ghash
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.110-1-a812bf                                                                                    b2eede414c82d2ebee84f74ebc) for kmod-crypto-gcm
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.110-1-a812bf                                                                                    b2eede414c82d2ebee84f74ebc) for kmod-mac80211
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.110-1-a812bf                                                                                    b2eede414c82d2ebee84f74ebc) for kmod-ath

Or is this not an error, instead it is more like a warning and it was installed anyways correctly?