Hello I am looking to put an official Openwrt onto this device. Openwrt seems to only explicitly support the A1, A2 and C1 versions. I think this would fall under the "K2P" hardware however not sure how these variants are organized.
I have a serial capture of the boot here:
https://pastebin.com/raw/YkUUF05n
Also at that point, i'm prompted with a login that I can not get past.
Any ideas or tips for this hardware?
Thank you for your time
I uploaded the image here openwrt-19.07.5-ramips to ram using the option 1 in the bootloader
1: Load system code to SDRAM via TFTP
It looks good so far and the kernel is able to boot, however encounter some sort of mtd issue when it tries to mount the rootfs
[ 4.658097] VFS: Cannot open root device "(null)" or unknown-block(31,6): error -5
[ 4.673245] Please append a correct "root=" boot option; here are the available partitions:
[ 4.689875] 1f00 192 mtdblock0
[ 4.689881] (driver?)
[ 4.702893] 1f01 64 mtdblock1
[ 4.702898] (driver?)
[ 4.715897] 1f02 64 mtdblock2
[ 4.715902] (driver?)
[ 4.728897] 1f03 320 mtdblock3
[ 4.728902] (driver?)
[ 4.741900] 1f04 15744 mtdblock4
[ 4.741905] (driver?)
[ 4.754914] 1f05 3217 mtdblock5
[ 4.754919] (driver?)
[ 4.767914] 1f06 12526 mtdblock6
[ 4.767918] (driver?)
[ 4.780917] 1f07 7808 mtdblock7
[ 4.780922] (driver?)
[ 4.793935] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,6)
[ 4.812120] Rebooting in 1 seconds..
I was hoping to see if this image could run first before flashing it, but don't think I can. This might be an issue for another thread but I'll ask..
Q: is there a way to run this in image in ram only before flashing it?
if you would like to see the full boot process of the failed boot it's here: https://pastebin.com/raw/6wa9Sg66
To load from RAM try this initramfs image.
The firmware that you've used try to load from flash.
123serge123 thank you sir! looks good, the 19.07.5 image now fully boots. However I think there is a difference in how the PCIe bus is handled ...
[ 0.574639] pull PCIe RST: RALINK_RSTCTRL = 4000000
[ 0.884666] release PCIe RST: RALINK_RSTCTRL = 7000000
[ 0.894734] ***** Xtal 40MHz *****
[ 0.901462] release PCIe RST: RALINK_RSTCTRL = 7000000
[ 0.911670] Port 0 N_FTS = 1b102800
[ 0.918565] Port 1 N_FTS = 1b102800
[ 0.925489] Port 2 N_FTS = 1b102800
[ 2.084197] PCIE1 no card, disable it(RST&CLK)
[ 2.092887] PCIE2 no card, disable it(RST&CLK)
[ 2.101686] -> 21007f2
[ 2.106533] PCIE0 enabled
[ 2.111718] PCI host bridge /pcie@1e140000 ranges:
[ 2.121245] MEM 0x0000000060000000..0x000000006fffffff
[ 2.131601] IO 0x000000001e160000..0x000000001e16ffff
[ 2.141968] PCI coherence region base: 0xbfbf8000, mask/settings: 0x60000000
[ 2.165074] mt7621_gpio 1e000600.gpio: registering 32 gpios
[ 2.176336] mt7621_gpio 1e000600.gpio: registering 32 gpios
[ 2.187531] mt7621_gpio 1e000600.gpio: registering 32 gpios
[ 2.199923] PCI host bridge to bus 0000:00
[ 2.207949] pci_bus 0000:00: root bus resource [mem 0x60000000-0x6fffffff]
[ 2.221626] pci_bus 0000:00: root bus resource [io 0xffffffff]
[ 2.233349] pci_bus 0000:00: root bus resource [??? 0x00000000 flags 0x0]
[ 2.246841] pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
[ 2.262992] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 2.279393] pci 0000:00:00.0: BAR 0: no space for [mem size 0x80000000]
[ 2.292431] pci 0000:00:00.0: BAR 0: failed to assign [mem size 0x80000000]
[ 2.306246] pci 0000:00:00.0: BAR 8: assigned [mem 0x60000000-0x600fffff]
[ 2.319715] pci 0000:00:00.0: BAR 1: assigned [mem 0x60100000-0x6010ffff]
[ 2.333206] pci 0000:01:00.0: BAR 0: assigned [mem 0x60000000-0x600fffff 64bit]
[ 2.347720] pci 0000:00:00.0: PCI bridge to [bus 01]
[ 2.357538] pci 0000:00:00.0: bridge window [mem 0x60000000-0x600fffff]
[ 2.372258] clocksource: Switched to clocksource GIC
Sure enough, no wireless devices show up which I'm suspecting is related to the above.
Full capture provided here: https://pastebin.com/raw/zLbm4Vm0
Any ideas for what could be missing?
I think that wifi drivers are missing in initramfs image. You can configure internet connection and try to install kmod-mt7615e package for test. But all your changes will be lost after reboot (initramfs image don't touch flash).
Another way is more interesting:
Thank you again 123serge123, I followed your instructions and flashed the image. Installed the module from the webgui package manager as instructed and it looks like it's running...
[ 13.361547] mt7615e 0000:01:00.0: HW/SW Version: 0x8a108a10, Build Time: 20180518100604a
[ 13.361547]
[ 14.301790] mt7615e 0000:01:00.0: N9 Firmware Version: _reserved_, Build Time: 20190103180756
[ 14.563335] mt7615e 0000:01:00.0: CR4 Firmware Version: _reserved_, Build Time: 20181207140436
(full boot log for reference here: https://pastebin.com/raw/FVudXKd3 )
Next issue I'm seeing is my android phone to connect to the AP. I think the issue is something with the DHCP negotiation however maybe it has an underlying root cause?
Sat Dec 26 07:52:40 2020 daemon.notice hostapd: wlan0: AP-STA-CONNECTED f4:60:e2:e0:f8:52
Sat Dec 26 07:52:40 2020 daemon.info hostapd: wlan0: STA f4:60:e2:e0:f8:52 RADIUS: starting accounting session AA8EBA2753AA9010
Sat Dec 26 07:52:40 2020 daemon.info hostapd: wlan0: STA f4:60:e2:e0:f8:52 WPA: pairwise key handshake completed (RSN)
Sat Dec 26 07:52:40 2020 daemon.info dnsmasq-dhcp[1810]: DHCPDISCOVER(br-lan) f4:60:e2:e0:f8:52
Sat Dec 26 07:52:40 2020 daemon.info dnsmasq-dhcp[1810]: DHCPOFFER(br-lan) 192.168.98.238 f4:60:e2:e0:f8:52
Sat Dec 26 07:52:45 2020 daemon.info dnsmasq-dhcp[1810]: DHCPDISCOVER(br-lan) f4:60:e2:e0:f8:52
Sat Dec 26 07:52:45 2020 daemon.info dnsmasq-dhcp[1810]: DHCPOFFER(br-lan) 192.168.98.238 f4:60:e2:e0:f8:52
Sat Dec 26 07:52:49 2020 daemon.info dnsmasq-dhcp[1810]: DHCPDISCOVER(br-lan) f4:60:e2:e0:f8:52
Sat Dec 26 07:52:49 2020 daemon.info dnsmasq-dhcp[1810]: DHCPOFFER(br-lan) 192.168.98.238 f4:60:e2:e0:f8:52
Sat Dec 26 07:52:56 2020 daemon.info dnsmasq-dhcp[1810]: DHCPDISCOVER(br-lan) f4:60:e2:e0:f8:52
Sat Dec 26 07:52:56 2020 daemon.info dnsmasq-dhcp[1810]: DHCPOFFER(br-lan) 192.168.98.238 f4:60:e2:e0:f8:52
Sat Dec 26 07:53:13 2020 daemon.info dnsmasq-dhcp[1810]: DHCPDISCOVER(br-lan) f4:60:e2:e0:f8:52
Sat Dec 26 07:53:13 2020 daemon.info dnsmasq-dhcp[1810]: DHCPOFFER(br-lan) 192.168.98.238 f4:60:e2:e0:f8:52
Sat Dec 26 07:53:47 2020 daemon.info dnsmasq-dhcp[1810]: DHCPDISCOVER(br-lan) f4:60:e2:e0:f8:52
Sat Dec 26 07:53:47 2020 daemon.info dnsmasq-dhcp[1810]: DHCPOFFER(br-lan) 192.168.98.238 f4:60:e2:e0:f8:52
Sat Dec 26 07:54:53 2020 daemon.info dnsmasq-dhcp[1810]: DHCPDISCOVER(br-lan) f4:60:e2:e0:f8:52
Sat Dec 26 07:54:53 2020 daemon.info dnsmasq-dhcp[1810]: DHCPOFFER(br-lan) 192.168.98.238 f4:60:e2:e0:f8:52
For what it's worth every device on the wired LAN gets assigned an IP with no issues. I don't have another 802.11ac device to test here (yet)
Your board have only one mt7615e pci-e adapter in DBDC (dual band dual client) mode but openwrt wiki says that
Unsupported Functions: Concurrent 2.4GHz and 5GHz WiFi.
Do you know if it still possible for me to use just the 5.8Ghz 802.11ac only? That is all I want from the device, but I only have 1 802.11ac device right now.
It looks like it can negotiate a connection,
Sat Dec 26 07:52:40 2020 daemon.notice hostapd: wlan0: AP-STA-CONNECTED f4:60:e2:e0:f8:52
Sat Dec 26 07:52:40 2020 daemon.info hostapd: wlan0: STA f4:60:e2:e0:f8:52 RADIUS: starting accounting session AA8EBA2753AA9010
Sat Dec 26 07:52:40 2020 daemon.info hostapd: wlan0: STA f4:60:e2:e0:f8:52 WPA: pairwise key handshake completed (RSN)
however the client device isn't accepting the DHCP offer for one reason or another. The STA device (cell phone) is reporting "Connected" then gets stuck at "Obtaining IP address from .."
I wish I had another 802.11ac device to see if the same thing happens so I could say the AP or STA is at fault.
Please let me know if any of my logic is wrong here or if more info is needed.
I'm not sure but it may be enough to change radio0 hwmode to 11a to force 5GHz. Something like:
uci set wireless.radio0.hwmode='11a'
uci set wireless.radio0.htmode='VHT'
uci set wireless.radio0.channel=36
uci commit wireless
But it's worth to try latest snapshot version. Support of mt7615e was improved in this version.