Topic: davidc502 1900ac 3200acm builds

The content of this topic has been archived between 26 Feb 2018 and 7 May 2018. Unfortunately there are posts – most likely complete pages – missing.

Page 153 of 229

Post #3801

davidc502

3 Nov 2017, 01:33

WWTK wrote:

what does all this gobbltygook mean?

Makefile:211: *** multiple target patterns.  Stop.
Makefile:25: recipe for target 'image-prereq' failed
make[5]: *** [image-prereq] Error 2
Makefile:13: recipe for target 'prereq' failed
make[4]: *** [prereq] Error 2
target/Makefile:23: recipe for target 'target/linux/prereq' failed
make[3]: *** [target/linux/prereq] Error 2
target/Makefile:17: recipe for target '/home/david/LEDE/staging_dir/target-arm_cortex-a9+vfpv3_musl_eabi/stamp/.target_prereq' failed
make[2]: *** [/home/david/LEDE/staging_dir/target-arm_cortex-a9+vfpv3_musl_eabi/stamp/.target_prereq] Error 2
/home/david/LEDE/include/toplevel.mk:196: recipe for target 'prereq' failed
make[1]: *** [prereq] Error 2
/home/david/LEDE/include/toplevel.mk:216: recipe for target 'world' failed
make: *** [world] Error 2

I get this now even from a new clone using my old .confg or making a new one.

Start at the top... Which image are you trying to build? It's saying something about multiple targets? Also it looks like some prerequisites are failing. Check to make sure you have all the packages installed needed to build with.

Post #3802

voltara

3 Nov 2017, 04:10

Just crashed at approximately 72 hours of uptime on r5201. As with several cases posted earlier, the "timed out" errors begin 10 seconds after hostapd logs a device association (in this case an Apple device.) After about 14 minutes, the device crashed and rebooted with a "NULL pointer dereference" kernel oops in mwl_fwcmd_destroy_ba.

Fri Nov  3 02:35:29 2017 daemon.info hostapd: wlan1-1: STA bc:a9:20:xx:xx:xx IEEE 802.11: associated (aid 1)
Fri Nov  3 02:35:29 2017 daemon.notice hostapd: wlan1-1: AP-STA-CONNECTED bc:a9:20:xx:xx:xx
Fri Nov  3 02:35:29 2017 daemon.info hostapd: wlan1-1: STA bc:a9:20:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Fri Nov  3 02:36:15 2017 daemon.notice hostapd: wlan1-1: AP-STA-POLL-OK 44:1c:a8:xx:xx:xx
Fri Nov  3 02:36:39 2017 kern.err kernel: [258652.717962] ieee80211 phy1: cmd 0x9136=SetWscIE timed out
Fri Nov  3 02:36:39 2017 kern.err kernel: [258652.723478] ieee80211 phy1: return code: 0x1136
Fri Nov  3 02:36:39 2017 kern.err kernel: [258652.728122] ieee80211 phy1: timeout: 0x1136
Fri Nov  3 02:36:43 2017 kern.err kernel: [258656.786018] ieee80211 phy1: cmd 0x801d=MEMAddrAccess timed out
Fri Nov  3 02:36:43 2017 kern.err kernel: [258656.791967] ieee80211 phy1: return code: 0x001d
Fri Nov  3 02:36:43 2017 kern.err kernel: [258656.796611] ieee80211 phy1: timeout: 0x001d
Fri Nov  3 02:36:47 2017 kern.err kernel: [258660.799821] ieee80211 phy1: cmd 0x801d=MEMAddrAccess timed out
...
...
...
Fri Nov  3 02:50:07 2017 kern.err kernel: [259460.045676] ieee80211 phy1: cmd 0x801d=MEMAddrAccess timed out
Fri Nov  3 02:50:07 2017 kern.err kernel: [259460.051621] ieee80211 phy1: return code: 0x001d
Fri Nov  3 02:50:07 2017 kern.err kernel: [259460.056266] ieee80211 phy1: timeout: 0x001d
Fri Nov  3 02:50:07 2017 daemon.info hostapd: wlan1-1: STA 00:6b:9e:xx:xx:xx IEEE 802.11: deauthenticated due to local deauth request
Fri Nov  3 02:50:11 2017 kern.err kernel: [259464.061634] ieee80211 phy1: cmd 0x9111=SetNewStation timed out
Fri Nov  3 02:50:11 2017 kern.err kernel: [259464.067587] ieee80211 phy1: return code: 0x1111
Fri Nov  3 02:50:11 2017 kern.err kernel: [259464.072222] ieee80211 phy1: timeout: 0x1111
Fri Nov  3 02:50:11 2017 daemon.info hostapd: wlan1-1: STA d0:57:7b:xx:xx:xx IEEE 802.11: deauthenticated due to local deauth request
Fri Nov  3 02:50:11 2017 kern.alert kernel: [259464.131392] Unable to handle kernel NULL pointer dereference at virtual address 0000000c
Fri Nov  3 02:50:11 2017 kern.alert kernel: [259464.139663] pgd = d45a0000
Fri Nov  3 02:50:11 2017 kern.alert kernel: [259464.142467] [0000000c] *pgd=14857831, *pte=00000000, *ppte=00000000
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.148895] Internal error: Oops: 17 [#1] SMP ARM
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.153703] Modules linked in: pppoe ppp_async pppox ppp_generic nf_nat_pptp nf_conntrack_pptp nf_conntrack_ipv6 mwlwifi mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE ftdi_sio cfg80211 xt_time xt_tcpudp xt_tcpmss xt_statistic xt_state xt_recent xt_policy xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_hl xt_helper xt_esp xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_connbytes xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_HL xt_DSCP xt_CT xt_CLFri Nov  3 02:50:11 2017 kern.warn kernel: [259464.225963]  nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_tftp nf_conntrack_snmp nf_conntrack_sip nf_conntrack_rtcache nf_conntrack_proto_gre nf_conntrack_irc nf_conntrack_h323 nf_conntrack_broadcast ts_kmp nf_conntrack_amanda iptable_mangle iptable_filter ipt_ah ipt_ECN ip_tables hidp hci_uart crc_ccitt compat btusb btmrvl_sdio btmrvl btintel bnep bluetooth fuse sch_cake em_nbyte sch_dsmark sch_pie sch_codel sch_gred act_ipt sch_teql cls_basic sch_prio em_meta Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.341302] CPU: 0 PID: 4460 Comm: hostapd Not tainted 4.9.58 #0
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.347419] Hardware name: Marvell Armada 380/385 (Device Tree)
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.353449] task: dddd4000 task.stack: d4520000
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.358091] PC is at mwl_fwcmd_destroy_ba+0x98/0xf4 [mwlwifi]
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.363950] LR is at mwl_fwcmd_destroy_ba+0x34/0xf4 [mwlwifi]
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.369806] pc : [<bf4f0624>]    lr : [<bf4f05c0>]    psr: 60000013
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.369806] sp : d4521c80  ip : 00000000  fp : 00000014
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.381504] r10: d94d0000  r9 : d94d0048  r8 : d94d0054
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.386836] r7 : d94e1620  r6 : d94e2924  r5 : 00000000  r4 : d94c0000
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.393476] r3 : 00000000  r2 : 00000002  r1 : 00000000  r0 : 00000000
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.400116] Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment none
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.407366] Control: 10c5387d  Table: 145a004a  DAC: 00000051
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.413221] Process hostapd (pid: 4460, stack limit = 0xd4520210)
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.419424] Stack: (0xd4521c80 to 0xd4522000)
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.423886] 1c80: d94d0054 00000007 d2d495e8 d94e45e0 d94e0be0 bf4f0ac8 d2d495e8 d94e1620
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.432184] 1ca0: d94e0be0 d4ad1714 d4530ce0 dd889000 c064ca40 bf4ebb94 d2d49000 00000002
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.440483] 1cc0: 00000001 d4ad1714 d9544f00 dd889000 c064ca40 bf47ec98 d94e0be0 d45304c0
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.448782] 1ce0: d2d49000 bf4812dc 00000002 00000002 d2d49000 d94e0be0 d45304c0 bf482270
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.457080] 1d00: d2d49000 00000000 00000000 d2d49000 d4ad1720 bf4823bc d45304c0 00000454
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.465379] 1d20: d4ad1720 bf482434 d94e0000 d4530000 d4521d5c bf4320dc d4ad1720 0002000c
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.473677] 1d40: 00000000 bf456f10 bf44d6c8 c03ceacc bf44cf8e d9544f00 d4ad9c00 59f956e8
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.481975] 1d60: 00000af7 d4ad1700 d4ad1710 d4ad1714 dd889000 c064ca40 d94e0000 d4530000
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.490273] 1d80: d4521da0 d4ad1700 d9544f00 c03ce824 d4ad9c00 d4521dcc 00000000 00000008
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.498571] 1da0: 00000000 c03cde00 c064e864 d9544f00 d9544f00 c03ce810 df4ba400 00000028
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.506869] 1dc0: d9544f00 c03cd804 d4ad9c00 7fffffff 00000000 d9544f00 00000000 d4521f68
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.515168] 1de0: 00000028 d4ad9c00 00000000 c03cdc70 00000000 c02226ec 00000028 d4a9df40
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.523466] 1e00: 00000000 0000116c 00000000 00000000 00000001 d4521f68 00000000 d4521e8c
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.531764] 1e20: df293e00 00000000 c0628fc8 00000000 00000000 c03872bc d4521f68 c038784c
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.540062] 1e40: 00000000 00000000 00000000 0030d020 00000028 bef53c54 00000000 d4521eb4
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.548361] 1e60: df293800 c0387a44 c0624dc0 00000000 bef53cac 0030d020 00004000 00000000
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.556659] 1e80: ffffffff ffffffff 301fbf68 00000000 00000000 c0628fc8 df293b00 00000000
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.564957] 1ea0: 00000000 00000000 bef53c48 00000010 00000000 00000000 00000000 00000020
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.573254] 1ec0: dfbdfdf0 00000075 00000000 bef537e4 00000075 00000000 00000000 00000001
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.581552] 1ee0: 00000000 00000000 d4521ed4 00000000 d38f898c 00000000 00000000 00000000
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.589849] 1f00: dddd4000 c005ab48 d4521f08 d4521f08 df401100 d38f8900 d38e6dd0 00000000
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.598148] 1f20: df401580 d38e6dd0 f8897278 0004093a 00000000 df293e00 bef53c38 00000000
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.606445] 1f40: 00000128 c000ef04 d4520000 00000000 b6ebf8c0 c03885e8 00000000 00000000
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.614744] 1f60: 00000000 fffffff7 d4521eac 0000000c 00000001 00000000 00000000 d4521e54
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.623042] 1f80: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.631340] 1fa0: b6f6910c c000ed40 00000000 00000000 00000005 bef53c38 00000000 00000000
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.639638] 1fc0: 00000000 00000000 b6f6910c 00000128 000aae10 00000000 000240f8 b6ebf8c0
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.647936] 1fe0: bef53be0 bef53bcc b6f3fecc b6f3f398 60000010 00000005 00000000 00000000
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.656279] [<bf4f0624>] (mwl_fwcmd_destroy_ba [mwlwifi]) from [<bf4f0ac8>] (mwl_fwcmd_del_sta_streams+0x1d4/0x330 [mwlwifi])
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.667724] [<bf4f0ac8>] (mwl_fwcmd_del_sta_streams [mwlwifi]) from [<bf4ebb94>] (mwl_mac80211_sta_remove+0x38/0x1c4 [mwlwifi])
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.679368] [<bf4ebb94>] (mwl_mac80211_sta_remove [mwlwifi]) from [<bf47ec98>] (drv_sta_state+0x16c/0x184 [mac80211])
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.690150] [<bf47ec98>] (drv_sta_state [mac80211]) from [<bf4812dc>] (sta_info_move_state+0xbc/0x1d0 [mac80211])
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.700571] [<bf4812dc>] (sta_info_move_state [mac80211]) from [<bf482270>] (sta_set_sinfo+0x954/0xa80 [mac80211])
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.711078] [<bf482270>] (sta_set_sinfo [mac80211]) from [<bf4823bc>] (__sta_info_destroy+0x20/0x28 [mac80211])
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.721325] [<bf4823bc>] (__sta_info_destroy [mac80211]) from [<bf482434>] (sta_info_destroy_addr_bss+0x2c/0x44 [mac80211])
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.732615] [<bf482434>] (sta_info_destroy_addr_bss [mac80211]) from [<bf4320dc>] (nl80211_del_station+0xe8/0xf0 [cfg80211])
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.743991] [<bf4320dc>] (nl80211_del_station [cfg80211]) from [<c03ceacc>] (genl_rcv_msg+0x2a8/0x330)
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.753425] [<c03ceacc>] (genl_rcv_msg) from [<c03cde00>] (netlink_rcv_skb+0x58/0xb4)
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.761376] [<c03cde00>] (netlink_rcv_skb) from [<c03ce810>] (genl_rcv+0x20/0x34)
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.768977] [<c03ce810>] (genl_rcv) from [<c03cd804>] (netlink_unicast+0x13c/0x200)
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.776753] [<c03cd804>] (netlink_unicast) from [<c03cdc70>] (netlink_sendmsg+0x2f0/0x30c)
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.785139] [<c03cdc70>] (netlink_sendmsg) from [<c03872bc>] (sock_sendmsg+0x14/0x24)
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.793088] [<c03872bc>] (sock_sendmsg) from [<c038784c>] (___sys_sendmsg+0x184/0x228)
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.801125] [<c038784c>] (___sys_sendmsg) from [<c03885e8>] (__sys_sendmsg+0x40/0x64)
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.809077] [<c03885e8>] (__sys_sendmsg) from [<c000ed40>] (ret_fast_syscall+0x0/0x3c)
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.817115] Code: e5840010 e5d81004 e5c41014 e598c000 (e59c300c)
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.823332] ---[ end trace 3fd7f24e0369665a ]---

Post #3803

steel_rat

3 Nov 2017, 08:59

davidc502 wrote:

WWTK wrote:
what does all this gobbltygook mean?
Makefile:211: *** multiple target patterns.  Stop.
Makefile:25: recipe for target 'image-prereq' failed
make[5]: *** [image-prereq] Error 2
Makefile:13: recipe for target 'prereq' failed
make[4]: *** [prereq] Error 2
target/Makefile:23: recipe for target 'target/linux/prereq' failed
make[3]: *** [target/linux/prereq] Error 2
target/Makefile:17: recipe for target '/home/david/LEDE/staging_dir/target-arm_cortex-a9+vfpv3_musl_eabi/stamp/.target_prereq' failed
make[2]: *** [/home/david/LEDE/staging_dir/target-arm_cortex-a9+vfpv3_musl_eabi/stamp/.target_prereq] Error 2
/home/david/LEDE/include/toplevel.mk:196: recipe for target 'prereq' failed
make[1]: *** [prereq] Error 2
/home/david/LEDE/include/toplevel.mk:216: recipe for target 'world' failed
make: *** [world] Error 2
I get this now even from a new clone using my old .confg or making a new one.
Start at the top... Which image are you trying to build? It's saying something about multiple targets? Also it looks like some prerequisites are failing. Check to make sure you have all the packages installed needed to build with.

Hello
After "git pull" I have this error too.
My router WRT3200ACM

Post #3804

davidc502

3 Nov 2017, 13:06

voltara wrote:

