Joined: 05 Apr 2017 Posts: 981 Location: Louisiana, USA
Posted: Thu Aug 16, 2018 13:00 Post subject:
Yemble wrote:
spuriousoffspring wrote:
Several people have been experiencing this issue and so far I haven't seen anything to help narrow it down.
@spurious
Someone on the Archer C9 thread suggested that the failed upgrade attempts on recent firmware maybe related to the browser being used, more specifically Chrome, and that IE works better. Not sure about this, however, I was using Chrome when my first upgrade attempt locked up. I think, although I can't be certain, that I may have been using Edge for my second, successful, upgrade attempt.
This is circumstantial evidence at best, so requires further proof!
My first thought is always the browser - mostly based on my own personal experience. Chrome does a terrific job of caching pages in memory. I use it as my regular GUI browser because I like the 'Open as a Window' desktop shortcut. However, I have always had issues when upgrading firmware. Especially when switching between DD-WRT, OpenWrt & Stock.
It always required a second browser (I usually use Edge) to do the initial setup & configuration after flashing.
Afterwards I cleared the history of all browsers and then I could re-navigate to 192.168.1.1.
Now I just keep three separate shortcuts on my desktop and whatever firmware I happen to be using at the time, I pin that shortcut to the Taskbar.
Linksys Venom @ http://192.168.1.1/#!/login
OpenWrt @ https://192.168.1.1/cgi-bin/luci
DD-WRT @ http://192.168.1.1
This probably explains about 75% of the upgrade issues on this forum. I think most people don't bother with the above browser steps, assume it didn't work and revert back.
That being said I have seen a few posts where the forum member specifically mentioned that different browsers were tried and the flash still failed.
As far as I can tell all of these have been from Linksys stock firmware to DD-WRT.
It's possible that most, if not all, of these could be fixed by downgrading the stock Linksys firmware and then flashing DD-WRT.
If this is the case then it's two relatively simple problems making it look like a much larger issue. _________________ DD-WRT Installation & Setup TUTORIAL http://www.dd-wrt.com/phpBB2/viewtopic.php?t=311117
FIRMWARE:OpenWrt SNAPSHOT r8217-2cc821e / LuCI Master (git-18.276.41146-280dd33) MODEM:ARRIS SURFBoard SB8200 ROUTER:Linksys WRT32X USB NAS:Western Digital BLACK 1 TB Hardrive + Startech USB 3.0 External SATA III Enclosure
Someone on the Archer C9 thread suggested that the failed upgrade attempts on recent firmware maybe related to the browser being used, more specifically Chrome, and that IE works better. Not sure about this, however, I was using Chrome when my first upgrade attempt locked up. I think, although I can't be certain, that I may have been using Edge for my second, successful, upgrade attempt.
This is circumstantial evidence at best, so requires further proof!
I used Chrome and yes, mine locked up on the first attempt as well. It posted "0% Downloaded" or similar at the bottom left corner and never progressed. It worked on the second attempt (again in Chrome). I wasn't sure if that's what was happening to others who have posted they were unable to upgrade, but after I made it through this slight hiccup everything is fine.
...oh but I was upgrading from an 8-month old version, so this is irrelevant. Nevermind.
I don't reboot daily, I just let it build uptime, but it definitely works right off the bat - as soon as I get a Wireless address, I can start streaming. However as I mentioned I have miniDLNA storing its media search to /jffs/minidlna/files.db. Maybe this helps? Donno. The storage is also (mostly) formatted exFAT (two 256GB thumb drives), except for a small 4GB EXT4 partition for JFFS on one of the drives. Maybe try creating the JFFS to store the search first (if you haven't already)? I was able to use partition magic (or similar) to cram this JFFS partition on the end of one of my drives without reformatting the whole thing.
I was wrong about the 34313/34315 (12/30/17) build having a "better" miniDLNA. I rebooted to that build and had it scan the files. It doesn't see my huge picture directories either... both versions miss a lot of photos for some reason. Googling about this to try to find a possible fix, will post if I figure anything out.
You're able to see media files on the dlna with the drive (partially) formatted exfat? I couldn't get my 3200acm to see or really even recognize my 2TB usb3 Seagate formatted exfat as it originally was. Reformatted to ext4 and haven't had any issues with nas/mdlna. Granted, currently on ver r33986 (12/04/17), but signs for me seemed to indicate Linux might not play nicely with exfat. Hopefully you can see all your exfat media when connected to a windows box?
[...] The storage is also (mostly) formatted exFAT (two 256GB thumb drives), except for a small 4GB EXT4 partition for JFFS on one of the drives. [...]
You're able to see media files on the dlna with the drive (partially) formatted exfat? [...] Hopefully you can see all your exfat media when connected to a windows box?
Yep, when using SMB to access these exFAT USB disks from Win10 everything is there. I even use SyncBack Pro (backup/sync software for Win) to backup photos/videos to these disks over WiFi... here's one mount report from my http://192.168.1.1/USB.asp (these are 256GB Sandisk units, this is the one that also has a JFFS at its end):
Code:
--- /dev/sda1
Block device, size 227.2 GiB (244007813120 bytes)
FAT32 file system (hints score 4 of 5)
Volume size 227.2 GiB (243947143168 bytes, 7444676 clusters of 32 KiB)
/dev/sda1 mounted to /tmp/mnt/sda1
Were you by any chance suggesting that EXT4 might help the miniDLNA performance (i.e. allow it to see all my files)? If so I would definitely give that a shot. Please let me know.
Yep, when using SMB to access these exFAT USB disks from Win10 everything is there. I even use SyncBack Pro (backup/sync software for Win) to backup photos/videos to these disks over WiFi... here's one mount report from my http://192.168.1.1/USB.asp (these are 256GB Sandisk units, this is the one that also has a JFFS at its end):
Code:
--- /dev/sda1
Block device, size 227.2 GiB (244007813120 bytes)
FAT32 file system (hints score 4 of 5)
Volume size 227.2 GiB (243947143168 bytes, 7444676 clusters of 32 KiB)
/dev/sda1 mounted to /tmp/mnt/sda1
Were you by any chance suggesting that EXT4 might help the miniDLNA performance (i.e. allow it to see all my files)? If so I would definitely give that a shot. Please let me know.
I'm assuming all your files on the exfat partitions are there when you plug the drive(s) directly into a win box, not through samba? Regardless, hopefully you have backups of backups of the important media files!
My personal experience with the 3200acm would suggest, yeah. One ext3 or 4 partition would probably play nicer with linux. Here's what I get on the usb tab (I also specified the uuid in the jffs field on the usb tab):
Code:
--- /dev/sda1
Block device, size 1.819 TiB (2000396321280 bytes)
Ext4 file system
Volume name "Seagte2TBII"
UUID 39B2AB12-C7C4-C24F-B468-6D599BF6146B (DCE, v12)
Last mounted at "/jffs"
Volume size 1.819 TiB (2000396320768 bytes, 488378008 blocks of 4 KiB)
/dev/sda1 mounted to /jffs
Had virtually no info when the drive was formatted exfat and wouldn't really even work with smb or mdlna.
Btw, your report says fat32. Is there a fat32 partition on your drive? I thought it was a mix of exfat and ext4? I might have misread..
Joined: 30 May 2017 Posts: 582 Location: Rural Manitoba
Posted: Fri Aug 17, 2018 19:05 Post subject:
I too had lockups and inaccessibility problems when I upgraded to r36596 and as soon as I tried to access wireless status.
I took my spare 3200, flashed it back to OEM through the gui, from there I upgraded to r36596. I now had to input all my settings, but all went well and without problem with accessing wireless status page. Incidentally on my first try I restored my backup to r36596 and everything started to hang when I tried to access the wireless status.
So, the moral of this is to upgrade to r36596 one must do a clean install. _________________ Starlink & DSL -> TPLink TL-R470T+
->
WRT3200acm Master WDS 5GHz 80Mhz CH 100 (+6) r55819
Ath1 2.4Ghz Disabled
99 Static Leases
ExpressVPN
WRT3200acm r55819 WDS Station 5Ghz
Ath1 AP N/G Mixed Channel 11 HT40
WRT1900Ac V1 5Ghz r55819 WDS Station
(Defective, no 2.4Ghz but 5Ghz works great)
WRT1900AC V1 5Ghz AC 80Mhz WDS Station r55819
2.4Ghz AP Ch1 HT20 Mixed
WRT1900ACS SPARE r54914
WRT1900AC SPARE r54914
WRT1900AC V1 5Ghz AC 80Mhz WDS-AP r55819
2.4Ghz AP Ch1 HT20 Mixed
WRT54G DD-WRT v3.0-r37305 micro AP CH 6 Mixed - Not in use
Joined: 30 May 2017 Posts: 582 Location: Rural Manitoba
Posted: Sat Aug 18, 2018 1:40 Post subject: Upgrade r36596
Now that I have update procedure down after re-reading the sticky I was able to upgrade my spare 3200 and one of my 1900's. I needed to test the hourly 5ghz dropouts on my wds. Using my 3200 as a master and the 1900 as a station both with r36596, I still got hourly drop/reset. As before if I disable security all is well and no drops. I also tested the inability of the 2.4ghz to communicate with esp8266 devices and there was no improvement, I still need to disable wmm. As a new problem when I used the 3200 to link to my ex7000 extender on the 5ghz. any esp8266 devices failed to connect. All these problems are with the 3200's only. The stock linksys does not exhibit the esp8266 failures. I did try LEDE and it is the same as dd-wrt for both problems. _________________ Starlink & DSL -> TPLink TL-R470T+
->
WRT3200acm Master WDS 5GHz 80Mhz CH 100 (+6) r55819
Ath1 2.4Ghz Disabled
99 Static Leases
ExpressVPN
WRT3200acm r55819 WDS Station 5Ghz
Ath1 AP N/G Mixed Channel 11 HT40
WRT1900Ac V1 5Ghz r55819 WDS Station
(Defective, no 2.4Ghz but 5Ghz works great)
WRT1900AC V1 5Ghz AC 80Mhz WDS Station r55819
2.4Ghz AP Ch1 HT20 Mixed
WRT1900ACS SPARE r54914
WRT1900AC SPARE r54914
WRT1900AC V1 5Ghz AC 80Mhz WDS-AP r55819
2.4Ghz AP Ch1 HT20 Mixed
WRT54G DD-WRT v3.0-r37305 micro AP CH 6 Mixed - Not in use
Linksys WRT32X
Firmware Version
DD-WRT v3.0-r36596 std (08/14/1
Kernel Version
Linux 4.9.119 #340 SMP PREEMPT Tue Aug 14 01:16:29 CEST 2018 armv7l
1. PPTP Server also does not work!
2. The message shows below with firefox after the upgrade:
Unable to connect
Firefox can’t establish a connection to the server at 192.168.1.1.
The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer’s network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.
3. MAC Address cannot revise in Ath0, Ath1 and Ath2.
