Hello,
is there a way to get a openwrt release for the ASUS 4G-AC53U?
I cant find any useful Information for this router on the internet.
I only know it has a 4 core armv7 cpu. It has "ath" interfaces when i type in ifconfig.
So what can i do to get an release for this ASUS router ?
it probably already runs openwrt, just not an official version/release.
open it up, post pics of the chips, and a boot log (or if you can get it through the devices' UI).
Ok thanks. I will do my best to get these things.
Post the output of ifconfig -a , dmesg, and uname -a, please. That already gives a lot of useful info
Here the output of "uname -a" :
Linux ASUS-4G-AC53U 3.14.77 #1 SMP PREEMPT Wed Jul 29 12:16:32 CST 2020 armv7l GNU/Linux
Of "ifconfig -a"
ath0 Link encap:Ethernet HWaddr 04:D9:F5:DE:C3:B0
UP BROADCAST RUNNING MTU:1500 Metric:1
RX packets:31823 errors:0 dropped:0 overruns:0 frame:0
TX packets:87921 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:10204979 (9.7 MiB) TX bytes:58347373 (55.6 MiB)
ath1 Link encap:Ethernet HWaddr 04:D9:F5:DE:C3:B4
UP BROADCAST RUNNING MTU:1500 Metric:1
RX packets:36110 errors:0 dropped:0 overruns:0 frame:0
TX packets:85919 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:7509828 (7.1 MiB) TX bytes:45801898 (43.6 MiB)
br0 Link encap:Ethernet HWaddr 04:D9:F5:DE:C3:B4
inet addr:192.168.10.1 Bcast:192.168.10.255 Mask:255.255.255.0
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1
RX packets:103697 errors:0 dropped:0 overruns:0 frame:0
TX packets:175444 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:20863983 (19.8 MiB) TX bytes:169690144 (161.8 MiB)
eth0 Link encap:Ethernet HWaddr 04:D9:F5:DE:C3:B0
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
eth1 Link encap:Ethernet HWaddr 04:D9:F5:DE:C3:B4
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1
RX packets:27547 errors:0 dropped:0 overruns:0 frame:0
TX packets:97434 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4667905 (4.4 MiB) TX bytes:78819207 (75.1 MiB)
imq0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
NOARP MTU:16000 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:11000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
imq1 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
NOARP MTU:16000 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:11000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MULTICAST MTU:65536 Metric:1
RX packets:32016 errors:0 dropped:0 overruns:0 frame:0
TX packets:32016 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6586302 (6.2 MiB) TX bytes:6586302 (6.2 MiB)
miireg Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
[NO FLAGS] MTU:0 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
usb0 Link encap:Ethernet HWaddr 32:8F:B8:31:F6:1F
inet addr:10.131.103.99 Bcast:10.131.103.99 Mask:255.255.255.255
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:188233 errors:0 dropped:0 overruns:0 frame:0
TX packets:111685 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:173955338 (165.8 MiB) TX bytes:23055036 (21.9 MiB)
wifi0 Link encap:UNSPEC HWaddr 04-D9-F5-DE-C3-B0-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:48364 errors:0 dropped:0 overruns:0 frame:0
TX packets:87901 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:2699
RX bytes:13137038 (12.5 MiB) TX bytes:58345394 (55.6 MiB)
Interrupt:200
wifi1 Link encap:UNSPEC HWaddr 04-D9-F5-DE-C3-B4-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:40797 errors:0 dropped:0 overruns:0 frame:0
TX packets:85859 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:2699
RX bytes:7574532 (7.2 MiB) TX bytes:45788349 (43.6 MiB)
Interrupt:201
ztly56b2qw Link encap:Ethernet HWaddr E2:9F:22:87:87:6C
inet addr:172.28.28.11 Bcast:172.28.28.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:2800 Metric:1
RX packets:25750 errors:0 dropped:0 overruns:0 frame:0
TX packets:4994 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:4347550 (4.1 MiB) TX bytes:1678210 (1.5 MiB)
don't forget dmesg, if it's to long to fit in a post, post it on pastebin, and post the link.
Its too much thats why i uploaded it to google drive i hope its ok ?
pastbin is better for unformated text, but I'm sure it'll do.
do a cat /proc/mtd and cat /proc/cpuinfo as well.
cat /proc/mtd :
mtd0: 00200000 00010000 "Bootloader"
mtd1: 08000000 00020000 "UBI_DEV"
mtd2: 0005d000 0001f000 "nvram"
mtd3: 0001f000 0001f000 "Factory"
mtd4: 0001f000 0001f000 "Factory2"
mtd5: 03013000 0001f000 "linux"
mtd6: 02e0f9c0 0001f000 "rootfs"
mtd7: 03013000 0001f000 "linux2"
mtd8: 02e0f9c0 0001f000 "rootfs2"
And /proc/cpuinfo
processor : 0
model name : ARMv7 Processor rev 5 (v7l)
BogoMIPS : 96.00
Features : swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xc07
CPU revision : 5
processor : 1
model name : ARMv7 Processor rev 5 (v7l)
BogoMIPS : 96.00
Features : swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xc07
CPU revision : 5
processor : 2
model name : ARMv7 Processor rev 5 (v7l)
BogoMIPS : 96.00
Features : swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xc07
CPU revision : 5
processor : 3
model name : ARMv7 Processor rev 5 (v7l)
BogoMIPS : 96.00
Features : swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xc07
CPU revision : 5
Hardware : Qualcomm (Flattened Device Tree)
Revision : 0000
Serial : 0000000000000000
Is this enough to build a release ?
I would be happy if i dont have to open the router.
If its enough to build under which target i have to look ?
Thanks !
Probably far from it, but it'll be enough to make an assessment.
Don't expect a fw any time soon.
@daniel who among the devs could take a look, whether the device's supportable or not ... ?
Machine model: Qualcomm Technologies, Inc. IPQ40xx/AP-DK01.1-C2
so build an initramfs image for the qcom_ap-dk01.1-c1 and try to boot that from RAM using serial console and tftp.
The first attempts will probably fail and require more fiddling with the DTS etc, but that's how to start. This is real work which doesn't just magically do itself... And hardware access is required so the number of persons who can do it is quite limited.
No this is only enough to see if the hardware itself is supported or has good drivers in OpenWrt so if it's worth even trying.
from dmesg
Machine model: Qualcomm Technologies, Inc. IPQ40xx/AP-DK01.1-C2
this CPU is supported, so it is possible to make an OpenWrt firmware for this device.
But adding a new device to Openwrt still requires a developer that has opened the device and is connected with serial console to test and debug the new build.
Ok i understand. I thought it is a bit easier of course its not.
Is there a chance to find a dev who is willing in to take my router and send it back to me at my costs ? Or is this too crazy ? I think i read something like that but i'am not sure where anymore.
So i mean the router is only for my garden in which i'am living only in the summer. Soon is winter and we would have time.
I have to say sorry for my bad english, its been a while that i learned it at school.
This is more common for dd-wrt project, their developers accept device donations and add firmware for them. But there it is a donation, they don't send it back.
For OpenWrt, you can try sending an email to the OpenWrt-Devel mailing list, and any OpenWrt developer or community contributor interested can contact you through email https://openwrt.org/contact#mailing_lists
Although be careful, the mailing list is public so there may be bad people that just want to steal your device.
If someone answers your email you probably need to ask for some references on previous work they did in OpenWrt, or check if the email of the person answering you is used by a known developer/contributor.
You can search on the github repository of OpenWrt, since all contributors include their email address in the code commits, for example this https://github.com/openwrt/openwrt/commit/4a2b1ff7fbd7aa910c2e29ae43d27fdddc58b177
or you can check previous emails in the mailing list in the mailing list archives to see if they sent code through that http://lists.openwrt.org/pipermail/openwrt-devel/
Adding more information about this device: