Topic: Update on Linksys WRT1900AC support

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

Page 568 of 598

Post #14176

sera

23 Mar 2017, 07:11

nitroshift wrote:

@sera
DSA traffic on Mamba is now on par with swconfig, using 4.10.4 and it was just the same with 4.10.1. Perfectly usable. Temperatures are below threshold, so fan never kicks in. Rango is working perfectly, wthout wireless drops or degradations, nor random reboots.
nitroshift

That means DSA is off the table, works fine now for all models, great!. As DSA provides much more features than swconfig it would be a shame otherwise.

The fan not kicking in isn't helpful for testing May I ask you to either lower the limits, stress your device or manually get it to spin. How to do it you can find in /sbin/fan_ctrl.sh. Only swrt-2017-03-22 has the latest driver.

Post #14177

dlang

23 Mar 2017, 08:43

the sqm package is scripts that use standard kernel functionality, not kernel modifications.

sqm is not needed unless you are:

1. overloading your link

and

2. do not have something like fq_codel functioning on the bottleneck side of the link.

So if you have a good ISP that implements fq_codel (or other active queue management) on the router on their side of the link, you won't have any problems downloading.

If you have active queue management on your side of the link (as opposed to on gig ethernet connected to a modem), then you will have no problems uploading.

but if you are stuck with bad vendor software on either end of your link, and saturate the link, you can run into problems.

Post #14178

tapper

23 Mar 2017, 09:02

sera wrote:

tapper wrote:
Hi I cant build swrt. Is there any ready builds ready to flash? For the 3200ACM. Just standard packages needed Luci UPMP SQM BCP38.
As you are blind I make an exception, dabbling in binaries takes a lot of time and I rather spend my limited time on getting the sources right. But if it's just a single diffconfig without any packages for later installation it's manageable. Will do a build later today. That being said Villeneuve did share his builds at least in the past.
About sqm, unlike OpenWrt I do not meddle with the kernel defaults. Using FIFO (no traffic shaping) and even with a over a thousand torrent connections I didn't see any issues. Ping round trip time to google stayed at a constant 1.1ms. Wireless at about 3ms.

Thanks. If you say it's good with out SQM I will take your word for it!

Post #14179

sera

23 Mar 2017, 10:40

dlang wrote:

the sqm package is scripts that use standard kernel functionality, not kernel modifications.

OpenWrt and I suspect LEDE do patch the kernel to replace the default qdisk and even patches the the replacement. So getting the real kernel defaults (which are kernel defaults for a reason) isn't that straight forward. I consider replacing FIFO a premature optimisation.

That said, the fiber is terminated in my living room with what you probably can call a sane ISP on the other end. The dslreport page reports zero buffer bloat and A+ quality link even under load. No "modem" involved, behaves like an Ethernet connection directly to the ISP.

Generally I only do traffic control when I see an issue that need be addressed. Which isn't the case for me here. Not saying this is true for everyone.

Post #14180

sera

23 Mar 2017, 10:47

tapper,

did a build as follows:

#!/usr/bin/env bash

PACKAGES=(
        luci-app-bcp38
        luci-app-upnp
        sqm-scripts
        )

make dirclean

./scripts/feeds uninstall -a
./scripts/feeds update -a

git checkout swrt-2017-03-22

cat > .config <<- _EOF_
        CONFIG_TARGET_mvebu=y
        CONFIG_TARGET_mvebu_Rango=y
        CONFIG_TARGET_BOARD="mvebu"
_EOF_

make defconfig

./scripts/feeds install -d y "${PACKAGES[@]}"

make -j12 world

The image using kernel 4.10.5 can be downloaded at:

openwrt-mvebu-rango-squashfs-factory.img: https://gpldr.in/v/tdoLbboiZn/MW3s86h96uqL1GtA
sha256sum: 7924ccf931c3e8229c987d15c89723d47c89cd1dabc177012ba26aa81838beab

Post #14181

tapper

23 Mar 2017, 14:19

@sera thanks I will let you know how i go on.

Post #14182

Chadster766

23 Mar 2017, 17:09

nitroshift wrote:

@sera
Rango is working perfectly, wthout wireless drops or degradations, nor random reboots.
nitroshift

@nitroshift,

