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 551 of 598

Post #13751

InkblotAdmirer

25 Nov 2016, 15:55

@sera I meant this in the manner @dlang stated -- it makes sense that all interfaces in the family are referenced the same regardless of underlying hardware. I personally don't care either way or even have a recommended solution (other than picking something for a logical reason and sticking with it...).

The original patch submission hints that the switch layout is identical in all cases anyway, I'm not sure about the network hardware. I agree the patch is poorly commented ("simplify network interface" or something like that -- no indication of impact to end user).

My reason for posting was only to provide a heads up that there's divergence between LEDE/OpenWRT (in the past there has been hope for a remerge or something) and one that impacts an upgrade. The more of these changes that propagate the harder that's going to be.

Post #13752

sera

25 Nov 2016, 17:20

InkblotAdmirer wrote:

@sera I meant this in the manner @dlang stated -- it makes sense that all interfaces in the family are referenced the same regardless of underlying hardware. I personally don't care either way or even have a recommended solution (other than picking something for a logical reason and sticking with it...).

Either way has a logical reason behind so why not sticking with what there is is the non obvious part. There is anyway a mess ahead with the reordering of the DT nodes in 4.6, so Lede users will go trough another change shortly. So both distributions still can end up with the same solution.

Some reasonable solutions could be:
* backport mainline commit and fixup base-files
* rename interface to wan/lan on boot to get rid of the semi random names ethX
* switch to DSA

InkblotAdmirer wrote:

The original patch submission hints that the switch layout is identical in all cases anyway, I'm not sure about the network hardware. I agree the patch is poorly commented ("simplify network interface" or something like that -- no indication of impact to end user).

The patch is based on the observation that currently kernel interface names map to the same switch port number for different models.

Post #13753

Villeneuve

25 Nov 2016, 21:48

Well, it's has been backed out.

Post #13754

davidc502

26 Nov 2016, 17:16

FYI -- I'm getting reports of users not being able to flash back to stock from lede r2217 and r2221.

If flashing through GUI -- The following message is displayed - "The uploaded image file does not contain a supported format. Make sure that you choose the generic image format for your platform."

If doing sysupgrade -- The following message is displayed - "Image metadata not found/Image check fw_tool_check image failed"

Post #13755

robd

26 Nov 2016, 20:09

davidc502 wrote:

FYI -- I'm getting reports of users not being able to flash back to stock from lede r2217 and r2221.
If flashing through GUI -- The following message is displayed - "The uploaded image file does not contain a supported format. Make sure that you choose the generic image format for your platform."
If doing sysupgrade -- The following message is displayed - "Image metadata not found/Image check fw_tool_check image failed"

I guess it is commit 9fc0bcdd18688724494e3364ec986318372129a4 in git.lede-project.org/?p=source.git

that adds the new metadata feature to mvebu.

Maybe setting /lib/upgrade/platform.sh back to the old version helps.

robd

Post #13756

davidc502

26 Nov 2016, 20:49

robd wrote:

davidc502 wrote:
FYI -- I'm getting reports of users not being able to flash back to stock from lede r2217 and r2221.
If flashing through GUI -- The following message is displayed - "The uploaded image file does not contain a supported format. Make sure that you choose the generic image format for your platform."
If doing sysupgrade -- The following message is displayed - "Image metadata not found/Image check fw_tool_check image failed"
I guess it is commit 9fc0bcdd18688724494e3364ec986318372129a4 in git.lede-project.org/?p=source.git
that adds the new metadata feature to mvebu.
Maybe setting /lib/upgrade/platform.sh back to the old version helps.

robd

According to Felix (He did the commit), you need to use the -F option in the sysupgrade. Awaiting to hear back from some of the users to see if this works or not.

"You can use sysupgrade -F to override that. I will change the error
message to include this hint.

- Felix"

Post #13757

JW0914

26 Nov 2016, 21:00

dlang wrote:

sera wrote:
InkblotAdmirer wrote:
It makes sense to unify these (why was shelby ever different in the first place??).
https://git.lede-project.org/?p=source. … b97ef7df1d
Why does it make sense? The commit message doesn't say so either. Maybe I'm just dense here but this isn't obvious to me.
Why it is as it is so that not setting up the switch with vlans still works as expected.
it makes sense to have all of the routers in this family use the same interface for wan rather than some using eth0 and some using eth1 (remember, neither of these is a physical port, they both have to go to the switch)

It does make sense to have all use the same interface, but mamba is the only odd man out, so it should be made to fall in line with the other 5 routers.

Doesn't seem like it was thought through very well, as instead of simply moving mamba inline, they chose to bring the 1200ac v1 & v2, 1900ac v2, 1900acs, and the 3200acm inline with mamba?
- That fundamentally lacks common sense, even more so since all, except mamba, use the Armada 385 SoC
@sera's right on with "rename interface to wan/lan on boot to get rid of the semi random names ethX"

(Last edited by JW0914 on 26 Nov 2016, 21:17)

Post #13758

Villeneuve

26 Nov 2016, 21:14

That certainly seems a little untoward. You are going to have to have a great deal of certainty in the image being forced.

