Build for Netgear R7800

Cool, thanks!

Hi @hnyman, I was trying to build my firmware (snapshot) starting from your your build with few more and less packages (with the online builder), until few days it was working fine but now I get a weird error regarding one package (that should be a WireGuard dependency):

Error: Impossible package selection
 STDERR
 * opkg_install_cmd: Cannot install package kmod-crypto-lib-blake2s.
make[2]: *** [Makefile:169: package_install] Error 255
make[1]: *** [Makefile:134: _call_manifest] Error 2
make: *** [Makefile:253: manifest] Error 2

If I made the build without it, works fine, I wonder if kmod-crypto-lib-blake2s is necessary for WireGuard to work or is only a temporary issue with this package? ...since I see that it is still inside your latest build:

CONFIG_PACKAGE_kmod-crypto-lib-blake2s=y

I don't understand why doesn't work from the onlie builder! :face_with_raised_eyebrow:

Thanks!

There has been changes in the kernel entropy handling a few weeks ago in Linux, backported to stable Linux recently, and those changes involve also blake2s by default, so it might be possible that the blake2s is now built-in or something like that.

Edit:
Looks like the guess about built-in was right...

It was still there in June 5th build, but not in the June 10th build, I think. (The kernel update was between those builds)

Edit2
See also discussion and link to the Linux commit in

1 Like

Okay, great thank you also for spotted it in git!

