Try .6 release...
Sorry for late,
@Bobcat have noticed some different on .6?
@mpratt14 o had try a more time ago and the issue it was not resolved.
I'll try the .6 as soon possible. Just today I had to make some changes to the channels and I had the problem that the interface was enabled but not active.
Update: I've seen already out the .7 .
https://firmware-selector.openwrt.org/?version=19.07.7&target=ipq40xx%2Fgeneric&id=linksys_ea8300
If I remember correctly, I have to boot from the desk with the original bior and use the factory firmware. quite right?
If I do a backup of the settings, I have the .5 and can I restore them to 06 or .7?
yes
you should be able to do a normal sysupgrade
Do not do sysupgrade, it replaces failover OEM partition...
Yes i remember that. I will boot in a original firmware bank then i load openwrt factory (not sysupgrade).
See my post here :
Hope this helps
I've read , thanks. I do the update as soon as possible and i hope to fix up the wifi radio issue.
Today I tried to upgrade OpenWRT. I rebooted with Advanced Reboot on the partition with the original firmware with no particular problems apart from the fact that after the reboot the modem light remained red for about 2 minutes before rebooting with the original firmware. The problem I encountered is the following:
In the Connectivity section I don't see the possibility to manually load the firmware from a local file as also described on https://www.linksys.com/us/support-article/?articleNum=140365#Manual. I remember somewhere I saw that there is a direct local address leading to the manual update page but I can't find it. Anyone remember it?
It's in the PR for when MR8300 was officially added: https://github.com/openwrt/openwrt/commit/a9071d02b5ab11fbd73ea42076a09f2fd8136517
Installation:
"Factory" images may be installed directly through the OEM GUI using
URL: https://ip-of-router/fwupdate.html (Typically 192.168.1.1)
Hello, what do you mean for PR? Because actually is'nt listed in release. Thanks for URL . I mean that.
I only see snapshot, no release.
Where do you find release ?
As I said, snapshot, not release...
Sorry to bump this thread, trying to install on an mr8300 and so far snapshots from (mr8300) 19.07 and 21.02 have failed with an 'error unauthorized' message and boot into stock. I'm using https://router-ip/fwupdate.html, just wondering if the ea8300 is the build i should be using or if something has changed to make the gui method inaccessible again, flashing from linksys 1.1.8.203202 which looks like it was released on 11/10/2020.
edit - apologies for the tag @cybrnook , looks like you've done the hard work on this so thought you might be interested.
edit 2 - tried a 19.07.7 ea8300 build (gui method) and failed with the same message, no real info in it, but this is it fwiw -
{
"result": "ErrorUnauthorized"
}
Not sure where you are going wrong, but I just pulled a brand new one out of the box and it worked first try with latest snapshot (and for those asking, mr8300 will be in 21.02 when it's released as I said before, you need to wait for the next major release. Hardware added after a major release has already come out normally gets added in the next major. Since MR8300 was added within the past 2 years (after ancient 19.xx) it will be in the next release).
Start on main page:
Modify URL:
Prompted to log in (admin/admin is the default):
Choose SnapShot (https://downloads.openwrt.org/snapshots/targets/ipq40xx/generic/openwrt-ipq40xx-generic-linksys_mr8300-squashfs-factory.bin):
Upload:
All Good:
Perhaps make sure your unit is factory reset so you're working with the default credentials.
3 Likes
That was it, although it would let me log in with the password i had set, the flash always failed, reset to default, login in with admin/admin and it worked perfect.
Thanks for the help @cybrnook and for your work getting the mr8300 onto OpenWrt, it's much appreciated.
1 Like
Enjoy! 
Glad we got it sorted out.
1 Like
Guy, today i've upgraded to 19.07.7 without any problem. However, the 5Ghz 100 Radio still not working. Seem same issue.
If i perform the "scan" he can found a network to associate. So seem the radio work in that way.
If useful:
Tue Mar 16 17:07:27 2021 daemon.notice netifd: radio0 (7483): cat: can't open '/var/run/wifi-phy0.pid': No such file or directory
Tue Mar 16 17:07:27 2021 daemon.notice netifd: radio0 (7483): WARNING (wireless_add_process): executable path /usr/sbin/wpad does not match process path (/proc/exe)
Tue Mar 16 17:07:27 2021 daemon.notice netifd: radio0 (7483): Command failed: Invalid argument
Tue Mar 16 17:07:27 2021 daemon.notice netifd: radio0 (7483): Device setup failed: HOSTAPD_START_FAILED
Tue Mar 16 17:07:33 2021 daemon.notice netifd: radio0 (7683): command failed: Not supported (-95)
Tue Mar 16 17:26:14 2021 daemon.notice netifd: radio0 (1144): cat: can't open '/var/run/wifi-phy0.pid': No such file or directory
Tue Mar 16 17:26:14 2021 daemon.notice netifd: radio0 (1144): WARNING (wireless_add_process): executable path /usr/sbin/wpad does not match process path (/proc/exe)
Tue Mar 16 17:26:14 2021 daemon.notice netifd: radio0 (1144): Command failed: Invalid argument
Tue Mar 16 17:26:14 2021 daemon.notice netifd: radio0 (1144): Device setup failed: HOSTAPD_START_FAILED
Tue Mar 16 17:30:04 2021 daemon.notice netifd: radio0 (2942): command failed: Not supported (-95)
Tue Mar 16 17:30:04 2021 user.notice mac80211: Failed command: iw phy phy0 set distance 0
Tue Mar 16 17:30:04 2021 daemon.err hostapd: Configuration file: /var/run/hostapd-phy0.conf
Tue Mar 16 17:30:06 2021 kern.warn kernel: [ 265.643990] ath10k_pci 0000:01:00.0: 10.4 wmi init: vdevs: 16 peers: 48 tid: 96
Tue Mar 16 17:30:06 2021 kern.warn kernel: [ 265.644033] ath10k_pci 0000:01:00.0: msdu-desc: 2500 skid: 32
Tue Mar 16 17:30:06 2021 kern.info kernel: [ 265.698397] 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'
Tue Mar 16 17:30:06 2021 kern.info kernel: [ 265.699334] ath10k_pci 0000:01:00.0: wmi print 'free: 114572 iram: 12804 sram: 29508'
Tue Mar 16 17:30:06 2021 kern.warn kernel: [ 266.001723] ath10k_pci 0000:01:00.0: Firmware lacks feature flag indicating a retry limit of > 2 is OK, requested limit: 4
Tue Mar 16 17:30:06 2021 kern.info kernel: [ 266.001932] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Tue Mar 16 17:30:06 2021 kern.info kernel: [ 266.015996] br-lan: port 2(wlan0) entered blocking state
Tue Mar 16 17:30:06 2021 kern.info kernel: [ 266.017488] br-lan: port 2(wlan0) entered disabled state
Tue Mar 16 17:30:06 2021 daemon.notice hostapd: ACS: Automatic channel selection started, this may take a bit
Tue Mar 16 17:30:06 2021 kern.info kernel: [ 266.023427] device wlan0 entered promiscuous mode
Tue Mar 16 17:30:06 2021 kern.warn kernel: [ 266.032420] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 0
Tue Mar 16 17:30:07 2021 kern.info kernel: [ 266.126131] br-lan: port 2(wlan0) entered disabled state
[ 377.478416] ath10k_pci 0000:01:00.0: 10.4 wmi init: vdevs: 16 peers: 48 tid: 96
[ 377.478463] ath10k_pci 0000:01:00.0: msdu-desc: 2500 skid: 32
[ 377.532815] 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'
[ 377.533728] ath10k_pci 0000:01:00.0: wmi print 'free: 114572 iram: 12804 sram: 29508'
[ 377.835959] ath10k_pci 0000:01:00.0: Firmware lacks feature flag indicating a retry limit of > 2 is OK, requested limit: 4
[ 377.836158] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 377.854497] br-lan: port 2(wlan0) entered blocking state
[ 377.854547] br-lan: port 2(wlan0) entered disabled state
[ 377.859307] device wlan0 entered promiscuous mode
[ 377.868121] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 0
[ 377.966522] br-lan: port 2(wlan0) entered disabled state
I was able to get the radio module working which I like because it means the hardware is okay. To make it work I went to change the country code when if I left it at "driver default" it would not work. I do not know if it is a normal fact because the other two radio modules, that is the 2.4 and the 5 bass channels, go immediately without changing any parameters. Therefore, any further details are not to be done on the radio modules of the "Qualcomm Atheros IPQ4019" but on the radio module "Qualcomm Atheros QCA9886 802.11nac" because that's what gives this kind of problem. I don't know if it's a driver problem or something but I think there is something to look at. Currently 4019 uses the "ath10k-firmware-qca4019-ct" drivers by default. I could try "ath10k-firmware-qca4019-ct-full-htt" and "ath10k-firmware-qca4019-ct-htt" but I don't know what changes between the different versions.
All this both on the 19.07.7 and on the 21.02 that I am now using and for now without problems. Besides, I didn't have to install Luci because she was already there.