Cannot test mega build (ftp://ftp.dd-wrt.com/betas/2018/03-05-2018-r35244/broadcom/dd-wrt.v24_mega_wrt600n.bin) on WRT600N because it is the same bin file as r35034.
Cannot test mega build (ftp://ftp.dd-wrt.com/betas/2018/03-05-2018-r35244/broadcom/dd-wrt.v24_mega_wrt600n.bin) on WRT600N because it is the same bin file as r35034.
Cannot test mega build (ftp://ftp.dd-wrt.com/betas/2018/03-05-2018-r35244/broadcom/dd-wrt.v24_mega_wrt600n.bin) on WRT600N because it is the same bin file as r35034.
Does this happen often? Is this normal?
This is usually a sign that the firmware file is too large to fit on your machine. It has happened to me on several different routers. _________________
R6800 BS K4.4 r46329 (Main router)
WNDR3700v3 r40009 (WAP)
--- Spares ---
R7500 Stock FW (Found it at the city dump alongside a EX7000)
WNDR4300 BS K3.18 r40559 (Flaky ethernet ports)
R7000 BS K4.4 r40750 (Dead ethernet ports, cooked to death in the attic a really hot summers day, about 105-110C)
WNDR4000 BS K3.10 r31899 (Loaned out to tenant who lives in my old home)
WNR2000v2 BS K2.6 r39230 (bricks and giggles)
+ A bunch of WRT54GL:s
I use my routers with pretty basic configuration. Only having WiFi + BT coexist enabled.
I don't have any USB devices connected.
Router/Version: Asus RT-AC68U A1
Firmware: DD-WRT v3.0-r35244 std (03/05/18 )
Kernel: Linux 4.4.120 #2685 SMP Mon Mar 5 08:03:45 CET 2018 armv7l
Operating Mode: Gateway
Reset: Yes
Connection Type: Mobile Broadband
Modem: Sierra 330U
Issues/Errors: Several unknown symbols in log:
sierra_net: Unknown symbol usbnet_set_msglevel (err 0)
sierra_net: Unknown symbol usbnet_write_cmd (err 0)
sierra_net: Unknown symbol usbnet_change_mtu (err 0)
sierra_net: Unknown symbol usbnet_get_msglevel (err 0)
sierra_net: Unknown symbol usbnet_open (err 0)
sierra_net: Unknown symbol usbnet_skb_return (err 0)
sierra_net: Unknown symbol usbnet_tx_timeout (err 0)
sierra_net: Unknown symbol usbnet_read_cmd (err 0)
sierra_net: Unknown symbol usbnet_get_settings (err 0)
sierra_net: Unknown symbol usbnet_suspend (err 0)
sierra_net: Unknown symbol usbnet_start_xmit (err 0)
sierra_net: Unknown symbol usbnet_get_drvinfo (err 0)
sierra_net: Unknown symbol usbnet_status_start (err 0)
sierra_net: Unknown symbol usbnet_get_endpoints (err 0)
sierra_net: Unknown symbol usbnet_nway_reset (err 0)
sierra_net: Unknown symbol usbnet_status_stop (err 0)
sierra_net: Unknown symbol usbnet_stop (err 0)
sierra_net: Unknown symbol usbnet_disconnect (err 0)
sierra_net: Unknown symbol usbnet_link_change (err 0)
sierra_net: Unknown symbol usbnet_set_settings (err 0)
sierra_net: Unknown symbol usbnet_probe (err 0)
sierra_net: Unknown symbol usbnet_resume (err 0)
usbcore: registered new interface driver option
usbserial: USB Serial support registered for GSM modem (1-port)
usbcore: registered new interface driver qcserial
usbserial: USB Serial support registered for Qualcomm USB modem
usbcore: registered new interface driver sierra
usbserial: USB Serial support registered for Sierra USB modem
sierra 1-1:1.0: Sierra USB modem converter detected
usb 1-1: Sierra USB modem converter now attached to ttyUSB0
sierra 1-1:1.1: Sierra USB modem converter detected
usb 1-1: Sierra USB modem converter now attached to ttyUSB1
sierra 1-1:1.2: Sierra USB modem converter detected
usb 1-1: Sierra USB modem converter now attached to ttyUSB2
sierra 1-1:1.3: Sierra USB modem converter detected
usb 1-1: Sierra USB modem converter now attached to ttyUSB3
sierra 1-1:1.4: Sierra USB modem converter detected
usb 1-1: Sierra USB modem converter now attached to ttyUSB4
I'm running r33772 right now, and according to *just* the bin sizes r35244 (r35034) is almost 80KB smaller.
smask wrote:
This is usually a sign that the firmware file is too large to fit on your machine. It has happened to me on several different routers.
Did you reset prior to flashing? This can also happen if the router runs out of memory prepping to flash. This is why install instruction say to reset prior to flashing, so that all the extra user-enabled memory-hogging features are disabled.
That said, I couldn't get my F7K8302 to flash 34929 when I was also running 33772. I ended up wget'ing and manually writing it from telnet. However, when I updated to 35244 from the GUI, it worked fine, so maybe it was a 33772 issue for some models.
If a reset doesn't help, nor flashing a smaller type first (then retry mega), and you want to try the wget route, it would also be a good idea to `stopservice httpd` first, for the memory aspect. _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
I'm running r33772 right now, and according to *just* the bin sizes r35244 (r35034) is almost 80KB smaller.
smask wrote:
This is usually a sign that the firmware file is too large to fit on your machine. It has happened to me on several different routers.
Did you reset prior to flashing? This can also happen if the router runs out of memory prepping to flash. This is why install instruction say to reset prior to flashing, so that all the extra user-enabled memory-hogging features are disabled.
That said, I couldn't get my F7K8302 to flash 34929 when I was also running 33772. I ended up wget'ing and manually writing it from telnet. However, when I updated to 35244 from the GUI, it worked fine, so maybe it was a 33772 issue for some models.
If a reset doesn't help, nor flashing a smaller type first (then retry mega), and you want to try the wget route, it would also be a good idea to `stopservice httpd` first, for the memory aspect.
I think that you skipped over a bit of the conversation, I had mentioned that I cannot test this build (dd-wrt.v24_mega_wrt600n.bin) because the bin file is the same as r35034. That in turn led them to mention that the build intended to be released might have been too big to flash since my WRT600N has only a 8MB flash.
Router/Version: Linksys Wrt300n v1.1
Firmware: DD-WRT v3.0-r35244 std (03/05/18)
Kernel: Linux 2.4.37 #48448 Mon Mar 5 06:37:12 CET 2018 mips
Previous: DD-WRT v3.0-r34929 std (02/12/18)
Mode/Status: GATEWAY-AP WAN/WLAN-DHCP
Reset: no
Issues/Errors: good so far
Last edited by BR07H3R on Wed Mar 14, 2018 23:03; edited 4 times in total
Not a big deal, but the button to hide the "please check out our new features" isn't working. _________________ Netgear XR500
Rogers Ignite Cable
150mbps down/15mbps up
I think that you skipped over a bit of the conversation
No, I didn't. The firmware is more likely to have not flashed, when it appeared to have done so. That is what started the discussion of the file possibly being too big (it isn't) and my comments thereafter.
That said, a hex edit compare of 35034 and 35244 would quickly determine if they really are the same or not. The non-mega file sizes did change, so maybe mega did just fail. _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
No, I didn't. The firmware is more likely to have not flashed, when it appeared to have done so. That is what started the discussion of the file possibly being too big (it isn't) and my comments thereafter.
That said, a hex edit compare of 35034 and 35244 would quickly determine if they really are the same or not. The non-mega file sizes did change, so maybe mega did just fail.
I think you did. My first post on this page/in this thread is:
Quote:
Cannot test mega build (ftp://ftp.dd-wrt.com/betas/2018/03-05-2018-r35244/broadcom/dd-wrt.v24_mega_wrt600n.bin) on WRT600N because it is the same bin file as r35034.
Does this happen often? Is this normal?
I didn't even flash r35244 because it is the same as r35034. It would have been a waste of time since it is not r35244 but it is in fact r35034.
Router/Version: Netgear WNR3500L (V1)
Firmware: DD-WRT v3.0-r35244 std (03/05/18 )
Kernel: Linux Linux 3.10.108-dd #17976 Mon Mar 5 14:32:56 CET 2018 mips (k3 Build)
Operating Mode: Gateway
Reset: No
Connection Type: Cable Broadband
Modem: Motorola Router
Issues/Errors: Several unknown symbols in log:
NTP
Jan 1 00:00:15 router daemon.err ntpclient[1383]: Failed resolving address to hostname 1.us.pool.ntp.org: Try again
Jan 1 00:00:15 router daemon.err ntpclient[1383]: Failed resolving server 1.us.pool.ntp.org: Network is down
Jan 1 00:00:15 router daemon.err process_monitor[1382]: cyclic NTP Update failed (servers 1.us.pool.ntp.org)
Jan 1 00:00:15 router daemon.err process_monitor[1382]: Last update failed, we need to re-update after 30 seconds
Jan 1 00:00:15 router daemon.debug process_monitor[1382]: We need to re-update after 3600 seconds
Jan 1 00:00:15 router daemon.info process_monitor[1382]: set timer: 3600 seconds, callback: ntp_main()
Jan 1 00:00:51 router daemon.err ntpclient[1484]: Failed resolving address to hostname 1.us.pool.ntp.org: Try again
Jan 1 00:00:51 router daemon.err ntpclient[1484]: Failed resolving server 1.us.pool.ntp.org: Network is down
Jan 1 00:00:51 router daemon.err process_monitor[1382]: cyclic NTP Update failed (servers 1.us.pool.ntp.org)
radvd
Jan 1 00:00:04 router daemon.warn radvd[1164]: invalid all-zeros prefix in /tmp/radvd.conf, line 11
Other Issues
I have also noticed the router will "drop" a wifi connection even though the connection is still active. This causes devices to not connect to a given site. In order to fix the issues, you have to disconnect, then re-connect the device in order for it to work. Extremely frustrating.