@davidc502,

Thanks for the quick reply! Guess I'll be staying on r2695 for now, and we'll see what happens with the 4.9.x kernel.

Thanks again!
ThePatrikos

Installed it (Shelby on v2 ) and it's working perfectly! Thanks @David!

Continued to test... Noticed that the collectd rrd was not rendering new data... looked and found that collectd was not running

Test 1:
- Did the upgrade "Keeping settings" from r3582 to r3716.
- Reinstalled all of my collectd plugins, but the collectd daemon never came up again... it was just not running after the first nor second boot. Tried to stop the service and start it again , but nothing.

Test 2:
- Now upgraded without keeping the settings.
- Restored the settings right after configuring the wifi network by using the option "To restore configuration files, you can upload a previously generated backup archive here."
- Reinstalled the collectd plugins ( I may have had to do this BEFORE restoring the backup file ... ? )
- Rebooted
- Collectd daemon still not working
- did a simple /etc/init.d/collectd restart , and the deamon started working
- rebooted
- collectd still happily working

Also getting this errors in the System Log , why could that be?

Mon Mar 13 01:24:48 2017 daemon.err insmod: module is already loaded - act_ipt
Mon Mar 13 01:24:48 2017 daemon.err insmod: module is already loaded - sch_ingress
Mon Mar 13 01:24:48 2017 daemon.err insmod: module is already loaded - act_mirred
Mon Mar 13 01:24:48 2017 daemon.err insmod: module is already loaded - cls_fw
Mon Mar 13 01:24:48 2017 daemon.err insmod: module is already loaded - cls_flow
Mon Mar 13 01:24:48 2017 daemon.err insmod: module is already loaded - cls_u32
Mon Mar 13 01:24:48 2017 daemon.err insmod: module is already loaded - sch_htb
Mon Mar 13 01:24:48 2017 daemon.err insmod: module is already loaded - sch_hfsc

Is QOS scripts running?  Also, which version of hardware do you have?

Ok, I managed to brick my WRT1900Ac v1. I updated to last firmware from Davidc502 but was having some problems, so I decided to go back to previous image. And, being very careful I did it from Linksys OEM firmware. But I used the sysimage instead of the factory image .

It seems now I can only use the serial interface to bring the router back to life. I've been reading all around and I think I can do it easily (I have a USB-TTL cable ready).

My only question, as it's something I haven't been able to found it is: which firmware should I use?

I like to have Linksys firmware in first partition and always flash Lede (or DD_Wrt) from there. Should I use the OEM firmware from Linksys site or other firmware? If so, which one?

Thanks in advance. And by the way, thanks for your work, David. Your Lede has been working fine for me for months. This "flashing the latest" obsession...

Edit: Another question. Flash both partitions or only one?

(Last edited by aluisperezh on 13 Mar 2017, 15:06)

You should be able to switch back to original firmware with the on/off power button method. then repeat flash with correct file

Unfortunately no. I've tried many times, with different timings, but it won't boot any way. I'm afraid that when using the image I used there's something broken in both partitions .

Thanks for your help anyway.

Regards,

