Not upgrading package base-files which is marked hold (flags=0x202).

@starcms I did exactly as you said in your message, and it is upgrading the base-files

Upgrading luci-base on root from git-17.115.45618-4669782-1 to git-17.116.42736-415b99d-1...
Downloading https://downloads.lede-project.org/snapshots/packages/arm_cortex-a9_vfpv3/luci/luci-base_git-17.116.42736-415b99d-1_arm_cortex-a9_vfpv3.ipk

Not sure why... I'm now afraid of rebooting the router

Look closely.  It was upgrading luci-base, not base-files

luci-base is fine.  Just not base-files.  Two entirely different packages.  You're fine!

(Last edited by starcms on 27 Apr 2017, 05:59)

@david, any idea why your updated kmod-mwlwifi causes my WRT1200AC running your Kernel 4.9 build to go into a bootloop?  Luckily I was able to recover it from failsafe mode and install the original kmod-mwlwifi file from your repo.

The kmod-mwlwifi.ipk are meant to be compatible with the entire WRT series.  The only thing that should matter is the kernel version they are compiled for.  @garfo77 reported that your updated version did work on his 3200ACM, but puts my 1200AC into a bootloop.  For the life of me, I can't figure out why that would be.

(Last edited by starcms on 27 Apr 2017, 05:58)

This is definitely now overwriting the current driver (mwlwifi.ko).  The question is why is it only compatible with the WRT3200ACM and not the rest of the WRT series?  If all you did was take the 0421 mwlwifi driver and add the latest commits, it should still work on the entire WRT series, not only the 3200ACM.

(Last edited by starcms on 27 Apr 2017, 06:08)

Ufff... thanks for making  me note that

I've rebooted and it worked ok , now I'm up-to-date on every package

Wonder what @davidc502 thinks about this approach?

EDIT

I figured it out.  i read a few pages back and saw i had to change the feeds. 

i flashed the 4.9 image for my wrt3200.  Im having problems downloading some packages i need such as umbim.  I added the /snapshot/ in the feeds and opkg updates just fine but many of the packages i try and get have errors.

Collected errors:
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for umbim:
 *     kernel (= 4.4.61-1-1acd2062c57cefc8c9eca86ec7a3e6fa) *     kernel (= 4.4.61-1-1acd2062c57cefc8c9eca86ec7a3e6fa) *     kernel (= 4.4.61-1-1acd2062c57cefc8c9eca86ec7a3e6fa) *     kernel (= 4.4.61-1-1acd2062c57cefc8c9eca86ec7a3e6fa) *     kernel (= 4.4.61-1-1acd2062c57cefc8c9eca86ec7a3e6fa) * 
 * opkg_install_cmd: Cannot install package umbim.

Starcms i even did your method and still get errors

failed to find dependency cdc_ncm
failed to find dependency cdc-wdm
1 module could not be probed
- cdc_mbim
Collected errors:
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for uqmi:
 *      kernel (= 4.9.20-1-f10f492cd346863edf0090a3c8391b46) *  kernel (= 4.9.20-1-f10f492cd346863edf0090a3c8391b46) *  kernel (= 4.9.20-1-f10f492cd346863edf0090a3c8391b46) *  kernel (= 4.9.20-1-f10f492cd346863edf0090a3c8391b46) *
 * opkg_install_cmd: Cannot install package uqmi.
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for umbim:
 *      kernel (= 4.9.20-1-f10f492cd346863edf0090a3c8391b46) *  kernel (= 4.9.20-1-f10f492cd346863edf0090a3c8391b46) *
 * opkg_install_cmd: Cannot install package umbim.
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for kmod-usb-net-sierrawireless:
 *      kernel (= 4.9.20-1-f10f492cd346863edf0090a3c8391b46) *
 * opkg_install_cmd: Cannot install package kmod-usb-net-sierrawireless.
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for kmod-usb-serial-wwan:
 *      kernel (= 4.9.20-1-f10f492cd346863edf0090a3c8391b46) *  kernel (= 4.9.20-1-f10f492cd346863edf0090a3c8391b46) *
 * opkg_install_cmd: Cannot install package kmod-usb-serial-wwan.
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for kmod-usb-serial-sierrawireless:
 *      kernel (= 4.9.20-1-f10f492cd346863edf0090a3c8391b46) *
 * opkg_install_cmd: Cannot install package kmod-usb-serial-sierrawireless.
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for kmod-usb-serial-qualcomm:
 *      kernel (= 4.9.20-1-f10f492cd346863edf0090a3c8391b46) *
 * opkg_install_cmd: Cannot install package kmod-usb-serial-qualcomm.
