I'm a little surprised on the pushback for enabling all channels in the driver. I thought iw would not let you pick channels if the regdomain requires DFS and the driver/chip doesn't support it. Surely there's somewhere where some of those channels are allowed and DFS isn't required.
Now that you got the patch accepted upstream, are you going to see if LEDE will pull in the patch again?
First, thank you so much for the investigation and fix. Speaking as a very inexperienced user, what kernel did this change roll into, and when will OpenWRT's snapshot builds finally start using it?
Seconded--obviously nobody is obligated to provide a custom build, but speaking as someone who spent over 15 hours unsuccessfully self-compiling this driver change, it would be much appreciated!
It doesn't look like the OpenWRT/LEDE project will be adopting the latest Linux kernel with this driver fix (4.15?) anytime soon...
heck even those channels would be good for me because on stock firm 161 worked fine with my device , its the 36-48 that my device does not see at all . thats why i was asking if the previous custom build was still available for a re-upload if possible . 5ghz bridge setup since i have 3 of these routers and a main on 3 floor bringing down over 5ghz instead of 2.4ghz sadly device is region locked so the only 5ghz channel that used to work with it was 161 -157-153 and i think even 149 as well .
Rebuild with 25 channels. It depends on your region to show the channels. Because DFS is not supported in driver so any DFS channels will not be shown.
This one the rebuild version based on latest 17.01.
Update! extra 5ghz channels are working again , I got my device connected as normal on the 161 , but just now noticed that even when dbm is set to 30 it caps out to 18 , not sure if its the hardware's limit or that the settings are not being applied but overall great great work @ximibaba. Thank You so much . Also is there a tutorial we can follow for grabing the source-code and compiling then kernel/img ?
@ximibaba That was very nice of you. Thank you, especially if you ended up setting up a build environment to recompile. Of course, big thanks to your work investigating the issue last year!
@ximibaba when i get my network issues all sorted out i wanted to take a dive into this , i usually do kernel work on android so i will be a noob at this but my goal is to find out if for this router i could increase the rx and tx power and some cpu overclocking as well . I used to run ddwrt on a old e1200 v2 and it had cpu oc and tx power but not rx , since i use these routers as bridges tx and rx power increase def are a nice upgrade without upgrading the hardware.
well i did something stupid in the hopes that in the new updates that maybe the channels are back like it was on stock . So i updated to 18.06.0 now im back to 4 5ghz channels that my devices cannot use. I really dont want to ask you to keep this project up to date so im wondering if you can coach me on how to setup my linux laptop to compile the update with your 5ghz patch to unlock all the 5ghz frequencies yet keeping it on 18.06.0 specially for like the security patches. Or if you have a github regarding this device.
And the worst part is that now it wont accept your build , 18.06.0 does not accept .tar upgrade files or i guess its because its a lower version compared to 18.06.0