Optimized build for IPQ40xx devices

Not exactly actually, the Linksys have two parts on flash for the firmwares, you can switch between. After flash, you receive one with original and one with OpenWRT.

Sorry, I may confuse you by 'one GUI interface'. But you brought out something I missed, so now I have 2 questions :slight_smile:

  1. How do I switch between the two FWs?
  2. Does OpenWRT with the factory.bin file have an embeded GUI or I need to to install the GUI component for OpenWRT? <----my original question.

Besides, now I have another question, after the installation of OpenWRT, I should have the root access to the router, right?

1)
For Primary Partition: /usr/sbin/fw_setenv boot_part 1 && reboot
For Secondary Partition: /usr/sbin/fw_setenv boot_part 2 && reboot

The Power Switch method above can be used.
This is the easiest way to revert your router to its stock firmware.
NOTE: This only applies if the OpenWRT firmware is not loaded on both firmware partitions.

Step 1: Power OFF the router with the Power Switch.
Step 2: Power ON the router and the Power light will start blinking. As soon as it turns OFF (for about 2 seconds), power OFF the router.
Step 3: Repeat Step 2 twice.
Step 4: Turn the power back ON and wait for the Power light to turn solid. It should now be booted using its alternate firmware partition.

TIP: The Power Switch method can be used multiple times, allowing you to go back and forth between the two partitions. One partition will contain the Linksys Production firmware, and the other will contain the OpenWRT firmware. You can revert from the Linksys firmware to the OpenWRT firmware (and vice versa) by using this method.

2)
Yes, GUI present.

3)
You receive root after the installation of OpenWRT.

1 Like

:+1:

Gotcha~

I have successfully installed the OpenWRT FW. Cheers~

Everything works fine, but I met a problem why one of the SSID wireless is not associated and the radio device is not active.

Is there a method of debugging if it's a hardware issue or the FW issue?

I have the same state. Not sure, but as I understand it's one more WiFi for ability to create a guest AP. Because in stock firmware we have this opportunity.

Hi any plan to add linksys wh01 firmware? was added last weak ago.
thanks

I check the spec and it says MR9000 is 3-band router. This device should be active.

But I also check the scan function and it can find the wifi signal around. So I guess it's not a HW issue.

Since radio0 supports only channels from 100 upwards, maybe it's a DFS issue? Could you restart radio0 and post the syslog?

Thanks for your advice! I think I have fixed this issue.

I check the syslog and found 'Frequency 5600 (primary) not allowed for AP mode, flags: 0x7e07979 RADAR

Primary frequency not allowed'

So I changed the frequency of this wireless to 'auto', and now it's active :slight_smile:

