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.
Wanted to add that wget (the one with SSL) seems to be missing in the most recent build.
I'm also having the wireless config issue others have mentioned on my 1900ACS V2. Deleting the config file removed the Wireless config page from Luci, and the wifi config command didn't seem to have an effect. I had flashed from your penultimate build.
(Last edited by anymouse617 on 21 Feb 2018, 15:58)
Wanted to add that wget (the one with SSL) seems to be missing in the most recent build.
I'm also having the wireless config issue others have mentioned on my 1900ACS V2. Deleting the config file removed the Wireless config page from Luci, and the wifi config command didn't seem to have an effect. I had flashed from your penultimate build.
I had posted that Samba and wget packages failed to compile when the experimental build was ready to be downloaded. I did select the busybox version of wget with SSL support, and when updating packages from command line or LuCi, opkg doesn't have an issue grabbing those packages from the repository via ssl. I wasn't sure if that was going to work or not and fortunately it did.
How did you get wifi working? Also, did you come from the factory Firmware over to the experimental build?
Just to add my 2 cents, the experimental build I did from Master with 4.14 Kernel and Winbond patch has been completely stable (4 days now) on my 3200ACM. Wifi speeds have been very satisfactory.
- Had to remove the mwifiex-sdio packages (disabling the phy2 3rd radio) in order to get DFS WiFi working.
- Samba will not compile and cannot be used.
anymouse617 wrote:Wanted to add that wget (the one with SSL) seems to be missing in the most recent build.
I'm also having the wireless config issue others have mentioned on my 1900ACS V2. Deleting the config file removed the Wireless config page from Luci, and the wifi config command didn't seem to have an effect. I had flashed from your penultimate build.
I had posted that Samba and wget packages failed to compile when the experimental build was ready to be downloaded. I did select the busybox version of wget with SSL support, and when updating packages from command line or LuCi, opkg doesn't have an issue grabbing those packages from the repository via ssl. I wasn't sure if that was going to work or not and fortunately it did.
How did you get wifi working? Also, did you come from the factory Firmware over to the experimental build?
Sorry, to clarify, I meant to say that wifi is completely not working regardless of the attempts I made to troubleshoot. The wifi LEDs don't turn on either. I flashed from your previous build.
(Last edited by anymouse617 on 22 Feb 2018, 13:46)
davidc502 wrote:anymouse617 wrote:Wanted to add that wget (the one with SSL) seems to be missing in the most recent build.
I'm also having the wireless config issue others have mentioned on my 1900ACS V2. Deleting the config file removed the Wireless config page from Luci, and the wifi config command didn't seem to have an effect. I had flashed from your penultimate build.
I had posted that Samba and wget packages failed to compile when the experimental build was ready to be downloaded. I did select the busybox version of wget with SSL support, and when updating packages from command line or LuCi, opkg doesn't have an issue grabbing those packages from the repository via ssl. I wasn't sure if that was going to work or not and fortunately it did.
How did you get wifi working? Also, did you come from the factory Firmware over to the experimental build?
Sorry, to clarify, I meant to say that wifi is completely not working regardless of the attempts I made to troubleshoot. The wifi LEDs don't turn on either. I flashed from your previous build.
Interesting, as the V2's seem to be playing a roll in this as well.
Just to add my 2 cents, the experimental build I did from Master with 4.14 Kernel and Winbond patch has been completely stable (4 days now) on my 3200ACM. Wifi speeds have been very satisfactory.
- Had to remove the mwifiex-sdio packages (disabling the phy2 3rd radio) in order to get DFS WiFi working.
- Samba will not compile and cannot be used.
I've had no issues with 4.14 so far, and wifi has been very stable as well. Hopefully the developers get Samba working again.
Also appears we have folks loosing wifi when upgrading which is very strange.
Has anyone tried the latest snapshot build on an WRT 1900 ACV2
i.e:
snapshots/experimental/r6177/targets/mvebu/generic/lede-mvebu-linksys-wrt1900acv2-squashfs-sysupgrade.bin
Thanks!
@davidc502
The last "safe" build for mwlwifi (my opinion) is 1/30/2018. I see there's been a commit today to fix "memory corruption" and that may fix things, but after 1/30 there are two issues:
1. Only one of the "vfs_write" sections causing problems is patched out by trunk. After this date another section was added and that will need to be manually patched.
2. There was also a problem introduced that will crash wifi.
Last, I did a test build last night and samba is building fine. I checked and there have been no recent changes to the package either -- I wouldn't wait for "the developers" on this one.
@davidc502
The last "safe" build for mwlwifi (my opinion) is 1/30/2018. I see there's been a commit today to fix "memory corruption" and that may fix things, but after 1/30 there are two issues:
1. Only one of the "vfs_write" sections causing problems is patched out by trunk. After this date another section was added and that will need to be manually patched.
2. There was also a problem introduced that will crash wifi.Last, I did a test build last night and samba is building fine. I checked and there have been no recent changes to the package either -- I wouldn't wait for "the developers" on this one.
Last I checked I didn't see Samba in the nightly builds? Others have commented it hasn't been in the nightly builds for some time, and there's a case open in Fly Spray.
So, now I'm scratching my head again 
As InkblotAdmirer said, samba is building just fine here too on 4.14.
nitroshift
The FS around samba build issue was short lived, and I guess not closed. Re the vfs_write issue in mwlwifi, see my last post, you can patch up to what was the last commit at that time.
Edit: And on the mwlwifi front todays commit seems to have addressed the issue caused by the commit just previous.
(Last edited by Villeneuve on 23 Feb 2018, 01:06)
@Villeneuve
The link is broken.
nitroshift
Correct link for commit mentioned by @Villeneuve is: https://github.com/kaloz/mwlwifi/commit … 498740e520
Hi,
friends need help to configure my 2.4 wifi to work in the 600mbps that is capable in the WRT1900ACS, already tried all the configs and does not change so it stays in 20mhz it does not change to 40 and it does not have option for VTH20 and the maximum speed that shows and 216.7 mbps (verified on the wifi explorer pro - mac),
I saw a video on YT but for being a WRT1900AC I did not get it to work without knowing if I could.
What configuration do you recommend?
Per https://github.com/kaloz/mwlwifi/commit … 498740e520 and https://github.com/kaloz/mwlwifi/issues/270, I believe the reboot issues on the WRT1900AC may have been found and are in the process of being fixed.
Hi,
friends need help to configure my 2.4 wifi to work in the 600mbps that is capable in the WRT1900ACS, already tried all the configs and does not change so it stays in 20mhz it does not change to 40 and it does not have option for VTH20 and the maximum speed that shows and 216.7 mbps (verified on the wifi explorer pro - mac),
I saw a video on YT but for being a WRT1900AC I did not get it to work without knowing if I could.
What configuration do you recommend?
Can you take a screen shot the wifi statistics graphs for 2.4Ghz for the past day?
By the way, its been my experience over 200mbps is pretty darn good for 2.4Ghz unless you live out in the boondocks with no interference. I can't get 100mbps on 2.4 where I live, but have no issues getting over 300mbps on 5Ghz.
Hi @David, thanks for help me,
let me try to explain better, I mean the speed of the router, not my internet link.
How do I view this graph? the speed I speak of would be the nominal that the router makes available to the devices, which will use according to its characteristics of the WIFI card (G, N, AC), but using a network analysis application, I see that the maximum speeds for the networks are respectively 450, 1300 Mbps (1750 total) only, and I do not know where and how to do this configuration.
on the WRT1900 use at home on a fiber link of 50/10 mbps already the WRT3200 is in the company on a fiber link of 200/100 mbps both running its latest version. the 3200 is a rock, perfectly holding up to 70 devices in its networks of 5 and 2.4 without problems, but the nominal speed shown by the WIFI Explorer Pro only shows 1900 mbps (600 + 1300) with 1300 Mbps missing to add up to 3200 mbps, but I think this is due to the fact that I did not have the 3 # radio turned on yet, right?
Per https://github.com/kaloz/mwlwifi/commit … 498740e520 and https://github.com/kaloz/mwlwifi/issues/270, I believe the reboot issues on the WRT1900AC may have been found and are in the process of being fixed.
@AjkayAlan
Thx for this info, I can confirm the build version from: 'yuhhaurlin' is stable and works withous WIFI problems.
Router: WRT1900ac v1
Firmware: OpenWrt SNAPSHOT r6225-9595a9e / LuCI Master (git-18.051.28524-09ea6db)
Kernel: 4.9.82
Status: Stable
(Last edited by racef@ce on 23 Feb 2018, 23:39)
Hi @David, thanks for help me,
let me try to explain better, I mean the speed of the router, not my internet link.
How do I view this graph? the speed I speak of would be the nominal that the router makes available to the devices, which will use according to its characteristics of the WIFI card (G, N, AC), but using a network analysis application, I see that the maximum speeds for the networks are respectively 450, 1300 Mbps (1750 total) only, and I do not know where and how to do this configuration.
on the WRT1900 use at home on a fiber link of 50/10 mbps already the WRT3200 is in the company on a fiber link of 200/100 mbps both running its latest version. the 3200 is a rock, perfectly holding up to 70 devices in its networks of 5 and 2.4 without problems, but the nominal speed shown by the WIFI Explorer Pro only shows 1900 mbps (600 + 1300) with 1300 Mbps missing to add up to 3200 mbps, but I think this is due to the fact that I did not have the 3 # radio turned on yet, right?
I guess you are aware all of that is just 'theoretical' speeds, and not actual speeds. You're never going to get 3200mbps out of the 3200acm.. ever, and that's on stock or lede/openwrt.
The way that it breaks down is the 3200acm is a dual band router, and really (shh don't tell anyone) it is a 1900ac model with a theoretical speed of 600mbps on 2.4 and around 1.3Gbps on 5Ghz band. However supposedly in 160hMhz width it can support something like 3 of those streams at the same time, and once again theoretically bumping that number potentially up to 2.6Gbps Hence why they call it the (3200 = (2.6 + 600)).
Okay, if I recall you were originally asking about 2.4ghz. Supposedly it's capable of 600mbps... Well, it's a bit of a marketing ploy I'm afraid, IMHO. 600mbps will require devices that support 40Mhz widths, which around most places is difficult because of all the channels are crowded anyway.
Really, I wouldn't get caught up in the theoretical numbers game.
Best Regards
*EDIT*
Don't get me wrong.. The 3200 is a bad-a$$ box with lots of CPU power and RAM behind it. I've gone from the 1900acV1 through to the 1900acs, and now the 3200acm, and it's by far the best yet. I think the deal with the 3200acm is that it is a bit before its time which means its going to be future proof.
(Last edited by davidc502 on 24 Feb 2018, 04:54)
By the way, its been my experience over 200mbps is pretty darn good for 2.4Ghz unless you live out in the boondocks with no interference. I can't get 100mbps on 2.4 where I live, but have no issues getting over 300mbps on 5Ghz.
Here are my 2.4 (@40 with noscan + reghack, 20+ networks around, 2xMiMo station:
Connecting to host 192.168.1.5, port 9000
Cookie: TTROLL-AW2.1519457434.912256.057eb10
TCP MSS: 0 (default)
[ 4] local 192.168.1.13 port 6806 connected to 192.168.1.5 port 9000
Starting Test: protocol: TCP, 1 streams, 131072 byte blocks, omitting 0 seconds, 10 second test
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-1.00 sec 16.4 MBytes 137 Mbits/sec
[ 4] 1.00-2.00 sec 18.9 MBytes 158 Mbits/sec
[ 4] 2.00-3.00 sec 19.6 MBytes 165 Mbits/sec
[ 4] 3.00-4.00 sec 20.0 MBytes 168 Mbits/sec
[ 4] 4.00-5.00 sec 20.6 MBytes 173 Mbits/sec
[ 4] 5.00-6.00 sec 19.8 MBytes 166 Mbits/sec
[ 4] 6.00-7.00 sec 18.1 MBytes 152 Mbits/sec
[ 4] 7.00-8.00 sec 18.6 MBytes 156 Mbits/sec
[ 4] 8.00-9.00 sec 19.8 MBytes 166 Mbits/sec
[ 4] 9.00-10.00 sec 17.6 MBytes 148 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
Test Complete. Summary Results:
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-10.00 sec 189 MBytes 159 Mbits/sec sender
[ 4] 0.00-10.00 sec 189 MBytes 159 Mbits/sec receiver
CPU Utilization: local/sender 21.8% (2.0%u/19.8%s), remote/receiver 19.4% (0.7%u/18.7%s)PS: Seems like no one meet multicast problems...
Also appears we have folks loosing wifi when upgrading which is very strange.
I can confirm that. After upgrading to the experimental r6177 on 3200, wireless connectivity is gone. etc/config/wireless is where it's supposed to be, and I can see the "wireless" tab in LuCI as well. However, it says "wireless disabled or not associated" and I cannot start it manually.
Rolled back to previous build.
Here are my logs:
at Feb 24 14:32:31 2018 kern.warn kernel: [ 9.452316] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 9.490549] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 9.551518] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 9.590890] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 9.630482] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.info kernel: [ 9.671124] hidraw: raw HID events driver (C) Jiri Kosina
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 9.677129] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 9.720505] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 9.760496] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 9.800747] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 9.840488] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 9.880810] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 9.920483] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 9.980828] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 10.020488] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 10.060771] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 10.100789] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 10.140478] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 10.200769] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 10.240473] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 10.280772] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 10.320475] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 10.380768] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 10.420472] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.info kernel: [ 10.460283] u32 classifier
Sat Feb 24 14:32:31 2018 kern.info kernel: [ 10.463003] input device check on
Sat Feb 24 14:32:31 2018 kern.info kernel: [ 10.466679] Actions configured
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 10.470627] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 10.520488] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 10.560732] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 10.600471] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.info kernel: [ 10.640267] Mirror/redirect action on
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 10.644458] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 10.680485] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 10.720777] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 10.760479] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 10.800493] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.info kernel: [ 10.841907] nf_conntrack version 0.5.0 (8192 buckets, 32768 max)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 10.848894] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 10.880537] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 10.940516] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 10.980799] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 11.020755] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 11.090484] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 11.130803] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 11.170487] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 11.210460] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 11.250798] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 11.290501] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 11.330803] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 11.370505] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 11.410757] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 11.450811] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 11.490489] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 11.530752] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 11.570486] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 11.630460] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 11.670776] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 11.710861] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 11.750498] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 11.790463] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 11.851403] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 11.890688] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 11.910929] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 11.950543] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 11.990816] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 12.030516] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 12.070802] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 12.110522] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 12.150778] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 12.193106] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 12.230598] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 12.280713] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 12.320468] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 12.360483] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 12.400854] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.info kernel: [ 12.451129] fuse init (API version 7.26)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 12.455816] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 12.500531] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.info kernel: [ 12.543269] Bluetooth: Core ver 2.22
Sat Feb 24 14:32:31 2018 kern.info kernel: [ 12.546893] NET: Registered protocol family 31
Sat Feb 24 14:32:31 2018 kern.info kernel: [ 12.551367] Bluetooth: HCI device and connection manager initialized
Sat Feb 24 14:32:31 2018 kern.info kernel: [ 12.557753] Bluetooth: HCI socket layer initialized
Sat Feb 24 14:32:31 2018 kern.info kernel: [ 12.562657] Bluetooth: L2CAP socket layer initialized
Sat Feb 24 14:32:31 2018 kern.info kernel: [ 12.567737] Bluetooth: SCO socket layer initialized
Sat Feb 24 14:32:31 2018 kern.info kernel: [ 12.573043] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Sat Feb 24 14:32:31 2018 kern.info kernel: [ 12.578379] Bluetooth: BNEP filters: protocol multicast
Sat Feb 24 14:32:31 2018 kern.info kernel: [ 12.583641] Bluetooth: BNEP socket layer initialized
Sat Feb 24 14:32:31 2018 kern.info kernel: [ 12.589837] Bluetooth: vendor=0x2df, device=0x9136, class=255, fn=2
Sat Feb 24 14:32:31 2018 kern.info kernel: [ 13.390458] Bluetooth: FW download over, size 695532 bytes
Sat Feb 24 14:32:31 2018 kern.err kernel: [ 14.009958] sdio platform data not available
Sat Feb 24 14:32:31 2018 kern.info kernel: [ 14.011464] usbcore: registered new interface driver btusb
Sat Feb 24 14:32:31 2018 kern.info kernel: [ 14.021956] Bluetooth: HCI UART driver ver 2.3
Sat Feb 24 14:32:31 2018 kern.info kernel: [ 14.026421] Bluetooth: HCI UART protocol H4 registered
Sat Feb 24 14:32:31 2018 kern.info kernel: [ 14.031589] Bluetooth: HCI UART protocol BCSP registered
Sat Feb 24 14:32:31 2018 kern.info kernel: [ 14.036925] Bluetooth: HCI UART protocol ATH3K registered
Sat Feb 24 14:32:31 2018 kern.info kernel: [ 14.042841] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
Sat Feb 24 14:32:31 2018 kern.info kernel: [ 14.048793] Bluetooth: HIDP socket layer initialized
Sat Feb 24 14:32:31 2018 kern.info kernel: [ 14.054492] ip_tables: (C) 2000-2006 Netfilter Core Team
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 14.380546] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.info kernel: [ 14.592642] Bluetooth: RFCOMM TTY layer initialized
Sat Feb 24 14:32:31 2018 kern.info kernel: [ 14.597551] Bluetooth: RFCOMM socket layer initialized
Sat Feb 24 14:32:31 2018 kern.info kernel: [ 14.602727] Bluetooth: RFCOMM ver 1.11
Sat Feb 24 14:32:31 2018 kern.info kernel: [ 14.607602] usbcore: registered new interface driver ums-alauda
Sat Feb 24 14:32:31 2018 kern.info kernel: [ 14.613934] usbcore: registered new interface driver ums-cypress
Sat Feb 24 14:32:31 2018 kern.info kernel: [ 14.620238] usbcore: registered new interface driver ums-datafab
Sat Feb 24 14:32:31 2018 kern.info kernel: [ 14.626509] usbcore: registered new interface driver ums-freecom
Sat Feb 24 14:32:31 2018 kern.info kernel: [ 14.632797] usbcore: registered new interface driver ums-isd200
Sat Feb 24 14:32:31 2018 kern.info kernel: [ 14.638987] usbcore: registered new interface driver ums-jumpshot
Sat Feb 24 14:32:31 2018 kern.info kernel: [ 14.645349] usbcore: registered new interface driver ums-karma
Sat Feb 24 14:32:31 2018 kern.info kernel: [ 14.651512] usbcore: registered new interface driver ums-sddr09
Sat Feb 24 14:32:31 2018 kern.info kernel: [ 14.657715] usbcore: registered new interface driver ums-sddr55
Sat Feb 24 14:32:31 2018 kern.info kernel: [ 14.663936] usbcore: registered new interface driver ums-usbat
Sat Feb 24 14:32:31 2018 kern.info kernel: [ 14.678180] xt_time: kernel timezone is -0000
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 14.840617] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.info kernel: [ 14.882516] PPP generic driver version 2.4.2
Sat Feb 24 14:32:31 2018 kern.info kernel: [ 14.887248] NET: Registered protocol family 24
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 14.892423] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 kern.warn kernel: [ 14.931421] mwlwifi: Unknown symbol vfs_write (err 0)
Sat Feb 24 14:32:31 2018 user.err kernel: [ 14.970037] kmodloader: 1 module could not be probed
Sat Feb 24 14:32:31 2018 user.err kernel: [ 14.975055] kmodloader: - mwlwifi - 0
Sat Feb 24 14:32:31 2018 daemon.notice haveged: haveged starting up
Sat Feb 24 14:32:31 2018 daemon.info haveged: haveged: ver: 1.9.2; arch: generic; vend: ; build: (gcc 5.5.0 CV); collect: 128K
Sat Feb 24 14:32:31 2018 daemon.info haveged: haveged: cpu: (); data: 32K (P); inst: 32K (P); idx: 16/40; sz: 32428/78796
Sat Feb 24 14:32:31 2018 daemon.info haveged: haveged: fills: 0, generated: 0
Sat Feb 24 14:32:32 2018 user.notice : Added device handler type: tunnel
Sat Feb 24 14:32:32 2018 user.notice : Added device handler type: Network device
Sat Feb 24 14:32:32 2018 user.notice : Added device handler type: bridge
Sat Feb 24 14:32:32 2018 user.notice : Added device handler type: veth
Sat Feb 24 14:32:32 2018 user.notice : Added device handler type: macvlan
Sat Feb 24 14:32:32 2018 user.notice : Added device handler type: 8021ad
Sat Feb 24 14:32:32 2018 user.notice : Added device handler type: 8021q
Sat Feb 24 14:32:32 2018 daemon.err block: /dev/ubiblock0_0 is already mounted on /rom
Sat Feb 24 14:32:32 2018 daemon.err block: /dev/ubi0_1 is already mounted on /overlay
Sat Feb 24 14:32:32 2018 daemon.notice netifd: Interface 'lan' is enabled
Sat Feb 24 14:32:32 2018 daemon.notice netifd: Interface 'lan' is setting up now
Sat Feb 24 14:32:32 2018 daemon.notice netifd: Interface 'lan' is now up
Sat Feb 24 14:32:32 2018 daemon.notice netifd: Interface 'loopback' is enabled
Sat Feb 24 14:32:32 2018 daemon.notice netifd: Interface 'loopback' is setting up now
Sat Feb 24 14:32:32 2018 daemon.notice netifd: Interface 'loopback' is now up
Sat Feb 24 14:32:32 2018 kern.info kernel: [ 16.931747] mvneta f1034000.ethernet eth0: configuring for fixed/sgmii link mode
Sat Feb 24 14:32:32 2018 kern.info kernel: [ 16.939289] mvneta f1034000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
Sat Feb 24 14:32:32 2018 kern.info kernel: [ 16.941265] br-lan: port 1(eth0) entered blocking state
Sat Feb 24 14:32:32 2018 kern.info kernel: [ 16.941267] br-lan: port 1(eth0) entered disabled state
Sat Feb 24 14:32:32 2018 kern.info kernel: [ 16.941362] device eth0 entered promiscuous mode
Sat Feb 24 14:32:32 2018 kern.info kernel: [ 16.942502] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready
Sat Feb 24 14:32:32 2018 daemon.notice netifd: Network device 'eth0' link is up
Sat Feb 24 14:32:32 2018 daemon.notice netifd: Network device 'lo' link is up
Sat Feb 24 14:32:32 2018 daemon.notice netifd: Interface 'loopback' has link connectivity
Sat Feb 24 14:32:32 2018 daemon.notice netifd: radio2 (1715): Could not find PHY for device 'radio2'
Sat Feb 24 14:32:32 2018 daemon.notice netifd: radio0 (1713): Could not find PHY for device 'radio0'
Sat Feb 24 14:32:33 2018 kern.info kernel: [ 16.982824] br-lan: port 1(eth0) entered blocking state
Sat Feb 24 14:32:33 2018 kern.info kernel: [ 16.988088] br-lan: port 1(eth0) entered forwarding state
Sat Feb 24 14:32:33 2018 daemon.notice netifd: bridge 'br-lan' link is up
Sat Feb 24 14:32:33 2018 daemon.notice netifd: Interface 'lan' has link connectivity
Sat Feb 24 14:32:33 2018 daemon.notice netifd: radio1 (1714): Could not find PHY for device 'radio1'
Sat Feb 24 14:32:33 2018 kern.info kernel: [ 17.001379] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
Sat Feb 24 14:32:33 2018 daemon.notice netifd: radio0 (1746): WARNING: Variable 'data' does not exist or is not an array/object
Sat Feb 24 14:32:33 2018 daemon.notice netifd: radio2 (1737): WARNING: Variable 'data' does not exist or is not an array/object
Sat Feb 24 14:32:33 2018 daemon.notice netifd: radio1 (1745): WARNING: Variable 'data' does not exist or is not an array/object(Last edited by floydburgermcdahm on 24 Feb 2018, 14:46)
@floydburgermcdahm
I see what you are talking about, and "wifi config" does not rebuild the wireless configuration. I've seen a similar issue a couple years ago, and am looking to see what the options were at that time.
I created another build and did a test upgrade, and wifi is hosed.
I just finished another build with kernel 4.9.82. Samba compiled as well as wget, and there were no problems with wifi.
I just finished another build with kernel 4.9.82. Samba compiled as well as wget, and there were no problems with wifi.
Thanks...r6302 works for me as well! I guess I'll just wait a little longer until the problems with 4.14 are fixed.
Hi.
I guess you are aware all of that is just 'theoretical' speeds, and not actual speeds. You're never going to get 3200mbps out of the 3200acm.. ever, and that's on stock or lede/openwrt.
The way that it breaks down is the 3200acm is a dual band router, and really (shh don't tell anyone) it is a 1900ac model with a theoretical speed of 600mbps on 2.4 and around 1.3Gbps on 5Ghz band. However supposedly in 160hMhz width it can support something like 3 of those streams at the same time, and once again theoretically bumping that number potentially up to 2.6Gbps Hence why they call it the (3200 = (2.6 + 600)).
Okay, if I recall you were originally asking about 2.4ghz. Supposedly it's capable of 600mbps... Well, it's a bit of a marketing ploy I'm afraid, IMHO. 600mbps will require devices that support 40Mhz widths, which around most places is difficult because of all the channels are crowded anyway.
Really, I wouldn't get caught up in the theoretical numbers game.
Best Regards
*EDIT*
Don't get me wrong.. The 3200 is a bad-a$$ box with lots of CPU power and RAM behind it. I've gone from the 1900acV1 through to the 1900acs, and now the 3200acm, and it's by far the best yet. I think the deal with the 3200acm is that it is a bit before its time which means its going to be future proof.
David I totally agree with you, even if I live in a country (Brazil) where officially these two equipments are not sold, so no WARRANTY, and ZERO support, that makes no difference in BRASIL Linksys leaves much to be desired in the matter of support, but even so I opted to buy them, since I had a good experience with WR54, and lastly with an EA6200 that still works today, and look at buying equipment in Brazil and complicated because besides the currency difference (change) we still pay 160% of taxes.
I really mean the speed stamped in the box of the product, I know in practice and complicated to use, but in other equipment programs like WIFI Explorer Pro, NetSpot Pro always show these speeds, as they do in the EA6200 or Archer C7, and in all other Routers I've used, except WRT, Kinksys says that the WRT3200 would be 3200Mbps, but in the applications it only shows 1750 or 1900 Mbps, already in the WRT1900ACS v2 the maximum was 1750 Mbps. Anyway even without using and good to know that this speed would be at the dog could be used. : D
two other doubts, I saw that they are speaking in kerne 4.XX for p WRT 3200, what would be the advantage of using an older kernel?
for the WRT line, there is already a more recent WIFI (hardwere) driver than the one we use in your vs. download?
where could you get this beta version for testing?
I thank you for your attention and patience, because the language barrier disturbs and confuses the reciocinio of what is written.
Guedes,