[2019-2-3]AC9华硕8M固件
本帖最后由 qqliji 于 2019-4-2 10:33 编辑抽时间整理了一下，有一定能力折腾的同学可以参考我这个过程来制作自己的固件啦！
开源地址：
https://github.com/JimLee1996/asuswrt-ac9/commits/master
1. 适配了GPIO
2. 精简了USB相关的功能（USB2.0真的很鸡肋，稳定才是关键)
3. IPv6、QiS都回来啦
4. 原汁原味，没有对web图片进行压缩等操作，并完美去除了多余的界面
5. 稳定、高效至上。通过修改makefile文件在kernel上优化，对冗余功能进行去除
6. 无线真的是TM稳如狗！
7. 有Koolproxy，采取在线下载的方式，默认关闭
8. 不开KP稳定性和原版没有任何区别
下载地址(度娘太坑了，换了蓝奏云)：
**** Hidden Message *****
有两个选择，带KP的和不带KP，压缩文件自取！
# 通过SSH连接到路由器上
# 开启Koolproxy
nvram set koolproxy_enable=1
# 只过滤视频
nvram set koolproxy_video_only=1
# 保存
nvram commit
# 无需重启，直接输入生效
kp_start
# 支持其他指令 kp_start, kp_stop, kp_restart
# 高级功能
# 8M开启jffs会报错，使用nvram投机取巧了一下，实现开机脚本
nvram set myscript_wan_start="shell command you wanna run"
nvram commit
# 命令就会开机自动运行了
关于发射功率问题
admin@(none):/tmp/home/root# wl -i eth1 txpwr_target_max
Maximum Tx Power Target (chanspec:0x1908): 26.5026.50 （2.4G功率）
admin@(none):/tmp/home/root# wl -i eth2 txpwr_target_max
Maximum Tx Power Target (chanspec:0xe29b): 24.0024.00 （5G功率）
输入上面两条命令查看是否小于此功率。比如我设置2.4G信道为1时功率只有21.5，具体自测。我2.4g信道设置的10, 5G设置的157。可作参考！
另外建议无线模式，频道带宽也作固定，不要设置为自动。
2.4G信号我没测试。如果有问题，请把无线网络-专业设置中2.4G项目里RTS门槛设置为0。 qqliji 发表于 2018-8-5 14:45
修复了一下，您再试试。
应该是能用了不过不知道最后两行啥意思还有就是我用中继模式的时候好像KP不起作用 也没办法看日志因为中继模式下不能访问路由器
May5 05:05:04 koolproxy: koolproxy v3.7.2
May5 05:05:04 koolproxy: log level=4
May5 05:05:04 koolproxy: thread count=2
May5 05:05:04 koolproxy: work path=/
May5 05:05:04 koolproxy: program path=/usr/sbin/koolproxy
May5 05:05:04 koolproxy: data path=/tmp
May5 05:05:04 koolproxy: ttl mode=0
May5 05:05:04 koolproxy: mark mode=0
May5 05:05:04 koolproxy: max fd=131070
May5 05:05:04 koolproxy: init adblock engine
May5 05:05:04 koolproxy: load adblock normal rule: /tmp/rules/koolproxy.txt
May5 05:05:04 koolproxy: WARN: load rule failed: /tmp/rules/koolproxy.txt
May5 05:05:04 koolproxy: load adblock daily rule: /tmp/rules/daily.txt
May5 05:05:04 koolproxy: WARN: load rule failed: /tmp/rules/daily.txt
May5 05:05:04 koolproxy: load adblock video rule: /tmp/rules/kp.dat
May5 05:05:04 koolproxy: WARN: load rule failed: /tmp/rules/kp.dat
May5 05:05:04 koolproxy: init https engine
May5 05:05:04 koolproxy: https engine: load_key_file /tmp/private/ca.key.pem failed: -1
May5 05:05:04 koolproxy: init https engine failed:-2, go with http mode only
May5 05:05:04 koolproxy: init proxy engine
May5 05:05:04 koolproxy: listen socket on :3000 success
May5 05:05:53 rc_service: httpd 140:notify_rc start_autodet
May5 05:06:39 rc_service: httpd 140:notify_rc restart_wan_if 0
May5 05:06:39 kernel: Attempt to kill tasklet from interrupt
May5 05:06:40 rc_service: httpd 140:notify_rc start_webs_update
May5 05:06:40 rc_service: waitting "restart_wan_if 0" via httpd ...
May5 05:06:42 pppd: pppd 2.4.7 started by admin, uid 0
May5 05:06:42 pppd: Connected to dc:d2:fc:23:62:f5 via interface eth0
May5 05:06:42 pppd: Connect: ppp0 <--> eth0
May5 05:06:45 pppd: PAP authentication succeeded
May5 05:06:45 pppd: peer from calling number DC:D2:FC:23:62:F5 authorized
May5 05:06:45 pppd: localIP address 10.37.13.61
May5 05:06:45 pppd: remote IP address 10.37.12.1
May5 05:06:45 pppd: primary DNS address 222.222.202.202
May5 05:06:45 pppd: secondary DNS address 222.222.222.222
May5 05:06:45 rc_service: ip-up 338:notify_rc start_firewall
May5 05:06:46 miniupnpd: shutting down MiniUPnPd
May5 05:06:46 nat: apply redirect rules
May5 05:06:46 rc_service: ip-up 338:notify_rc stop_upnp
May5 05:06:46 rc_service: waitting "start_firewall" via ip-up ...
May5 05:06:47 rc_service: httpd 140:notify_rc chpass
May5 05:06:47 rc_service: waitting "start_firewall" via ip-up ...
May5 05:06:47 kernel: nf_conntrack_rtsp v0.6.21 loading
May5 05:06:47 kernel: nf_nat_rtsp v0.6.21 loading
May5 05:06:47 miniupnpd: version 1.9 started
May5 05:06:47 miniupnpd: HTTP listening on port 54764
May5 05:06:47 miniupnpd: Listening for NAT-PMP/PCP traffic on port 5351
May5 05:06:48 rc_service: ip-up 338:notify_rc start_upnp
May5 05:06:48 rc_service: waitting "stop_upnp" via ip-up ...
May5 05:06:48 miniupnpd: shutting down MiniUPnPd
May5 05:06:50 rc_service: httpd 140:notify_rc restart_wireless;restart_time
May5 05:06:50 miniupnpd: version 1.9 started
May5 05:06:50 miniupnpd: HTTP listening on port 53342
May5 05:06:50 miniupnpd: Listening for NAT-PMP/PCP traffic on port 5351
May5 05:07:03 rc_service: zcip 429:notify_rc start_firewall
May5 05:07:03 rc_service: waitting "restart_wireless;restart_time" via httpd ...
May5 05:07:04 kernel: klogd: exiting
May5 05:07:04 syslogd exiting
May5 13:07:04 syslogd started: BusyBox v1.17.4
May5 13:07:04 kernel: klogd started: BusyBox v1.17.4 (2018-07-07 23:15:02 CST)
May5 13:07:05 nat: apply nat rules (/tmp/nat_rules_ppp0_eth0)
May5 13:07:05 miniupnpd: version 1.9 started
May5 13:07:05 miniupnpd: HTTP listening on port 55663
May5 13:07:05 miniupnpd: Listening for NAT-PMP/PCP traffic on port 5351
May5 13:07:05 hour monitor: daemon is starting
May5 13:07:05 hour monitor: daemon terminates
May5 05:07:06 zcip client: configured 169.254.54.210
May5 13:07:07 miniupnpd: shutting down MiniUPnPd
May5 13:07:07 nat: apply nat rules (/tmp/nat_rules_ppp0_eth0)
May5 13:07:08 miniupnpd: version 1.9 started
May5 13:07:08 miniupnpd: HTTP listening on port 45612
May5 13:07:08 miniupnpd: Listening for NAT-PMP/PCP traffic on port 5351
May5 05:07:08 WAN Connection: WAN was restored.
May5 05:07:10 ntp: start NTP update
Aug7 03:03:21 koolproxy: koolproxy v3.7.2
Aug7 03:03:21 koolproxy: log level=4
Aug7 03:03:21 koolproxy: thread count=2
Aug7 03:03:21 koolproxy: work path=/
Aug7 03:03:21 koolproxy: program path=/usr/sbin/koolproxy
Aug7 03:03:21 koolproxy: data path=/tmp
Aug7 03:03:21 koolproxy: ttl mode=0
Aug7 03:03:21 koolproxy: mark mode=0
Aug7 03:03:21 koolproxy: max fd=131070
Aug7 03:03:21 koolproxy: init adblock engine
Aug7 03:03:21 koolproxy: load adblock normal rule: /tmp/rules/koolproxy.txt
Aug7 03:03:21 koolproxy: WARN: load rule failed: /tmp/rules/koolproxy.txt
Aug7 03:03:21 koolproxy: load adblock daily rule: /tmp/rules/daily.txt
Aug7 03:03:21 koolproxy: WARN: load rule failed: /tmp/rules/daily.txt
Aug7 03:03:21 koolproxy: load adblock video rule: /tmp/rules/kp.dat
Aug7 03:03:21 koolproxy: WARN: load rule failed: /tmp/rules/kp.dat
Aug7 03:03:21 koolproxy: init https engine
Aug7 03:03:21 koolproxy: https engine: load_key_file /tmp/private/ca.key.pem failed: -1
Aug7 03:03:21 koolproxy: init https engine failed:-2, go with http mode only
Aug7 03:03:21 koolproxy: init proxy engine
Aug7 03:03:21 koolproxy: listen socket on :3000 success
Aug7 03:03:31 koolproxy: update detect: /tmp/rules/koolproxy.txt, online md5: d6521aab8b3e0f24c7c86d2d3f4e8870, local md5:
Aug7 03:03:31 koolproxy: update failed: /tmp/rules/koolproxy.txt, code: -2, online md5: d6521aab8b3e0f24c7c86d2d3f4e8870, download md5:
Aug7 03:03:31 koolproxy: update detect: /tmp/rules/daily.txt, online md5: 4b03e9ad7fadf244d78ead3c76cd4f83, local md5:
Aug7 03:03:33 koolproxy: update success: /tmp/rules/daily.txt
Aug7 03:03:34 koolproxy: update detect: /tmp/rules/kp.dat, online md5: 3476aaa4ae95feb29f56019954df1606, local md5:
Aug7 03:03:36 koolproxy: update success: /tmp/rules/kp.dat
Aug7 03:03:36 koolproxy: update detect: /usr/sbin/koolproxy, online md5: 61d352e44c5a962128a2a4a069833efc, local md5: 13105e5dadc03148048c47265e61b764
Aug7 03:03:39 koolproxy: update failed: /usr/sbin/koolproxy, code: 200, online md5: 61d352e44c5a962128a2a4a069833efc, download md5: 61d352e44c5a962128a2a4a069833efc
Aug7 03:03:39 koolproxy: reboot by rules update
Aug7 03:03:40 koolproxy: koolproxy v3.7.2
Aug7 03:03:40 koolproxy: log level=4
Aug7 03:03:40 koolproxy: thread count=2
Aug7 03:03:40 koolproxy: work path=/
Aug7 03:03:40 koolproxy: program path=/usr/sbin/koolproxy
Aug7 03:03:40 koolproxy: data path=/tmp
Aug7 03:03:40 koolproxy: ttl mode=0
Aug7 03:03:40 koolproxy: mark mode=0
Aug7 03:03:40 koolproxy: max fd=131070
Aug7 03:03:40 koolproxy: init adblock engine
Aug7 03:03:40 koolproxy: load adblock normal rule: /tmp/rules/koolproxy.txt
Aug7 03:03:40 koolproxy: WARN: load rule failed: /tmp/rules/koolproxy.txt
Aug7 03:03:40 koolproxy: load adblock daily rule: /tmp/rules/daily.txt
Aug7 03:03:40 koolproxy: load adblock video rule: /tmp/rules/kp.dat
Aug7 03:03:40 koolproxy: init https engine
Aug7 03:03:40 koolproxy: https engine: load_key_file /tmp/private/ca.key.pem failed: -1
Aug7 03:03:40 koolproxy: init https engine failed:-2, go with http mode only
Aug7 03:03:40 koolproxy: init proxy engine
Aug7 03:03:40 koolproxy: listen socket on :3000 success
Aug7 03:03:50 koolproxy: update detect: /tmp/rules/koolproxy.txt, online md5: d6521aab8b3e0f24c7c86d2d3f4e8870, local md5:
Aug7 03:03:53 koolproxy: update success: /tmp/rules/koolproxy.txt
Aug7 03:03:54 koolproxy: update detect: /usr/sbin/koolproxy, online md5: 61d352e44c5a962128a2a4a069833efc, local md5: 13105e5dadc03148048c47265e61b764
Aug7 03:03:56 koolproxy: update failed: /usr/sbin/koolproxy, code: 200, online md5: 61d352e44c5a962128a2a4a069833efc, download md5: 61d352e44c5a962128a2a4a069833efc
Aug7 03:03:56 koolproxy: reboot by rules update
Aug7 03:03:57 koolproxy: koolproxy v3.7.2
Aug7 03:03:57 koolproxy: log level=4
Aug7 03:03:57 koolproxy: thread count=2
Aug7 03:03:57 koolproxy: work path=/
Aug7 03:03:57 koolproxy: program path=/usr/sbin/koolproxy
Aug7 03:03:57 koolproxy: data path=/tmp
Aug7 03:03:57 koolproxy: ttl mode=0
Aug7 03:03:57 koolproxy: mark mode=0
Aug7 03:03:57 koolproxy: max fd=131070
Aug7 03:03:57 koolproxy: init adblock engine
Aug7 03:03:57 koolproxy: load adblock normal rule: /tmp/rules/koolproxy.txt
Aug7 03:03:59 koolproxy: load adblock daily rule: /tmp/rules/daily.txt
Aug7 03:03:59 koolproxy: load adblock video rule: /tmp/rules/kp.dat
Aug7 03:03:59 koolproxy: init https engine
Aug7 03:03:59 koolproxy: https engine: load_key_file /tmp/private/ca.key.pem failed: -1
Aug7 03:03:59 koolproxy: init https engine failed:-2, go with http mode only
Aug7 03:04:00 koolproxy: init proxy engine
Aug7 03:04:00 koolproxy: listen socket on :3000 success
Aug7 03:04:11 koolproxy: update detect: /usr/sbin/koolproxy, online md5: 61d352e44c5a962128a2a4a069833efc, local md5: 13105e5dadc03148048c47265e61b764
Aug7 03:04:14 koolproxy: update failed: /usr/sbin/koolproxy, code: 200, online md5: 61d352e44c5a962128a2a4a069833efc, download md5: 61d352e44c5a962128a2a4a069833efc
刷了27号的版本这次KP好像根本没启动
May5 13:04:56 syslogd started: BusyBox v1.17.4
May5 13:04:56 kernel: klogd started: BusyBox v1.17.4 (2018-07-07 23:15:02 CST)
May5 13:04:56 kernel: Linux version 2.6.36.4brcmarm (root@asus) (gcc version 4.5.3 (Buildroot 2012.02) ) #2 PREEMPT Sun Jul 8 00:10:34 CST 2018
May5 13:04:56 kernel: CPU: ARMv7 Processor revision 5 (ARMv7), cr=10c53c7f
May5 13:04:56 kernel: CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
May5 13:04:56 kernel: Machine: Northstar Prototype
May5 13:04:56 kernel: Ignoring unrecognised tag 0x00000000
May5 13:04:56 kernel: Memory policy: ECC disabled, Data cache writealloc
May5 13:04:56 kernel: Built 1 zonelists in Zone order, mobility grouping on.Total pages: 32512
May5 13:04:56 kernel: Kernel command line: root=/dev/mtdblock2 console=ttyS0,115200 init=/sbin/preinit earlyprintk debug
May5 13:04:56 kernel: Memory: 125588k/125588k available, 5484k reserved, 0K highmem
May5 13:04:56 kernel: Virtual kernel memory layout:
May5 13:04:56 kernel: vector: 0xffff0000 - 0xffff1000 ( 4 kB)
May5 13:04:56 kernel: fixmap: 0xfff00000 - 0xfffe0000 ( 896 kB)
May5 13:04:56 kernel: DMA : 0xf7e00000 - 0xffe00000 ( 128 MB)
May5 13:04:56 kernel: vmalloc : 0x88800000 - 0xf0000000 (1656 MB)
May5 13:04:56 kernel: lowmem: 0x80000000 - 0x88000000 ( 128 MB)
May5 13:04:56 kernel: modules : 0x7f000000 - 0x80000000 (16 MB)
May5 13:04:56 kernel: .init : 0x80008000 - 0x80038000 ( 192 kB)
May5 13:04:56 kernel: .text : 0x80038000 - 0x803cc000 (3664 kB)
May5 13:04:56 kernel: .data : 0x803e4000 - 0x804016e0 ( 118 kB)
May5 13:04:56 kernel: Mount-cache hash table entries: 512
May5 13:04:56 kernel: Found ST compatible serial flash with 128 64KB blocks; total size 8MB
May5 13:04:56 kernel: ACP (Accelerator Coherence Port) enabled
May5 13:04:56 kernel: bio: create slab <bio-0> at 0
May5 13:04:56 kernel: PCI: no core
May5 13:04:56 kernel: PCI: no core
May5 13:04:56 kernel: PCI: Fixing up bus 0
May5 13:04:56 kernel: PCI: Fixing up bus 1
May5 13:04:56 kernel: PCI: scanning bus 0 !!!
May5 13:04:56 kernel: PCI: Fixing up bus 0
May5 13:04:56 kernel: VFS: Disk quotas dquot_6.5.2
May5 13:04:56 kernel: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
May5 13:04:57 kernel: pflash: found no supported devices
May5 13:04:57 kernel: bcmsflash: squash filesystem found at block 30
May5 13:04:57 kernel: Creating 5 MTD partitions on "bcmsflash":
May5 13:04:57 kernel: 0x000000000000-0x000000040000 : "boot"
May5 13:04:57 kernel: 0x000000040000-0x0000007f0000 : "linux"
May5 13:04:57 kernel: 0x0000001e29d8-0x0000007f0000 : "rootfs"
May5 13:04:57 kernel: 0x0000007f0000-0x000000800000 : "jffs2"
May5 13:04:57 kernel: 0x0000007f0000-0x000000800000 : "nvram"
May5 13:04:57 kernel: === p p t p init ===
May5 13:04:57 kernel: Registering the dns_resolver key type
May5 13:04:57 kernel: VFS: Mounted root (squashfs filesystem) readonly on device 31:2.
May5 13:04:57 kernel: ctf: module license 'Proprietary' taints kernel.
May5 13:04:57 kernel: Disabling lock debugging due to kernel taint
May5 13:04:57 kernel: et_module_init: passivemode set to 0x0
May5 13:04:57 kernel: et_module_init: txworkq set to 0x0
May5 13:04:57 kernel: et_module_init: et_txq_thresh set to 0xce4
May5 13:04:57 kernel: et_module_init: et_rxlazy_timeout set to 0x3e8
May5 13:04:57 kernel: et_module_init: et_rxlazy_framecnt set to 0x20
May5 13:04:57 kernel: bcm_robo_enable_switch: EEE is disabled
May5 13:04:57 kernel: eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 9.10.178.61 (r667680)
May5 13:04:57 kernel: wl_module_init: passivemode set to 0x0
May5 13:04:57 kernel: wl_module_init: txworkq set to 0x0
May5 13:04:57 kernel: PCI: Enabling device 0001:01:00.0 (0140 -> 0142)
May5 13:04:57 kernel: eth1: Broadcom BCM43227 802.11 Wireless Controller 9.10.178.61 (r667680)
May5 13:04:57 kernel: eth2: Broadcom BCM43c8 802.11 Wireless Controller 9.10.178.61 (r667680)
May5 13:04:57 nat: apply redirect rules
May5 13:04:57 WAN Connection: Fail to connect with some issues.
May5 13:05:03 dnsmasq: warning: no upstream servers configured
May5 13:05:03 RT-AC1200G+: start httpd:80
May5 13:05:04 hour monitor: daemon is starting
May5 13:05:04 hour monitor: daemon terminates
May5 13:05:04 miniupnpd: version 1.9 started
May5 13:05:04 miniupnpd: HTTP listening on port 44765
May5 13:05:04 miniupnpd: Listening for NAT-PMP/PCP traffic on port 5351
May5 13:05:04 pppd: pppd 2.4.7 started by admin, uid 0
May5 13:05:04 pppd: Connected to dc:d2:fc:23:62:f5 via interface eth0
May5 13:05:04 pppd: Connect: ppp0 <--> eth0
May5 13:05:07 pppd: PAP authentication succeeded
May5 13:05:07 pppd: peer from calling number DC:D2:FC:23:62:F5 authorized
May5 13:05:08 pppd: localIP address 10.37.4.240
May5 13:05:08 pppd: remote IP address 10.37.4.1
May5 13:05:08 pppd: primary DNS address 222.222.202.202
May5 13:05:08 pppd: secondary DNS address 222.222.222.222
May5 13:05:08 rc_service: ip-up 186:notify_rc start_firewall
May5 13:05:09 miniupnpd: shutting down MiniUPnPd
May5 13:05:09 nat: apply nat rules (/tmp/nat_rules_ppp0_eth0)
May5 13:05:09 rc_service: ip-up 186:notify_rc stop_upnp
May5 13:05:09 rc_service: waitting "start_firewall" via ip-up ...
May5 13:05:10 kernel: nf_conntrack_rtsp v0.6.21 loading
May5 13:05:10 kernel: nf_nat_rtsp v0.6.21 loading
May5 13:05:10 rc_service: ip-up 186:notify_rc start_upnp
May5 13:05:10 rc_service: waitting "stop_upnp" via ip-up ...
May5 13:05:12 WAN Connection: WAN was restored.
May5 13:05:12 miniupnpd: version 1.9 started
May5 13:05:12 miniupnpd: HTTP listening on port 46700
May5 13:05:12 miniupnpd: Listening for NAT-PMP/PCP traffic on port 5351
May5 13:05:13 ntp: start NTP update
Aug1 12:12:05 rc_service: zcip 261:notify_rc start_firewall
Aug1 12:12:05 zcip client: configured 169.254.54.210
Aug1 12:12:05 miniupnpd: shutting down MiniUPnPd
Aug1 12:12:05 nat: apply nat rules (/tmp/nat_rules_ppp0_eth0)
Aug1 12:12:06 miniupnpd: version 1.9 started
Aug1 12:12:06 miniupnpd: HTTP listening on port 48313
Aug1 12:12:06 miniupnpd: Listening for NAT-PMP/PCP traffic on port 5351
Forest000 发表于 2018-7-13 21:36
AP问题解决了，我还想问一下您是怎么解决日志jffs2报错的问题和target.mak的参数设定是什么样的，谢谢。
...
jffs2的疯狂报错的问题我也发现了，原因肯定是和ROM太小导致地址无法正确映射导致的。所以，目前考虑jffs2用处不大，我就直接注释掉了。我的target.mk参数没动，我是在src/router目录下通过make menuconfig配置功能的，注意要修改src/Makefile中，有一个@cd开头的语句（总共6个） ... .config，那个语句会覆盖之前config的文件，注释掉就好。然后其他的就修改src/router/Makefile，有一些obj-y的注释掉就好了 好东西啊，谢谢楼主分享 今天刷了一个旧版梅林，现在就出了新梅林https://www.right.com.cn/forum//mobcent//app/data/phiz/default/09.png
现在就出了新梅林 本帖最后由 mjyhj 于 2018-7-8 02:22 编辑
GOOD，收藏了。
和原版信号对比如何
谢谢楼主分享谢谢楼主分享 谢谢发现小飞飞 谢谢，好东西
感谢分享，下载试试。 看看，，看看 哇，一早醒来竟然发现AC9的8M梅林更新了！辛苦了 这是好东西，梅林还是8M的，AC9看来要梅开二度了 好东西，有空试试
和之前的版本有啥区别
好啊，一直没有硬改过