It has a flash ID unlike any I have ever seen on a wrt160nl or e2100l.
You should link this post in the ticket you have open.... maybe BS can get you a fix.
Thanks -
Status: Flashed OK
Reset: Reset NVRAM, manually changed settings back
Errors:
UBIFS error (pid 1): ubifs_mount: cannot open "ubi0:rootfs", error -19
UBIFS error (pid 451): ubifs_mount: cannot open "ubi0:rootfs_data", error -19
ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/QCA99X0/hw2.0/firmware-6.bin failed with error -2
ath10k_pci 0001:01:00.0: Direct firmware load for ath10k/pre-cal-pci-0001:01:00.0.bin failed with error -2
ath10k_pci 0001:01:00.0: failed to fetch board data for bus=pci,vendor=168c,device=0040,subsystem-vendor=168c,subsystem-device=0002 from ath10k/QCA99X0/hw2.0/board-2.bin
qcom-dwc3-ssphy 110f8830.phy: cannot get HSIO settings from device node, using default values
bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter
voltage drivers not compiled into kernel for phy (100f8830.phy 110f8830.phy 110f8800.phy 110f8800.phy) --> vddcx , v3p3 , v1p8
soc:usb30@0 supply gdsc not found , soc:usb30@1 supply gdsc not found
nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
USB and Sata no automount after power cycle
Still have to force it to run the .rc_startup after mount, then I have to go into Services/USB and hit apply (after every boot)
Still has USB problems, no automount, seems like a "timing" issue, as rmmod and insmod xhci-hcd corrects issue
Devoured a taco 12 pack and felt guilty for adding my own nacho cheese chips instead of buying the more expensive nacho cheese shells
Router: DIR-615 i1
Status: Good
Reset: Reset to defaults with flash procedure; erased NVRAM before and after flash
Errors: None
Router: TL-WDR3600 v. 1.5
Status: Buggy
Reset: Reset to defaults with flash procedure; erased NVRAM before and after flash
Errors: After about 30 minutes, internet traffic came to a grinding halt and httpd was nearly unresponsive. Had to login via telnet to reboot, and each command via telnet took over 20 seconds to execute. Flashed back to 33006, as this is the last good build for this router. Builds 33180, 33215, 33257 and 33342 all cause the unit to randomly reboot.
I'm using a TP-Link TL-WR841ND v7 and was getting random reboots too till 33342.. reverted to 32868 (but I think 33215 could have worked too).. this 33345 im testing right now but somehow I already know I'll have reboots lol
edit: YES I'M HAVING REBOOTS! going back to 33215
Last edited by heiler on Mon Oct 02, 2017 2:05; edited 2 times in total
Router: D-Link DIR-859 A3
Firmware DD-WRT v3.0-r33345 std (09/11/17)
Kernel: Forgot to note the kernel version before I reverted.
Status: QOS bug
Reset: No
Upgraded from 33215 via web interface GUI
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Thu Sep 14, 2017 0:24 Post subject:
Deltabongo2 wrote:
Router: D-Link DIR-859 A3
Firmware DD-WRT v3.0-r33345 std (09/11/17)
Kernel: Forgot to note the kernel version before I reverted.
Status: QOS bug
Reset: No
Upgraded from 33215 via web interface GUI
- 5Ghz radio disabled
- QOS Enabled
QOS is using the Uplink limit as the download limit. Reverted to 33215 and all is ok.
as usual brainslayer never touches qos, except when trying to make it smaller which is exactly what broke it this time.. _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
Router: D-Link DIR-859 A3
Firmware DD-WRT v3.0-r33345 std (09/11/17)
Kernel: Forgot to note the kernel version before I reverted.
Status: QOS bug
Reset: No
Upgraded from 33215 via web interface GUI
- 5Ghz radio disabled
- QOS Enabled
QOS is using the Uplink limit as the download limit. Reverted to 33215 and all is ok.
as usual brainslayer never touches qos, except when trying to make it smaller which is exactly what broke it this time..
QOS worked ok on 3700v4 also 160NL ... using global settings only htb fq_codel. Not backwards on these.
Many tests but all with different settings under 15000k.
Only noticed DL would always be right on or very slightly over settings and
UL tests bout same as always.... a little under what is set.
Router: D-Link DIR-859 A3
Firmware DD-WRT v3.0-r33345 std (09/11/17)
Kernel: Forgot to note the kernel version before I reverted.
Status: QOS bug
Reset: No
Upgraded from 33215 via web interface GUI
- 5Ghz radio disabled
- QOS Enabled
QOS is using the Uplink limit as the download limit. Reverted to 33215 and all is ok.
Posted: Thu Sep 14, 2017 9:58 Post subject: Re: Tried to fash doesnt work
teslacoil wrote:
Dioid wrote:
After 2-3 seconds of flashing reboot and then after 2 mins later it shows 33342 and works what the..... Doesnt flash. Never had this before.
Router: Archer c7 v2
Firmware: DD-WRT v3.0-r33342 std (09/09/17)
tried to update to DD-WRT v3.0-r33345
Reset: no
Quite strange. tried with newest Firefox with webinterface and Ubuntu 16.04.
SEEMS TO BE DEFECTIVE for me.
Erase the NVRAM before and after the flash, and reset to defaults with the flash procedure. It's not "defective" until you actually follow the correct flashing procedure.
Erased NVRAM too same problem reboots after af few seconds of flashing, says update successful and noting was flashed it shows 33342 like always. tride to flash 33215 same problem. Flashing via webgui does not, how can i do it with tftpd?
Posted: Thu Sep 14, 2017 13:03 Post subject: Re: Tried to fash doesnt work
Dioid wrote:
Erased NVRAM too same problem reboots after af few seconds of flashing, says update successful and noting was flashed it shows 33342 like always. tride to flash 33215 same problem. Flashing via webgui does not, how can i do it with tftpd?
I'm using a TP-Link TL-WR841ND v7 and was getting random reboots too till 33342.. reverted to 32868 (but I think 33006 could have worked too).. this 33345 im testing right now but somehow I already know I'll have reboots lol
On the TL-WDR3600, flashed back to 33006 last night. I had 33345 running for a couple days until the firmware caused the router to reboot itself. 33006 on this particular router is rock solid.
Posted: Thu Sep 14, 2017 18:42 Post subject: Re: Tried to fash doesnt work
teslacoil wrote:
Dioid wrote:
Erased NVRAM too same problem reboots after af few seconds of flashing, says update successful and noting was flashed it shows 33342 like always. tride to flash 33215 same problem. Flashing via webgui does not, how can i do it with tftpd?
Posted: Thu Sep 14, 2017 20:16 Post subject: Re: Tried to fash doesnt work
Dioid wrote:
teslacoil wrote:
Dioid wrote:
Erased NVRAM too same problem reboots after af few seconds of flashing, says update successful and noting was flashed it shows 33342 like always. tride to flash 33215 same problem. Flashing via webgui does not, how can i do it with tftpd?