You aren't having issues with mwlwifi on the WRT3200ACM?

If so what is your secret since everyone else is?

https://github.com/kaloz/mwlwifi/issues/118

(Last edited by Chadster766 on 23 Mar 2017, 17:30)

Post #14183

dlang

23 Mar 2017, 17:16

sera wrote:

That said, the fiber is terminated in my living room with what you probably can call a sane ISP on the other end. The dslreport page reports zero buffer bloat and A+ quality link even under load. No "modem" involved, behaves like an Ethernet connection directly to the ISP.

Yep, in that setup (and with fiber, I'm assuming a good high speed so not a significant bottleneck) you would not need any sort of queue management.

Post #14184

davidc502

23 Mar 2017, 17:49

Chadster766 wrote:

nitroshift wrote:
@sera
Rango is working perfectly, wthout wireless drops or degradations, nor random reboots.
nitroshift
@nitroshift,
You aren't having issues with mwlwifi on the WRT3200ACM?
If so what is your secret since everyone else is?
https://github.com/kaloz/mwlwifi/issues/118

Yeah, inquiring minds want to know. I've heard a few people talking about the 4.9.x kernel working better, but have not had a chance to test yet.

Post #14185

sera

23 Mar 2017, 17:58

Chadster,

I haven't seen any issues with my Linksys WRT3200ACM (Rango) and mwlwifi. Everything points to compat-wireless for 4.4 to be at fault here. Swrt doesn't use compat-wireless at all and I have yet to see an issue. The mwlwifi driver runs native on 4.9 unlike 4.4, so compat-wireless should play much less of a role here. Feel free to try to break swrt!

Post #14186

tapper

23 Mar 2017, 17:59

Hi @sera I am getting The uploaded image file does not contain a supported format. Make sure that you choose the generic image format for your platform.
Would i have to sysupgrade -f? or flash back to stock. I do have TTL if needed.

(Last edited by tapper on 23 Mar 2017, 18:03)

Post #14187

Chadster766

23 Mar 2017, 18:08

sera wrote:

Chadster,
I haven't seen any issues with my Linksys WRT3200ACM (Rango) and mwlwifi. Everything points to compat-wireless for 4.4 to be at fault here. Swrt doesn't use compat-wireless at all and I have yet to see an issue. The mwlwifi driver runs native on 4.9 unlike 4.4, so compat-wireless should play much less of a role here. Feel free to try to break swrt!

I've run 4.9.x and the issue still exists. It appears after a couple days operation. The symptoms are unstable wireless connections.

Feb 28 19:07:59 MCDEBIAN kernel: ieee80211 phy0: cmd 0x9122=UpdateEncryption timed out
Feb 28 19:07:59 MCDEBIAN kernel: ieee80211 phy0: return code: 0x1122
Feb 28 19:07:59 MCDEBIAN kernel: ieee80211 phy0: timeout: 0x1122
Feb 28 19:07:59 MCDEBIAN kernel: ieee80211 phy0: failed execution
Feb 28 19:07:59 MCDEBIAN kernel: wlan0: failed to remove key (2, ff:ff:ff:ff:ff:ff) from hardware (-5)
Feb 28 19:08:03 MCDEBIAN kernel: ieee80211 phy0: cmd 0x9122=UpdateEncryption timed out
Feb 28 19:08:03 MCDEBIAN kernel: ieee80211 phy0: return code: 0x1122
Feb 28 19:08:03 MCDEBIAN kernel: ieee80211 phy0: timeout: 0x1122
Feb 28 19:08:03 MCDEBIAN kernel: ieee80211 phy0: failed execution
Feb 28 19:08:03 MCDEBIAN kernel: wlan0: failed to set key (2, ff:ff:ff:ff:ff:ff) to hardware (-5)
Feb 28 19:08:07 MCDEBIAN hostapd[2828]: wlan1: STA 6c:ad:f8:b8:53:c0 IEEE 802.11: authenticated
Feb 28 19:08:07 MCDEBIAN hostapd[2828]: wlan1: STA 6c:ad:f8:b8:53:c0 IEEE 802.11: associated (aid 3)

Feb 28 19:03:53 MCDEBIAN dhcpd[2691]: DHCPOFFER on 192.168.200.111 to 10:92:66:46:11:27 (android-c08375e720de81a8) via br0
Feb 28 19:04:17 MCDEBIAN hostapd[2828]: wlan0: STA 16:91:82:00:88:a8 IEEE 802.11: disassociated due to inactivity
Feb 28 19:04:22 MCDEBIAN kernel: ieee80211 phy0: cmd 0x9122=UpdateEncryption timed out
Feb 28 19:04:22 MCDEBIAN kernel: ieee80211 phy0: return code: 0x1122
Feb 28 19:04:22 MCDEBIAN kernel: ieee80211 phy0: timeout: 0x1122
Feb 28 19:04:22 MCDEBIAN kernel: ieee80211 phy0: failed execution
Feb 28 19:04:22 MCDEBIAN kernel: wlan0: failed to remove key (0, 16:91:82:00:88:a8) from hardware (-5)
Feb 28 19:04:22 MCDEBIAN hostapd[2828]: wlan0: STA 16:91:82:00:88:a8 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Feb 28 19:04:22 MCDEBIAN kernel: ------------[ cut here ]------------
Feb 28 19:04:22 MCDEBIAN kernel: WARNING: CPU: 0 PID: 2828 at net/mac80211/agg-tx.c:398 ___ieee80211_stop_tx_ba_session+0x204/0x208
Feb 28 19:04:22 MCDEBIAN kernel: Modules linked in: cls_u32 sch_cbq nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter xt_conntrack iptable_filter iptable_mangle ipt_MASQUERAD
Feb 28 19:04:22 MCDEBIAN kernel: CPU: 0 PID: 2828 Comm: hostapd Tainted: G        W       4.9.12 #14
Feb 28 19:04:22 MCDEBIAN kernel: Hardware name: Marvell Armada 380/385 (Device Tree)

Which is why most WRT3200ACM owners are desperately waiting for @yuhhaurlin to finish a driver redesign to work with a new chip firmware:

https://github.com/mrvltest/mwlwifi

Post #14188

sera

23 Mar 2017, 18:34

Chadster,

Uptime of over 14 days and TBs of data transferred (using 4.11, not tested anything earlier / nitroshift is using 4.10). That obviously doesn't mean you will see the same, but chances are.

Is McDebian using compat-wireless?

Post #14189

sera

23 Mar 2017, 18:38

tapper wrote:

Hi @sera I am getting The uploaded image file does not contain a supported format. Make sure that you choose the generic image format for your platform.
Would i have to sysupgrade -f? or flash back to stock. I do have TTL if needed.

I presume you are using LEDE then, like proper malware it prevents you to uninstall it. Yes, you will have to use sysupgrade -f or another means of de-bricking (power switch / tftp / whatever). You can't flash back to stock either, only to LEDE images.

Edit: Joust remembered that the sysupgrade fix wasn't pulled in yet for CC, so flashing from stock or an other swrt install is by far the best method.

(Last edited by sera on 23 Mar 2017, 18:43)

Post #14190

Villeneuve

23 Mar 2017, 18:41

@tapper, yes you are going to have to force the image. I have indeed put up a build based on @sera latest, but is based on kernel next. I have flashed it to a rango, no testing on mamba as I am trying to keep that running on LEDE looking for random reboot issue.

Post #14191

Chadster766

23 Mar 2017, 18:43

sera wrote:

Chadster,
Uptime of over 14 days and TBs of data transferred (using 4.11, not tested anything earlier / nitroshift is using 4.10). That obviously doesn't mean you will see the same, but chances are.
Is McDebian using compat-wireless?

No just the pure mwlwifi driver.

Have you or nitroshift communicated this to @yuhhaurlin? He believes the only solution is a driver redesign with a new chip firmware.

My testing was done with kernel and modules 4.9.12. I guess this is a good opportunity to test 4.9.17.

The reason I'm not leaving 4.9.x is it's the recent long term release I've been waiting a few years for.

Post #14192

sera

23 Mar 2017, 19:13

Chadster,

David Lin (yuhhaurlin) doesn't seem to be pressured at all Yes, I reported my findings: https://github.com/kaloz/mwlwifi/issues … -282661825

The longterm release I'm waiting for doesn't exist yet Guess for you it's working DSA support. 4.11 ditches the legacy bindings for the modern ones. Possibly the last bigger change in awhile on that front.

Post #14193

Chadster766

23 Mar 2017, 19:18

sera wrote:

Chadster,
The longterm release I'm waiting for doesn't exist yet Guess for you it's working DSA support. 4.11 ditches the legacy bindings for the modern ones. Possibly the last bigger change in awhile on that front.

Wouldn't those major changes\fixes be included into a 4.9.x long term release eventually?

Post #14194

dolemhao

23 Mar 2017, 19:30

Hi everyone

I got a problem here and I need some help
My device is 1900ac v1 ''mamba"
A few days ago, I reinstalled the whole system because of a software corruption. But after reinstalling and rebooting, the 5G disappear. There was only one radio Marvell 88W8864 802.11bgn. I have tried reinstalling the official firmware. But even if I switched on 5G(there was 5g switch icon in official firmware)in webage, there was no 5g signal. Also, I checked the kernel log.

[   13.849014] <<Marvell 802.11ac Wireless Network Driver version 10.3.0.3>>
[   13.855733] pci 0000:00:02.0: enabling device (0140 -> 0142)
[   13.861653] mwlwifi 0000:02:00.0: enabling device (0140 -> 0142)
[   13.867816] ieee80211 phy0: priv->iobase0 = d1000000
[   13.872918] ieee80211 phy0: priv->iobase1 = d1200000
[   13.877934] ieee80211 phy0: priv->pcmd_buf = ce904000  priv->pphys_cmd_buf = e904000
[   13.973861] ieee80211 phy0: fw download start 88
[   14.093905] ieee80211 phy0: FwSize = 116356 downloaded Size = 116356 curr_iteration 65509
[   14.357262] ieee80211 phy0: 0;
[   14.615589] ieee80211 phy0: 0;
[   14.873821] ieee80211 phy0: 0;
[   14.961969] ieee80211 phy0: complete
[   14.965617] ieee80211 phy0: 2G: enable
[   14.969385] ieee80211 phy0: 5G: disable
[   14.973284] ieee80211 phy0: TX: 4 antennas
[   14.977406] ieee80211 phy0: RX: 4 antennas
[   14.983511] ieee80211 phy0: pcmd = ce904000
[   14.988523] ieee80211 phy0: mwl_fwcmd_set_hw_specs ...
[   14.993740] ieee80211 phy0:   -->pPhysTxRing[0] = ea00000
[   14.999167] ieee80211 phy0:   -->pPhysTxRing[1] = ea04000
[   15.004635] ieee80211 phy0:   -->pPhysTxRing[2] = ea08000
[   15.010063] ieee80211 phy0:   -->pPhysTxRing[3] = ea0c000
[   15.015530] ieee80211 phy0:   -->pPhysRxRing    = e89c000
[   15.020959] ieee80211 phy0:   -->numtxq 20 wcbperq 256 totalrxwcb 256
[   15.032495] ieee80211 phy0: firmware version: 0x7020806
[   15.052017] ieee80211 phy0: phy0: FCC
[   15.055711] ieee80211 phy0: Channel: 1: 0x0 0x0 0xf
[   15.060626] ieee80211 phy0: 17 11 11 11 10 10 10 10 f f f f 0 0 0 0 
[   15.067056] ieee80211 phy0: Channel: 2: 0x0 0x0 0xf
[   15.072022] ieee80211 phy0: 17 16 16 16 16 16 16 14 10 10 10 10 0 0 0 0 
[   15.078757] ieee80211 phy0: Channel: 3: 0x0 0x0 0xf
[   15.083729] ieee80211 phy0: 17 16 16 16 16 16 16 14 10 10 10 10 0 0 0 0 
[   15.090464] ieee80211 phy0: Channel: 4: 0x0 0x0 0xf
[   15.095424] ieee80211 phy0: 17 16 16 16 16 16 16 14 10 10 10 10 0 0 0 0 
[   15.102205] ieee80211 phy0: Channel: 5: 0x0 0x0 0xf
[   15.107124] ieee80211 phy0: 17 16 16 16 16 16 16 14 10 10 10 10 0 0 0 0 
[   15.113899] ieee80211 phy0: Channel: 6: 0x0 0x0 0xf
[   15.118818] ieee80211 phy0: 17 16 16 16 16 16 16 14 10 10 10 10 0 0 0 0 
[   15.125593] ieee80211 phy0: Channel: 7: 0x0 0x0 0xf
[   15.130512] ieee80211 phy0: 17 16 16 16 16 16 16 14 10 10 10 10 0 0 0 0 
[   15.137287] ieee80211 phy0: Channel: 8: 0x0 0x0 0xf
[   15.142252] ieee80211 phy0: 17 16 16 16 16 16 16 14 10 10 10 10 0 0 0 0 
[   15.148987] ieee80211 phy0: Channel: 9: 0x0 0x0 0xf
[   15.153946] ieee80211 phy0: 17 16 16 16 16 16 16 14 10 10 10 10 0 0 0 0 
[   15.160682] ieee80211 phy0: Channel: 10: 0x0 0x0 0xf
[   15.165728] ieee80211 phy0: 17 16 16 16 16 16 16 14 10 10 10 10 0 0 0 0 
[   15.172508] ieee80211 phy0: Channel: 11: 0x0 0x0 0xf
[   15.177514] ieee80211 phy0: 17 11 11 11 11 11 11 11 10 10 10 10 0 0 0 0 
[   15.234154] i2c /dev entries driver
[   15.299167] ip_tables: (C) 2000-2006 Netfilter Core Team
[   15.312550] nf_conntrack version 0.5.0 (3995 buckets, 15980 max)
[   15.429511] xt_time: kernel timezone is -0000
[   15.443275] PPP generic driver version 2.4.2
[   15.448816] NET: Registered protocol family 24
[   19.476332] device eth0 entered promiscuous mode
[   19.483317] br-lan: port 1(eth0) entered forwarding state
[   19.488790] br-lan: port 1(eth0) entered forwarding state
[   19.506705] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[   20.065415] cfg80211: Calling CRDA for country: JP
[   20.070440] ieee80211 phy0: phy0: FCC
[   20.074195] ieee80211 phy0: Channel: 1: 0x0 0x0 0xf
[   20.079103] ieee80211 phy0: 17 11 11 11 10 10 10 10 f f f f 0 0 0 0 
[   20.085527] ieee80211 phy0: Channel: 2: 0x0 0x0 0xf
[   20.090443] ieee80211 phy0: 17 16 16 16 16 16 16 14 10 10 10 10 0 0 0 0 
[   20.097221] ieee80211 phy0: Channel: 3: 0x0 0x0 0xf
[   20.102184] ieee80211 phy0: 17 16 16 16 16 16 16 14 10 10 10 10 0 0 0 0 
[   20.109010] ieee80211 phy0: Channel: 4: 0x0 0x0 0xf
[   20.113949] ieee80211 phy0: 17 16 16 16 16 16 16 14 10 10 10 10 0 0 0 0 
[   20.120747] ieee80211 phy0: Channel: 5: 0x0 0x0 0xf
[   20.125761] ieee80211 phy0: 17 16 16 16 16 16 16 14 10 10 10 10 0 0 0 0 
[   20.132563] ieee80211 phy0: Channel: 6: 0x0 0x0 0xf
[   20.137483] ieee80211 phy0: 17 16 16 16 16 16 16 14 10 10 10 10 0 0 0 0 
[   20.144259] ieee80211 phy0: Channel: 7: 0x0 0x0 0xf
[   20.149178] ieee80211 phy0: 17 16 16 16 16 16 16 14 10 10 10 10 0 0 0 0 
[   20.155939] ieee80211 phy0: Channel: 8: 0x0 0x0 0xf
[   20.160840] ieee80211 phy0: 17 16 16 16 16 16 16 14 10 10 10 10 0 0 0 0 
[   20.167605] ieee80211 phy0: Channel: 9: 0x0 0x0 0xf
[   20.172552] ieee80211 phy0: 17 16 16 16 16 16 16 14 10 10 10 10 0 0 0 0 
[   20.179279] ieee80211 phy0: Channel: 10: 0x0 0x0 0xf
[   20.184282] ieee80211 phy0: 17 16 16 16 16 16 16 14 10 10 10 10 0 0 0 0 
[   20.191005] ieee80211 phy0: Channel: 11: 0x0 0x0 0xf
[   20.196009] ieee80211 phy0: 17 11 11 11 11 11 11 11 10 10 10 10 0 0 0 0 
[   20.202788] cfg80211: Regulatory domain changed to country: JP
[   20.208666] cfg80211:  DFS Master region: JP
[   20.212910] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[   20.222755] cfg80211:   (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[   20.230883] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
[   20.238983] cfg80211:   (4910000 KHz - 4990000 KHz @ 40000 KHz), (N/A, 2300 mBm), (N/A)
[   20.247145] cfg80211:   (5030000 KHz - 5090000 KHz @ 40000 KHz), (N/A, 2300 mBm), (N/A)
[   20.255237] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[   20.264882] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[   20.274450] cfg80211:   (5490000 KHz - 5710000 KHz @ 160000 KHz), (N/A, 2300 mBm), (0 s)
[   20.471542] br-lan: port 1(eth0) entered disabled state
[   21.471519] mvneta f1070000.ethernet eth0: link up
[   21.476403] br-lan: port 1(eth0) entered forwarding state
[   21.481936] br-lan: port 1(eth0) entered forwarding state
[   21.511493] mvneta f1074000.ethernet eth1: link up
[   21.516341] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[   21.652362] ieee80211 phy0: change: 0xffffffff
[   21.700487] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   21.709356] device wlan0 entered promiscuous mode
[   21.714347] br-lan: port 2(wlan0) entered forwarding state
[   21.719893] br-lan: port 2(wlan0) entered forwarding state
[   21.773025] ieee80211 phy0: change: 0x100
[   21.775751] ieee80211 phy0: change: 0x40
[   21.941581] ieee80211 phy0: change: 0x40
[   22.097379] pppoe-wan: renamed from ppp0
[   22.114554] ieee80211 phy0: change: 0x40
[   22.271478] ieee80211 phy0: change: 0x40
[   22.431510] ieee80211 phy0: change: 0x40
[   22.488158] br-lan: port 2(wlan0) entered disabled state
[   22.591507] ieee80211 phy0: change: 0x40
[   22.751508] ieee80211 phy0: change: 0x40
[   22.911505] ieee80211 phy0: change: 0x40
[   23.071525] ieee80211 phy0: change: 0x40
[   23.231526] ieee80211 phy0: change: 0x40
[   23.391535] ieee80211 phy0: change: 0x40
[   23.447695] ieee80211 phy0: change: 0x100
[   23.481441] br-lan: port 1(eth0) entered forwarding state
[   23.621556] ieee80211 phy0: change: 0x100
[   23.626574] ieee80211 phy0: change: 0x42
[   23.702712] br-lan: port 2(wlan0) entered forwarding state
[   23.708293] br-lan: port 2(wlan0) entered forwarding state
[   23.714035] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   23.777885] IPv6: ADDRCONF(NETDEV_UP): wlan0-1: link is not ready
[   24.100571] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0-1: link becomes ready
[   25.701452] br-lan: port 2(wlan0) entered forwarding state
[ 7480.967622] ieee80211 phy0: result error
[ 7481.976014] ieee80211 phy0: result error
[10815.268398] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
[24438.159987] ieee80211 phy0: result error
[24439.210909] ieee80211 phy0: result error
[24936.505021] ieee80211 phy0: result error
[24937.567355] ieee80211 phy0: result error
[84582.417173] ieee80211 phy0: result error
[84583.479873] ieee80211 phy0: result error
[109902.549446] ieee80211 phy0: result error
[109903.562959] ieee80211 phy0: result error
[111619.646003] ieee80211 phy0: result error
[111620.655793] ieee80211 phy0: result error
[149272.110571] ieee80211 phy0: result error
[149626.357409] ieee80211 phy0: result error
[149627.366319] ieee80211 phy0: result error
[149725.659494] ieee80211 phy0: result error
[149726.677429] ieee80211 phy0: result error
[149739.234675] ieee80211 phy0: result error
[149740.342331] ieee80211 phy0: result error
[160945.517806] ieee80211 phy0: result error
[160946.539566] ieee80211 phy0: result error
[167046.544263] ieee80211 phy0: result error
[167047.552506] ieee80211 phy0: result error
[172227.885768] pppoe-wan: renamed from ppp0
[183272.362516] ieee80211 phy0: result error
[183273.372288] ieee80211 phy0: result error
[192535.322629] ieee80211 phy0: result error
[226747.273728] ieee80211 phy0: result error
[226748.281959] ieee80211 phy0: result error
[226749.289906] ieee80211 phy0: result error
[260018.874238] ieee80211 phy0: result error
[260019.988919] ieee80211 phy0: result error
[264854.469093] ieee80211 phy0: result error
[264855.550523] ieee80211 phy0: result error
[265719.702797] ieee80211 phy0: result error
[265720.758756] ieee80211 phy0: result error
[266754.458398] ieee80211 phy0: result error
[266755.473362] ieee80211 phy0: result error
[267022.442528] ieee80211 phy0: result error
[267023.451886] ieee80211 phy0: result error
[267024.461807] ieee80211 phy0: result error
[267028.043023] ieee80211 phy0: result error
[267029.068541] ieee80211 phy0: result error
[267034.662683] ieee80211 phy0: result error
[271227.048927] ieee80211 phy0: result error
[271228.067274] ieee80211 phy0: result error
[289223.594673] ieee80211 phy0: result error
[289224.623650] ieee80211 phy0: result error
[331641.474375] ieee80211 phy0: result error
[331642.491069] ieee80211 phy0: result error
[344432.411050] pppoe-wan: renamed from ppp0