root@LEDE:~#

(Last edited by westrem on 27 Apr 2017, 07:01)

David, I am not using OpenVPN, I am using "openconnect" (installed with opkg).
There is no any configuration for openconnect. It's simple command line string to connect. I have use the one wich is working fine on my ubuntu machine and main router with "padavan" firmware (openconnect also installed as opkg package).

Since you are not using openconnect (and I suppose noone else use it) - i am able to reproduce same error with gmail and gnutls_cli.
Simply run

gnutls-cli -p 443  gmail.com

and you'll see the error:

*** Fatal error: A TLS fatal alert has been received.
*** Received alert [20]: Bad record MAC
*** handshake has failed: A TLS fatal alert has been received.

Same happen with openconnect on your build.
Same commands (either openconnect or gnutls_cli) run OK on ubuntu.

I've installed new driver on my WRT3200 and got a bootloop.
After power off and power on it appears boot partition was changed and booted to previous firmware
Lede Testing SNAPSHOT r3963-7ae58be

EDIT:
Yes, I have David's LEDE on both MTD's... since I've done sysupgrade last time when David build new one with "wlan driver fixed".

(Last edited by AddRemover on 27 Apr 2017, 16:18)

Unknown reason, but do understand that the wifi driver being worked on is for the 3200acm, and though it "should" be okay for other models, it's far from completed, and there could be complications yet to be worked out for other models.

Currently anyone who is updating the driver for hardware other than the 3200acm is inviting trouble. Heck, updating the 3200acm is trouble enough   lol

Anyhow, you'll probably have to go to the other partition if you haven't done so already.

After the reported issues some are having I'm wondering if it isn't better going the "mwlwifi.ko" route??? 

There are a few new commits with the driver today, so I'll make a pass with it this evening and post the mwlwifi.ko. Will test it out first and report if it causes issues.  I believe the current kernel version would be 4.9.20

I can confirm external disk access issues were resolved by upgrading to kernel 4.9. Thanks for the heads up.

Saw a post with someone sharing an updated 3200acm build on cybers thread. "Hi all I thought I would share my personal build that is nearly the same as Cybrnook's enjoy guys and girls!

Kernel 4.9.24 and with all latest commits (mwlwifi) from today/on Apr 27, 2017" Just a heads up, thanks for the builds ;] I'm one happy wrt1200ac v2 owner.

Kernel 4.9 testing continues here ... after days of flawless routing and wi-fi performance on my 1900 ACS v2, today I've lost wifi connectivity suddenly on all wifi stations. Luckily enough, I've followed David's advise and I have been saving the logs to USB, so here's what I can see happened just before the blackout:

Thu Apr 27 18:34:26 2017 daemon.notice hostapd: wlan1: AP-STA-DISCONNECTED 38:c9:86:93:99:6b
Thu Apr 27 18:34:26 2017 daemon.notice hostapd: wlan1: AP-STA-DISCONNECTED f0:24:75:4f:d4:16
Thu Apr 27 18:34:26 2017 daemon.notice hostapd: wlan1: AP-STA-DISCONNECTED 74:8d:08:9f:95:4e
Thu Apr 27 18:34:26 2017 daemon.notice hostapd: wlan1: AP-STA-DISCONNECTED a0:99:9b:2d:57:91
Thu Apr 27 18:34:26 2017 daemon.notice hostapd: wlan1: AP-STA-DISCONNECTED cc:25:ef:b8:a1:85
Thu Apr 27 18:34:26 2017 daemon.notice hostapd: wlan1: AP-STA-DISCONNECTED 48:a1:95:05:99:c7
Thu Apr 27 18:34:26 2017 daemon.notice hostapd: wlan1: AP-STA-DISCONNECTED 88:51:fb:21:5f:62

Thu Apr 27 18:35:56 2017 daemon.notice hostapd: Station 48:a1:95:05:99:c7 trying to disassociate, but it is not associated

I've SSH'd from the Internet, did a "wifi" to bring it down and up again... nothing , still not being able to connect to the wifi network ( even tough I could see the network was being advertised! ) . Did a /etc/init.d/network restart ... nothing, same thing.