(I'm a guy who likes to take risks :smiley: I tried to build the snapshot without the blake2s and it worked, WireGuard works too, just tested.)

Oh okay, probably I checked the txt file from your wrong build, there're too many numbers in the dropbox folder :sweat_smile: Now I checked the correct build of your Dropbox folder and I can't find it! My mistake. If I saw that blake2s wasn't in your build I would have tried without asking.

I don't understand this, there's a link with blake2s lib and this comment?

Thanks again btw!

@hnyman sorry for the tag... Did you notice problem with 2.4 ghz in latest firmware?

For some reason on my case 2.4ghz doesn't work till i use the following command

rmmod ath10k_pci && wifi down && insmod ath10k_pci && wifi up

I notice in the log this

Thu Jun 16 16:45:11 2022 daemon.info uwsgi-luci: spawned uWSGI master process (pid: 16904)
Thu Jun 16 16:45:12 2022 daemon.err uwsgi[1179]: Thu Jun 16 16:45:12 2022 - [emperor] vassal /etc/uwsgi/vassals/luci-webui.ini is now loyal
Thu Jun 16 16:45:22 2022 daemon.notice hostapd: Remove interface 'wlan3'
Thu Jun 16 16:45:22 2022 daemon.notice hostapd: wlan3: interface state ENABLED->DISABLED
Thu Jun 16 16:45:22 2022 daemon.notice hostapd: wlan3: AP-DISABLED
Thu Jun 16 16:45:22 2022 daemon.notice hostapd: wlan3: CTRL-EVENT-TERMINATING
Thu Jun 16 16:45:22 2022 daemon.notice hostapd: nl80211: deinit ifname=wlan3 disabled_11b_rates=0
Thu Jun 16 16:45:22 2022 kern.info kernel: [  935.276280] device wlan3 left promiscuous mode
Thu Jun 16 16:45:22 2022 kern.info kernel: [  935.276418] br-lan: port 5(wlan3) entered disabled state
Thu Jun 16 16:45:22 2022 kern.warn kernel: [  935.316220] ath10k_pci 0001:01:00.0: peer-unmap-event: unknown peer id 1
Thu Jun 16 16:45:22 2022 kern.warn kernel: [  935.316322] ath10k_pci 0001:01:00.0: peer-unmap-event: unknown peer id 1
Thu Jun 16 16:45:22 2022 daemon.notice netifd: Network device 'wlan3' link is down
Thu Jun 16 16:45:22 2022 daemon.info avahi-daemon[2380]: Interface wlan3.IPv6 no longer relevant for mDNS.
Thu Jun 16 16:45:22 2022 daemon.info avahi-daemon[2380]: Leaving mDNS multicast group on interface wlan3.IPv6 with address fe80::7ad2:94ff:fe52:3610.
Thu Jun 16 16:45:22 2022 daemon.info avahi-daemon[2380]: Withdrawing address record for fe80::7ad2:94ff:fe52:3610 on wlan3.
Thu Jun 16 16:45:22 2022 daemon.notice netifd: Wireless device 'radio1' is now down
Thu Jun 16 16:45:23 2022 daemon.notice hostapd: Configuration file: /var/run/hostapd-phy3.conf (phy wlan3) --> new PHY
Thu Jun 16 16:45:29 2022 kern.warn kernel: [  942.886557] ath10k_pci 0001:01:00.0: Unknown eventid: 36933
Thu Jun 16 16:45:29 2022 kern.info kernel: [  942.890428] br-lan: port 5(wlan3) entered blocking state
Thu Jun 16 16:45:29 2022 kern.info kernel: [  942.891024] br-lan: port 5(wlan3) entered disabled state
Thu Jun 16 16:45:29 2022 kern.info kernel: [  942.896836] device wlan3 entered promiscuous mode
Thu Jun 16 16:45:29 2022 kern.info kernel: [  942.902092] br-lan: port 5(wlan3) entered blocking state
Thu Jun 16 16:45:29 2022 kern.info kernel: [  942.906412] br-lan: port 5(wlan3) entered listening state
Thu Jun 16 16:45:29 2022 daemon.notice hostapd: wlan3: interface state UNINITIALIZED->COUNTRY_UPDATE
Thu Jun 16 16:45:29 2022 kern.info kernel: [  942.952817] br-lan: port 5(wlan3) entered disabled state
Thu Jun 16 16:45:31 2022 daemon.notice netifd: Wireless device 'radio1' is now up
Thu Jun 16 16:45:35 2022 kern.info kernel: [  948.287880] IPv6: ADDRCONF(NETDEV_CHANGE): wlan3: link becomes ready
Thu Jun 16 16:45:35 2022 kern.info kernel: [  948.288112] br-lan: port 5(wlan3) entered blocking state
Thu Jun 16 16:45:35 2022 kern.info kernel: [  948.293432] br-lan: port 5(wlan3) entered listening state
Thu Jun 16 16:45:35 2022 daemon.notice netifd: Network device 'wlan3' link is up

peer-unmap-event: unknown peer id 1 is this normal?

I'm trying to understand if something is wrong on my side

For those not aware, there's a lot of discussion recently around the wifi issues after 21.02.1 in this thread:

Hi, I just loaded the stable openwrt-22.03(owrt2203-r19450-515404a81b-20220619) on my R7800 and it works great.

But I noticed that the opkg repository is "https://downloads.openwrt.org/releases/22.03-SNAPSHOT/packages/..." which is always changing.

Is there an opkg repository setting which fixes the packages at the same time as the r19450 was built?

Also the official releases have similar moving-target repos for the userspace packages. No fixed version archive is available.
See the packages symlink in https://downloads.openwrt.org/releases/22.03.0-rc4/

(But the official releases have fixed repos for the kernel modules.)

I switched to the 22.03.0-rc4 packages for the application files, and they work, but as mentioned the kernel modules are different. I can't find the packages which match the owrt2203-r19450-515404a81b-20220619 build I am using.

Does anyone know if they are located anywhere? I need to install a kmod and the files in the 22.03.0-rc4 packages are incompatible.

You can't easily install kmods into private builds due to kernel config checksums.

Hi, I tried updating to both master-r19863-fd72e595c2-20220620 & owrt2203-r19450-515404a81b-20220619 and afterwards curl (possibly more) stopped working. What's worse, even when downgrading back to OpenWrt 22.03-SNAPSHOT, r19370-e90f74feb6 (which previously worked) curl remains broken. When trying to run it says:

root@openwrt:~# curl
Error loading shared library libwolfssl.so.5.3.0.ee39414e: No such file or directory (needed by /usr/bin/curl)
Error relocating /usr/bin/curl: curl_easy_header: symbol not found
Error relocating /usr/bin/curl: curl_easy_nextheader: symbol not found

I have a script that installs all my extra packages after each upgrade (luci-app-nut luci-app-unbound luci-app-uhttpd ntpd ntp-utils mc msmtp curl snmpd ca-certificates luci-app-upnp ca-bundle knot-dig bc rsyslog ddns-scripts-noip bind-host bash sshpass mosquitto-ssl tcpdump-mini) and that logged these:

Collected errors:
 * resolve_conffiles: Existing conffile /etc/msmtprc is different from the conffile in the new package. The new conffile will be placed at /etc/msmtprc-opkg.
 * resolve_conffiles: Existing conffile /etc/config/snmpd is different from the conffile in the new package. The new conffile will be placed at /etc/config/snmpd-opkg.
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.125-1-8e33a0b32a2bbc7ea449ef8047fb3db2) for kmod-nf-reject6
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.125-1-8e33a0b32a2bbc7ea449ef8047fb3db2) for kmod-nf-ipt
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.125-1-8e33a0b32a2bbc7ea449ef8047fb3db2) for kmod-nf-log
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.125-1-8e33a0b32a2bbc7ea449ef8047fb3db2) for kmod-nf-log6
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.125-1-8e33a0b32a2bbc7ea449ef8047fb3db2) for kmod-nf-ipt6
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.125-1-8e33a0b32a2bbc7ea449ef8047fb3db2) for kmod-nf-reject
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.125-1-8e33a0b32a2bbc7ea449ef8047fb3db2) for kmod-ipt-core
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.125-1-8e33a0b32a2bbc7ea449ef8047fb3db2) for kmod-ip6tables
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.125-1-8e33a0b32a2bbc7ea449ef8047fb3db2) for kmod-nfnetlink
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.125-1-8e33a0b32a2bbc7ea449ef8047fb3db2) for kmod-nf-conntrack
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.125-1-8e33a0b32a2bbc7ea449ef8047fb3db2) for kmod-nf-conntrack6
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.125-1-8e33a0b32a2bbc7ea449ef8047fb3db2) for kmod-nf-nat
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.125-1-8e33a0b32a2bbc7ea449ef8047fb3db2) for kmod-crypto-hash
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.125-1-8e33a0b32a2bbc7ea449ef8047fb3db2) for kmod-crypto-crc32c
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.125-1-8e33a0b32a2bbc7ea449ef8047fb3db2) for kmod-lib-crc32c
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.125-1-8e33a0b32a2bbc7ea449ef8047fb3db2) for kmod-nft-core
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.125-1-8e33a0b32a2bbc7ea449ef8047fb3db2) for kmod-nft-compat
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.125-1-8e33a0b32a2bbc7ea449ef8047fb3db2) for kmod-nf-conntrack-netlink
 * resolve_conffiles: Existing conffile /etc/rsyslog.conf is different from the conffile in the new package. The new conffile will be placed at /etc/rsyslog.conf-opkg.
 * resolve_conffiles: Existing conffile /etc/mosquitto/mosquitto.conf is different from the conffile in the new package. The new conffile will be placed at /etc/mosquitto/mosquitto.conf-opkg.

