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.
this is what I have....
6<<%s version %s>>
Marvell 802.11ac Wireless Network Driver
10.3.0.3thanks Northbound. I didn't know it could be read.
You are welcome. But someone else originally posted the info I just try to remember what I read and learn 
clb wrote:gufus wrote:With AC use 80MHz
Also the 88W8864 chip does not support 160MHz
Thanks again... assuming you're talking about the channel width? If so I'm already using 80MHz
Mode: AC
Channel: auto (40 (5.200 GHz))
Width: 80MHz
Transmit Power: 20dBm (100 mW)Any other ideas?
Yes channel width to 80MHz
set your Country Code
Don't use autocheck whats busy
iw wlan1 scan |grep -e SSID -e 'primary channel' -e signal:Try a higher channel 144 - 161
I use (63 mW) Transmit Power
whats busy here
root@AC1900M:~# iw wlan1 scan |grep -e SSID -e 'primary channel' -e signal:
signal: -69.00 dBm
SSID: SHAW-3437A0-5G
* primary channel: 44
signal: -96.00 dBm
SSID: SHAW-212F40-5G
* primary channel: 44
signal: -92.00 dBm
SSID: OptikTV_10ADC53B
* primary channel: 48
signal: -96.00 dBm
SSID: SHAW-9D2465-5G
* primary channel: 149
signal: -78.00 dBm
SSID: SHAW-65500D-5G
* primary channel: 149
signal: -82.00 dBm
SSID: OptikTV_960B400B
* primary channel: 157
root@AC1900M:~#
Weird, I am trying to use AC and if I set mine on a higher channel, it doesn't allow me to connect at all.
# iw wlan1 info
Interface wlan1
ifindex 10
wdev 0x100000002
addr 00:25:9c:13:aa:74
type AP
wiphy 1
Marvell 88W8864 802.11nac (radio1)
Channel: 140 (5.700 GHz) | Bitrate: ? Mbit/s
Signal: 0 dBm / Noise: -96 dBm
0% SSID: Xaxa | Mode: Master
BSSID: XX:XX:XX:XX:XX:XX | Encryption: WPA2 PSK (CCMP)
gufus wrote:clb wrote:Thanks again... assuming you're talking about the channel width? If so I'm already using 80MHz
Mode: AC
Channel: auto (40 (5.200 GHz))
Width: 80MHz
Transmit Power: 20dBm (100 mW)Any other ideas?
Yes channel width to 80MHz
set your Country Code
Don't use autocheck whats busy
iw wlan1 scan |grep -e SSID -e 'primary channel' -e signal:Try a higher channel 144 - 161
I use (63 mW) Transmit Power
whats busy here
root@AC1900M:~# iw wlan1 scan |grep -e SSID -e 'primary channel' -e signal:
signal: -69.00 dBm
SSID: SHAW-3437A0-5G
* primary channel: 44
signal: -96.00 dBm
SSID: SHAW-212F40-5G
* primary channel: 44
signal: -92.00 dBm
SSID: OptikTV_10ADC53B
* primary channel: 48
signal: -96.00 dBm
SSID: SHAW-9D2465-5G
* primary channel: 149
signal: -78.00 dBm
SSID: SHAW-65500D-5G
* primary channel: 149
signal: -82.00 dBm
SSID: OptikTV_960B400B
* primary channel: 157
root@AC1900M:~#Weird, I am trying to use AC and if I set mine on a higher channel, it doesn't allow me to connect at all.
# iw wlan1 info
Interface wlan1
ifindex 10
wdev 0x100000002
addr 00:25:9c:13:aa:74
type AP
wiphy 1Marvell 88W8864 802.11nac (radio1)
Channel: 140 (5.700 GHz) | Bitrate: ? Mbit/s
Signal: 0 dBm / Noise: -96 dBm
0% SSID: Xaxa | Mode: Master
BSSID: XX:XX:XX:XX:XX:XX | Encryption: WPA2 PSK (CCMP)
What country code do you have set? Channels 149-161 are only available in some regulatory domains (USA and Ukraine to name two, but not UK or much of EU) - Channels 52 to 140 are only available pretty much anywhere in the world subject to DFS functioning - which it doesn't on the Linksys at this point in time.
I'd don't think there's any warnings in OpenWRT to alert you when you've set an 'illegal' channel for the country code the unit is set to.
xhemp wrote:gufus wrote:Yes channel width to 80MHz
set your Country Code
Don't use autocheck whats busy
iw wlan1 scan |grep -e SSID -e 'primary channel' -e signal:Try a higher channel 144 - 161
I use (63 mW) Transmit Power
whats busy here
root@AC1900M:~# iw wlan1 scan |grep -e SSID -e 'primary channel' -e signal:
signal: -69.00 dBm
SSID: SHAW-3437A0-5G
* primary channel: 44
signal: -96.00 dBm
SSID: SHAW-212F40-5G
* primary channel: 44
signal: -92.00 dBm
SSID: OptikTV_10ADC53B
* primary channel: 48
signal: -96.00 dBm
SSID: SHAW-9D2465-5G
* primary channel: 149
signal: -78.00 dBm
SSID: SHAW-65500D-5G
* primary channel: 149
signal: -82.00 dBm
SSID: OptikTV_960B400B
* primary channel: 157
root@AC1900M:~#Weird, I am trying to use AC and if I set mine on a higher channel, it doesn't allow me to connect at all.
# iw wlan1 info
Interface wlan1
ifindex 10
wdev 0x100000002
addr 00:25:9c:13:aa:74
type AP
wiphy 1Marvell 88W8864 802.11nac (radio1)
Channel: 140 (5.700 GHz) | Bitrate: ? Mbit/s
Signal: 0 dBm / Noise: -96 dBm
0% SSID: Xaxa | Mode: Master
BSSID: XX:XX:XX:XX:XX:XX | Encryption: WPA2 PSK (CCMP)What country code do you have set? Channels 149-161 are only available in some regulatory domains (USA and Ukraine to name two, but not UK or much of EU) - Channels 52 to 140 are only available pretty much anywhere in the world subject to DFS functioning - which it doesn't on the Linksys at this point in time.
I'd don't think there's any warnings in OpenWRT to alert you when you've set an 'illegal' channel for the country code the unit is set to.
GB (UK). I tried other channels (lower than 149) but still doesn't work.
I got now configured as 64 and this is what I see:
Marvell 88W8864 802.11nac (radio1)
Channel: 64 (5.320 GHz) | Bitrate:
iw wlan1 info shows this:
# iw wlan1 info
Interface wlan1
ifindex 9
wdev 0x100000002
addr 00:25:9c:13:aa:74
type AP
wiphy 1
The interface is up and accepts an iw scan:
iw wlan1 scan |grep -e SSID -e 'primary channel' -e signal:
signal: -79.00 dBm
SSID: BTHub4-6WS8
* primary channel: 40
signal: -80.00 dBm
SSID: BTWifi-with-FON
* primary channel: 40
signal: -80.00 dBm
SSID: BTWifi-X
* primary channel: 40
signal: -88.00 dBm
SSID: BTHub3-RC9C
* primary channel: 48
signal: -73.00 dBm
SSID: BTHub3-RC9C
* primary channel: 48
But it doesn't even show as available to connect from any of my boxes. It will just accept if I set to channel 40, for example.
Is there anything I am missing?
Edit: Hmm, channel 40 to 48 work fine.
Other channels, I can see some errors on the logs:
Wed Aug 26 16:12:52 2015 daemon.notice netifd: radio1 (2859): ELOOP: remaining socket: sock=19 eloop_data=0x1e163f8 user_data=(nil) handler=0x2fb24
Wed Aug 26 16:12:52 2015 daemon.notice netifd: radio1 (2859): cat: can't open '/var/run/wifi-phy1.pid': No such file or directory
Wed Aug 26 16:12:52 2015 daemon.notice netifd: radio1 (2859): Command failed: Invalid argument
ed Aug 26 16:15:11 2015 daemon.notice netifd: radio1 (4563): wlan1: interface state HT_SCAN->DFS
Wed Aug 26 16:15:11 2015 daemon.notice netifd: radio1 (4563): wlan1: DFS-CAC-START freq=5260 chan=52 sec_chan=1, width=1, seg0=58, seg1=0, cac_time=60s
Wed Aug 26 16:15:11 2015 kern.debug kernel: [ 617.037810] ieee80211 phy1: change: 0x40
Wed Aug 26 16:15:11 2015 kern.debug kernel: [ 617.091935] ieee80211 phy1: change: 0x100
Wed Aug 26 16:15:11 2015 daemon.notice netifd: radio1 (4563): DFS start_dfs_cac() failed, -1
Wed Aug 26 16:15:11 2015 daemon.notice netifd: radio1 (4563): Interface initialization failed
Wed Aug 26 16:15:11 2015 daemon.notice netifd: radio1 (4563): wlan1: interface state DFS->DISABLED
Wed Aug 26 16:15:11 2015 daemon.notice netifd: radio1 (4563): wlan1: AP-DISABLED
Wed Aug 26 16:15:11 2015 daemon.notice netifd: radio1 (4563): wlan1: interface state DISABLED->DISABLED
Wed Aug 26 16:15:11 2015 daemon.notice netifd: radio1 (4563): wlan1: AP-DISABLED
Wed Aug 26 16:15:11 2015 daemon.notice netifd: radio1 (4563): hostapd_free_hapd_data: Interface wlan1 wasn't started
(Last edited by xhemp on 26 Aug 2015, 16:15)
sc61 wrote:xhemp wrote:Weird, I am trying to use AC and if I set mine on a higher channel, it doesn't allow me to connect at all.
# iw wlan1 info
Interface wlan1
ifindex 10
wdev 0x100000002
addr 00:25:9c:13:aa:74
type AP
wiphy 1Marvell 88W8864 802.11nac (radio1)
Channel: 140 (5.700 GHz) | Bitrate: ? Mbit/s
Signal: 0 dBm / Noise: -96 dBm
0% SSID: Xaxa | Mode: Master
BSSID: XX:XX:XX:XX:XX:XX | Encryption: WPA2 PSK (CCMP)What country code do you have set? Channels 149-161 are only available in some regulatory domains (USA and Ukraine to name two, but not UK or much of EU) - Channels 52 to 140 are only available pretty much anywhere in the world subject to DFS functioning - which it doesn't on the Linksys at this point in time.
I'd don't think there's any warnings in OpenWRT to alert you when you've set an 'illegal' channel for the country code the unit is set to.
GB (UK). I tried other channels (lower than 149) but still doesn't work.
I got now configured as 64 and this is what I see:Marvell 88W8864 802.11nac (radio1)
Channel: 64 (5.320 GHz) | Bitrate:iw wlan1 info shows this:
# iw wlan1 info
Interface wlan1
ifindex 9
wdev 0x100000002
addr 00:25:9c:13:aa:74
type AP
wiphy 1The interface is up and accepts an iw scan:
iw wlan1 scan |grep -e SSID -e 'primary channel' -e signal:
signal: -79.00 dBm
SSID: BTHub4-6WS8
* primary channel: 40
signal: -80.00 dBm
SSID: BTWifi-with-FON
* primary channel: 40
signal: -80.00 dBm
SSID: BTWifi-X
* primary channel: 40
signal: -88.00 dBm
SSID: BTHub3-RC9C
* primary channel: 48
signal: -73.00 dBm
SSID: BTHub3-RC9C
* primary channel: 48But it doesn't even show as available to connect from any of my boxes. It will just accept if I set to channel 40, for example.
Is there anything I am missing?Edit: Hmm, channel 40 to 48 work fine.
Other channels, I can see some errors on the logs:Wed Aug 26 16:12:52 2015 daemon.notice netifd: radio1 (2859): ELOOP: remaining socket: sock=19 eloop_data=0x1e163f8 user_data=(nil) handler=0x2fb24
Wed Aug 26 16:12:52 2015 daemon.notice netifd: radio1 (2859): cat: can't open '/var/run/wifi-phy1.pid': No such file or directory
Wed Aug 26 16:12:52 2015 daemon.notice netifd: radio1 (2859): Command failed: Invalid argumented Aug 26 16:15:11 2015 daemon.notice netifd: radio1 (4563): wlan1: interface state HT_SCAN->DFS
Wed Aug 26 16:15:11 2015 daemon.notice netifd: radio1 (4563): wlan1: DFS-CAC-START freq=5260 chan=52 sec_chan=1, width=1, seg0=58, seg1=0, cac_time=60s
Wed Aug 26 16:15:11 2015 kern.debug kernel: [ 617.037810] ieee80211 phy1: change: 0x40
Wed Aug 26 16:15:11 2015 kern.debug kernel: [ 617.091935] ieee80211 phy1: change: 0x100
Wed Aug 26 16:15:11 2015 daemon.notice netifd: radio1 (4563): DFS start_dfs_cac() failed, -1
Wed Aug 26 16:15:11 2015 daemon.notice netifd: radio1 (4563): Interface initialization failed
Wed Aug 26 16:15:11 2015 daemon.notice netifd: radio1 (4563): wlan1: interface state DFS->DISABLED
Wed Aug 26 16:15:11 2015 daemon.notice netifd: radio1 (4563): wlan1: AP-DISABLED
Wed Aug 26 16:15:11 2015 daemon.notice netifd: radio1 (4563): wlan1: interface state DISABLED->DISABLED
Wed Aug 26 16:15:11 2015 daemon.notice netifd: radio1 (4563): wlan1: AP-DISABLED
Wed Aug 26 16:15:11 2015 daemon.notice netifd: radio1 (4563): hostapd_free_hapd_data: Interface wlan1 wasn't started
5GHz band status in the UK is summarised here:-
http://darrengauntlett.com/a-quick-guid … hz-part-2/
In my experience, current state of play with WRT1900AC with country code set to UK you will only actually be able to transmit/receive data on channels 36, 40, 44, 48 - irrespective of whether you're using Linksys FW, or OpenWRT CC14.07, 15.05 RC2 or 15.05 RC3. As discussed a few pages back in this thread it seems that Marvell's chipset driver doesn't currently support DFS full stop.
Thanks, sc61.
It's a bit concerning that they (linksys) sell something in a standard and do not fully support it.
I will go some pages back and have a look at the discussion you mentioned.
Thanks, sc61.
It's a bit concerning that they (linksys) sell something in a standard and do not fully support it.
I will go some pages back and have a look at the discussion you mentioned.
..and while I'm bitching about the radio functionality, there is no control over beacon Tx power either, it doesn't matter what you set via GUI or UCI, beacon power is always the same. Again this seems to be a fundamental Marvell driver issue that can't be fixed within OpenWRT.
xhemp wrote:Thanks, sc61.
It's a bit concerning that they (linksys) sell something in a standard and do not fully support it.
I will go some pages back and have a look at the discussion you mentioned...and while I'm bitching about the radio functionality, there is no control over beacon Tx power either, it doesn't matter what you set via GUI or UCI, beacon power is always the same. Again this seems to be a fundamental Marvell driver issue that can't be fixed within OpenWRT.
That too. Not OpenWRT's fault, OpenWRT just turns this router in a proper device with loads of different uses but thinking that the wireless driver is that flakey is indeed sad.
Hope they sort it out, let's see.
Thanks for the clarification, again.
(Last edited by xhemp on 27 Aug 2015, 15:15)
can someone please tell me the feed urls from opkg.conf for RC3 ?
I jsut installed rc3 to test and there are no feed urls in it?
can someone please tell me the feed urls from opkg.conf for RC3 ?
I jsut installed rc3 to test and there are no feed urls in it?
https://forum.openwrt.org/viewtopic.php?id=52219
modify according to needs
src/gz chaos_calmer_base http://downloads.openwrt.org/DISTRO_PATH/packages/base
src/gz chaos_calmer_telephony http://downloads.openwrt.org/DISTRO_PATH/packages/telephony
src/gz chaos_calmer_packages http://downloads.openwrt.org/DISTRO_PATH/packages/packages
src/gz chaos_calmer_routing http://downloads.openwrt.org/DISTRO_PATH/packages/routing
src/gz chaos_calmer_luci http://downloads.openwrt.org/DISTRO_PATH/packages/luci
src/gz chaos_calmer_management http://downloads.openwrt.org/DISTRO_PATH/packages/management
(Last edited by makarel on 26 Aug 2015, 18:28)
alirz wrote:can someone please tell me the feed urls from opkg.conf for RC3 ?
I jsut installed rc3 to test and there are no feed urls in it?https://forum.openwrt.org/viewtopic.php?id=52219
modify according to needssrc/gz chaos_calmer_base http://downloads.openwrt.org/DISTRO_PATH/packages/base
src/gz chaos_calmer_telephony http://downloads.openwrt.org/DISTRO_PATH/packages/telephony
src/gz chaos_calmer_packages http://downloads.openwrt.org/DISTRO_PATH/packages/packages
src/gz chaos_calmer_routing http://downloads.openwrt.org/DISTRO_PATH/packages/routing
src/gz chaos_calmer_luci http://downloads.openwrt.org/DISTRO_PATH/packages/luci
src/gz chaos_calmer_management http://downloads.openwrt.org/DISTRO_PATH/packages/management
thanks but i dont know what to put in place of "DISTRO_PATCH". Is it supposed to be "Chaos_calmer" ? How does it get pointed to RC3 repo?
I believe this issue (workaround) is listed in the 1900ac wiki
makarel wrote:alirz wrote:can someone please tell me the feed urls from opkg.conf for RC3 ?
I jsut installed rc3 to test and there are no feed urls in it?https://forum.openwrt.org/viewtopic.php?id=52219
modify according to needssrc/gz chaos_calmer_base http://downloads.openwrt.org/DISTRO_PATH/packages/base
src/gz chaos_calmer_telephony http://downloads.openwrt.org/DISTRO_PATH/packages/telephony
src/gz chaos_calmer_packages http://downloads.openwrt.org/DISTRO_PATH/packages/packages
src/gz chaos_calmer_routing http://downloads.openwrt.org/DISTRO_PATH/packages/routing
src/gz chaos_calmer_luci http://downloads.openwrt.org/DISTRO_PATH/packages/luci
src/gz chaos_calmer_management http://downloads.openwrt.org/DISTRO_PATH/packages/managementthanks but i dont know what to put in place of "DISTRO_PATCH". Is it supposed to be "Chaos_calmer" ? How does it get pointed to RC3 repo?
To make it easy peasy 4 ya
dest root /
dest ram /tmp
lists_dir ext /var/opkg-lists
option overlay_root /overlay
src/gz chaos_calmer_base http://downloads.openwrt.org/chaos_calm … kages/base
src/gz chaos_calmer_luci http://downloads.openwrt.org/chaos_calm … kages/luci
src/gz chaos_calmer_packages http://downloads.openwrt.org/chaos_calm … s/packages
src/gz chaos_calmer_routing http://downloads.openwrt.org/chaos_calm … es/routing
src/gz chaos_calmer_telephony http://downloads.openwrt.org/chaos_calm … /telephony
src/gz chaos_calmer_management http://downloads.openwrt.org/chaos_calm … management
src/gz chaos_calmer_targets http://downloads.openwrt.org/chaos_calm … es/targets
option check_signature 1
@ Davidc502 and gufus
Thanks
Anyone here using openssh instead of dropbear on the wrt1900ac?
I keep getting these messages in the log:
Could not load host key: /etc/ssh/ssh_host_ecdsa_key
Could not load host key: /etc/ssh/ssh_host_ed25519_key
I already created those keys at that path... Every freakin brute force attack triggers those error also... Trying to reduce logging a bit. On another note i cannot even seen to lower openssh's logging.
@ Davidc502 and gufus
Thanks
Tip
Everything from the initial flashing is in /rom (on the NAND)
running the latest trunk with the new wifi driver(10.0.3.8). I must say at least the 5GHZ performance, speed wise, is at least 40% faster than the previous 10.0.3.0 driver. Hopefully i dont encounter the lockups! will see.
running the latest trunk with the new wifi driver(10.0.3.8). I must say at least the 5GHZ performance, speed wise, is at least 40% faster than the previous 10.0.3.0 driver. Hopefully i dont encounter the lockups! will see.
In case you missed this here:
https://forum.openwrt.org/viewtopic.php … 38#p288438
10.0.3.8 has been recalled by Belkin and advise revert back to 10.0.3.0 and wait for the next update.
I believe that 10.0.3.8 by now should have been removed from all posts.
Are you sure that you are running 10.0.3.8. I recall a post reporting incorrect version information but I can't remember the context to search for it.
Rick
(Last edited by RickStep on 27 Aug 2015, 00:45)
Which driver do I have?
root@OpenWrt:~# md5sum /lib/firmware/mwlwifi/88W8864.bin
ed4225cbcb5d1e6a8f0b7a4ec045c6dd /lib/firmware/mwlwifi/88W8864.bin
tia
alirz wrote:running the latest trunk with the new wifi driver(10.0.3.8). I must say at least the 5GHZ performance, speed wise, is at least 40% faster than the previous 10.0.3.0 driver. Hopefully i dont encounter the lockups! will see.
In case you missed this here:
https://forum.openwrt.org/viewtopic.php … 38#p288438
10.0.3.8 has been recalled by Belkin and advise revert back to 10.0.3.0 and wait for the next update.
I believe that 10.0.3.8 by now should have been removed from all posts.
Are you sure that you are running 10.0.3.8. I recall a post reporting incorrect version information but I can't remember the context to search for it.
Rick
I know what you're talking about. I know the driver was supposed to be reverted back to the older version on trunk but someone else mentione like two days ago that apparently kaloz's revert didnt work or something.
Seems like I am running 10.0.3.8. First the wifi AC performance is a lot better.
The router shows the following in /lib/modules/3.18.20/mwlwifi.ko
version %s>>^@Marvell 802.11ac Wireless Network Driver^@^@^@^@10.3.0.8^
Also makefile has : PKG_SOURCE_VERSION:=59e0d3d167a5bc2c03010df4ed54cc0653b5ae58
isnt that the new one?
trunk still has 10.3.0.8, CC has 10.3.0.3. It depends what branch you've checked out.
aaf953e1baf9cd65979103c4fda98c0bd48f4759 is the commit you want to use for 10.3.0.3
that said, 10.3.0.8 and 10.3.0.3 use the same firmware, just different kernel module.
(Last edited by nyt on 27 Aug 2015, 03:58)
Which driver do I have?
root@OpenWrt:~# md5sum /lib/firmware/mwlwifi/88W8864.bin
ed4225cbcb5d1e6a8f0b7a4ec045c6dd /lib/firmware/mwlwifi/88W8864.bintia
That will just tell you which firmware. If you want to see which driver...
root@ZOMGWTFBBQWIFI:~# strings /lib/modules/3.18.20/mwlwifi.ko | grep 10.3
10.3.0.3
/home/nyt/archive/openwrt/wrt1900ac/cc/build_dir/target-arm_cortex-a9+vfpv3_musl-1.1.10_eabi/linux-mvebu/mwlwifi-10.3.0.8-20150819/tx.c
Thanks, I had to sub in my kernel.
root@OpenWrt:~# strings /lib/modules/3.18.17/mwlwifi.ko | grep 10.3
10.3.0.3
/home/buildbot/slave-local/mvebu_generic/build/build_dir/target-arm_cortex-a9+vfpv3_uClibc-0.9.33.2_eabi/linux-mvebu/mwlwifi-10.3.0.3-20150619/tx.c
Thanks, I had to sub in my kernel.
root@OpenWrt:~# strings /lib/modules/3.18.17/mwlwifi.ko | grep 10.3
10.3.0.3
/home/buildbot/slave-local/mvebu_generic/build/build_dir/target-arm_cortex-a9+vfpv3_uClibc-0.9.33.2_eabi/linux-mvebu/mwlwifi-10.3.0.3-20150619/tx.c
That's an old kernel. You may still have 10.3.0.3 without the latest firmware. You can see the commits here.
# strings /lib/modules/3.18.10//mwlwifi.ko | grep "10."
10.2.8.5.p0
# iw wlan1 info
Interface wlan1
ifindex 12
wdev 0x100000002
addr 00:25:9c:13:0f:d8
type AP
wiphy 1
channel 149 (5745 MHz), width: 80 MHz, center1: 5775 MHzSo far no problems, but could be a bit faster 
(Last edited by belliash on 27 Aug 2015, 09:21)