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

Post #726

OperatorOverload

27 Aug 2014, 17:54

Chadster766 wrote:

Chadster766 wrote:
To give WRT1900AC owners more than one option for OpenWRT I suggest the below:
Fork https://github.com/jimmychungbelkin/Mamba
Build a known good codebase AAv3.9 (git tag v3.9) as described in post https://forum.openwrt.org/viewtopic.php … 14#p244714
Create a new GitHub Repository and upload only the AAv3.9 baseline
IMHO this is the best case starting point.
I guess since I suggested it I should try to get it done.

Sounds good Chad. I've also forked the mrvl_wlan_v7drv on Github and am working on getting it to compile against trunk. That's a different stream here, but the efforts are definitely related. I'm definitely not a Linux kernel developer and would appreciate help from anybody who is willing to give it. Fork is at https://github.com/OperatorOverload/mrvl_wlan_v7drv/

OpOv

Post #727

gufus

27 Aug 2014, 21:50

Chadster766 wrote:

Chadster766 wrote:
To give WRT1900AC owners more than one option for OpenWRT I suggest the below:
Fork https://github.com/jimmychungbelkin/Mamba
Build a known good codebase AAv3.9 (git tag v3.9) as described in post https://forum.openwrt.org/viewtopic.php … 14#p244714
Create a new GitHub Repository and upload only the AAv3.9 baseline
IMHO this is the best case starting point.
I guess since I suggested it I should try to get it done.

Agreed

BTY, 5ghz works fine

encryption psk2+ccmp aes
ASUS USB-AC53 802.11ac Wireless USB Adapter (192.168.200.210)
http://www.gypsy-designs.com/71.jpg

(Last edited by gufus on 27 Aug 2014, 22:40)

Post #728

Chadster766

27 Aug 2014, 21:55

gufus wrote:

Chadster766 wrote:
Chadster766 wrote:
To give WRT1900AC owners more than one option for OpenWRT I suggest the below:
Fork https://github.com/jimmychungbelkin/Mamba
Build a known good codebase AAv3.9 (git tag v3.9) as described in post https://forum.openwrt.org/viewtopic.php … 14#p244714
Create a new GitHub Repository and upload only the AAv3.9 baseline
IMHO this is the best case starting point.
I guess since I suggested it I should try to get it done.
Agreed
BTY, 5ghz works fine
encryption psk2+ccmp
ASUS USB-AC53 802.11ac Wireless USB Adapter (192.168.200.210)
http://www.gypsy-designs.com/71.jpg

I'm committing the code to the new repository now. It will take a while. My first attempt failed due to file size limits. That's a GitHub rookie for ya

Post #729

OperatorOverload

28 Aug 2014, 03:31

Ok, my forked version of the wlan_v7 driver now builds against OpenWRT trunk for anybody who would like to start going down that road, which I see as a parallel effort to getting the AA and BB working well using the source driver. No idea if it works yet as I've not tried to load the image.

Fork is here: https://github.com/OperatorOverload/mrvl_wlan_v7drv

Post #730

Chadster766

28 Aug 2014, 16:57

Chadster766 wrote:

Chadster766 wrote:
To give WRT1900AC owners more than one option for OpenWRT I suggest the below:
Fork https://github.com/jimmychungbelkin/Mamba
Build a known good codebase AAv3.9 (git tag v3.9) as described in post https://forum.openwrt.org/viewtopic.php … 14#p244714
Create a new GitHub Repository and upload only the AAv3.9 baseline
IMHO this is the best case starting point.
I guess since I suggested it I should try to get it done.

This is completed
https://github.com/Chadster766/McWRT

All Suggestions, Coders and Admins welcome to contribute!

Post #731

nyt

28 Aug 2014, 19:20

nyt wrote:

So I have their latest barrier breaker build compiled, I'll test sometime soon when I have time. Seems feeds.conf.default needed some love.
-rw-r--r-- 1 nyt users 16777216 Aug 26 00:16 openwrt-mvebu-mamba-jffs2-128k.img
$ cat feeds.conf.default
src-git packages git://git.openwrt.org/packages.git
src-git packages2 https://github.com/openwrt/packages.git
src-git luci git://nbd.name/luci.git
src-git routing git://github.com/openwrt-routing/packages.git
src-git telephony http://feeds.openwrt.nanl.de/openwrt/telephony.git

Running this now with the belkin binary drivers. Doesn't seem to have the previous issues where transfers would cause hangs. However, walked around the house with laptop transferring a file from the network over 5ghz and it caused the kernel to OOPS and reboot.