Fri Nov  3 02:35:29 2017 daemon.info hostapd: wlan1-1: STA bc:a9:20:xx:xx:xx IEEE 802.11: associated (aid 1)
Fri Nov  3 02:35:29 2017 daemon.notice hostapd: wlan1-1: AP-STA-CONNECTED bc:a9:20:xx:xx:xx
Fri Nov  3 02:35:29 2017 daemon.info hostapd: wlan1-1: STA bc:a9:20:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Fri Nov  3 02:36:15 2017 daemon.notice hostapd: wlan1-1: AP-STA-POLL-OK 44:1c:a8:xx:xx:xx
Fri Nov  3 02:36:39 2017 kern.err kernel: [258652.717962] ieee80211 phy1: cmd 0x9136=SetWscIE timed out
Fri Nov  3 02:36:39 2017 kern.err kernel: [258652.723478] ieee80211 phy1: return code: 0x1136
Fri Nov  3 02:36:39 2017 kern.err kernel: [258652.728122] ieee80211 phy1: timeout: 0x1136
Fri Nov  3 02:36:43 2017 kern.err kernel: [258656.786018] ieee80211 phy1: cmd 0x801d=MEMAddrAccess timed out
Fri Nov  3 02:36:43 2017 kern.err kernel: [258656.791967] ieee80211 phy1: return code: 0x001d
Fri Nov  3 02:36:43 2017 kern.err kernel: [258656.796611] ieee80211 phy1: timeout: 0x001d
Fri Nov  3 02:36:47 2017 kern.err kernel: [258660.799821] ieee80211 phy1: cmd 0x801d=MEMAddrAccess timed out
...
...
...
Fri Nov  3 02:50:07 2017 kern.err kernel: [259460.045676] ieee80211 phy1: cmd 0x801d=MEMAddrAccess timed out
Fri Nov  3 02:50:07 2017 kern.err kernel: [259460.051621] ieee80211 phy1: return code: 0x001d
Fri Nov  3 02:50:07 2017 kern.err kernel: [259460.056266] ieee80211 phy1: timeout: 0x001d
Fri Nov  3 02:50:07 2017 daemon.info hostapd: wlan1-1: STA 00:6b:9e:xx:xx:xx IEEE 802.11: deauthenticated due to local deauth request
Fri Nov  3 02:50:11 2017 kern.err kernel: [259464.061634] ieee80211 phy1: cmd 0x9111=SetNewStation timed out
Fri Nov  3 02:50:11 2017 kern.err kernel: [259464.067587] ieee80211 phy1: return code: 0x1111
Fri Nov  3 02:50:11 2017 kern.err kernel: [259464.072222] ieee80211 phy1: timeout: 0x1111
Fri Nov  3 02:50:11 2017 daemon.info hostapd: wlan1-1: STA d0:57:7b:xx:xx:xx IEEE 802.11: deauthenticated due to local deauth request
Fri Nov  3 02:50:11 2017 kern.alert kernel: [259464.131392] Unable to handle kernel NULL pointer dereference at virtual address 0000000c
Fri Nov  3 02:50:11 2017 kern.alert kernel: [259464.139663] pgd = d45a0000
Fri Nov  3 02:50:11 2017 kern.alert kernel: [259464.142467] [0000000c] *pgd=14857831, *pte=00000000, *ppte=00000000
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.148895] Internal error: Oops: 17 [#1] SMP ARM
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.153703] Modules linked in: pppoe ppp_async pppox ppp_generic nf_nat_pptp nf_conntrack_pptp nf_conntrack_ipv6 mwlwifi mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE ftdi_sio cfg80211 xt_time xt_tcpudp xt_tcpmss xt_statistic xt_state xt_recent xt_policy xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_hl xt_helper xt_esp xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_connbytes xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_HL xt_DSCP xt_CT xt_CLFri Nov  3 02:50:11 2017 kern.warn kernel: [259464.225963]  nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_tftp nf_conntrack_snmp nf_conntrack_sip nf_conntrack_rtcache nf_conntrack_proto_gre nf_conntrack_irc nf_conntrack_h323 nf_conntrack_broadcast ts_kmp nf_conntrack_amanda iptable_mangle iptable_filter ipt_ah ipt_ECN ip_tables hidp hci_uart crc_ccitt compat btusb btmrvl_sdio btmrvl btintel bnep bluetooth fuse sch_cake em_nbyte sch_dsmark sch_pie sch_codel sch_gred act_ipt sch_teql cls_basic sch_prio em_meta Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.341302] CPU: 0 PID: 4460 Comm: hostapd Not tainted 4.9.58 #0
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.347419] Hardware name: Marvell Armada 380/385 (Device Tree)
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.353449] task: dddd4000 task.stack: d4520000
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.358091] PC is at mwl_fwcmd_destroy_ba+0x98/0xf4 [mwlwifi]
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.363950] LR is at mwl_fwcmd_destroy_ba+0x34/0xf4 [mwlwifi]
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.369806] pc : [<bf4f0624>]    lr : [<bf4f05c0>]    psr: 60000013
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.369806] sp : d4521c80  ip : 00000000  fp : 00000014
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.381504] r10: d94d0000  r9 : d94d0048  r8 : d94d0054
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.386836] r7 : d94e1620  r6 : d94e2924  r5 : 00000000  r4 : d94c0000
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.393476] r3 : 00000000  r2 : 00000002  r1 : 00000000  r0 : 00000000
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.400116] Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment none
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.407366] Control: 10c5387d  Table: 145a004a  DAC: 00000051
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.413221] Process hostapd (pid: 4460, stack limit = 0xd4520210)
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.419424] Stack: (0xd4521c80 to 0xd4522000)
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.423886] 1c80: d94d0054 00000007 d2d495e8 d94e45e0 d94e0be0 bf4f0ac8 d2d495e8 d94e1620
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.432184] 1ca0: d94e0be0 d4ad1714 d4530ce0 dd889000 c064ca40 bf4ebb94 d2d49000 00000002
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.440483] 1cc0: 00000001 d4ad1714 d9544f00 dd889000 c064ca40 bf47ec98 d94e0be0 d45304c0
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.448782] 1ce0: d2d49000 bf4812dc 00000002 00000002 d2d49000 d94e0be0 d45304c0 bf482270
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.457080] 1d00: d2d49000 00000000 00000000 d2d49000 d4ad1720 bf4823bc d45304c0 00000454
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.465379] 1d20: d4ad1720 bf482434 d94e0000 d4530000 d4521d5c bf4320dc d4ad1720 0002000c
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.473677] 1d40: 00000000 bf456f10 bf44d6c8 c03ceacc bf44cf8e d9544f00 d4ad9c00 59f956e8
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.481975] 1d60: 00000af7 d4ad1700 d4ad1710 d4ad1714 dd889000 c064ca40 d94e0000 d4530000
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.490273] 1d80: d4521da0 d4ad1700 d9544f00 c03ce824 d4ad9c00 d4521dcc 00000000 00000008
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.498571] 1da0: 00000000 c03cde00 c064e864 d9544f00 d9544f00 c03ce810 df4ba400 00000028
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.506869] 1dc0: d9544f00 c03cd804 d4ad9c00 7fffffff 00000000 d9544f00 00000000 d4521f68
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.515168] 1de0: 00000028 d4ad9c00 00000000 c03cdc70 00000000 c02226ec 00000028 d4a9df40
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.523466] 1e00: 00000000 0000116c 00000000 00000000 00000001 d4521f68 00000000 d4521e8c
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.531764] 1e20: df293e00 00000000 c0628fc8 00000000 00000000 c03872bc d4521f68 c038784c
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.540062] 1e40: 00000000 00000000 00000000 0030d020 00000028 bef53c54 00000000 d4521eb4
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.548361] 1e60: df293800 c0387a44 c0624dc0 00000000 bef53cac 0030d020 00004000 00000000
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.556659] 1e80: ffffffff ffffffff 301fbf68 00000000 00000000 c0628fc8 df293b00 00000000
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.564957] 1ea0: 00000000 00000000 bef53c48 00000010 00000000 00000000 00000000 00000020
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.573254] 1ec0: dfbdfdf0 00000075 00000000 bef537e4 00000075 00000000 00000000 00000001
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.581552] 1ee0: 00000000 00000000 d4521ed4 00000000 d38f898c 00000000 00000000 00000000
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.589849] 1f00: dddd4000 c005ab48 d4521f08 d4521f08 df401100 d38f8900 d38e6dd0 00000000
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.598148] 1f20: df401580 d38e6dd0 f8897278 0004093a 00000000 df293e00 bef53c38 00000000
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.606445] 1f40: 00000128 c000ef04 d4520000 00000000 b6ebf8c0 c03885e8 00000000 00000000
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.614744] 1f60: 00000000 fffffff7 d4521eac 0000000c 00000001 00000000 00000000 d4521e54
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.623042] 1f80: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.631340] 1fa0: b6f6910c c000ed40 00000000 00000000 00000005 bef53c38 00000000 00000000
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.639638] 1fc0: 00000000 00000000 b6f6910c 00000128 000aae10 00000000 000240f8 b6ebf8c0
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.647936] 1fe0: bef53be0 bef53bcc b6f3fecc b6f3f398 60000010 00000005 00000000 00000000
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.656279] [<bf4f0624>] (mwl_fwcmd_destroy_ba [mwlwifi]) from [<bf4f0ac8>] (mwl_fwcmd_del_sta_streams+0x1d4/0x330 [mwlwifi])
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.667724] [<bf4f0ac8>] (mwl_fwcmd_del_sta_streams [mwlwifi]) from [<bf4ebb94>] (mwl_mac80211_sta_remove+0x38/0x1c4 [mwlwifi])
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.679368] [<bf4ebb94>] (mwl_mac80211_sta_remove [mwlwifi]) from [<bf47ec98>] (drv_sta_state+0x16c/0x184 [mac80211])
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.690150] [<bf47ec98>] (drv_sta_state [mac80211]) from [<bf4812dc>] (sta_info_move_state+0xbc/0x1d0 [mac80211])
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.700571] [<bf4812dc>] (sta_info_move_state [mac80211]) from [<bf482270>] (sta_set_sinfo+0x954/0xa80 [mac80211])
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.711078] [<bf482270>] (sta_set_sinfo [mac80211]) from [<bf4823bc>] (__sta_info_destroy+0x20/0x28 [mac80211])
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.721325] [<bf4823bc>] (__sta_info_destroy [mac80211]) from [<bf482434>] (sta_info_destroy_addr_bss+0x2c/0x44 [mac80211])
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.732615] [<bf482434>] (sta_info_destroy_addr_bss [mac80211]) from [<bf4320dc>] (nl80211_del_station+0xe8/0xf0 [cfg80211])
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.743991] [<bf4320dc>] (nl80211_del_station [cfg80211]) from [<c03ceacc>] (genl_rcv_msg+0x2a8/0x330)
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.753425] [<c03ceacc>] (genl_rcv_msg) from [<c03cde00>] (netlink_rcv_skb+0x58/0xb4)
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.761376] [<c03cde00>] (netlink_rcv_skb) from [<c03ce810>] (genl_rcv+0x20/0x34)
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.768977] [<c03ce810>] (genl_rcv) from [<c03cd804>] (netlink_unicast+0x13c/0x200)
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.776753] [<c03cd804>] (netlink_unicast) from [<c03cdc70>] (netlink_sendmsg+0x2f0/0x30c)
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.785139] [<c03cdc70>] (netlink_sendmsg) from [<c03872bc>] (sock_sendmsg+0x14/0x24)
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.793088] [<c03872bc>] (sock_sendmsg) from [<c038784c>] (___sys_sendmsg+0x184/0x228)
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.801125] [<c038784c>] (___sys_sendmsg) from [<c03885e8>] (__sys_sendmsg+0x40/0x64)
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.809077] [<c03885e8>] (__sys_sendmsg) from [<c000ed40>] (ret_fast_syscall+0x0/0x3c)
Fri Nov  3 02:50:11 2017 kern.emerg kernel: [259464.817115] Code: e5840010 e5d81004 e5c41014 e598c000 (e59c300c)
Fri Nov  3 02:50:11 2017 kern.warn kernel: [259464.823332] ---[ end trace 3fd7f24e0369665a ]---