Tue Jun 21 20:18:53 2022 user.info : luci: accepted login on /admin/dashboard for root from 192.168.53.229
Tue Jun 21 20:19:44 2022 user.info : luci: accepted login on /admin/status/syslog for root from 192.168.53.229
Tue Jun 21 20:19:54 2022 daemon.warn odhcpd[3310]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Tue Jun 21 20:19:59 2022 kern.warn kernel: [187279.457258] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
Tue Jun 21 20:19:59 2022 daemon.notice hostapd: Configuration file: /var/run/hostapd-phy0.conf (phy wlan0) --> new PHY
Tue Jun 21 20:20:01 2022 kern.warn kernel: [187281.779505] ath10k_pci 0000:01:00.0: Unknown eventid: 36933
Tue Jun 21 20:20:01 2022 daemon.notice hostapd: Frequency 5600 (primary) not allowed for AP mode, flags: 0x7e07979 RADAR
Tue Jun 21 20:20:01 2022 daemon.err hostapd: Primary frequency not allowed
Tue Jun 21 20:20:01 2022 daemon.warn hostapd: wlan0: IEEE 802.11 Configured channel (120) or frequency (5600) not found from the channel list of the current mode (2) IEEE 802.11a
Tue Jun 21 20:20:01 2022 daemon.warn hostapd: wlan0: IEEE 802.11 Hardware does not support configured channel
Tue Jun 21 20:20:01 2022 daemon.err hostapd: Could not select hw_mode and channel. (-3)
Tue Jun 21 20:20:01 2022 daemon.notice hostapd: wlan0: interface state UNINITIALIZED->DISABLED
Tue Jun 21 20:20:01 2022 daemon.notice hostapd: wlan0: AP-DISABLED
Tue Jun 21 20:20:01 2022 daemon.err hostapd: wlan0: Unable to setup interface.
Tue Jun 21 20:20:01 2022 daemon.notice hostapd: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Tue Jun 21 20:20:01 2022 kern.info kernel: [187281.795175] br-lan: port 4(wlan0) entered blocking state
Tue Jun 21 20:20:01 2022 kern.info kernel: [187281.795191] br-lan: port 4(wlan0) entered disabled state
Tue Jun 21 20:20:01 2022 kern.info kernel: [187281.795777] device wlan0 entered promiscuous mode
Tue Jun 21 20:20:01 2022 kern.info kernel: [187281.864352] device wlan0 left promiscuous mode
Tue Jun 21 20:20:01 2022 kern.info kernel: [187281.864621] br-lan: port 4(wlan0) entered disabled state
Tue Jun 21 20:20:01 2022 kern.warn kernel: [187281.915664] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
Tue Jun 21 20:20:01 2022 daemon.notice hostapd: wlan0: CTRL-EVENT-TERMINATING
Tue Jun 21 20:20:01 2022 daemon.err hostapd: hostapd_free_hapd_data: Interface wlan0 wasn't started
Tue Jun 21 20:20:01 2022 daemon.notice netifd: radio0 (19540): Command failed: Invalid argument
Tue Jun 21 20:20:01 2022 daemon.notice netifd: radio0 (19540): Device setup failed: HOSTAPD_START_FAILED
Tue Jun 21 20:20:01 2022 daemon.notice netifd: Wireless device 'radio0' set retry=0
Tue Jun 21 20:20:01 2022 daemon.crit netifd: Wireless device 'radio0' setup failed, retry=0
Tue Jun 21 20:20:02 2022 daemon.notice netifd: Wireless device 'radio0' is now down
Tue Jun 21 20:20:40 2022 kern.warn kernel: [187320.989860] ath10k_pci 0000:01:00.0: Unknown eventid: 36933
Tue Jun 21 20:23:34 2022 kern.warn kernel: [187494.895259] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
Tue Jun 21 20:23:35 2022 daemon.notice hostapd: Configuration file: /var/run/hostapd-phy0.conf (phy wlan0) --> new PHY
Tue Jun 21 20:23:37 2022 kern.warn kernel: [187497.107981] ath10k_pci 0000:01:00.0: Unknown eventid: 36933
Tue Jun 21 20:23:37 2022 daemon.notice hostapd: ACS: Automatic channel selection started, this may take a bit
Tue Jun 21 20:23:37 2022 daemon.notice hostapd: wlan0: interface state UNINITIALIZED->ACS
Tue Jun 21 20:23:37 2022 daemon.notice hostapd: wlan0: ACS-STARTED
Tue Jun 21 20:23:37 2022 kern.info kernel: [187497.114966] br-lan: port 4(wlan0) entered blocking state
Tue Jun 21 20:23:37 2022 kern.info kernel: [187497.114983] br-lan: port 4(wlan0) entered disabled state
Tue Jun 21 20:23:37 2022 kern.info kernel: [187497.115447] device wlan0 entered promiscuous mode
Tue Jun 21 20:23:38 2022 daemon.notice netifd: Wireless device 'radio0' is now up
Tue Jun 21 20:23:40 2022 daemon.notice hostapd: wlan0: ACS-COMPLETED freq=5745 channel=149
Tue Jun 21 20:23:40 2022 daemon.notice hostapd: wlan0: interface state ACS->HT_SCAN
Tue Jun 21 20:23:41 2022 daemon.notice netifd: Network device 'wlan0' link is up
Tue Jun 21 20:23:41 2022 kern.info kernel: [187501.721224] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Tue Jun 21 20:23:41 2022 kern.info kernel: [187501.721502] br-lan: port 4(wlan0) entered blocking state
Tue Jun 21 20:23:41 2022 kern.info kernel: [187501.721512] br-lan: port 4(wlan0) entered forwarding state
Tue Jun 21 20:23:41 2022 daemon.notice hostapd: wlan0: interface state HT_SCAN->ENABLED
Tue Jun 21 20:23:41 2022 daemon.notice hostapd: wlan0: AP-ENABLED

Hey, check the thread above. Change the wireless frequency to auto. The problem will be fixed.

I think the default FW probably has a issue of setting the frequency to a wrong data. Should be fixed. @NoTengoBattery

1 Like

What regulatory domain / country did you set radio0 to?

Now,the wireless country is displayed as US. Where to set it up? I don't see there's field to change it.

Signal: 0 dBm | Noise: -106 dBm
Bitrate: 0.0 Mbit/s | Country: US

Where you edit wireless settings in Advanced Settings -> Country Code

It's really bad to use openwrt on linksysea6350v3 with openwrt, very unstable 2.4ghz despite corrections and possible improvements, core saturation problems, I went back to using my xiaomi mi router 4a with padavan, show this linksys with default firmware is the best option. The compiler abandoned us a few months ago.

OK, so why you want to know the country code setup?

