Your reports for Marvell units are greatly appreciated !
Router:
Firmware:
Kernel:
Status:
Reset:
Errors:
This build thread is for reporting successes and problem with loading this experimental test build. This is important info for developers and users. Always state your hardware and SPECIFIC build. Do not ask questions about your specific router or how to configure it in this thread; create your own thread to discuss any specific problems you have or need resolved. Please also do not respond to such questions. This thread is to report info, not to seek it. Posts that do not add to understanding this build will be deleted. Make sure you know how to flash properly and the risk before using this build. It is important to adhere to these requirements, to keep this thread from becoming impossibly long and useless. If you don't know what build to flash and how to flash properly and have a means of recovery if things should go wrong, do NOT flash this experimental test build. _________________ THERE ARE NO STRANGERS HERE; ONLY FRIENDS YOU HAVEN'T YET MET.
________________________________________________________________________________________________________
DD-WRT CHANGELOG | DEVICES | DD-WRT BUILDS | KONG BUILDS | UNOFFICIAL BUILDS | DD-WRT in VIRTUALBOX
Joined: 13 Jun 2006 Posts: 1608 Location: SE Michigan USA
Posted: Fri Oct 07, 2016 19:40 Post subject:
This build will install through the Linksys UI on my wrt1900ac v1. Last 3 builds would report a file too big error. Looks like Brainslayer has found the magic to make it work.
Also has an updated wireless driver.
# strings /lib/ath9k/mwlwifi.ko | grep 10.3
10.3.1.0-20160917
10.3.1.0-20160917
Wireless performance on 5GHz does not seem to be quite as good as previous build that did work on my wrt1900ac in my limited iperf test. I do not think everyone experiences this problem, but when I start out with the wireless 5GHz set to channel 149 the 5GHz light does not go on and the SSID is not being broadcast. If I set the channel to a lower number like 36, save and apply, then set channel to 149 everything works. Not sure why, but have seen this before with Brainslayer builds.
Router: wrt1900ac v1
Firmware: 30731
Kernel: 3.18.42
Status: up and running
Reset: yes
Errors: no
2 BS DD-WRTs here, both operational, but both have the same issue: incredible CPU temperature fluctuation, between 0 and a few hundred million degreesC. Which seems unrealistic
I noticed that 30709 did it as well, so last working temperature showings are from 30681.
Router: wrt1200ac
Firmware: 30731
Kernel: 3.18.42
Status: up and running
Reset: yes
Errors: no
Anomaly: (incorrect CPU temperature, reporting either 0C or a few hundred million degreesC )
Router: wrt1900acs v1
Firmware: 30731
Kernel: 3.18.42
Status: up and running
Reset: yes
Errors: no
Anomaly: (incorrect CPU temperature, reporting either 0C or a few hundred million degreesC )
Joined: 17 Feb 2010 Posts: 611 Location: Yorkshire (GOC)
Posted: Fri Oct 07, 2016 20:55 Post subject:
SpreadFoxtrot wrote:
2 BS DD-WRTs here, both operational, but both have the same issue: incredible CPU temperature fluctuation, between 0 and a few hundred million degreesC. Which seems unrealistic
I noticed that 30709 did it as well, so last working temperature showings are from 30681.
Router: wrt1200ac
Firmware: 30731
Kernel: 3.18.42
Status: up and running
Reset: yes
Errors: no
Anomaly: (incorrect CPU temperature, reporting either 0C or a few hundred million degreesC )
Router: wrt1900acs v1
Firmware: 30731
Kernel: 3.18.42
Status: up and running
Reset: yes
Errors: no
Anomaly: (incorrect CPU temperature, reporting either 0C or a few hundred million degreesC )
Joined: 13 Jun 2006 Posts: 1608 Location: SE Michigan USA
Posted: Fri Oct 07, 2016 21:30 Post subject:
My wrt1900ac v1 is showing cpu temp of 83 to 84 degrees. Now understand that I set the fan turn on at 85 and off at 80 so this is to be expected. If I were to leave the fan setting at the default I am sure it would be lower, but since this is the Linksys defaults I figure it is good enough for me
This build will install through the Linksys UI on my wrt1900ac v1. Last 3 builds would report a file too big error. Looks like Brainslayer has found the magic to make it work.
Also has an updated wireless driver.
# strings /lib/ath9k/mwlwifi.ko | grep 10.3
10.3.1.0-20160917
10.3.1.0-20160917
Wireless performance on 5GHz does not seem to be quite as good as previous build that did work on my wrt1900ac in my limited iperf test. I do not think everyone experiences this problem, but when I start out with the wireless 5GHz set to channel 149 the 5GHz light does not go on and the SSID is not being broadcast. If I set the channel to a lower number like 36, save and apply, then set channel to 149 everything works. Not sure why, but have seen this before with Brainslayer builds.
Router: wrt1900ac v1
Firmware: 30731
Kernel: 3.18.42
Status: up and running
Reset: yes
Errors: no
--bill
I assume this is the driver coming from the new 3200 model.
Joined: 13 Jun 2006 Posts: 1608 Location: SE Michigan USA
Posted: Sat Oct 08, 2016 3:15 Post subject:
cybrnook wrote:
myersw wrote:
This build will install through the Linksys UI on my wrt1900ac v1. Last 3 builds would report a file too big error. Looks like Brainslayer has found the magic to make it work.
Also has an updated wireless driver.
# strings /lib/ath9k/mwlwifi.ko | grep 10.3
10.3.1.0-20160917
10.3.1.0-20160917
Wireless performance on 5GHz does not seem to be quite as good as previous build that did work on my wrt1900ac in my limited iperf test. I do not think everyone experiences this problem, but when I start out with the wireless 5GHz set to channel 149 the 5GHz light does not go on and the SSID is not being broadcast. If I set the channel to a lower number like 36, save and apply, then set channel to 149 everything works. Not sure why, but have seen this before with Brainslayer builds.
Router: wrt1900ac v1
Firmware: 30731
Kernel: 3.18.42
Status: up and running
Reset: yes
Errors: no
--bill
I assume this is the driver coming from the new 3200 model.
That would be my guess. Just glad they are backporting to the old iron and making available to Brainslayer and I am guessing Openwrt and hopefully LEDE.
This build will install through the Linksys UI on my wrt1900ac v1. Last 3 builds would report a file too big error. Looks like Brainslayer has found the magic to make it work.
Also has an updated wireless driver.
# strings /lib/ath9k/mwlwifi.ko | grep 10.3
10.3.1.0-20160917
10.3.1.0-20160917
Wireless performance on 5GHz does not seem to be quite as good as previous build that did work on my wrt1900ac in my limited iperf test. I do not think everyone experiences this problem, but when I start out with the wireless 5GHz set to channel 149 the 5GHz light does not go on and the SSID is not being broadcast. If I set the channel to a lower number like 36, save and apply, then set channel to 149 everything works. Not sure why, but have seen this before with Brainslayer builds.
Router: wrt1900ac v1
Firmware: 30731
Kernel: 3.18.42
Status: up and running
Reset: yes
Errors: no
--bill
I assume this is the driver coming from the new 3200 model.
That would be my guess. Just glad they are backporting to the old iron and making available to Brainslayer and I am guessing Openwrt and hopefully LEDE.
--bill
I would assume BS pulled it out, or has another source. the mwlwifi Kaloz driver which everything today is based off of its still on the -1 release as the latest. So this came from somewhere else. Not sure lede/openwrt have the same luxury. who would linksys even send the unit to over there anyways, not sure who the primary maintainer would be to do the port.
Joined: 13 Jun 2006 Posts: 1608 Location: SE Michigan USA
Posted: Sat Oct 08, 2016 4:39 Post subject:
@cybrnook
Keep in mind that Brainslayer is working with Linksys/Marvell on the wrt3200acm and has drivers for that. Maybe they have slipped him some drivers for these as well or he has figured out how to adapt them to the current routers. Last time he posted something he was saying there were issues with the 5GHz wireless on the new toy.
The state of Openwrt/LEDE may be making DD-WRT the go to for the wrt3200acm 3rd party support unlike when the wrt1900ac v1 came out. Hopefully the LEDE team can pull things together as they were the principle ones behind Openwrt before the reft. Have not seen anything on Openwrt forums about support. Brainslayer seemed to indicate he did not think the LEDE folks have a wr3200acm and was not sure about Openwrt. Lots of speculation around these two.
@cybrnook
Keep in mind that Brainslayer is working with Linksys/Marvell on the wrt3200acm and has drivers for that. Maybe they have slipped him some drivers for these as well or he has figured out how to adapt them to the current routers. Last time he posted something he was saying there were issues with the 5GHz wireless on the new toy.
The state of Openwrt/LEDE may be making DD-WRT the go to for the wrt3200acm 3rd party support unlike when the wrt1900ac v1 came out. Hopefully the LEDE team can pull things together as they were the principle ones behind Openwrt before the reft. Have not seen anything on Openwrt forums about support. Brainslayer seemed to indicate he did not think the LEDE folks have a wr3200acm and was not sure about Openwrt. Lots of speculation around these two.
--bill
Yep, that's exactly what I meant. I know BS is working with Linksys, and I think he's the only one. So either he has a non-public fork of the mwlwifi driver, or he's somehow extracted it from the unit he got from Linksys (Former I assume being the case).
And for the OpenWRT/LEDE side, that's exactly what I meant. With it being in such the mess that it is, who would linksys even send the unit to to get day 1 opensource support, Kaloz? (even though LEDE seems to be having the traction these days...) No idea just talking....
I put this build on my WRT1200 V1 tonight, took Kongs latest off so I could start from stock, factory to dd went fine but dd to dd failed and booted me back to stock. Since I was already back in stock I reset to defaults and tried factory to dd again and it also failed. It's a little late here so I just put Kong back on and it worked fine, factory to dd and dd to dd, I'll try again tomorrow with this build.
edit - took 5 tries, but it finally flashed from this beta build (30731) to this beta build (30731), flashed it twice more to make sure and it worked fine both times, so it seems to be a bit finicky on that first dd to dd web flash, but once it works it seems to work fine.
Belkin/Linksys/Marvell provide only binary blobs to the 3rd party devs so no the driver is not opensource as we normally think of it.
--bill
So how are OpenWRT using it? Don't they have a policy of only supporting open drivers? WiFi chip firmware can be closed though, but driver itself should be open if I understood correctly.
)