I see this in the beginning of the log.

Fri Nov  3 02:50:11 2017 kern.err kernel: [259464.061634] ieee80211 phy1: cmd 0x9111=SetNewStation timed out

There should be a fix soon for the issue.

Post #3805

rainkinz

3 Nov 2017, 13:49

Just to confirm the issue with the timeouts, e.g.:

Fri Nov  3 02:50:11 2017 kern.err kernel: [259464.061634] ieee80211 phy1: cmd 0x9111=SetNewStation timed out

Is only happening to the 3200acm's right? I have a 1900acv2 and looking to upgrade.

Thanks!

Post #3806

anymouse617

3 Nov 2017, 14:59

Just wanted to chime in that I've been running the latest image on ACS v2 and have had no issues

Post #3807

davidc502

3 Nov 2017, 15:08

rainkinz wrote:

Just to confirm the issue with the timeouts, e.g.:
Fri Nov  3 02:50:11 2017 kern.err kernel: [259464.061634] ieee80211 phy1: cmd 0x9111=SetNewStation timed out
Is only happening to the 3200acm's right? I have a 1900acv2 and looking to upgrade.
Thanks!

Correct, the 3200acm is affected at this time. However, this issue wouldn't stop me from upgrading the hardware to the 3200acm.

Post #3808