The faults dissapeared as soon as I disabled QOS from Startup (which I assumed it's the SQM QOS script) . I have QOS is running ... SQM QOS is disabled. I have a 1900ACS v2.

Are you good to go with doing the USB/TTL method?

I read the new 3200acm driver may be ready to start testing by the end of the month.

Yeah, I recovered the router yesterday and reflashed your firmware without any trouble (well, except that the 2.4GHz LED is not working , but I'll open it again some time...).

The problem I have now is that I cannot boot to OEM firmware. Perhaps it's booting, but I can't access the router by the usual 192.168.1.1 or www.linksyssmartwifi.com addresses.

And when I try to install OEM FW from LEDE I always get the "non supported format" message. Just downloaded Linksys FW again with the same results. I'll try from CLI...

Regards and thanks for your support.

Edit: Tried from CLI but it seems I need "-F" parameter. Is that right? I remember having read around here of this problem with 3200, but not with 1900... I'm on r3293

Edit 2: Ok, the 3-reboot trick worked. I updated to r3716 and I remembered why I had to go back. The "Update lists" button for software doesn't work:

Downloading https://davidc502sis.dynamic-dns.net/snapshots/r3716/targets/mvebu/generic/packages/Packages.gz
*** Failed to download the package list from https://davidc502sis.dynamic-dns.net/snapshots/r3716/targets/mvebu/generic/packages/Packages.gz

Downloading https://davidc502sis.dynamic-dns.net/snapshots/r3716/packages/arm_cortex-a9_vfpv3/base/Packages.gz
*** Failed to download the package list from https://davidc502sis.dynamic-dns.net/snapshots/r3716/packages/arm_cortex-a9_vfpv3/base/Packages.gz

Downloading https://davidc502sis.dynamic-dns.net/snapshots/r3716/packages/arm_cortex-a9_vfpv3/luci/Packages.gz
*** Failed to download the package list from https://davidc502sis.dynamic-dns.net/snapshots/r3716/packages/arm_cortex-a9_vfpv3/luci/Packages.gz

Downloading https://davidc502sis.dynamic-dns.net/snapshots/r3716/packages/arm_cortex-a9_vfpv3/packages/Packages.gz
*** Failed to download the package list from https://davidc502sis.dynamic-dns.net/snapshots/r3716/packages/arm_cortex-a9_vfpv3/packages/Packages.gz

Downloading https://davidc502sis.dynamic-dns.net/snapshots/r3716/packages/arm_cortex-a9_vfpv3/routing/Packages.gz
*** Failed to download the package list from https://davidc502sis.dynamic-dns.net/snapshots/r3716/packages/arm_cortex-a9_vfpv3/routing/Packages.gz

Downloading https://davidc502sis.dynamic-dns.net/snapshots/r3716/packages/arm_cortex-a9_vfpv3/telephony/Packages.gz
*** Failed to download the package list from https://davidc502sis.dynamic-dns.net/snapshots/r3716/packages/arm_cortex-a9_vfpv3/telephony/Packages.gz

Failed to establish connection
Failed to establish connection
Failed to establish connection
Failed to establish connection
Failed to establish connection
Failed to establish connection
Collected errors:
 * opkg_download: Failed to download https://davidc502sis.dynamic-dns.net/snapshots/r3716/targets/mvebu/generic/packages/Packages.gz, wget returned 4.
 * opkg_download: Check your network settings and connectivity.

 * opkg_download: Failed to download https://davidc502sis.dynamic-dns.net/snapshots/r3716/packages/arm_cortex-a9_vfpv3/base/Packages.gz, wget returned 4.
 * opkg_download: Check your network settings and connectivity.

 * opkg_download: Failed to download https://davidc502sis.dynamic-dns.net/snapshots/r3716/packages/arm_cortex-a9_vfpv3/luci/Packages.gz, wget returned 4.
 * opkg_download: Check your network settings and connectivity.

 * opkg_download: Failed to download https://davidc502sis.dynamic-dns.net/snapshots/r3716/packages/arm_cortex-a9_vfpv3/packages/Packages.gz, wget returned 4.
 * opkg_download: Check your network settings and connectivity.

 * opkg_download: Failed to download https://davidc502sis.dynamic-dns.net/snapshots/r3716/packages/arm_cortex-a9_vfpv3/routing/Packages.gz, wget returned 4.
 * opkg_download: Check your network settings and connectivity.

 * opkg_download: Failed to download https://davidc502sis.dynamic-dns.net/snapshots/r3716/packages/arm_cortex-a9_vfpv3/telephony/Packages.gz, wget returned 4.
 * opkg_download: Check your network settings and connectivity.

I can manually download Packages.gz from my computer, but the router doesn't seem to like it.

Edit 3: More info. It's related to DNS. Maybe r3716 does not like restoring my backup. I'll try to start from scratch later, but by now I'm going back to r3293

(Last edited by aluisperezh on 14 Mar 2017, 09:15)

Hello,

     I've done a lot of reading of WRT threads and instructions...only to find out that many were long deprecated, or no longer required (ex: ipkg-opt & optware package requirements to enable file sharing). With a lot of conflicting information, or lack of updated/outdated notifications, I do not have the highest confidence in the relevance of the material I've gone through so far, so apologies for the nub questions:

-1 Does the first warning (below) in the RANGO_WARNING.txt file still apply, and if so, is there any potential timeframe for it to be addressed, or is there no workaround available to prevent it?

RANGO_WARNING.txt:
2/12/2016

This is a WARNING about installing LEDE on the wrt3200acm "RANGO". After flashing LEDE, it may not be possible to flash another image, factory or anything else, without a USB to TTL cable using the serial method.

-2 I do not see a link or file for the Release Notes for the latest version released; where did I not look that I should have looked, or can that be linked to on the davidc502sis.dynamic-dns info page, and/or included in the download files, like the RANGO_WARNING.txt?

-3 Coming from DD-WRT on the WRT3200ACM, is there a more direct process to flash LEDE, or is it just revert to stock first, throwing in as many 30-30-30's as I have the patience for?

(Last edited by ryanexec on 14 Mar 2017, 23:44)

@ryanexec

1. I've had some say it doesn't apply, but since I've experienced it first hand, and others have confirmed, the warning will stay on the site until I can flash at least twice without the USB/TTL method.

2. Currently, there are not any release notes provided. I'm just one person who has limited time, so I have to pick and choose what's done.

3. I've never used DD-WRT before, but if it has the option to flash and NOT keep any settings, then it's probably safe to flash directly to LEDE. I stress probably thought    If it didn't work well you can use recovery to take the image back to DD-WRT.

Concern to flashing WRT3200 with LEDEfirmware (your compilation).

Only USB/TTL method is possible or We can login via ssh and change boot partition (like below) to this with OEM firmware and flash from OEM web gui once again and again?

ubootenv get boot_part 
ubootenv set boot_part 2 #or 1 depends which partition is actually active
reboot

(Last edited by silelis on 15 Mar 2017, 12:22)

@silelis

You can certainly try to set the boot partition.

@david
Tried your latest, 3/12/2017, build on my wrt1900acs v1. Still have issue of no IP address from ISP and no Internet, of course, after doing a custom MAC on the WAN interface. KNOW you said probably would not be fixed until 4.9, but thought I would give it a try.

Cybrnook's latest beta is using the 4.9 kernel and no issues with assigning a MAC to the WAN interface.

Just an update
--bill

(Last edited by bill1228 on 15 Mar 2017, 16:23)

I do have a test 4.9 build, so if you want to try it let me know and I'll put it up on the server for you to download.

@david.
Sure give me access to test build for 4.9 and I will give it a go.  Will be installed on a wrt1900acs v1.
--bill

It's not going to work yet. v1 on kernel 4.9 = constant reboots.  Until that's fixed we can't move forward with the new kernel.

@david
Ok. Guess I will wait. Thought maybe your 4.9 would work on the wrt1900acs v1 as cybrnook's latest beta is 4.9 and runs with my custom MAC on the wrt1900acs v1.

Note it is a wrt1900acs not a wrt1900ac v1 which I know has issues. 

--bill

Ops... I saw v1 and thought the original v1.   I've tested on my acs, and the new kernel runs really well.

See link below.

https://davidc502sis.dynamic-dns.net/sn … /r3681.zip

(Last edited by davidc502 on 15 Mar 2017, 23:54)

@david
Figured you might have missed the 's' in the acs.   Easy enough to do.
Installed r3681 on my wrt1900acs v1. I was able to modify the WAN MAC and still get a IPv4 address from the ISP as I should get. So that is fixed in this build. Everything else that I use, wireless, routing and Internet access is working fine. No issues so far and do not expect any.

Will give you a heads up if I do encounter any issues.

Thanks for all the effort you put into providing us stupid Linksys folks with a excellent firmware build. Have to admit it is the look of the old wrt54g that got me hooked. Hopefully we get a good driver here at the end of the month.

--bill

(Last edited by bill1228 on 16 Mar 2017, 01:20)

Glad to help out Bill.  Hopefully, we will get this LEDE/Openwrt stuff that's happening behind the scenes, 'behind' us as well. In other words I hope they get it figured out, and move forward as one voice instead of how they are fractured today.

Best Regards,

Can you confirm the WIFI on wrt1900acs is completely stable with lots of devices connected (stressing the network), and no bandwidth throughput fluctuations?

I hope the WRT3200ACM will come also to this WIFI stability...