Post #13759

JW0914

26 Nov 2016, 21:19

I've made the following post in the WRT3200ACM giveaway thread... does anyone have any other dev mentions I should add to my post?

Post #13760

davidc502

26 Nov 2016, 21:58

Villeneuve wrote:

That certainly seems a little untoward. You are going to have to have a great deal of certainty in the image being forced.

Agreed.. I don't know the whole story behind the change, but seems to me that it needs to work correctly, rather than putting a band-aid of using the -F option.

---- One user has reported back that the -F option works.

Post #13761

northbound

27 Nov 2016, 03:26

I do not keep a factory flash and have not had one for awhile but the last update would not flash
lede-mvebu-linksys-wrt1900ac-squashfs-factory.img "invalid"
but lede-mvebu-linksys-wrt1900ac-squashfs-sysupgrade.bin did work.
May be a fluke only here, I am on 4.4.35
Just a FYI.
Will dig deeper later, no time now.

Post #13762

paulwrt

27 Nov 2016, 03:54

paulwrt wrote:

Hi, the 2.4gHz SSID just disappear (hidden in setting) but 5ghz keep working. The 2.4ghz channel I am using (channel 4) is somehow identifiable in wifi-Analyzer but just its SSID is not shown
This problem seems appear when I start use USB sd-card on the router.
Log:-
openwrt kern.err kernel: [42333.845342] ieee80211 phy1: cmd 0x801c=80211RadioControl timed out
Hardware:-
Model Linksys WRT1900ACv2
Firmware Version OpenWrt Chaos Calmer 15.05.1 / LuCI 15.05-142-gb6330a1 Release (git-15.363.78009-956be55)
Kernel Version 3.18.23

UPDATE
2.4gHz still just disappear randomly but 5ghz keep working!!!!
Need reboot to restore the 2.4gHz - not an satisfactory option indeed!
Maybe not related to the external USB.

Model Linksys WRT1900ACv2
Firmware Version OpenWrt Chaos Calmer 15.05.1 / LuCI 15.05-142-gb6330a1 Release (git-15.363.78009-956be55)
Kernel Version 3.18.23

NEW LOG:-