WildByDesign

3 Nov 2017, 17:39

WRT3200ACM has received a new firmware update from Linksys.

Ver. 1.0.6.184351
Latest Date: 10/27/2017

Release Notes: http://downloads.linksys.com/downloads/ … 184351.txt

Firmware version:    1.0.6.184351
Release date:        October 27, 2017

- Integrated WLAN driver v9.1.1.4 and FW v9.3.1.2
- Added support for Winbond and MXIC flash
- Fixed VPN access over PPTP
- General bug fixes

Is anyone in the position to be able to try this firmware out to determine whether or not is has a newer firmware version or anything interesting?

I was not able to extract the image file using 7-Zip or mount the image to get more information from it. And also not in the position to flash the router back to Linksys at the moment for experimentation as I prefer to stick just to LEDE.

Thank you for your time. Cheers!

Post #3809

WWTK

3 Nov 2017, 22:28

davidc502 wrote:

WWTK wrote:
what does all this gobbltygook mean?
Makefile:211: *** multiple target patterns.  Stop.
Makefile:25: recipe for target 'image-prereq' failed
make[5]: *** [image-prereq] Error 2
Makefile:13: recipe for target 'prereq' failed
make[4]: *** [prereq] Error 2
target/Makefile:23: recipe for target 'target/linux/prereq' failed
make[3]: *** [target/linux/prereq] Error 2
target/Makefile:17: recipe for target '/home/david/LEDE/staging_dir/target-arm_cortex-a9+vfpv3_musl_eabi/stamp/.target_prereq' failed
make[2]: *** [/home/david/LEDE/staging_dir/target-arm_cortex-a9+vfpv3_musl_eabi/stamp/.target_prereq] Error 2
/home/david/LEDE/include/toplevel.mk:196: recipe for target 'prereq' failed
make[1]: *** [prereq] Error 2
/home/david/LEDE/include/toplevel.mk:216: recipe for target 'world' failed
make: *** [world] Error 2
nevermind, looks like they fixed it.
I get this now even from a new clone using my old .confg or making a new one.
Start at the top... Which image are you trying to build? It's saying something about multiple targets? Also it looks like some prerequisites are failing. Check to make sure you have all the packages installed needed to build with.

The multiple targets message is the first one right after trying to build even clean from git pull and update and install feeds. using my old config or making a new one gave the same result.
everything but the mvbe targets would build OK. all the 1900 and 3200 build would fail.

(Last edited by WWTK on 3 Nov 2017, 22:32)

Post #3810

Villeneuve

3 Nov 2017, 22:31

The fix is in for the commit that broke things yesterday.

Post #3811

tapper

3 Nov 2017, 23:44

- Added support for Winbond and MXIC flash
This could mien that there will be wrt3200acm with new flash chips hitting the streets. When this happened with the c7 there was some bricks.

Post #3812

bill1228

4 Nov 2017, 05:04

Watching Netflix tonight and had the 5GHz drop twice. Running r5201 on my wrt3200. One time was when I was trying to get to the Amazon Fire TV home screen. Got message of no Internet and popped up the wireless setting page. Showed connected, but no Internet soon followed by connected and Internet available. Comcast has not blown down their firmware on to my modem yet so was able to look at logs. Modem did not go down or loose Internet connection. Had similar issue with r5113. Do not have this issue with DD-WRT latest, r33607. Was running r5201 to see if it was safe for me to come back. Guess not. Will be reinstalling DD-WRT tomorrow when I get a window.