(Last edited by nyt on 28 Aug 2014, 19:21)

Post #732

gufus

28 Aug 2014, 20:36

Chadster766 wrote:

gufus wrote:
Chadster766 wrote:
You can look at the v3.9_config file to find out.
https://github.com/jimmychungbelkin/Mam … 3.9_config
Ah, not bulit in
I could try to add it to the image if you tell me what packages are required from the v3.9_config list.

Just this to yes in config

# CONFIG_PACKAGE_webif-iw-lua-openvpn

Post #733

gufus

28 Aug 2014, 20:40

Chadster766 wrote:

Chadster766 wrote:
Chadster766 wrote:
To give WRT1900AC owners more than one option for OpenWRT I suggest the below:
Fork https://github.com/jimmychungbelkin/Mamba
Build a known good codebase AAv3.9 (git tag v3.9) as described in post https://forum.openwrt.org/viewtopic.php … 14#p244714
Create a new GitHub Repository and upload only the AAv3.9 baseline
IMHO this is the best case starting point.
I guess since I suggested it I should try to get it done.
This is completed
https://github.com/Chadster766/McWRT
All Suggestions, Coders and Admins welcome to contribute!

A+

Nice job!

Post #734

Chadster766

28 Aug 2014, 20:50

gufus wrote:

Chadster766 wrote:
gufus wrote:
Ah, not bulit in
I could try to add it to the image if you tell me what packages are required from the v3.9_config list.
Just this to yes in config
# CONFIG_PACKAGE_webif-iw-lua-openvpn

That should be easy enough. I will give it a shot.

(Last edited by Chadster766 on 28 Aug 2014, 20:52)

Post #735

gufus

28 Aug 2014, 21:07

Chadster766 wrote:

gufus wrote:
Chadster766 wrote:
I could try to add it to the image if you tell me what packages are required from the v3.9_config list.
Just this to yes in config
# CONFIG_PACKAGE_webif-iw-lua-openvpn
That should be easy enough. I will give it a shot.

Maybe try the new img from /tmp

eg: /tmp# sysupgrade -c openwrt-mvebu-mamba-jffs2-128k.img

upgrade-option:
-d <delay> add a delay before rebooting
-f <config> restore configuration from .tar.gz (file or url)
-i interactive mode
-c attempt to preserve all changed files in /etc/
-n do not save configuration over reflash
-F | --force
Flash image even if image checks fail, this is dangerous!
-q less verbose
-v more verbose
-h | --help display this help

backup-command:
-b | --create-backup <file>
create .tar.gz of files specified in sysupgrade.conf
then exit. Does not flash an image. If file is '-',
i.e. stdout, verbosity is set to 0 (i.e. quiet).
-r | --restore-backup <file>
restore a .tar.gz created with sysupgrade -b
then exit. Does not flash an image. If file is '-',
the archive is read from stdin.

(Last edited by gufus on 28 Aug 2014, 21:21)

Post #736

nyt

28 Aug 2014, 22:08

So, the latest BB build uses this driver, which seems to have a static .a component. However, it also appears newer than the build you guys are compiling.

https://github.com/jimmychungbelkin/Mam … /marvellac

Post #737

gufus

28 Aug 2014, 22:29

nyt wrote:

So, the latest BB build uses this driver, which seems to have a static .a component. However, it also appears newer than the build you guys are compiling.
https://github.com/jimmychungbelkin/Mam … /marvellac

lib_w8864.a

This?

Post #738

nyt

28 Aug 2014, 22:58

gufus wrote:

nyt wrote:
So, the latest BB build uses this driver, which seems to have a static .a component. However, it also appears newer than the build you guys are compiling.
https://github.com/jimmychungbelkin/Mam … /marvellac
lib_w8864.a
This?

Yep, but it seems xferring files on 5ghz now causes a kernel oops. good times.

Post #739

nyt

29 Aug 2014, 02:19

nyt wrote:

gufus wrote:
nyt wrote:
So, the latest BB build uses this driver, which seems to have a static .a component. However, it also appears newer than the build you guys are compiling.
https://github.com/jimmychungbelkin/Mam … /marvellac
lib_w8864.a
This?
Yep, but it seems xferring files on 5ghz now causes a kernel oops. good times.

and 2.4ghz

trying a fresh aa build with the new driver now.

Post #740

nyt

29 Aug 2014, 02:46

nyt wrote:

nyt wrote:
gufus wrote:
lib_w8864.a
This?
Yep, but it seems xferring files on 5ghz now causes a kernel oops. good times.
and 2.4ghz
trying a fresh aa build with the new driver now.

crashes in aa as well. will try the regular mrvl_wlan_v7drv instead.

[  301.280453] [<c00cafac>] (kfree+0x0/0xb0) from [<c0386ce0>] (__kfree_skb+0x1fc/0x2b0)
[  301.288307]  r6:bf070658 r5:bf28ac38 r4:cf2f1da0 r3:00000000
[  301.294038] [<c0386ae4>] (__kfree_skb+0x0/0x2b0) from [<c0386de8>] (consume_skb+0x54/0x58)
[  301.302326]  r5:bf28ac38 r4:ce81c000
[  301.305944] [<c0386d94>] (consume_skb+0x0/0x58) from [<c0391924>] (dev_kfree_skb_any+0x44/0x48)
[  301.314723] [<c03918e0>] (dev_kfree_skb_any+0x0/0x48) from [<bf02c4b8>] (_969+0x1a4/0x1a8 [ap8x])
[  301.323672] [<bf02c314>] (_969+0x0/0x1a8 [ap8x]) from [<bf049f2c>] (_751+0xd1c/0x175c [ap8x])
[  301.332266] [<bf049210>] (_751+0x0/0x175c [ap8x]) from [<bf01769c>] (_1315+0x15c/0x3dc [ap8x])
[  301.340931] [<bf017540>] (_1315+0x0/0x3dc [ap8x]) from [<c006b878>] (tasklet_action+0xa0/0x120)
[  301.349662] [<c006b7d8>] (tasklet_action+0x0/0x120) from [<c006bd14>] (__do_softirq+0x9c/0x134)
[  301.358394] [<c006bc78>] (__do_softirq+0x0/0x134) from [<c006c140>] (irq_exit+0x4c/0x54)
[  301.366518] [<c006c0f4>] (irq_exit+0x0/0x54) from [<c000e9b8>] (handle_IRQ+0x84/0xc0)
[  301.374377] [<c000e934>] (handle_IRQ+0x0/0xc0) from [<c0008190>] (asm_do_IRQ+0x10/0x14)
[  301.382404]  r5:60000013 r4:c000ec84
[  301.386017] [<c0008180>] (asm_do_IRQ+0x0/0x14) from [<c000d534>] (__irq_svc+0x34/0xe8)
[  301.393958] Exception stack(0xc0601f50 to 0xc0601f98)

Post #741

nyt

29 Aug 2014, 02:48

greymattr wrote:

nyt wrote:
greymattr wrote:
Hi all,
I really hope this is the last update I post before the inital WRT1900AC wireless driver is released.
I will admit that this process is taking much longer than I thought it would, but I am very grateful to the engineers at Marvell for making sure that everything 'checks out' prior to the release. Currently we are making sure there are no legal issues with the release, and that is a time consuming process.
So far the testing of the open source driver has been going well, for the few people who have access to it. However, I would not be surprised if there were updates in the future.
Some users may be disappointed to learn that the release will contain a pre-built library. While this may not be ideal for some users, it is good progress and will allow for developers to recompile the driver as updates are made to the kernel. Going forward I am sure efforts will be made to incorporate a wireless driver where developers have access to 100% of the source.
Personally, I would like to thank you for your patience, and understanding through this process. As soon as we are able to release the driver, I will post another update.

So after all the promises of an open source driver being released, it's not being delivered. Is there any ETA on when the promises made will actually be met? Will there be a refund program available for these routers?
This may sound harsh, but understand that some of us do not want to run binary code from a company that has released routers with backdoors.
nyt,
I really do understand your concerns, and there are people advocating for your side. I really hope that we can meet the expectations of our users. Initially the release contained a binary kernel module that could not be rebuilt. The current package can be rebuilt as kernel updates are made. We are moving in the right direction, and I anticipate we will continue to do so in the future.
In the interim, if there is some functionality within the router which is needed for some specific project, or if you discover the wireless acting nefarious please reach out to us at Belkin.
As always, I thank you for your interest, support, and patience. Without persistent, enthusiastic OpenWrt developers like your self, projects like the WRT1900AC would never be undertaken in the first place. Despite your opinion of our effort, from one developer to another, I appreciate you helping us push this forward.

Any chance we can get an actually functional driver in the near future?

Post #742

Chadster766

29 Aug 2014, 03:22

https://github.com/Chadster766/McWRT

Try the image in the Initial Release to compare wifi driver compilation.