How could I get it working again? Thanks!

@hugalafutro there were some changes to the wolfssl lib and a bug that was fixed can you try using newer build?

I am installing master-r19863-fd72e595c2-20220620 will report when it's all back up.

@Ansuel On master-r19863-fd72e595c2-20220620 curl works again, still getting these though should I be worried? I do not know how to figure out which of the packages throws the errors

 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.127-1-41a6b3a2a6a232633bd48b14452c4604) for kmod-nf-reject6
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.127-1-41a6b3a2a6a232633bd48b14452c4604) for kmod-nf-ipt
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.127-1-41a6b3a2a6a232633bd48b14452c4604) for kmod-nf-log
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.127-1-41a6b3a2a6a232633bd48b14452c4604) for kmod-nf-log6
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.127-1-41a6b3a2a6a232633bd48b14452c4604) for kmod-nf-ipt6
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.127-1-41a6b3a2a6a232633bd48b14452c4604) for kmod-nf-reject
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.127-1-41a6b3a2a6a232633bd48b14452c4604) for kmod-ipt-core
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.127-1-41a6b3a2a6a232633bd48b14452c4604) for kmod-ip6tables
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.127-1-41a6b3a2a6a232633bd48b14452c4604) for kmod-nfnetlink
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.127-1-41a6b3a2a6a232633bd48b14452c4604) for kmod-nf-conntrack
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.127-1-41a6b3a2a6a232633bd48b14452c4604) for kmod-nf-conntrack6
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.127-1-41a6b3a2a6a232633bd48b14452c4604) for kmod-nf-nat
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.127-1-41a6b3a2a6a232633bd48b14452c4604) for kmod-crypto-hash
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.127-1-41a6b3a2a6a232633bd48b14452c4604) for kmod-crypto-crc32c
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.127-1-41a6b3a2a6a232633bd48b14452c4604) for kmod-lib-crc32c
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.127-1-41a6b3a2a6a232633bd48b14452c4604) for kmod-nft-core
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.127-1-41a6b3a2a6a232633bd48b14452c4604) for kmod-nft-compat
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.127-1-41a6b3a2a6a232633bd48b14452c4604) for kmod-nf-conntrack-netlink

Sorry, there is not much that you could do.
OpenWrt kernel modules are tightly tied to the specific build options, and installing kmods to private builds is difficult.

Now the basic problem is that kernel minor version has been updated since I last compiled my build. And the curl package in the repo requires the current kernel kmods, while my build has slightly older installed.