OpenWrt Forum Archive

Topic: davidc502 1900ac 3200acm builds

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.

northbound wrote:
davidc502 wrote:

I need a few testers to determine is wifi is working or not. When I flash, I get some blank dropdowns in the SSID configuration, but is this my situation or is it happening to everyone? This does have the latest commit for the wifi driver.

https://davidc502sis.dynamic-dns.net/sn … /cortexa9/

I have not been on here in quite awhile. But after I saw nbd had pushed commit to trunk

https://git.openwrt.org/?p=openwrt/stag … 6848943e9a

which is a fix or a hack however you want to look at it for the ac1900acv1 I did a fresh build from trunk. I ran into the wifi dropdown issue instead of dinking with it I just deleted the /etc/config/wireless and rebooted and reconfigured.

OpenWrt SNAPSHOT, r6503-5faa955
-----------------------------------------------------
root@LEDE:~# uname -a
Linux LEDE 4.14.27 #0 SMP Mon Mar 19 22:28:49 2018 armv7l GNU/Linux
root@LEDE:~# uptime
19:14:31 up 3 days, 21:55,  load average: 0.00, 0.00, 0.00
root@LEDE:~#

Hopefully this helps someone.

Which reminds me..... If we have some v1 owners they may want to try r6520 out since this does directly affect the reboot issue. wifi aside smile

https://davidc502sis.dynamic-dns.net/sn … /cortexa9/

northbound wrote:
davidc502 wrote:

I need a few testers to determine is wifi is working or not. When I flash, I get some blank dropdowns in the SSID configuration, but is this my situation or is it happening to everyone? This does have the latest commit for the wifi driver.

https://davidc502sis.dynamic-dns.net/sn … /cortexa9/

I have not been on here in quite awhile. But after I saw nbd had pushed commit to trunk

https://git.openwrt.org/?p=openwrt/stag … 6848943e9a

which is a fix or a hack however you want to look at it for the ac1900acv1 I did a fresh build from trunk. I ran into the wifi dropdown issue instead of dinking with it I just deleted the /etc/config/wireless and rebooted and reconfigured.

OpenWrt SNAPSHOT, r6503-5faa955
-----------------------------------------------------
root@LEDE:~# uname -a
Linux LEDE 4.14.27 #0 SMP Mon Mar 19 22:28:49 2018 armv7l GNU/Linux
root@LEDE:~# uptime
19:14:31 up 3 days, 21:55,  load average: 0.00, 0.00, 0.00
root@LEDE:~#

Hopefully this helps someone.


Thanks for that Northbound.  It will at least help me when I take the step(hopefully this weekend)

Sorry @davidc502 I was not trying to hijack your thread.
I just thought it might help someone. :-)

northbound wrote:

Sorry @davidc502 I was not trying to hijack your thread.
I just thought it might help someone. :-)

This is not my thread... It's everyone's!

No thread police here... post what you like.

northbound wrote:
davidc502 wrote:

I need a few testers to determine is wifi is working or not. When I flash, I get some blank dropdowns in the SSID configuration, but is this my situation or is it happening to everyone? This does have the latest commit for the wifi driver.

https://davidc502sis.dynamic-dns.net/sn … /cortexa9/

I have not been on here in quite awhile. But after I saw nbd had pushed commit to trunk

https://git.openwrt.org/?p=openwrt/stag … 6848943e9a

which is a fix or a hack however you want to look at it for the ac1900acv1 I did a fresh build from trunk. I ran into the wifi dropdown issue instead of dinking with it I just deleted the /etc/config/wireless and rebooted and reconfigured.

OpenWrt SNAPSHOT, r6503-5faa955
-----------------------------------------------------
root@LEDE:~# uname -a
Linux LEDE 4.14.27 #0 SMP Mon Mar 19 22:28:49 2018 armv7l GNU/Linux
root@LEDE:~# uptime
19:14:31 up 3 days, 21:55,  load average: 0.00, 0.00, 0.00
root@LEDE:~#

Hopefully this helps someone.

I'll try deleting and rebooting tomorrow and seeing if that will fix the problem.


thanks,

The suggested process Northbound quoted worked for me.

Both wireless radios working after removing config, rebooting, and reconfig after.

root@routi:~# uname -a            
Linux routi 4.14.27 #0 SMP Thu Mar 22 12:29:22 2018 armv7l GNU/Linux

root@routi:~# uptime
 21:09:01 up 28 min,  load average: 0.00, 0.01, 0.00

Thanks again Northbound

Just installed r6302 SHELBY in my 1900ACS