Sun Nov 27 04:20:50 2016 kern.err kernel: [100232.719482] ieee80211 phy1: timeout: 0x1111
Sun Nov 27 04:20:50 2016 kern.err kernel: [100232.723768] ieee80211 phy1: failed execution
Sun Nov 27 04:20:52 2016 kern.err kernel: [100234.721953] ieee80211 phy1: cmd 0x9125=BAStream timed out
Sun Nov 27 04:20:52 2016 kern.err kernel: [100234.727466] ieee80211 phy1: return code: 0x1125
Sun Nov 27 04:20:52 2016 kern.err kernel: [100234.732101] ieee80211 phy1: timeout: 0x1125
Sun Nov 27 04:20:52 2016 kern.err kernel: [100234.736392] ieee80211 phy1: destroy ba failed execution
Sun Nov 27 04:20:54 2016 kern.err kernel: [100236.735471] ieee80211 phy1: cmd 0x9111=SetNewStation timed out
Sun Nov 27 04:20:54 2016 kern.err kernel: [100236.741432] ieee80211 phy1: return code: 0x1111
Sun Nov 27 04:20:54 2016 kern.err kernel: [100236.746069] ieee80211 phy1: timeout: 0x1111
Sun Nov 27 04:20:54 2016 kern.err kernel: [100236.750362] ieee80211 phy1: failed execution
Sun Nov 27 04:20:54 2016 daemon.info hostapd: wlan1: STA 54:44:08:7e:08:64 IEEE 802.11: deauthenticated due to local deauth request
Sun Nov 27 04:20:54 2016 daemon.info hostapd: wlan1: STA 38:2c:4a:17:8f:96 IEEE 802.11: deauthenticated due to local deauth request
Sun Nov 27 04:20:56 2016 kern.err kernel: [100238.749213] ieee80211 phy1: cmd 0x9111=SetNewStation timed out
Sun Nov 27 04:20:56 2016 kern.err kernel: [100238.755162] ieee80211 phy1: return code: 0x1111
Sun Nov 27 04:20:56 2016 kern.err kernel: [100238.759803] ieee80211 phy1: timeout: 0x1111
Sun Nov 27 04:20:56 2016 kern.err kernel: [100238.764125] ieee80211 phy1: failed execution
Sun Nov 27 04:20:56 2016 daemon.info hostapd: wlan1: STA 54:a0:50:c5:06:15 IEEE 802.11: deauthenticated due to local deauth request
Sun Nov 27 04:20:58 2016 kern.err kernel: [100240.767770] ieee80211 phy1: cmd 0x8050=broadcast_ssid_enable timed out
Sun Nov 27 04:20:58 2016 kern.err kernel: [100240.774416] ieee80211 phy1: return code: 0x0050
Sun Nov 27 04:20:58 2016 kern.err kernel: [100240.779061] ieee80211 phy1: timeout: 0x0050
Sun Nov 27 04:20:58 2016 kern.err kernel: [100240.783347] ieee80211 phy1: failed execution
Sun Nov 27 04:21:00 2016 kern.err kernel: [100242.786545] ieee80211 phy1: cmd 0x8127=SetInformationElements timed out
Sun Nov 27 04:21:00 2016 kern.err kernel: [100242.793279] ieee80211 phy1: return code: 0x0127
Sun Nov 27 04:21:00 2016 kern.err kernel: [100242.797922] ieee80211 phy1: timeout: 0x0127
Sun Nov 27 04:21:00 2016 kern.err kernel: [100242.802212] ieee80211 phy1: failed execution
Sun Nov 27 04:21:02 2016 kern.err kernel: [100244.800217] ieee80211 phy1: cmd 0x801c=80211RadioControl timed out
Sun Nov 27 04:21:02 2016 kern.err kernel: [100244.806515] ieee80211 phy1: return code: 0x001c
Sun Nov 27 04:21:02 2016 kern.err kernel: [100244.811150] ieee80211 phy1: timeout: 0x001c
Sun Nov 27 04:21:02 2016 kern.err kernel: [100244.815436] ieee80211 phy1: failed execution
Sun Nov 27 04:21:04 2016 kern.err kernel: [100246.813307] ieee80211 phy1: cmd 0x8126=SetFixedRate timed out
Sun Nov 27 04:21:04 2016 kern.err kernel: [100246.819169] ieee80211 phy1: return code: 0x0126
Sun Nov 27 04:21:04 2016 kern.err kernel: [100246.823818] ieee80211 phy1: timeout: 0x0126
Sun Nov 27 04:21:04 2016 kern.err kernel: [100246.828110] ieee80211 phy1: failed execution
Sun Nov 27 04:25:00 2016 cron.info crond[1151]: USER root pid 32465 cmd /sbin/fan_ctrl.sh
Sun Nov 27 04:30:00 2016 cron.info crond[1151]: USER root pid 32470 cmd /sbin/fan_ctrl.sh
Sun Nov 27 04:30:36 2016 kern.err kernel: [100819.016671] ieee80211 phy1: cmd 0x9122=UpdateEncryption timed out
Sun Nov 27 04:30:36 2016 kern.err kernel: [100819.022887] ieee80211 phy1: return code: 0x1122
Sun Nov 27 04:30:36 2016 kern.err kernel: [100819.027526] ieee80211 phy1: timeout: 0x1122
Sun Nov 27 04:30:36 2016 kern.err kernel: [100819.031822] ieee80211 phy1: failed execution
Sun Nov 27 04:30:36 2016 kern.err kernel: [100819.036196] wlan1: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-5)
Sun Nov 27 04:30:38 2016 kern.err kernel: [100821.042657] ieee80211 phy1: cmd 0x9122=UpdateEncryption timed out
Sun Nov 27 04:30:38 2016 kern.err kernel: [100821.048872] ieee80211 phy1: return code: 0x1122
Sun Nov 27 04:30:38 2016 kern.err kernel: [100821.053507] ieee80211 phy1: timeout: 0x1122
Sun Nov 27 04:30:38 2016 kern.err kernel: [100821.057800] ieee80211 phy1: failed execution
Sun Nov 27 04:30:38 2016 kern.err kernel: [100821.062175] wlan1: failed to set key (1, ff:ff:ff:ff:ff:ff) to hardware (-5)
Sun Nov 27 04:35:00 2016 cron.info crond[1151]: USER root pid 32613 cmd /sbin/fan_ctrl.sh
Sun Nov 27 04:40:00 2016 cron.info crond[1151]: USER root pid 32620 cmd /sbin/fan_ctrl.sh
Sun Nov 27 04:40:40 2016 kern.err kernel: [101423.072804] ieee80211 phy1: cmd 0x9122=UpdateEncryption timed out
Sun Nov 27 04:40:40 2016 kern.err kernel: [101423.079014] ieee80211 phy1: return code: 0x1122
Sun Nov 27 04:40:40 2016 kern.err kernel: [101423.083656] ieee80211 phy1: timeout: 0x1122
Sun Nov 27 04:40:40 2016 kern.err kernel: [101423.087942] ieee80211 phy1: failed execution
Sun Nov 27 04:40:40 2016 kern.err kernel: [101423.092320] wlan1: failed to set key (2, ff:ff:ff:ff:ff:ff) to hardware (-5)
Sun Nov 27 04:45:00 2016 cron.info crond[1151]: USER root pid 32764 cmd /sbin/fan_ctrl.sh
Sun Nov 27 04:50:00 2016 cron.info crond[1151]: USER root pid 302 cmd /sbin/fan_ctrl.sh
Sun Nov 27 04:50:42 2016 kern.err kernel: [102025.120613] ieee80211 phy1: cmd 0x9122=UpdateEncryption timed out
Sun Nov 27 04:50:42 2016 kern.err kernel: [102025.126828] ieee80211 phy1: return code: 0x1122
Sun Nov 27 04:50:42 2016 kern.err kernel: [102025.131463] ieee80211 phy1: timeout: 0x1122
Sun Nov 27 04:50:42 2016 kern.err kernel: [102025.135756] ieee80211 phy1: failed execution
Sun Nov 27 04:50:42 2016 kern.err kernel: [102025.140130] wlan1: failed to set key (1, ff:ff:ff:ff:ff:ff) to hardware (-5)
Sun Nov 27 04:55:00 2016 cron.info crond[1151]: USER root pid 454 cmd /sbin/fan_ctrl.sh
Sun Nov 27 05:00:00 2016 cron.info crond[1151]: USER root pid 460 cmd /sbin/fan_ctrl.sh
Sun Nov 27 05:00:44 2016 kern.err kernel: [102627.143325] ieee80211 phy1: cmd 0x9122=UpdateEncryption timed out
Sun Nov 27 05:00:44 2016 kern.err kernel: [102627.149543] ieee80211 phy1: return code: 0x1122
Sun Nov 27 05:00:44 2016 kern.err kernel: [102627.154183] ieee80211 phy1: timeout: 0x1122
Sun Nov 27 05:00:44 2016 kern.err kernel: [102627.158479] ieee80211 phy1: failed execution
Sun Nov 27 05:00:44 2016 kern.err kernel: [102627.162857] wlan1: failed to set key (2, ff:ff:ff:ff:ff:ff) to hardware (-5)
Sun Nov 27 05:05:00 2016 cron.info crond[1151]: USER root pid 606 cmd /sbin/fan_ctrl.sh
Sun Nov 27 05:10:00 2016 cron.info crond[1151]: USER root pid 611 cmd /sbin/fan_ctrl.sh
Sun Nov 27 05:10:46 2016 kern.err kernel: [103229.180481] ieee80211 phy1: cmd 0x9122=UpdateEncryption timed out
Sun Nov 27 05:10:46 2016 kern.err kernel: [103229.186695] ieee80211 phy1: return code: 0x1122
Sun Nov 27 05:10:46 2016 kern.err kernel: [103229.191330] ieee80211 phy1: timeout: 0x1122
Sun Nov 27 05:10:46 2016 kern.err kernel: [103229.195616] ieee80211 phy1: failed execution
Sun Nov 27 05:10:46 2016 kern.err kernel: [103229.199996] wlan1: failed to set key (1, ff:ff:ff:ff:ff:ff) to hardware (-5)
Sun Nov 27 05:15:00 2016 cron.info crond[1151]: USER root pid 757 cmd /sbin/fan_ctrl.sh
Sun Nov 27 05:20:00 2016 cron.info crond[1151]: USER root pid 762 cmd /sbin/fan_ctrl.sh
Sun Nov 27 05:20:48 2016 kern.err kernel: [103831.212571] ieee80211 phy1: cmd 0x9122=UpdateEncryption timed out
Sun Nov 27 05:20:48 2016 kern.err kernel: [103831.218782] ieee80211 phy1: return code: 0x1122
Sun Nov 27 05:20:48 2016 kern.err kernel: [103831.223424] ieee80211 phy1: timeout: 0x1122
Sun Nov 27 05:20:48 2016 kern.err kernel: [103831.227711] ieee80211 phy1: failed execution
Sun Nov 27 05:20:48 2016 kern.err kernel: [103831.232090] wlan1: failed to set key (2, ff:ff:ff:ff:ff:ff) to hardware (-5)
Sun Nov 27 05:25:00 2016 cron.info crond[1151]: USER root pid 909 cmd /sbin/fan_ctrl.sh
Sun Nov 27 05:30:00 2016 cron.info crond[1151]: USER root pid 914 cmd /sbin/fan_ctrl.sh
Sun Nov 27 05:30:50 2016 kern.err kernel: [104433.244578] ieee80211 phy1: cmd 0x9122=UpdateEncryption timed out
Sun Nov 27 05:30:50 2016 kern.err kernel: [104433.250789] ieee80211 phy1: return code: 0x1122
Sun Nov 27 05:30:50 2016 kern.err kernel: [104433.255430] ieee80211 phy1: timeout: 0x1122
Sun Nov 27 05:30:50 2016 kern.err kernel: [104433.259717] ieee80211 phy1: failed execution
Sun Nov 27 05:30:50 2016 kern.err kernel: [104433.264095] wlan1: failed to set key (1, ff:ff:ff:ff:ff:ff) to hardware (-5)
Sun Nov 27 05:35:00 2016 cron.info crond[1151]: USER root pid 1059 cmd /sbin/fan_ctrl.sh
Sun Nov 27 05:40:00 2016 cron.info crond[1151]: USER root pid 1064 cmd /sbin/fan_ctrl.sh
Sun Nov 27 05:40:52 2016 kern.err kernel: [105035.281714] ieee80211 phy1: cmd 0x9122=UpdateEncryption timed out
Sun Nov 27 05:40:52 2016 kern.err kernel: [105035.287931] ieee80211 phy1: return code: 0x1122
Sun Nov 27 05:40:52 2016 kern.err kernel: [105035.292570] ieee80211 phy1: timeout: 0x1122
Sun Nov 27 05:40:52 2016 kern.err kernel: [105035.296865] ieee80211 phy1: failed execution
Sun Nov 27 05:40:52 2016 kern.err kernel: [105035.301240] wlan1: failed to set key (2, ff:ff:ff:ff:ff:ff) to hardware (-5)
Sun Nov 27 05:45:00 2016 cron.info crond[1151]: USER root pid 1211 cmd /sbin/fan_ctrl.sh
Sun Nov 27 05:50:00 2016 cron.info crond[1151]: USER root pid 1218 cmd /sbin/fan_ctrl.sh
Sun Nov 27 05:50:54 2016 kern.err kernel: [105637.318274] ieee80211 phy1: cmd 0x9122=UpdateEncryption timed out
Sun Nov 27 05:50:54 2016 kern.err kernel: [105637.324485] ieee80211 phy1: return code: 0x1122
Sun Nov 27 05:50:54 2016 kern.err kernel: [105637.329126] ieee80211 phy1: timeout: 0x1122
Sun Nov 27 05:50:54 2016 kern.err kernel: [105637.333413] ieee80211 phy1: failed execution
Sun Nov 27 05:50:54 2016 kern.err kernel: [105637.337792] wlan1: failed to set key (1, ff:ff:ff:ff:ff:ff) to hardware (-5)
Sun Nov 27 05:55:00 2016 cron.info crond[1151]: USER root pid 1370 cmd /sbin/fan_ctrl.sh
Sun Nov 27 06:00:00 2016 cron.info crond[1151]: USER root pid 1375 cmd /sbin/fan_ctrl.sh
Sun Nov 27 06:00:56 2016 kern.err kernel: [106239.365396] ieee80211 phy1: cmd 0x9122=UpdateEncryption timed out
Sun Nov 27 06:00:56 2016 kern.err kernel: [106239.371610] ieee80211 phy1: return code: 0x1122
Sun Nov 27 06:00:56 2016 kern.err kernel: [106239.376245] ieee80211 phy1: timeout: 0x1122
Sun Nov 27 06:00:56 2016 kern.err kernel: [106239.380537] ieee80211 phy1: failed execution
Sun Nov 27 06:00:56 2016 kern.err kernel: [106239.384911] wlan1: failed to set key (2, ff:ff:ff:ff:ff:ff) to hardware (-5)
Sun Nov 27 06:05:00 2016 cron.info crond[1151]: USER root pid 1519 cmd /sbin/fan_ctrl.sh
Sun Nov 27 06:10:00 2016 cron.info crond[1151]: USER root pid 1525 cmd /sbin/fan_ctrl.sh
Sun Nov 27 06:10:58 2016 kern.err kernel: [106841.393075] ieee80211 phy1: cmd 0x9122=UpdateEncryption timed out
Sun Nov 27 06:10:58 2016 kern.err kernel: [106841.399289] ieee80211 phy1: return code: 0x1122
Sun Nov 27 06:10:58 2016 kern.err kernel: [106841.403924] ieee80211 phy1: timeout: 0x1122
Sun Nov 27 06:10:58 2016 kern.err kernel: [106841.408217] ieee80211 phy1: failed execution
Sun Nov 27 06:10:58 2016 kern.err kernel: [106841.412591] wlan1: failed to set key (1, ff:ff:ff:ff:ff:ff) to hardware (-5)
Sun Nov 27 06:15:00 2016 cron.info crond[1151]: USER root pid 1671 cmd /sbin/fan_ctrl.sh
Sun Nov 27 06:20:00 2016 cron.info crond[1151]: USER root pid 1678 cmd /sbin/fan_ctrl.sh
Sun Nov 27 06:21:00 2016 kern.err kernel: [107443.418717] ieee80211 phy1: cmd 0x9122=UpdateEncryption timed out
Sun Nov 27 06:21:00 2016 kern.err kernel: [107443.424933] ieee80211 phy1: return code: 0x1122
Sun Nov 27 06:21:00 2016 kern.err kernel: [107443.429568] ieee80211 phy1: timeout: 0x1122
Sun Nov 27 06:21:00 2016 kern.err kernel: [107443.433862] ieee80211 phy1: failed execution
Sun Nov 27 06:21:00 2016 kern.err kernel: [107443.438238] wlan1: failed to set key (2, ff:ff:ff:ff:ff:ff) to hardware (-5)
Sun Nov 27 06:25:00 2016 cron.info crond[1151]: USER root pid 1822 cmd /sbin/fan_ctrl.sh
Sun Nov 27 06:30:00 2016 cron.info crond[1151]: USER root pid 1827 cmd /sbin/fan_ctrl.sh
Sun Nov 27 06:30:37 2016 daemon.notice netifd: wan (1672): Sending renew...
Sun Nov 27 06:30:37 2016 daemon.notice netifd: wan (1672): Lease of 14.136.47.237 obtained, lease time 43200
Sun Nov 27 06:31:03 2016 kern.err kernel: [108045.460258] ieee80211 phy1: cmd 0x9122=UpdateEncryption timed out
Sun Nov 27 06:31:03 2016 kern.err kernel: [108045.466474] ieee80211 phy1: return code: 0x1122
Sun Nov 27 06:31:03 2016 kern.err kernel: [108045.471113] ieee80211 phy1: timeout: 0x1122
Sun Nov 27 06:31:03 2016 kern.err kernel: [108045.475408] ieee80211 phy1: failed execution
Sun Nov 27 06:31:03 2016 kern.err kernel: [108045.479782] wlan1: failed to set key (1, ff:ff:ff:ff:ff:ff) to hardware (-5)
Sun Nov 27 06:35:00 2016 cron.info crond[1151]: USER root pid 1986 cmd /sbin/fan_ctrl.sh
Sun Nov 27 06:40:00 2016 cron.info crond[1151]: USER root pid 1991 cmd /sbin/fan_ctrl.sh
Sun Nov 27 06:41:05 2016 kern.err kernel: [108647.516819] ieee80211 phy1: cmd 0x9122=UpdateEncryption timed out
Sun Nov 27 06:41:05 2016 kern.err kernel: [108647.523036] ieee80211 phy1: return code: 0x1122
Sun Nov 27 06:41:05 2016 kern.err kernel: [108647.527672] ieee80211 phy1: timeout: 0x1122
Sun Nov 27 06:41:05 2016 kern.err kernel: [108647.531958] ieee80211 phy1: failed execution
Sun Nov 27 06:41:05 2016 kern.err kernel: [108647.536340] wlan1: failed to set key (2, ff:ff:ff:ff:ff:ff) to hardware (-5)
Sun Nov 27 06:45:00 2016 cron.info crond[1151]: USER root pid 2134 cmd /sbin/fan_ctrl.sh
Sun Nov 27 06:50:00 2016 cron.info crond[1151]: USER root pid 2139 cmd /sbin/fan_ctrl.sh
Sun Nov 27 06:51:07 2016 kern.err kernel: [109249.543645] ieee80211 phy1: cmd 0x9122=UpdateEncryption timed out
Sun Nov 27 06:51:07 2016 kern.err kernel: [109249.549861] ieee80211 phy1: return code: 0x1122
Sun Nov 27 06:51:07 2016 kern.err kernel: [109249.554504] ieee80211 phy1: timeout: 0x1122
Sun Nov 27 06:51:07 2016 kern.err kernel: [109249.558791] ieee80211 phy1: failed execution
Sun Nov 27 06:51:07 2016 kern.err kernel: [109249.563164] wlan1: failed to set key (1, ff:ff:ff:ff:ff:ff) to hardware (-5)
Sun Nov 27 06:55:00 2016 cron.info crond[1151]: USER root pid 2282 cmd /sbin/fan_ctrl.sh
Sun Nov 27 07:00:00 2016 cron.info crond[1151]: USER root pid 2288 cmd /sbin/fan_ctrl.sh
Sun Nov 27 07:01:09 2016 kern.err kernel: [109851.592959] ieee80211 phy1: cmd 0x9122=UpdateEncryption timed out
Sun Nov 27 07:01:09 2016 kern.err kernel: [109851.599175] ieee80211 phy1: return code: 0x1122
Sun Nov 27 07:01:09 2016 kern.err kernel: [109851.603813] ieee80211 phy1: timeout: 0x1122
Sun Nov 27 07:01:09 2016 kern.err kernel: [109851.608108] ieee80211 phy1: failed execution
Sun Nov 27 07:01:09 2016 kern.err kernel: [109851.612483] wlan1: failed to set key (2, ff:ff:ff:ff:ff:ff) to hardware (-5)
Sun Nov 27 07:05:00 2016 cron.info crond[1151]: USER root pid 2432 cmd /sbin/fan_ctrl.sh
Sun Nov 27 07:10:00 2016 cron.info crond[1151]: USER root pid 2437 cmd /sbin/fan_ctrl.sh
Sun Nov 27 07:11:11 2016 kern.err kernel: [110453.626276] ieee80211 phy1: cmd 0x9122=UpdateEncryption timed out
Sun Nov 27 07:11:11 2016 kern.err kernel: [110453.632491] ieee80211 phy1: return code: 0x1122
Sun Nov 27 07:11:11 2016 kern.err kernel: [110453.637126] ieee80211 phy1: timeout: 0x1122
Sun Nov 27 07:11:11 2016 kern.err kernel: [110453.641418] ieee80211 phy1: failed execution
Sun Nov 27 07:11:11 2016 kern.err kernel: [110453.645793] wlan1: failed to set key (1, ff:ff:ff:ff:ff:ff) to hardware (-5)
Sun Nov 27 07:14:18 2016 daemon.info hostapd: wlan0: STA 40:40:a7:5b:d6:ec IEEE 802.11: authenticated
Sun Nov 27 07:14:18 2016 daemon.info hostapd: wlan0: STA 40:40:a7:5b:d6:ec IEEE 802.11: associated (aid 1)
Sun Nov 27 07:14:18 2016 daemon.info hostapd: wlan0: STA 40:40:a7:5b:d6:ec WPA: pairwise key handshake completed (RSN)
Sun Nov 27 07:14:19 2016 daemon.info dnsmasq-dhcp[1865]: DHCPREQUEST(br-lan) 192.168.0.72 40:40:a7:5b:d6:ec 
Sun Nov 27 07:14:19 2016 daemon.info dnsmasq-dhcp[1865]: DHCPACK(br-lan) 192.168.0.72 40:40:a7:5b:d6:ec android-4a6b30309c637b14
Sun Nov 27 07:15:00 2016 cron.info crond[1151]: USER root pid 2581 cmd /sbin/fan_ctrl.sh
Sun Nov 27 07:16:21 2016 daemon.info hostapd: wlan0: STA 40:40:a7:5b:d6:ec IEEE 802.11: authenticated
Sun Nov 27 07:16:21 2016 daemon.info hostapd: wlan0: STA 40:40:a7:5b:d6:ec IEEE 802.11: associated (aid 1)
Sun Nov 27 07:16:21 2016 daemon.info hostapd: wlan0: STA 40:40:a7:5b:d6:ec WPA: pairwise key handshake completed (RSN)
Sun Nov 27 07:16:22 2016 daemon.info dnsmasq-dhcp[1865]: DHCPREQUEST(br-lan) 192.168.0.72 40:40:a7:5b:d6:ec 
Sun Nov 27 07:16:22 2016 daemon.info dnsmasq-dhcp[1865]: DHCPACK(br-lan) 192.168.0.72 40:40:a7:5b:d6:ec android-4a6b30309c637b14
Sun Nov 27 07:17:54 2016 daemon.info hostapd: wlan0: STA 40:40:a7:5b:d6:ec IEEE 802.11: authenticated
Sun Nov 27 07:17:54 2016 daemon.info hostapd: wlan0: STA 40:40:a7:5b:d6:ec IEEE 802.11: associated (aid 1)
Sun Nov 27 07:17:54 2016 daemon.info hostapd: wlan0: STA 40:40:a7:5b:d6:ec WPA: pairwise key handshake completed (RSN)
Sun Nov 27 07:17:54 2016 daemon.info dnsmasq-dhcp[1865]: DHCPREQUEST(br-lan) 192.168.0.72 40:40:a7:5b:d6:ec 
Sun Nov 27 07:17:54 2016 daemon.info dnsmasq-dhcp[1865]: DHCPACK(br-lan) 192.168.0.72 40:40:a7:5b:d6:ec android-4a6b30309c637b14
Sun Nov 27 07:18:17 2016 authpriv.info dropbear[2586]: Child connection from 192.168.0.72:60084
Sun Nov 27 07:18:18 2016 authpriv.info dropbear[2586]: Exit before auth: Exited normally
Sun Nov 27 07:18:18 2016 authpriv.info dropbear[2587]: Child connection from 192.168.0.72:37654
Sun Nov 27 07:18:19 2016 authpriv.info dropbear[2587]: Exit before auth: Exited normally
Sun Nov 27 07:19:13 2016 authpriv.info dropbear[2588]: Child connection from 192.168.0.72:47138
Sun Nov 27 07:19:34 2016 authpriv.notice dropbear[2588]: Password auth succeeded for 'root' from 192.168.0.72:47138
Sun Nov 27 07:20:00 2016 cron.info crond[1151]: USER root pid 2594 cmd /sbin/fan_ctrl.sh
Sun Nov 27 07:21:11 2016 daemon.info hostapd: wlan0: STA 40:40:a7:5b:d6:ec WPA: group key handshake completed (RSN)
Sun Nov 27 07:21:13 2016 kern.err kernel: [111055.642798] ieee80211 phy1: cmd 0x9122=UpdateEncryption timed out
Sun Nov 27 07:21:13 2016 kern.err kernel: [111055.649011] ieee80211 phy1: return code: 0x1122
Sun Nov 27 07:21:13 2016 kern.err kernel: [111055.653646] ieee80211 phy1: timeout: 0x1122
Sun Nov 27 07:21:13 2016 kern.err kernel: [111055.657932] ieee80211 phy1: failed execution
Sun Nov 27 07:21:13 2016 kern.err kernel: [111055.662312] wlan1: failed to set key (2, ff:ff:ff:ff:ff:ff) to hardware (-5)