(Last edited by bill1228 on 4 Nov 2017, 17:10)

Post #3813

davidc502

4 Nov 2017, 15:53

bill1228 wrote:

Watching Netflix tonight and had the 5GHz drop twice. Running r5201 on my wrt3200. One time was when I was trying to get to the Amazon Fire TV home screen. Got message of no Internet and popped up the wireless setting page. Showed connected, but no Internet soon followed by connected and Internet available. Comcast has blown down their firmware on to my modem yet so was able to look at logs. Modem did not go down or loose Internet connection. Had similar issue with r5113. Do not have this issue with DD-WRT latest, r33607. Was running r5201 to see if it was safe for me to come back. Guess not. Will be reinstalling DD-WRT tomorrow when I get a window.

Thanks Bill. This is a known issue, and we have yet to post that it has been fixed. From what I understand, yuhhaurlin is working to correct the problem.

Post #3814

bill1228

4 Nov 2017, 17:14

davidc502 wrote:

bill1228 wrote:
Watching Netflix tonight and had the 5GHz drop twice. Running r5201 on my wrt3200. One time was when I was trying to get to the Amazon Fire TV home screen. Got message of no Internet and popped up the wireless setting page. Showed connected, but no Internet soon followed by connected and Internet available. Comcast has not blown down their firmware on to my modem yet so was able to look at logs. Modem did not go down or loose Internet connection. Had similar issue with r5113. Do not have this issue with DD-WRT latest, r33607. Was running r5201 to see if it was safe for me to come back. Guess not. Will be reinstalling DD-WRT tomorrow when I get a window.
Thanks Bill. This is a known issue, and we have yet to post that it has been fixed. From what I understand, yuhhaurlin is working to correct the problem.

Thanks, David. That is what I was thinking. Not sure why I do not have the same issue when running DD-WRT. Brainslayer is incorporating the same firmware version and wireless driver version as LEDE. Have run his latest for days and no issues and there is a teen who has texted me when I am at the store that there are wireless issues.
So I would know if I did not experience myself.

(Last edited by bill1228 on 4 Nov 2017, 17:15)

Post #3815

davidc502

4 Nov 2017, 17:26

bill1228 wrote:

davidc502 wrote:
bill1228 wrote:
Watching Netflix tonight and had the 5GHz drop twice. Running r5201 on my wrt3200. One time was when I was trying to get to the Amazon Fire TV home screen. Got message of no Internet and popped up the wireless setting page. Showed connected, but no Internet soon followed by connected and Internet available. Comcast has not blown down their firmware on to my modem yet so was able to look at logs. Modem did not go down or loose Internet connection. Had similar issue with r5113. Do not have this issue with DD-WRT latest, r33607. Was running r5201 to see if it was safe for me to come back. Guess not. Will be reinstalling DD-WRT tomorrow when I get a window.
Thanks Bill. This is a known issue, and we have yet to post that it has been fixed. From what I understand, yuhhaurlin is working to correct the problem.
Thanks, David. That is what I was thinking. Not sure why I do not have the same issue when running DD-WRT. Brainslayer is incorporating the same firmware version and wireless driver version as LEDE. Have run his latest for days and no issues and there is a teen who has texted me when I am at the store that there are wireless issues.
So I would know if I did not experience myself.

Well, if everything is the same (packages/drivers etc) they don't seem to be telling anyone how they are doing it, specifically yuhhaurlin Otherwise the fix would have been in already. So, something is different or not.

(Last edited by davidc502 on 4 Nov 2017, 17:29)

Post #3816

adri

4 Nov 2017, 18:07

anymouse617 wrote:

Just wanted to chime in that I've been running the latest image on ACS v2 and have had no issues

Same here, no issues with R5201 on a WRT1900 ACS V1.

Post #3817

kirkgbr

4 Nov 2017, 18:38

If anyone is interested, Sams Club has the wrt3200acm on sale fro $149

Post #3818

bill1228

4 Nov 2017, 20:20

davidc502 wrote:

bill1228 wrote:
davidc502 wrote:
Thanks Bill. This is a known issue, and we have yet to post that it has been fixed. From what I understand, yuhhaurlin is working to correct the problem.
Thanks, David. That is what I was thinking. Not sure why I do not have the same issue when running DD-WRT. Brainslayer is incorporating the same firmware version and wireless driver version as LEDE. Have run his latest for days and no issues and there is a teen who has texted me when I am at the store that there are wireless issues.
So I would know if I did not experience myself.
Well, if everything is the same (packages/drivers etc) they don't seem to be telling anyone how they are doing it, specifically yuhhaurlin Otherwise the fix would have been in already. So, something is different or not.

Just a FYI. This is the firmware and wireless driver versions on DD-WRT r33607. I think these are the same as what you are using, forgot to check before I reinstalled DD-WRT, but previously when I checked they were the same.

cat /sys/kernel/debug/ieee80211/phy0/mwlwifi/info

driver name: mwlwifi
chip type: 88W8964
hw version: 7
driver version: 10.3.4.0-20170810
firmware version: 0x09030008
power table loaded from dts: no
firmware region code: 0x10
mac address: 60:38:e0:13:80:9a
2g: enable
5g: enable
antenna: 4 4
irq number: 46
ap macid support: 0000ffff
sta macid support: 00010000
macid used: 00000001
radio: enable
iobase0: e0c00000
iobase1: e0e80000
tx limit: 1024
rx limit: 16384

Post #3819

kylum