Please, please please, please  FIX TRANSMISSION PACKAGE BUILD (package transmission-daemon-openssl).
Since months it's no available anymore :-( :-( :-(


Regards.

Did a quick test run with my WRT1900AC/v2 with your test build. Could not find the wireless config file in /etc/config to delete. For some reason, this build was not as fast as the one i used over a month ago. Don't have the build number off hand but it was one in late Feb.

This was a fresh install, as all my tests are done that way.

Will cross fingers for another test build to try out on the 28th.

(Last edited by Notsofast on 24 Mar 2018, 11:29)

Build r6520 for the wrt3200acm seems to be missing the mwlwifi firmware
by default.

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.14.27 (davidc502@pc2) (gcc version 7.3.0 (OpenWrt GCC 7.3.0 r6520-02fba1a181)) #0 SMP Thu Mar 22 20:54:20 2018
[    0.000000] CPU: ARMv7 Processor [414fc091] revision 1 (ARMv7), cr=10c5387d

[    9.335110] <<Marvell Mac80211 Wireless PCIE Network Driver version 10.3.4.0-20180305>>
[    9.343181] pci 0000:00:01.0: enabling device (0140 -> 0142)
[    9.348966] ieee80211 phy0: priv->pcmd_buf = ddee8000  priv->pphys_cmd_buf = 1dee8000
[    9.349005] mwlwifi 0000:01:00.0: Direct firmware load for mwlwifi/88W8964.bin failed with error -2
[    9.358099] mwlwifi 0000:01:00.0: Falling back to user helper
[    9.368328] firmware mwlwifi!88W8964.bin: firmware_loading_store: map pages failed
[    9.376057] ieee80211 phy0: cannot find firmware image <mwlwifi/88W8964.bin>
[    9.383152] ieee80211 phy0: firmware init fail
[    9.387615] ieee80211 phy0: fail to initialize firmware
[    9.392902] mwlwifi: probe of 0000:01:00.0 failed with error -5
[    9.398910] pci 0000:00:02.0: enabling device (0140 -> 0142)
[    9.404678] ieee80211 phy1: priv->pcmd_buf = dde94000  priv->pphys_cmd_buf = 1de94000
[    9.404699] mwlwifi 0000:02:00.0: Direct firmware load for mwlwifi/88W8964.bin failed with error -2
[    9.413794] mwlwifi 0000:02:00.0: Falling back to user helper
[    9.423051] firmware mwlwifi!88W8964.bin: firmware_loading_store: map pages failed
[    9.430725] ieee80211 phy1: cannot find firmware image <mwlwifi/88W8964.bin>
[    9.437806] ieee80211 phy1: firmware init fail
[    9.442283] ieee80211 phy1: fail to initialize firmware
[    9.447564] mwlwifi: probe of 0000:02:00.0 failed with error -5

I did a manual install of mwlwifi-firmware-88w8864, mwlwifi-firmware-88w8897, and mwlwifi-firmware-88w8964.  After a reboot the wifi drivers loaded and wifi became available for configuration and use.

Enginerd wrote:

Build r6520 for the wrt3200acm seems to be missing the mwlwifi firmware
by default.

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.14.27 (davidc502@pc2) (gcc version 7.3.0 (OpenWrt GCC 7.3.0 r6520-02fba1a181)) #0 SMP Thu Mar 22 20:54:20 2018
[    0.000000] CPU: ARMv7 Processor [414fc091] revision 1 (ARMv7), cr=10c5387d

[    9.335110] <<Marvell Mac80211 Wireless PCIE Network Driver version 10.3.4.0-20180305>>
[    9.343181] pci 0000:00:01.0: enabling device (0140 -> 0142)
[    9.348966] ieee80211 phy0: priv->pcmd_buf = ddee8000  priv->pphys_cmd_buf = 1dee8000
[    9.349005] mwlwifi 0000:01:00.0: Direct firmware load for mwlwifi/88W8964.bin failed with error -2
[    9.358099] mwlwifi 0000:01:00.0: Falling back to user helper
[    9.368328] firmware mwlwifi!88W8964.bin: firmware_loading_store: map pages failed
[    9.376057] ieee80211 phy0: cannot find firmware image <mwlwifi/88W8964.bin>
[    9.383152] ieee80211 phy0: firmware init fail
[    9.387615] ieee80211 phy0: fail to initialize firmware
[    9.392902] mwlwifi: probe of 0000:01:00.0 failed with error -5
[    9.398910] pci 0000:00:02.0: enabling device (0140 -> 0142)
[    9.404678] ieee80211 phy1: priv->pcmd_buf = dde94000  priv->pphys_cmd_buf = 1de94000
[    9.404699] mwlwifi 0000:02:00.0: Direct firmware load for mwlwifi/88W8964.bin failed with error -2
[    9.413794] mwlwifi 0000:02:00.0: Falling back to user helper
[    9.423051] firmware mwlwifi!88W8964.bin: firmware_loading_store: map pages failed
[    9.430725] ieee80211 phy1: cannot find firmware image <mwlwifi/88W8964.bin>
[    9.437806] ieee80211 phy1: firmware init fail
[    9.442283] ieee80211 phy1: fail to initialize firmware
[    9.447564] mwlwifi: probe of 0000:02:00.0 failed with error -5

