This partially reverts commit 22c47df242.
Devices in ath79-generic like the TP-Link EAP225-Outdoor v1 are really
unstable with the non -ct Wave2 firmware and regulary crash with 100% memory
consumption when only a handful devices are connected via 5 GHz.
closesfreifunk-gluon/gluon#2827
(cherry picked from commit 4badb2702e)
targets without usb-support fail to build without this change
Co-authored-by: David Bauer <mail@david-bauer.net>
(cherry picked from commit e53308b61e)
AVM Fritz!Box 7520 and Fritz!Box 7530 use the same hardware platform and can
only be distinguished by using the urlader partition or the fritz-tffs tools
and read the ProductID (Fritz_Box_HW247).
(cherry picked from commit 5888a50cba)
The GL-MT1300 is a high-performance new generation pocket-sized router
that offers a powerful hardware and first-class cybersecurity protocol
with unique and modern design.
Specifications:
- SoC: MT7621A, Dual-Core @880MHz
- RAM: 256 MB DDR3
- Flash: 32 MB
- Ethernet: 3 x 10/100/1000: 2 x LAN + 1 x WAN
- Wireless: 1 x MT7615D Dual-Band 2.4GHz(400Mbps) + 5GHz(867Mbps)
- USB: 1 x USB 3.0 port
- Slot: 1 x MicroSD card slot
- Button: 1 x Reset button
- Switch: 1 x Mode switch
- LED: 1 x Blue LED + 1 x White LED
MAC addresses based on vendor firmware:
WAN : factory 0x4000
LAN : Mac from factory 0x4000 + 1
2.4GHz : factory 0x4
5GHz : Mac form factory 0x4 + 1
Flashing instructions:
1.Connect to one of LAN ports.
2.Set the static IP on the PC to 192.168.1.2.
3.Press the Reset button and power the device (do not release the button).
After waiting for the blue led to flash 5 times, the white led will
come on and release the button.
4.Browse the 192.168.1.1 web page and update firmware according to web
tips.
5.The blue led will flash when the firmware is being upgraded.
6.The blue led stops blinking to indicate that the firmware upgrade is
complete and U-Boot automatically starts the firmware.
The WRE6066, has in contrast to other ip40xx devices, has only 128MB system RAM.
This results in OOM situations and instability, to circumvent this we need
to use ath10k-smallbuffers.
Signed-off-by: skorpy <skorpy@frankfurt.ccc.de>
(cherry picked from commit a7a0257f6f)
Co-authored-by: skorpy <skorpy@frankfurt.ccc.de>
The device was introduced in #2332 and merged in 102a4b9350.
It appears that the autoupdater name wasn't correct and devices therefore don't receive updates.
root@64295-ggw3-20b399bb366f-132:~# lua -e 'print(require("platform_info").get_image_name())'
enterasys-ws-ap3705i
(cherry picked from commit 24955cce99)
Co-authored-by: Tom Herbers <mail@tomherbers.de>
Now that OpenWrt implements a proper fix for the stalled boots on 74kc
boards, the previous workaround can be removed.
Signed-off-by: David Bauer <mail@david-bauer.net>
(cherry picked from commit ec57f6c666)
It looks like boot hangs on an AC-Mesh for unknown reasons. The last
message seen on the console is:
[ 0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes, linear)
But interestingly, it seems like enabling AIO somehow works around this
problem. Changing any off the following options seem to have the same
effect at the moment for Linux 5.10.160+5.10.161
# CONFIG_KERNEL_AIO is not set
# CONFIG_KERNEL_CGROUPS is not set
# CONFIG_KERNEL_FANOTIFY is not set
# CONFIG_KERNEL_FHANDLE is not set
# CONFIG_KERNEL_IO_URING is not set
# CONFIG_KERNEL_IPV6_MROUTE is not set
# CONFIG_KERNEL_IPV6_SEG6_LWTUNNEL is not set
# CONFIG_KERNEL_IP_MROUTE is not set
CONFIG_KERNEL_PROC_STRIPPED=y
Just enable CONFIG_AIO until the actual problem was fixed.
Link: https://github.com/freifunk-gluon/gluon/issues/2784
(cherry picked from commit 536c771f3f)
Upstream added a standalone SPI kernel-loader which fixes the unbootable
image for the WDR4900. Thus, we can re-introduce this device to Gluon.
Signed-off-by: David Bauer <mail@david-bauer.net>
(cherry picked from commit 301443da02)
Ubiquiti Nanostation Loco M XW was renamed in v2022.1.x, but the alias to the old name was missing, so devices running the old release did not update.
(cherry picked from commit dc8055682e)
Co-authored-by: goligo <ich@malte.de>
Support for the device was (re)added in #2455
(merged as 94e04393b1)
(cherry picked from commit cd37fe5d60)
Co-authored-by: Tom Herbers <mail@tomherbers.de>
Specification:
SoC: MediaTek MT7628AN
RAM: 64MiB
Flash: 8MiB
Wifi:
- 2.4GHz: MT7628AN
- 5GHz: MT7612EN
LAN: 1x 10/100 Mbps
Flash instructions:
Flash factory image through stock firmware WEB UI.
Back to stock is possible by using TFTP and stripping down the Firmware
provided by TP-Link to a initramfs.
The flash space between 0x650000 and 0x7f0000
is blank in the stock firmware so I left it out as well.
Note: Buffalo has introduced hardware changes without bumping the
revision number. 19.07 did not support the rb-variant so there's no need
to implement a migration for the rb-variant.
Every g300nh supported by Gluon should either be the s-variant or
been flashed wrongly.
Gone due to
commit 45c84a117b ("ar71xx: drop target")
Gone due to
commit 45c84a1 ("ar71xx: drop target")
Note that it was wrongly marked as device class tiny in
commit 7fd7116e2a ("targets: add device-class flags") in the past,
the device has 64MB RAM and not 32MB.
Also, the device has no "led-running" assigned in DTS. The device has
three LEDs: "green:vpn", "green:lan" and "green:wlan". The first LED,
"green:vpn", has a "V" icon and was used to show the VPN connection
status in the vendor firmware. This LED will be used via the newly
added "led-boot" fallback in gluon-setup-mode. But will be unused
during normal operation due to the unassigned "led-running" in DTS.
Signed-off-by: Linus Lüssing <linus.luessing@c0d3.blue>
