Thanks, however I fixed the issue by just unpluging the power cord for 30 secs. The real issue is why the router went in "fake" factory reset. In this state the router didn't accepted sys upgrades.
PS: or maybe it was a recovery, however luci didn't reported that it was entered recovery.
I think there's something on this in one of the preceding million posts on this thread, but...
If the router has a kernel crash, it writes some crash log files to ram disk in /sys/fs/pstore/. Upon reboot, if those files exist, then the bootloader goes into recovery mode. But, if you delete the files explicitly, or wipe the ram disk by powering off the device for say 30 seconds, then the router will come back up in "normal" mode and boot from the last image you installed.
1 Like
I have completed everything and it works okay so far. I have enabled ondemand and bss coloring however i havent enabled wed (will wait for this to be enabled upstream, i can wait).
My setup is quite simple:
- openwrt 22.03.3
- rt3200 is connected to isp router (dmz, since no bridge)
- I use WiFi exclusively AX (80MHz, mixed WPA2/3, 100mW), WiFi 4 is disabled
- no additional packages other than default ones
- enabled packet steering and hw/sw offload enabled
- Mac address for rt3200 is changed for wan (
a2:xy:xy:xy:xyrange, same for WiFi) I have addedluci-app-statfor stats but i will remove it. Luci is disabled, i do stuff via ssh for monitoring etc however i startuthhpdto test Luci if i have to change something.
Since i do most of my chores via Luci, i have noticed something: if Luci is started via ssh and and i select to restart AX WiFi of do wifi [down|up] then i cannot connect to Luci anymore and i got the following in logread:
Sun Mar 19 12:26:39 2023 kern.err kernel: [ 1232.727135] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:39 2023 kern.err kernel: [ 1232.735034] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:39 2023 kern.err kernel: [ 1232.742579] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:39 2023 kern.err kernel: [ 1232.750958] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:39 2023 kern.err kernel: [ 1232.758851] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:39 2023 kern.err kernel: [ 1232.767152] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:39 2023 kern.err kernel: [ 1232.774781] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:39 2023 kern.err kernel: [ 1232.782319] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:39 2023 kern.err kernel: [ 1232.790652] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:43 2023 kern.warn kernel: [ 1237.603593] print_req_error: 31338 callbacks suppressed
Sun Mar 19 12:26:43 2023 kern.err kernel: [ 1237.603604] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sun Mar 19 12:26:43 2023 kern.err kernel: [ 1237.620659] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sun Mar 19 12:26:44 2023 kern.err kernel: [ 1237.631422] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sun Mar 19 12:26:44 2023 kern.err kernel: [ 1237.642969] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sun Mar 19 12:26:44 2023 kern.err kernel: [ 1237.653751] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sun Mar 19 12:26:44 2023 kern.err kernel: [ 1237.665241] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sun Mar 19 12:26:44 2023 kern.err kernel: [ 1237.676027] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sun Mar 19 12:26:44 2023 kern.err kernel: [ 1237.687426] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sun Mar 19 12:26:44 2023 kern.err kernel: [ 1237.698184] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sun Mar 19 12:26:44 2023 kern.err kernel: [ 1237.709652] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sun Mar 19 12:26:44 2023 kern.warn kernel: [ 1237.723539] buffer_io_error: 31338 callbacks suppressed
Sun Mar 19 12:26:44 2023 kern.err kernel: [ 1237.723999] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:44 2023 kern.err kernel: [ 1237.737136] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:44 2023 kern.err kernel: [ 1237.745529] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:44 2023 kern.err kernel: [ 1237.753138] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:44 2023 kern.err kernel: [ 1237.761547] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:44 2023 kern.err kernel: [ 1237.769200] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:44 2023 kern.err kernel: [ 1237.777081] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:44 2023 kern.err kernel: [ 1237.785098] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:44 2023 kern.err kernel: [ 1237.792670] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:44 2023 kern.err kernel: [ 1237.800740] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:48 2023 kern.warn kernel: [ 1242.613526] print_req_error: 31136 callbacks suppressed
Sun Mar 19 12:26:48 2023 kern.err kernel: [ 1242.613537] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sun Mar 19 12:26:48 2023 kern.err kernel: [ 1242.630399] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sun Mar 19 12:26:49 2023 kern.err kernel: [ 1242.641583] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sun Mar 19 12:26:49 2023 kern.err kernel: [ 1242.653100] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sun Mar 19 12:26:49 2023 kern.err kernel: [ 1242.663962] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sun Mar 19 12:26:49 2023 kern.err kernel: [ 1242.675446] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sun Mar 19 12:26:49 2023 kern.err kernel: [ 1242.686291] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sun Mar 19 12:26:49 2023 kern.err kernel: [ 1242.698007] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sun Mar 19 12:26:49 2023 kern.err kernel: [ 1242.708868] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sun Mar 19 12:26:49 2023 kern.err kernel: [ 1242.720485] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sun Mar 19 12:26:49 2023 kern.warn kernel: [ 1242.733526] buffer_io_error: 31130 callbacks suppressed
Sun Mar 19 12:26:49 2023 kern.err kernel: [ 1242.733532] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:49 2023 kern.err kernel: [ 1242.746805] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:49 2023 kern.err kernel: [ 1242.754531] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:49 2023 kern.err kernel: [ 1242.762153] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:49 2023 kern.err kernel: [ 1242.770570] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:49 2023 kern.err kernel: [ 1242.778473] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:49 2023 kern.err kernel: [ 1242.786845] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:49 2023 kern.err kernel: [ 1242.794474] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:49 2023 kern.err kernel: [ 1242.802012] Buffer I/O error on dev mtdblock2, logical block 32, async page read
Sun Mar 19 12:26:49 2023 kern.err kernel: [ 1242.810447] Buffer I/O error on dev mtdblock2, logical block 32, async page read
I rarely see issues on my other routers because i mostly use default openwrt with default settings and some adjustments of existing stuff so you can say i am quite a boring user 
. If i can try something, please let me know so you can gather more data but be aware that this RT3200 is my main router from today and all tests can be executed after working hours.
1 Like
I have discovered another weirdness, unsure what is happening but WiFi reconnects all clients if you open channel analysis. Problem and how to reproduce it:
- Connect to VPN on any WiFi connected client however make sure to set not to reconnect if WiFi is lost (so you can observe WiFi loss)
- Open Luci > Channel Analysis > 5GHz tab
- Wait a bit and observe WiFi devices reconnecting
Log shows very little:
Mon Mar 20 09:57:04 2023 daemon.info hostapd: wlan1: STA xy:xy:xy:xy:xy:xy IEEE 802.11: authenticated
Mon Mar 20 09:57:05 2023 daemon.info hostapd: wlan1: STA xy:xy:xy:xy:xy:xy IEEE 802.11: associated (aid 6)
Mon Mar 20 09:57:05 2023 daemon.info hostapd: wlan1: STA xy:xy:xy:xy:xy:xy IEEE 802.11: associated (aid 6)
Mon Mar 20 09:57:07 2023 daemon.info hostapd: wlan1: STA xy:xy:xy:xy:xy:xy WPA: pairwise key handshake completed (RSN)
Mon Mar 20 09:57:07 2023 daemon.notice hostapd: wlan1: EAPOL-4WAY-HS-COMPLETED xy:xy:xy:xy:xy:xy
Mon Mar 20 09:57:10 2023 daemon.info hostapd: wlan1: STA xy:xy:xy:xy:xy:xy IEEE 802.11: associated (aid 1)
Mon Mar 20 09:57:10 2023 daemon.info hostapd: wlan1: STA xy:xy:xy:xy:xy:xy IEEE 802.11: associated (aid 1)
Mon Mar 20 09:57:11 2023 daemon.info hostapd: wlan1: STA xy:xy:xy:xy:xy:xy WPA: pairwise key handshake completed (RSN)
Mon Mar 20 09:57:11 2023 daemon.notice hostapd: wlan1: EAPOL-4WAY-HS-COMPLETED xy:xy:xy:xy:xy:xy
Mon Mar 20 09:57:12 2023 daemon.info hostapd: wlan1: STA xy:xy:xy:xy:xy:xy IEEE 802.11: authenticated
Mon Mar 20 09:57:18 2023 daemon.info hostapd: wlan1: STA xy:xy:xy:xy:xy:xy IEEE 802.11: authenticated
Mon Mar 20 09:57:19 2023 daemon.info hostapd: wlan1: STA xy:xy:xy:xy:xy:xy IEEE 802.11: associated (aid 6)
Mon Mar 20 09:57:19 2023 daemon.info hostapd: wlan1: STA xy:xy:xy:xy:xy:xy IEEE 802.11: associated (aid 6)
Mon Mar 20 09:57:20 2023 daemon.info hostapd: wlan1: STA xy:xy:xy:xy:xy:xy IEEE 802.11: associated (aid 1)
Mon Mar 20 09:57:20 2023 daemon.info hostapd: wlan1: STA xy:xy:xy:xy:xy:xy IEEE 802.11: associated (aid 1)
Mon Mar 20 09:57:20 2023 daemon.info hostapd: wlan1: STA xy:xy:xy:xy:xy:xy IEEE 802.11: authenticated
Mon Mar 20 09:57:20 2023 daemon.info hostapd: wlan1: STA xy:xy:xy:xy:xy:xy IEEE 802.11: associated (aid 5)
Mon Mar 20 09:57:20 2023 daemon.info hostapd: wlan1: STA xy:xy:xy:xy:xy:xy WPA: pairwise key handshake completed (RSN)
Mon Mar 20 09:57:20 2023 daemon.notice hostapd: wlan1: EAPOL-4WAY-HS-COMPLETED xy:xy:xy:xy:xy:xy
Mon Mar 20 09:57:21 2023 daemon.info hostapd: wlan1: STA xy:xy:xy:xy:xy:xy WPA: pairwise key handshake completed (RSN)
Mon Mar 20 09:57:21 2023 daemon.notice hostapd: wlan1: EAPOL-4WAY-HS-COMPLETED xy:xy:xy:xy:xy:xy
Mon Mar 20 09:57:21 2023 daemon.info hostapd: wlan1: STA xy:xy:xy:xy:xy:xy WPA: pairwise key handshake completed (RSN)
Mon Mar 20 09:57:21 2023 daemon.notice hostapd: wlan1: EAPOL-4WAY-HS-COMPLETED xy:xy:xy:xy:xy:xy
Mon Mar 20 09:57:21 2023 daemon.info hostapd: wlan1: STA xy:xy:xy:xy:xy:xy IEEE 802.11: authenticated
dmesg shows no changes. If you stay in Luci, connections drop from time to time. While this is not a problem for regular "consumer" devices, it is for working @ home. I dont think i would even notice this if i was not working from home today. Maybe some AX weirdness, cannot tell really. I rarely open this section in Lucu so it is not big a deal.
This is the expected behavior: If you open the Channel Analysis tab the 5 GHz radio has to hop over and scan all channels. As the clients expect the AP to constantly send beacons on the same channel, this is forcefully lead to disconnect all clients -- unless there is an additional antenna and receiving radio intended only for scanning, which is not present on the RT3200. But you can find this in professional access points such as the UniFi 6 LR which is otherwise very similar to the RT3200. I'm not even sure if we support congruent scanning in software even in case of a scanning-radio/antenna being present.
5 Likes
@daniel Do you expect impact on rt3200 with your recent Mediatek commits? I saw they are mostly for more recent chips...
@umayer The new code is used also on MT7622 and also for MT7531. However, on the RT3200 it doesn't make any difference, the SerDes on both sides of that link between MT7622 and MT7531 is setup in exactly the same way. And I have of course tested this on my E8450 device and confirm that it works just as well as before.
1 Like
Dear sir, is it possible for you to write a more detailed mesh walkthrough for the web-based interface? I can't seem to handle command lines here. I am thinking of buying another E8450 to be the child node, but I guess the walkthrough at Linksys Official Support - Adding a child node to the Linksys Dual-Band EasyMesh WiFi Router is not applicable to openWRT'd parent node? Do I have to openwrt the child node first? Thanks.
I have completed some of my, amateur, measurements. They are mostly the same as others reported in this thread.
Device spent 0,124 kWh during 24 hours, leading to an average of 5,16 Watts per hour. When device is in active use, it is hovering around 5.5 Watts.
My setup is simple: one wan cable, 6+ WiFi clients (AC/AX mix, 100mW transmit power), no SQM nor anything interesting.
Has there been any resolution to this? I'm also experiencing an unnecessary limit of 27dBm on channel 149.