Post #13763

sera

27 Nov 2016, 09:49

JW0914 wrote:

@sera's right on with "rename interface to wan/lan on boot to get rid of the semi random names ethX"

If it were the golden bullet I'd had submitted a pull request already. Dlang is right that it is equivalent with what Lede had for short wrt. having the same identifier for the same purpose across the series. Renaming is just a means to get the identifiers under distribution control to get past the 4.6 hurdle and while at it give them more meaningful names.

Edit: typo

(Last edited by sera on 27 Nov 2016, 09:50)

Post #13764

sera

27 Nov 2016, 09:52

Villeneuve wrote:

That certainly seems a little untoward. You are going to have to have a great deal of certainty in the image being forced.

Guess it's meant as a workaround until fixed or reverted, can't imagine Felix considering this how it should work.

Post #13765

sera

27 Nov 2016, 10:09

@paulwrt

I suggest you try the images at https://downloads.openwrt.org/people/kaloz/ Those are staging builds of the stable branch CC which come with recent wireless driver. The driver in the actual 15.05.1 release is to old to be any good.

Post #13766

moccolo

27 Nov 2016, 11:33

@david502

Hi, i have been away for a while and now i read something about switch configuration change? Does it mean if i flash the new image for caiman switch configuratiuon is different?

Sorry for the question but didnt have time to read about it backwards.