I did a manual install of mwlwifi-firmware-88w8864, mwlwifi-firmware-88w8897, and mwlwifi-firmware-88w8964.  After a reboot the wifi drivers loaded and wifi became available for configuration and use.

Ah, i guess i will try that  tomorrow 1st thing, as it seems that is probably why I have no config file.

May try a clean install of the WRT1900ACS version to verify for myself, that i can use Davids Cobra builds, as i am using stock UK  Linksys Cobra build on my 1900AC/V2.

Thanks for everyone's input - Great Help!

What I found was the mwlwifi directory was missing. The mwlwifi directory is what holds all of the firmware. I re-created the mwlwifi directory, as others suggested, and dropped in the firmware, and rebooted.  Wifi is working like it should.

It looks like this issue is affecting all models through the line.

For others who want to try this latest build. After flashing, create the mwlwifi direction in /lib/firmware/   
After re-creating the directory, drop the firmware into that directory. You can use wget command or download to your pc and scp, or use a gui tool. The firmware is found here -- https://github.com/kaloz/mwlwifi/tree/m … n/firmware    If you don't know which one to download, just download all three as the router will figure out which one to use.

Link to the latest build -- https://davidc502sis.dynamic-dns.net/sn … /cortexa9/

Hi David, r6520 has any major difference from r6365?

Keltere wrote:

Hi David, r6520 has any major difference from r6365?

Kernel bumps, Latest wifi drivers, and various other package updates.  "Major" probably not.

Anyone knows how to do a "release and renew" on LEDE properly?

i cant find a way on how to do it.

Relaxation wrote:

Anyone knows how to do a "release and renew" on LEDE properly?

i cant find a way on how to do it.

Did you try

ifdown eth1
ifup eth1

I think you can string them together with "&&" if needed.

Also, I read a post to do the following.

Release: killall -SIGUSR2 udhcpc
Renew: killall -SIGUSR1 udhcpc

(Last edited by davidc502 on 24 Mar 2018, 14:22)

Just as a note of reference for the current firmware not copying over from the source package.

The Makefile for mwlwifi has been changed fairly drastically dealing with copying over the firmware. I think I can fix it though.

the killall works but i want to know how to do the other method.

what should i do with the "ifdown eth1" and "ifup eth1"? how do i string it with &&?

davidc502 wrote:
Relaxation wrote:

Anyone knows how to do a "release and renew" on LEDE properly?

i cant find a way on how to do it.

Did you try

ifdown eth1
ifup eth1

I think you can string them together with "&&" if needed.

Also, I read a post to do the following.

Release: killall -SIGUSR2 udhcpc
Renew: killall -SIGUSR1 udhcpc

Relaxation wrote:

the killall works but i want to know how to do the other method.

what should i do with the "ifdown eth1" and "ifup eth1"? how do i string it with &&?

davidc502 wrote:
Relaxation wrote:

Anyone knows how to do a "release and renew" on LEDE properly?

i cant find a way on how to do it.

Did you try

ifdown eth1
ifup eth1

I think you can string them together with "&&" if needed.

Also, I read a post to do the following.

Release: killall -SIGUSR2 udhcpc
Renew: killall -SIGUSR1 udhcpc

ifdown eth1 && ifup eth1   

If you want to give it a little more time

ifdown eth1; sleep 15; ifup eth1

davidc502 wrote:

Just as a note of reference for the current firmware not copying over from the source package.

The Makefile for mwlwifi has been changed fairly drastically dealing with copying over the firmware. I think I can fix it though.

I have emailed hauke@hauke-m.de  and _@jsl.io

https://github.com/lede-project/source/ … 098fd92153

Has there been a change since my r4901 install. I have these contents in file kmod-mwlwifi:

opkg files kmod-mwlwifi