Rebooted the router, and now it's working ok.

NOTE: I'm using David's latest 4.9 test build, and put all of the "newer" LEDE packages on top of it.

(Last edited by mariano.silva on 27 Apr 2017, 22:52)

A little earlier I built the latest driver, and tried both .ipk and .ko methods, and both ended in reboot loops. Essentially the router would go down when wifi attempted to come up.

With that in mind, a new complete build is being worked on and will be uploaded to the site when completed. Kernel 4.9.x will be the main build, and suspect V1 owners will have problems with it. The plan is to build a 4.4.x with a link to it for v1 owners.

(Last edited by davidc502 on 28 Apr 2017, 00:15)

Thanks for all the hard work, @david!  My guess would be when you built the driver separately, you were missing some config files (or something) that is normally present when you build the entire image, hence causing the bootloops.  Only a guess though

And I was able to fix my bootloop problem by using failsafe mode and (re)installing the kmod-mwlwifi.ipk from your repo.  All good, didn't lose a thing.

For those that were bootlooping, if you let it bootloop 5 times in a row, it would automatically switch to the firmware on the other partition and boot up.

(Last edited by starcms on 28 Apr 2017, 02:06)

@david,

Btw, just for clarity, on your releases webpage, https://davidc502sis.dynamic-dns.net/releases/, for Caimen 1200AC, you should put Version 1 or 2, just like for Shleby 1900ACS.  Also, I would include the 1200AC at the top of the page for devices recommended to install Kernel 4.9 on.  Works perfectly!

For those that don't know, the only difference between versions 1 and 2 of caimen and shelby is that version 2 has the power table parameters stored in eeprom and cannot be altered.  They flat-out ignore the parameters in the build which is installed.  This was done to make the FCC happy, so that people can't be modifying their routers for example to enable channels 12 and 13, or increase the transmit power, or to disable DFS (radar detection).

So basically if you have a 1200AC V2, 1900ACS V2, or 3200ACM, you cannot "hack" the power tables.  No way around it.

Edit: So in my opinion, the 1900AC V2 or 1900ACS V1 are the best models.

(Last edited by starcms on 28 Apr 2017, 08:41)

that what was happened with my 3200.
Will wait new image from David to update again

Yes, 3200 on kernel 4.9. WiFi speed of 5Ghz degrades over time, sometimes it shuts down the 5GHz network completely and has to be rebooted, especially after downloading some large files in a row. I don't see anything in kernel/system logs though... There is almost no interference in the neighborhood right now.

2.4GHz is totally stable. Same goes for the 1900ACS v1 with kernel 4.9 in general.

By the way, did not add platform to path but all of my devices can connect just fine.

(Last edited by floydburgermcdahm on 28 Apr 2017, 09:41)

Any idea if anyone is looking into what the issue is with 4.9.x kernels on v1? Are we just going to be stranded with the 4.4.x kernels forever?

I do know that there's a case open on the issue. 

Actually, there's a more important issue at hand than the kernel bump.. A security issue out on kernel's 4.5 and lower where attackers can execute arbitrary code. So, if for nothing else the issue needs to be fixed ASAP.

Last night the first build failed, I made an adjustment and kicked it off again, and when I woke up this morning it had completed. This afternoon when I get back from work, I'll post the new images to the site.

(Last edited by davidc502 on 28 Apr 2017, 13:41)

New images based on 4.9.x with the latest wifi commits are available to download and install.

I have not had a chance to test yet, and won't be able to until late this evening or tomorrow. Feel free to post any issues, but I'll have limited time to respond.

Hopefully around midnight tonight I'll be able to start a alternative 4.4 kernel build for V1 users still having issues with 4.9.x.

Good news is that it booted fine on my WRT1200AC, so it looks like the you solved the bootloop issues concerning the new commits to the mwlwifi driver.  Can't comment on any performance improvements for the 3200ACM.

Great work!

(Last edited by starcms on 29 Apr 2017, 00:36)

Please help, unable to update...

I have r3988 kernel 4.9 on my 3200 now. Running very unstable, was hoping to test the new r4xxx build but can't perform a simple upgrade.

sysupgrade -v -F returns "cannot find target partition"

I tried both .img and .bin files

What gives?

WRT3200ACM - main - up and running very well.
WRT1900ACv2 - ap - up and running very well.