i was thinking about upgrading to your image of 2016-11-26

thx
moccolo

Post #13767

Driver007

27 Nov 2016, 12:40

what speeds people get from samba whit usb3? can't get above 20MB/s LAN/WIFI.

WRT1900ACv2 whit lede build.

Post #13768

robd

27 Nov 2016, 14:08

Driver007 wrote:

what speeds people get from samba whit usb3? can't get above 20MB/s LAN/WIFI.
WRT1900ACv2 whit lede build.

wrt1900ACS
LEDE Reboot r1953 / LuCI Master (git-16.288.36935-1e1a706) [Kernel 4.4.26]
Copy from USB drive to local client over WLAN (5GHz): up to 50 MByte/sec.

Post #13769

davidc502

27 Nov 2016, 15:32

moccolo wrote:

@david502
Hi, i have been away for a while and now i read something about switch configuration change? Does it mean if i flash the new image for caiman switch configuratiuon is different?
Sorry for the question but didnt have time to read about it backwards.
i was thinking about upgrading to your image of 2016-11-26
thx
moccolo

The good news is that the change was reverted.

David

Post #13770

mikemccartney

27 Nov 2016, 16:04

According to Felix (He did the commit), you need to use the -F option in the sysupgrade. Awaiting to hear back from some of the users to see if this works or not.