(Last edited by Chadster766 on 29 Aug 2014, 03:23)

Post #743

nyt

29 Aug 2014, 03:25

The old driver in mrvl_wlan_v7drv package still has the same locking up issues.... but I guess that's better than router reset issues... I can just avoid 5ghz on that one.

mrvl_wlan_v7drv has 7.2.3.9-W8864 (locks on 5ghz xfers)
marvellac has rel-drv-v8.2.5.6.p3-fw-v7.2.5.6/ (crashes router with bad frees during xfer)

I'll try building the other one linked I guess...

(Last edited by nyt on 29 Aug 2014, 03:30)

Post #744

Chadster766

29 Aug 2014, 03:29

nyt wrote:

The old driver in mrvl_wlan_v7drv package still has the same locking up issues.... but I guess that's better than router reset issues... I can just avoid 5ghz on that one.

I compiled the driver quite a bit differently so don't assume they behave the same please. Do testing to discover the differences.

I discovered that WPA doesn't work but WPA2 does.

Look at gufus recent testing reports. He's running this image as well and mentions no issues with 5ghz and WPA2 so far.

It would be great if you tried the image first but if you don't that's fine too. If you have issue compiling let me know. I'm new to GitHub and may have missing something in the initial commit.

(Last edited by Chadster766 on 29 Aug 2014, 03:33)

Post #745

nyt

29 Aug 2014, 03:31

Chadster766 wrote:

nyt wrote:
The old driver in mrvl_wlan_v7drv package still has the same locking up issues.... but I guess that's better than router reset issues... I can just avoid 5ghz on that one.
I compiled the driver quite a bit differently so don't assume they behave the same please. Do testing to discover the differences.
I discovered that WPA doesn't work but WPA2 does.
Look at gufus recent testing reports. He's running this image as well and mentions no issues with 5ghz and WPA2 so far.

That wasn't in reply to you, that was an update from what I've tested so far. I've also since updated the post.

mrvl_wlan_v7drv has 7.2.3.9-W8864 (locks on 5ghz xfers)
marvellac has rel-drv-v8.2.5.6.p3-fw-v7.2.5.6/ (crashes router with bad frees during xfer)

I'll test the other posted driver shortly or tomorrow.

(Last edited by nyt on 29 Aug 2014, 03:31)

Post #746

Chadster766

29 Aug 2014, 03:35

nyt wrote:

Chadster766 wrote:
nyt wrote:
The old driver in mrvl_wlan_v7drv package still has the same locking up issues.... but I guess that's better than router reset issues... I can just avoid 5ghz on that one.
I compiled the driver quite a bit differently so don't assume they behave the same please. Do testing to discover the differences.
I discovered that WPA doesn't work but WPA2 does.
Look at gufus recent testing reports. He's running this image as well and mentions no issues with 5ghz and WPA2 so far.
That wasn't in reply to you, that was an update from what I've tested so far. I've also since updated the post.
mrvl_wlan_v7drv has 7.2.3.9-W8864 (locks on 5ghz xfers)
marvellac has rel-drv-v8.2.5.6.p3-fw-v7.2.5.6/ (crashes router with bad frees during xfer)
I'll test the other posted driver shortly or tomorrow.

That would be nice. Also I revised my previous post a little bit.

Post #747

nyt

29 Aug 2014, 03:46

Chadster766 wrote:

nyt wrote:
Chadster766 wrote:
I compiled the driver quite a bit differently so don't assume they behave the same please. Do testing to discover the differences.
I discovered that WPA doesn't work but WPA2 does.
Look at gufus recent testing reports. He's running this image as well and mentions no issues with 5ghz and WPA2 so far.
That wasn't in reply to you, that was an update from what I've tested so far. I've also since updated the post.
mrvl_wlan_v7drv has 7.2.3.9-W8864 (locks on 5ghz xfers)
marvellac has rel-drv-v8.2.5.6.p3-fw-v7.2.5.6/ (crashes router with bad frees during xfer)
I'll test the other posted driver shortly or tomorrow.
That would be nice. Also I revised my previous post a little bit.

Building now. Will see how it does in the BB tree. I'm preferring it over the AA tree atm.

Post #748

nyt

29 Aug 2014, 03:53

ok, built 7.2.5.4-W8864... going to flash and report back.

Post #749

nyt

29 Aug 2014, 03:59

Lots of unknown symbol scroll. Guess I'll have to try against AA

