@hnyman see the previous link, the home page of R7800 on OpenWrt, I can't pin the direct section so you need to browse the page.
No, I am not going to a build for that. The problem only materialised with the first installation with the "factory" image, but subsequent sysupgrades will work ok in any case.
The advice is wiki assumes that there is just one faulty block, but there is no certainty on that.
I feel that the best solution might be to use RAM based initramfs image for the initial factory install, and then sysupgrade from that running image.
Forum has discussions about that.
I have a kind of broken R7800
- Netgear OS Kind : work well except a weird dns bug with routerlogin.net
- DD Wrt : work but wifi is slow with AX200 clients
- Open Wrt : reboot randomly after installation, starting from some build after the big layout partition change.
I also have broken ssl chip 
I use both DDWRT and OpenWRT and do not have problems with my AX200 client but default settings of DDWRT are not the best
I experience a strange Wi-Fi issue with this build ( to be precise: OpenWrt SNAPSHOT r14694-e788e9bd87 / LuCI Master git-20.280.41447-12e50de )
It happens from time to time that my Wi-Fi devices disconnect. Typically I realize it only because google home says it cannot connect to the Internet.
Today, I managed to capture the dmesg output when it happened. See below.
Any idea what the cause might be? I believe that the wi-fi typically comes up again after a while, but I'm not quite certain. It does work again after doing an 'enable' in the Luci UI.
[1848421.386767] ath10k_pci 0001:01:00.0: SWBA overrun on vdev 1, skipped old beacon
[2504211.330368] device wlan0 left promiscuous mode
[2504211.330484] br-lan: port 2(wlan0) entered disabled state
[2504211.362664] ath10k_pci 0000:01:00.0: mac flush null vif, drop 0 queues 0xffff
[2504211.365099] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 0
[2504211.368810] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 0
[2504211.375792] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 0
[2504211.485939] ath10k_pci 0001:01:00.0: No VIF found for vdev 1
[2504211.485965] ath10k_pci 0001:01:00.0: wmi-event-beacon-tx, could not find vdev for id: 1
[2504211.510997] ath10k_pci 0001:01:00.0: No VIF found for vdev 1
[2504211.511017] ath10k_pci 0001:01:00.0: received addba event for invalid vdev_id: 1
[2504211.516376] ath10k_pci 0001:01:00.0: No VIF found for vdev 1
[2504211.523350] ath10k_pci 0001:01:00.0: received addba event for invalid vdev_id: 1
[2504211.529828] ath10k_pci 0001:01:00.0: No VIF found for vdev 1
[2504211.536708] ath10k_pci 0001:01:00.0: received addba event for invalid vdev_id: 1
[2504211.542513] ath10k_pci 0001:01:00.0: No VIF found for vdev 1
[2504211.549999] ath10k_pci 0001:01:00.0: received addba event for invalid vdev_id: 1
[2504211.557184] ath10k_pci 0001:01:00.0: No VIF found for vdev 1
[2504211.563451] ath10k_pci 0001:01:00.0: received addba event for invalid vdev_id: 1
[2504211.721730] Virtual device wlan1-1 asks to queue packet!
[2504211.730622] Virtual device wlan1-1 asks to queue packet!
[2504211.941718] Virtual device wlan1-1 asks to queue packet!
[2504211.941809] Virtual device wlan1-1 asks to queue packet!
[2504212.161562] Virtual device wlan1-1 asks to queue packet!
[2504212.371715] Virtual device wlan1-1 asks to queue packet!
[2504212.591819] Virtual device wlan1-1 asks to queue packet!
[2504213.261631] Virtual device wlan1-1 asks to queue packet!
[2504213.501757] Virtual device wlan1-1 asks to queue packet!
[2504214.651055] ath10k_pci 0001:01:00.0: WARNING: failed to wait for beacon tx callback for vdev 1: 0
[2504214.651372] ath10k_pci 0001:01:00.0: peer-unmap-event: unknown peer id 1
[2504214.658932] ath10k_pci 0001:01:00.0: peer-unmap-event: unknown peer id 1
[2504214.666865] br-iot: port 2(wlan1-1) entered disabled state
[2504214.673167] ath10k_pci 0001:01:00.0: peer-unmap-event: unknown peer id 1
[2504214.687412] device wlan1-1 left promiscuous mode
[2504214.687444] br-iot: port 2(wlan1-1) entered disabled state
[2504214.960400] device wlan1 left promiscuous mode
[2504214.960509] br-lan: port 3(wlan1) entered disabled state
[2504214.991145] ath10k_pci 0001:01:00.0: mac flush null vif, drop 0 queues 0xffff
[2504214.992398] ath10k_pci 0001:01:00.0: peer-unmap-event: unknown peer id 0
[2504214.997256] ath10k_pci 0001:01:00.0: peer-unmap-event: unknown peer id 0
[2504215.004279] ath10k_pci 0001:01:00.0: peer-unmap-event: unknown peer id 0
[2504226.072217] ath10k_pci 0000:01:00.0: unsupported HTC service id: 1536
[2504226.072252] ath10k_pci 0000:01:00.0: 10.4 wmi init: vdevs: 16 peers: 48 tid: 96
[2504226.077734] ath10k_pci 0000:01:00.0: msdu-desc: 2500 skid: 32
[2504226.160855] ath10k_pci 0000:01:00.0: wmi print 'P 48/48 V 16 K 144 PH 176 T 186 msdu-desc: 2500 sw-crypt: 0 ct-sta: 0'
[2504226.161691] ath10k_pci 0000:01:00.0: wmi print 'free: 84920 iram: 13316 sram: 11224'
[2504226.552648] ath10k_pci 0000:01:00.0: Firmware lacks feature flag indicating a retry limit of > 2 is OK, requested limit: 4
[2504226.566903] br-lan: port 2(wlan0) entered blocking state
[2504226.566965] br-lan: port 2(wlan0) entered disabled state
[2504226.572060] device wlan0 entered promiscuous mode
[2504232.492598] ath10k_pci 0001:01:00.0: unsupported HTC service id: 1536
[2504232.493404] ath10k_pci 0001:01:00.0: 10.4 wmi init: vdevs: 16 peers: 48 tid: 96
[2504232.498011] ath10k_pci 0001:01:00.0: msdu-desc: 2500 skid: 32
[2504232.583397] ath10k_pci 0001:01:00.0: wmi print 'P 48/48 V 16 K 144 PH 176 T 186 msdu-desc: 2500 sw-crypt: 0 ct-sta: 0'
[2504232.584268] ath10k_pci 0001:01:00.0: wmi print 'free: 84920 iram: 13316 sram: 11224'
[2504233.331620] ath10k_pci 0001:01:00.0: Firmware lacks feature flag indicating a retry limit of > 2 is OK, requested limit: 4
[2504233.338378] br-lan: port 3(wlan1) entered blocking state
[2504233.342083] br-lan: port 3(wlan1) entered disabled state
[2504233.347806] device wlan1 entered promiscuous mode
[2504233.353133] br-lan: port 3(wlan1) entered blocking state
[2504233.357468] br-lan: port 3(wlan1) entered forwarding state
[2504233.370751] br-lan: port 3(wlan1) entered disabled state
[2504240.916746] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[2504240.917052] br-lan: port 2(wlan0) entered blocking state
[2504240.922289] br-lan: port 2(wlan0) entered forwarding state
[2504243.969068] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
[2504243.969553] br-lan: port 3(wlan1) entered blocking state
[2504243.974663] br-lan: port 3(wlan1) entered forwarding state
[2504243.987601] br-iot: port 2(wlan1-1) entered blocking state
[2504243.987626] br-iot: port 2(wlan1-1) entered disabled state
[2504243.992614] device wlan1-1 entered promiscuous mode
[2504244.006482] br-iot: port 2(wlan1-1) entered blocking state
[2504244.006508] br-iot: port 2(wlan1-1) entered forwarding state
[2504244.037020] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1-1: link becomes ready
[2627642.621161] device wlan0 left promiscuous mode
[2627642.621263] br-lan: port 2(wlan0) entered disabled state
[2627642.654476] ath10k_pci 0000:01:00.0: mac flush null vif, drop 0 queues 0xffff
[2627642.656409] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 0
[2627642.660744] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 0
[2627642.667609] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 0
[2627642.803994] ath10k_pci 0001:01:00.0: No VIF found for vdev 1
[2627642.804032] ath10k_pci 0001:01:00.0: received addba event for invalid vdev_id: 1
[2627642.809391] ath10k_pci 0001:01:00.0: No VIF found for vdev 1
[2627642.816341] ath10k_pci 0001:01:00.0: received addba event for invalid vdev_id: 1
[2627642.822192] ath10k_pci 0001:01:00.0: No VIF found for vdev 1
[2627642.829701] ath10k_pci 0001:01:00.0: no vif for vdev_id 1 found
[2627642.836762] ath10k_pci 0001:01:00.0: No VIF found for vdev 1
[2627642.841671] ath10k_pci 0001:01:00.0: received addba event for invalid vdev_id: 1
[2627642.853344] ath10k_pci 0001:01:00.0: peer-unmap-event: unknown peer id 1
[2627642.854940] ath10k_pci 0001:01:00.0: peer-unmap-event: unknown peer id 1
[2627642.861814] ath10k_pci 0001:01:00.0: peer-unmap-event: unknown peer id 1
[2627642.869279] br-iot: port 2(wlan1-1) entered disabled state
[2627642.886664] device wlan1-1 left promiscuous mode
[2627642.886693] br-iot: port 2(wlan1-1) entered disabled state
[2627643.121206] device wlan1 left promiscuous mode
[2627643.121303] br-lan: port 3(wlan1) entered disabled state
[2627643.161929] ath10k_pci 0001:01:00.0: mac flush null vif, drop 0 queues 0xffff
[2627643.163155] ath10k_pci 0001:01:00.0: peer-unmap-event: unknown peer id 0
[2627643.168047] ath10k_pci 0001:01:00.0: peer-unmap-event: unknown peer id 0
[2627643.175225] ath10k_pci 0001:01:00.0: peer-unmap-event: unknown peer id 0
root@dg1sek-router:~#
Just downloaded and installed "master-r14947-0f7a3288e1-20201115 (ath10k-ct) " today.
After installation (clean install with rest of settings) I logged into the the Luci interface, set up my router passwords and set up wireless names, channels, passwords, etc. After this I then went to System, then Software, then hit the Update Lists button. Tried to find the "Stubby" package but it appears to be missing.
I had DNS over TLS working fine via the instructions found here: [Tutorial] [No CLI] Configuring DNS over TLS with LuCI using Stubby and Dnsmasq. Since I can not find the "Stubby" package I am unable to install DNS over TLS as I had before.
Am I missing something.
If you look at the buildbot failure logs, you can notice that lots of packages currently fail in buildbot, including stubby.
You need to wait until sources are fixed so that buildbot is happy again.
1 Like
Thank You for your quick reply.
I reverted to the "stable openwrt-19.07" and everything is working correctly.
It's interesting that the "master-r14935-95b0751d0f-20201113" and prior had the "Stubby" packages. I guess they introduced some bugs in the latest master package. Guess I'll stay with the stable...
Also, I want to thank you for creating these firmware packages for the R7800. Your efforts are greatly appreciated!
Hi,
do you have any repository of older builds of yours? I just tried master-r14965-3f1109bf2a-20201117 and seems there still some issues with the repos as unbound is completely gone from them and I wanted to revert to the older version I was sure I kept a backup of, but turns out I didn't.
edit: Uh oh, I found a month old build of yours, but unbound is still not in the repos guess I'll forgo using it for now until it gets sorted. Found ERROR: package/feeds/packages/unbound failed to build. in the latest buildbot logs so I'll keep checking until it's successful, looks like lot of packages failed to build. I should also learn to read as it is literally discussed in the posts above...
Is using the just-released 5.9ghz unlicensed spectrum going to require a firmware update or is there a package update that I'm missing?
1 Like
That will require new hardware, router- and client side.
Are you sure? This is spectrum that is already legal in parts of the world.
1 Like
165-173 is already supported... am i wrong?
It wasn't unlicensed in the US until just now.
1 Like
Hello, I wanted to say many thanks to Hnyman, really enjoying the Openwrt on R7800. Have set up 3 as APs with 4 VLANs associated 4 SSIDs. Been running over the last few days and trying to get familiar with Luci.
Is there a max associated clients setting within the build? Is the setting available to modify in Luci?
I am receiving "Access Point Temporarily Full" message on my phone wifi connections screen and the phone refuses to connect to my preferred SSID (auto-reconnect) network, period. It does not connect to an AP farther away. When I move around the house, eventually it will connect.
Also noticed the phone will connect to a different SSID right away at the same spot. Settings other than SSID and security key are the same.
EDIT: Just turned on wifi throttling in developer options and the phone started connecting OK.
Maybe a bit offtopic, I see this build uses openssl while snapshots use wolfssl. I ran into a problem on a different device because of wolfssl. @hnyman - is wolfssl known to be problematic?
@wired I believe it is because Luci ssl is using openssl. When Luci uses WolfSSL hynman will probably transition to WolfSSL (saw another thread where hynman was looking to see if luci was planning on being transitioned over to wolfssl).
Interesting, thank you. luci-ssl seems to depend on wolfssl already, but maybe it doesn't work well yet as that seems to be the problem I ran into on a different device using snapshot builds.
Wrong. Luci-ssl used to default to mbedssl, and now defaults to wolfssl (in master).
No such plans.
Openssl is intentional choice, as my build includes packages that only support SSL via openssl. (I removed vsftpd from the build but it was also such package).
LuCI itself has no knowledge of the underlying SSL library. Library is accessed via ustreamssl wrapper, that provides compatibility with supported library.
When wolfssl was due to WPA3 added to OpenWrt defaults to a few months ago, Luci-ssl was left with mbedssl, which caused casual users to have both in firmware. That's why I wanted to make sure that wolfssl is used also by LuCI. (Note that my own build uses only openssl)
No idea. I have never used it.
1 Like
According to very recent discussions on IRC, wolfssl is probably not getting installed by default anymore (and for 20.xy.z), as it seems to be very buggy in combination with ustream-ssl (thereby affecting luci over https, both in terms of forward (certificate-) compatibility coming from mbedtls and reliability/ timeouts).
3 Likes