Please consider adding kernel support for chacha20poly1305, it is very useful when setting up ipsec tunnel, greatly improving performance over aes algorithm on ipa40xx platform. It has been merged into original openwrt.

1 Like

Just wanted to check which channels are available in your setup. Your problem looks definitely related to radar detection. Channel 149 works because it doesn't require DFS. What is the output of iw phy phy0 channels?

I changed channel to auto and select my country code, and looks like for me all works correct:

root@Router:~# iw phy phy0 channels
Band 2:
	* 5180 MHz [36] (disabled)
	* 5200 MHz [40] (disabled)
	* 5220 MHz [44] (disabled)
	* 5240 MHz [48] (disabled)
	* 5260 MHz [52] (disabled)
	* 5280 MHz [56] (disabled)
	* 5300 MHz [60] (disabled)
	* 5320 MHz [64] (disabled)
	* 5500 MHz [100] 
	  Maximum TX power: 20.0 dBm
	  Radar detection
	  Channel widths: 20MHz HT40+ VHT80
	  DFS state: usable (for 88071 sec)
	  DFS CAC time: 60000 ms
	* 5520 MHz [104] 
	  Maximum TX power: 20.0 dBm
	  Radar detection
	  Channel widths: 20MHz HT40- HT40+ VHT80
	  DFS state: usable (for 88071 sec)
	  DFS CAC time: 60000 ms
	* 5540 MHz [108] 
	  Maximum TX power: 20.0 dBm
	  Radar detection
	  Channel widths: 20MHz HT40- HT40+ VHT80
	  DFS state: usable (for 88071 sec)
	  DFS CAC time: 60000 ms
	* 5560 MHz [112] 
	  Maximum TX power: 20.0 dBm
	  Radar detection
	  Channel widths: 20MHz HT40- HT40+ VHT80
	  DFS state: usable (for 88071 sec)
	  DFS CAC time: 60000 ms
	* 5580 MHz [116] 
	  Maximum TX power: 20.0 dBm
	  Radar detection
	  Channel widths: 20MHz HT40- HT40+ VHT80
	  DFS state: usable (for 88071 sec)
	  DFS CAC time: 60000 ms
	* 5600 MHz [120] 
	  Maximum TX power: 20.0 dBm
	  Radar detection
	  Channel widths: 20MHz HT40- HT40+ VHT80
	  DFS state: usable (for 88071 sec)
	  DFS CAC time: 60000 ms
	* 5620 MHz [124] 
	  Maximum TX power: 20.0 dBm
	  Radar detection
	  Channel widths: 20MHz HT40- HT40+ VHT80
	  DFS state: usable (for 88071 sec)
	  DFS CAC time: 60000 ms
	* 5640 MHz [128] 
	  Maximum TX power: 20.0 dBm
	  Radar detection
	  Channel widths: 20MHz HT40- HT40+ VHT80
	  DFS state: usable (for 88071 sec)
	  DFS CAC time: 60000 ms
	* 5660 MHz [132] 
	  Maximum TX power: 20.0 dBm
	  Radar detection
	  Channel widths: 20MHz HT40- HT40+ VHT80
	  DFS state: available (for 87988 sec)
	  DFS CAC time: 60000 ms
	* 5680 MHz [136] 
	  Maximum TX power: 20.0 dBm
	  Radar detection
	  Channel widths: 20MHz HT40- HT40+ VHT80
	  DFS state: available (for 87988 sec)
	  DFS CAC time: 60000 ms
	* 5700 MHz [140] 
	  Maximum TX power: 20.0 dBm
	  Radar detection
	  Channel widths: 20MHz HT40- HT40+ VHT80
	  DFS state: available (for 87988 sec)
	  DFS CAC time: 60000 ms
	* 5720 MHz [144] 
	  Maximum TX power: 20.0 dBm
	  Radar detection
	  Channel widths: 20MHz HT40- VHT80
	  DFS state: available (for 87988 sec)
	  DFS CAC time: 60000 ms
	* 5745 MHz [149] 
	  Maximum TX power: 20.0 dBm
	  Channel widths: 20MHz HT40+ VHT80
	* 5765 MHz [153] 
	  Maximum TX power: 20.0 dBm
	  Channel widths: 20MHz HT40- HT40+ VHT80
	* 5785 MHz [157] 
	  Maximum TX power: 20.0 dBm
	  Channel widths: 20MHz HT40- HT40+ VHT80
	* 5805 MHz [161] 
	  Maximum TX power: 20.0 dBm
	  Channel widths: 20MHz HT40- HT40+ VHT80
	* 5825 MHz [165] 
	  Maximum TX power: 20.0 dBm
	  Channel widths: 20MHz HT40- VHT80
	* 5845 MHz [169] (disabled)
	* 5865 MHz [173] (disabled)
root@Router:~# 

Does 'country code' matter?