I was on LEDE build 2321 that wouldn't flash and the -F option you mentioned worked for me (thanks btw), i'm on wrt1200 v1. There had been a bug report on LEDEs bug tracker about it that's now removed, so it may be fixed but i don't know for sure.

edit - ignore that last part, just saw David's comment that it was reverted.

edit part duex - ignore my first edit, just realized Davids comment was about something other than the flash problem.

(Last edited by mikemccartney on 27 Nov 2016, 17:14)

Post #13771

paulwrt

27 Nov 2016, 16:08

Thanks.

OpenWrt is new to me - hope can handle upgrading to development version. It is very comprehensive and powerful indeed.

I am checking it. Should i use the:-

...factory.img, or
...sysupgrade.tar?

sera wrote:

paulwrt
I suggest you try the images at downloads.openwrt.org/people/kaloz/ Those are staging builds of the stable branch CC which come with recent wireless driver. The driver in the actual 15.05.1 release is to old to be any good.

(Last edited by paulwrt on 27 Nov 2016, 18:02)

Post #13772

mojolacerator

27 Nov 2016, 16:32

paulwrt wrote:

Thanks.
OpenWrt is new to me - hope can handle upgrading to development version. It is very comprehensive and powerful indeed.
I am checking it. Should i use the:-
...factory.img, or
...sysupgrade.tar?