I cannot find anything about phy1(should be 5g)

Anyone has any idea?

(Last edited by dolemhao on 23 Mar 2017, 19:31)

Post #14195

sera

23 Mar 2017, 19:37

Chadster766 wrote:

sera wrote:
Chadster,
The longterm release I'm waiting for doesn't exist yet Guess for you it's working DSA support. 4.11 ditches the legacy bindings for the modern ones. Possibly the last bigger change in awhile on that front.
Wouldn't those major changes\fixes be included into a 4.9.x long term release eventually?

Not a bug-fix, so no backport will happen. It shouldn't matter much either. Just hinting that the spurt that started with 4.7 seems to come to an end with 4.11.

---

The buffer manager and the follow-up cleanup patch for the pwm-fan addition got merged today and the regression fix (uart) is addressed in todays linux-next. 8/12 patches targeted for 4.12 are in. Maybe there is even enough time left at the end for polishing and upstreaming Rango as well.

Post #14196

tapper

23 Mar 2017, 23:32

Hi @seraI could not get your build to flash so i flashed a build from Villeneuve with your paches.

Post #14197

JW0914

24 Mar 2017, 03:24

@dolemhao Please post your wireless config [/etc/config/wireless], minus SSIDs and passwords.

Do you by chance have any iOS devices which were connected?