4 Nov 2017, 20:36

I’m aware of the issue but just wanted to report that r5113 on my 3200acm finally crashed after 9 days uptime. It crashed when I was at my sons soccer game and no devices were connected wirelessly during that time.

(Last edited by kylum on 4 Nov 2017, 20:38)

Post #3820

davidc502

4 Nov 2017, 20:46

bill1228 wrote:

davidc502 wrote:
bill1228 wrote:
Thanks, David. That is what I was thinking. Not sure why I do not have the same issue when running DD-WRT. Brainslayer is incorporating the same firmware version and wireless driver version as LEDE. Have run his latest for days and no issues and there is a teen who has texted me when I am at the store that there are wireless issues.
So I would know if I did not experience myself.
Well, if everything is the same (packages/drivers etc) they don't seem to be telling anyone how they are doing it, specifically yuhhaurlin Otherwise the fix would have been in already. So, something is different or not.
Just a FYI. This is the firmware and wireless driver versions on DD-WRT r33607. I think these are the same as what you are using, forgot to check before I reinstalled DD-WRT, but previously when I checked they were the same.
cat /sys/kernel/debug/ieee80211/phy0/mwlwifi/info
driver name: mwlwifi
chip type: 88W8964
hw version: 7
driver version: 10.3.4.0-20170810
firmware version: 0x09030008
power table loaded from dts: no
firmware region code: 0x10
mac address: 60:38:e0:13:80:9a
2g: enable
5g: enable
antenna: 4 4
irq number: 46
ap macid support: 0000ffff
sta macid support: 00010000
macid used: 00000001
radio: enable
iobase0: e0c00000
iobase1: e0e80000
tx limit: 1024
rx limit: 16384

KRACK patches included?

Post #3821

bill1228

4 Nov 2017, 22:15

davidc502 wrote:

bill1228 wrote:
davidc502 wrote:
Well, if everything is the same (packages/drivers etc) they don't seem to be telling anyone how they are doing it, specifically yuhhaurlin Otherwise the fix would have been in already. So, something is different or not.
Just a FYI. This is the firmware and wireless driver versions on DD-WRT r33607. I think these are the same as what you are using, forgot to check before I reinstalled DD-WRT, but previously when I checked they were the same.
cat /sys/kernel/debug/ieee80211/phy0/mwlwifi/info
driver name: mwlwifi
chip type: 88W8964
hw version: 7
driver version: 10.3.4.0-20170810
firmware version: 0x09030008
power table loaded from dts: no
firmware region code: 0x10
mac address: 60:38:e0:13:80:9a
2g: enable
5g: enable
antenna: 4 4
irq number: 46
ap macid support: 0000ffff
sta macid support: 00010000
macid used: 00000001
radio: enable
iobase0: e0c00000
iobase1: e0e80000
tx limit: 1024
rx limit: 16384
KRACK patches included?

@david
Yes the KRACK patches are installed. In theory there should not be any difference between DD-WRT and LEDE.

Post #3822

davidc502

4 Nov 2017, 23:07

bill1228 wrote:

davidc502 wrote:
bill1228 wrote:
Just a FYI. This is the firmware and wireless driver versions on DD-WRT r33607. I think these are the same as what you are using, forgot to check before I reinstalled DD-WRT, but previously when I checked they were the same.
cat /sys/kernel/debug/ieee80211/phy0/mwlwifi/info
driver name: mwlwifi
chip type: 88W8964
hw version: 7
driver version: 10.3.4.0-20170810
firmware version: 0x09030008
power table loaded from dts: no
firmware region code: 0x10
mac address: 60:38:e0:13:80:9a
2g: enable
5g: enable
antenna: 4 4
irq number: 46
ap macid support: 0000ffff
sta macid support: 00010000
macid used: 00000001
radio: enable
iobase0: e0c00000
iobase1: e0e80000
tx limit: 1024
rx limit: 16384
KRACK patches included?
@david
Yes the KRACK patches are installed. In theory there should not be any difference between DD-WRT and LEDE.

If it is based on Trunk sources, then I wouldn't know why it would behave differently. At one time I thought I heard they converted everything over to C before compiling, but wouldn't know if that makes any difference or not.

Post #3823

gsustek

5 Nov 2017, 22:30

Hi, it's been a long time that i wrote something, nevertheless now is the time, because i just build image for my 3200acm, from .config and uploaded config file from 1900acs(just changed hostname )...So wireless is a little bit weird. should i need to pay an attention? maybe rebuild wireless settings?

Regards...

Post #3824

davidc502

5 Nov 2017, 22:43

gsustek wrote:

Hi, it's been a long time that i wrote something, nevertheless now is the time, because i just build image for my 3200acm, from .config and uploaded config file from 1900acs(just changed hostname )...So wireless is a little bit weird. should i need to pay an attention? maybe rebuild wireless settings?
Regards...

Make adjustments because the 3200acm has 3 wifi chips compared with 2 the 1900acs has. Just disable radio2 and make sure the AC configurations are on Radio0 and N is on Radio1.

Post #3825

gsustek

5 Nov 2017, 22:45

hi, davidc,

i do not have default wireless file... i remember, that there is some command to recreate /etc/config/wireless .....
did you add some features to vanilla LEDE build? like special config....

edit:
rm -f /etc/config/wireless
wifi config > /etc/config/wireless

(Last edited by gsustek on 5 Nov 2017, 22:57)

Sorry, posts 3826 to 3825 are missing from our archive.

Page 153 of 229