Package kmod-mwlwifi (4.9.51+10.3.4.0-20170810-1) is installed on root and has the following files:
/lib/firmware/mwlwifi/88W8864.bin
/etc/modules.d/50-mwlwifi
/lib/firmware/mwlwifi/88W8964.bin
/lib/modules/4.9.51/mwlwifi.ko
/lib/firmware/mwlwifi/Marvell_license.txt
/lib/firmware/mwlwifi/88W8897.bin

When I look in the newest version I find only the kernel module without the firmware:

kmod-mwlwifi - 4.14.27+10.3.4.0-20180305-1

beginner67890 wrote:

Has there been a change since my r4901 install. I have these contents in file kmod-mwlwifi:

opkg files kmod-mwlwifi

Package kmod-mwlwifi (4.9.51+10.3.4.0-20170810-1) is installed on root and has the following files:
/lib/firmware/mwlwifi/88W8864.bin
/etc/modules.d/50-mwlwifi
/lib/firmware/mwlwifi/88W8964.bin
/lib/modules/4.9.51/mwlwifi.ko
/lib/firmware/mwlwifi/Marvell_license.txt
/lib/firmware/mwlwifi/88W8897.bin

When I look in the newest version I find only the kernel module without the firmware:

kmod-mwlwifi - 4.14.27+10.3.4.0-20180305-1

The firmware has been moved to individual packages:

    - mwlwifi-firmware-88w8864
    - mwlwifi-firmware-88w8897
    - mwlwifi-firmware-88w8964

The right firmware package has been added as a dependency to the kmod-mwlwifi package.

adri wrote:

The firmware has been moved to individual packages:

    - mwlwifi-firmware-88w8864
    - mwlwifi-firmware-88w8897
    - mwlwifi-firmware-88w8964

The right firmware package has been added as a dependency to the kmod-mwlwifi package.

Thanks adri-

So maybe the next build after this (control file):

Package: kmod-mwlwifi
Version: 4.14.27+10.3.4.0-20180305-1
Depends: kernel (=4.14.27-1-6fb667f67f11a492db7b1d3673a80ba3), kmod-mac80211
Source: package/kernel/mwlwifi
License: ISC
Section: kernel
Maintainer: Imre Kaloz <kaloz@openwrt.org>
Architecture: arm_cortex-a9_vfpv3
Installed-Size: 74230
Description:  Marvell 88W8864/88W8897/88W8964 wireless driver
joeykork wrote:

I'm another happy customer on r6365. Sysupgraded my r4??? WRT1200AC

Can't wait for kernel 4.14!

I have one more kernel config request for next build:
+NET_VRF=y

config NET_VRF
    tristate "Virtual Routing and Forwarding (Lite)"
    depends on IP_MULTIPLE_TABLES
    depends on NET_L3_MASTER_DEV
    depends on IPV6 || IPV6=n
    depends on IPV6_MULTIPLE_TABLES || IPV6=n
    ---help---
      This option enables the support for mapping interfaces into VRF's. The
      support enables VRF devices.

VRF is a very trick feature and allows split-tunnel routing by destination for VPNs
in a simpler fashion than "Linux Policy Routing" (ipset => iptables -j MARK => ip rule)

see: https://www.netdevconf.org/1.1/proceedi … torial.pdf

I second this request smile

I have no wifi luci config after install r6520 on 1900ACS v2. What can i do to active wifi?. there is no wireless config file in /etc/config also. Thanks

(Last edited by oldchip on 24 Mar 2018, 20:35)

antonsamoziv wrote:
joeykork wrote:

I'm another happy customer on r6365. Sysupgraded my r4??? WRT1200AC

Can't wait for kernel 4.14!

I have one more kernel config request for next build:
+NET_VRF=y

config NET_VRF
    tristate "Virtual Routing and Forwarding (Lite)"
    depends on IP_MULTIPLE_TABLES
    depends on NET_L3_MASTER_DEV
    depends on IPV6 || IPV6=n
    depends on IPV6_MULTIPLE_TABLES || IPV6=n
    ---help---
      This option enables the support for mapping interfaces into VRF's. The
      support enables VRF devices.

VRF is a very trick feature and allows split-tunnel routing by destination for VPNs
in a simpler fashion than "Linux Policy Routing" (ipset => iptables -j MARK => ip rule)

see: https://www.netdevconf.org/1.1/proceedi … torial.pdf

I second this request smile

Go back to 5084 and read down, as all the info to get it operational is covered. Either download and install each wifi package or create a new folder and populate it with the proper drivers in the link given by David.