@all What is uboot-mvebu-clearfog and how does it correlate to WRT routers?

(Last edited by JW0914 on 24 Mar 2017, 03:57)

Post #14198

lifehacksback

24 Mar 2017, 05:38

@sera
I'm completely intrigued by your knowledge of the linux network stack as well as your ability to work easily over openwrt. Is there a secret to your knowledge? Book? anything?

Post #14199

nitroshift

24 Mar 2017, 05:55

@JW0914

uboot-mvebu-clearfog is the bootloader for the clearfog board which is built around a Marvell Armada SoC.

nitroshift

Post #14200

dlang

24 Mar 2017, 08:57

sera wrote:

tapper wrote:
Hi @sera I am getting The uploaded image file does not contain a supported format. Make sure that you choose the generic image format for your platform.
Would i have to sysupgrade -f? or flash back to stock. I do have TTL if needed.
I presume you are using LEDE then, like proper malware it prevents you to uninstall it. Yes, you will have to use sysupgrade -f or another means of de-bricking (power switch / tftp / whatever). You can't flash back to stock either, only to LEDE images.

I believe that this is the result of a LUCI "upgrade", so as soon as OpenWRT upgrades to the current LUCI build it will have the same problem. I do hope they revert this soon. This is what happens when you try too hard to idiot proof things, you break legitimate uses.

To answer Tapper, you will need to do the sysupgrade -f

Page 568 of 598