[   79.022441] ap8x: Unknown symbol MICCounterMeasureInvoke_Sta (err 0)
[   79.028886] ap8x: Unknown symbol wetHashDeInit (err 0)
[   79.034121] ap8x: Unknown symbol smeCopyBssProfile (err 0)
[   79.039684] ap8x: Unknown symbol smeParseIeType (err 0)
[   79.044973] ap8x: Unknown symbol linkMgtStart (err 0)
[   79.050097] ap8x: Unknown symbol mlmeApiSetRfChannel (err 0)
[   79.055815] ap8x: Unknown symbol sme_DisableKeyMgmtTimer (err 0)
[   79.061896] ap8x: Unknown symbol linkMgtStop (err 0)
[   79.066920] ap8x: Unknown symbol linkMgtParseWpsInfo (err 0)
[   79.072654] ap8x: Unknown symbol linkMgtParseWpaIe (err 0)
[   79.078203] ap8x: Unknown symbol tmpClientSSID (err 0)
[   79.083409] ap8x: Unknown symbol mib_MrvlRSN_GrpKeyUr1 (err 0)
[   79.089301] ap8x: Unknown symbol smeSendScanRequest (err 0)
[   79.094950] ap8x: Unknown symbol defaultKeyMgmtInit (err 0)
[   79.100595] ap8x: Unknown symbol smeStopBss (err 0)
[   79.105541] ap8x: Unknown symbol smeGetScanResults (err 0)
[   79.111102] ap8x: Unknown symbol GetParentStaBSSID (err 0)
[   79.116647] ap8x: Unknown symbol vmacGetVMacEntryByAddr (err 0)
[   79.122637] ap8x: Unknown symbol sme_GetParentVMacEntry (err 0)
[   79.128620] ap8x: Unknown symbol ewbWlanRecv (err 0)
[   79.133657] ap8x: Unknown symbol linkMgtReStart (err 0)
[   79.138961] ap8x: Unknown symbol wetHashInit (err 0)
[   79.144006] ap8x: Unknown symbol sme_GetStaSecurityMibsPtr (err 0)
[   79.150256] ap8x: Unknown symbol linkMgtParseScanResult (err 0)
[   79.156238] ap8x: Unknown symbol sme_GetKeyMgmtInfoStaPtr (err 0)
[   79.162408] ap8x: Unknown symbol syncSrv_ParseAttribWithinFrame (err 0)
[   79.169105] ap8x: Unknown symbol sme_SetClientPeerInfo (err 0)
[   79.175019] ap8x: Unknown symbol smeInitParentSession (err 0)
[   79.180839] ap8x: Unknown symbol smeGetStaLinkInfo (err 0)
[   79.186387] ap8x: Unknown symbol mlmeApiGetStaLinkInfo (err 0)
[   79.192291] ap8x: Unknown symbol linkMgtParseWpsIe (err 0)
[   79.197834] ap8x: Unknown symbol vmacGetVMacStaInfo (err 0)
[   79.203495] ap8x: Unknown symbol sme_GetStaSystemMibsPtr (err 0)
[   79.209573] ap8x: Unknown symbol parentGetVMacId (err 0)
[   79.214950] ap8x: Unknown symbol hashTable (err 0)
[   79.219813] ap8x: Unknown symbol SendDelBASta (err 0)
[   79.224936] ap8x: Unknown symbol smeSetBssProfile (err 0)
[   79.230412] ap8x: Unknown symbol sme_GetClientPeerInfo (err 0)
[   79.236303] ap8x: Unknown symbol linkMgtParseHTGenIe (err 0)
[   79.242032] ap8x: Unknown symbol ewbLanRecv (err 0)
[   79.246970] ap8x: Unknown symbol SendAddBAReqSta (err 0)
[   79.252359] ap8x: Unknown symbol ProcessEAPoLSta (err 0)
kmod: 1 module could not be probed

Post #750

Chadster766

29 Aug 2014, 04:03

nyt wrote:

ok, built 7.2.5.4-W8864... going to flash and report back.

Be sure to read my README.md on how to get the wireless driver to start on boot.

I've tried the same thing with the new BB version and I discovered the below (from one of my previous posts):

I discovered in this BB version the open source wifi driver doesn't work but it does compile. More config work and investigation will be needed to get the open source wifi driver to fire up on this version. Also the existing binary ap8x.ko is located in two packages marvellac and mrvl_wlan_v7drv. So just choosing to not build marvellac is not enough to keep the binary driver from being used.

(Last edited by Chadster766 on 29 Aug 2014, 04:03)

Sorry, posts 751 to 750 are missing from our archive.

Page 30 of 598