sera wrote:
Villeneuve wrote:
That certainly seems a little untoward. You are going to have to have a great deal of certainty in the image being forced.
Guess it's meant as a workaround until fixed or reverted, can't imagine Felix considering this how it should work.

...factory.img

just a suggestion, be sure to flash from Linksys stock firmware

Post #13773

muronghan

27 Nov 2016, 16:39

H,@paulwrt, I can be wrong. But please be aware that the wifi drive for CC.01 r48532 which is the official release, is quite out of date and full of bugs. You shall have to compile it by yourself with new thread if you want to stick to CC.01.

Meanwhile, data transfer thru USB3.0 hurts the 2.4GHz performance. That is the issue everyone knows.

(Last edited by muronghan on 27 Nov 2016, 16:42)

Post #13774

cybrnook2002

27 Nov 2016, 18:01

muronghan wrote:

H,@paulwrt, I can be wrong. But please be aware that the wifi drive for CC.01 r48532 which is the official release, is quite out of date and full of bugs. You shall have to compile it by yourself with new thread if you want to stick to CC.01.
Meanwhile, data transfer thru USB3.0 hurts the 2.4GHz performance. That is the issue everyone knows.

Or use one of Kaloz's build:

https://downloads.openwrt.org/people/kaloz/

Post #13775

paulwrt

27 Nov 2016, 18:05

Thanks all for your help!

I am not aware of the USB3.0 problem - I am using the USB2.0(eSATA) only
(I have suspected my radio 2.5gHZ problem start when i start use the USB port... but w/o knowledge to investigate).

muronghan wrote:

H,@paulwrt, I can be wrong. But please be aware that the wifi drive for CC.01 r48532 which is the official release, is quite out of date and full of bugs. You shall have to compile it by yourself with new thread if you want to stick to CC.01.
Meanwhile, data transfer thru USB3.0 hurts the 2.4GHz performance. That is the issue everyone knows.

(Last edited by paulwrt on 27 Nov 2016, 18:12)

Page 551 of 598