Posted: Tue May 24, 2022 5:22 Post subject: Latest builds of ddwrt fail on Netgear r6300 v1
Ive been running FreshTomato for the last 5 years or so. Decided to switch back to ddwrt. Loading latest couple of builds it looks like they fail on r6300v1.
Ive tried the 30/30/30, cant even get a link to the router via the RJ45 ports at all. Perhaps its the size of the kernel. I loaded older build (DD-WRT v3.0-r46788 giga (05/28/21)) and it works fine. Newer builds are in the ~26mb range and have this issue.
Serial output of entire boot sequence:
Code:
CFE for R6300 version: v1.0.2
Build Date: Wed Apr 25 16:29:10 CST 2012
Init Arena
Init Devs.
Boot partition size = 262144(0x40000)
Found an ST compatible serial flash with 32 64KB blocks; total size 2MB
Found a Samsung NAND flash with 2048B pages or 128KB blocks; total size 128MB
et0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 5.100.138
CPU type 0x19749: 600MHz
Tot mem: 131072 KBytes
Committing NVRAM...done
Waiting for reset button release...don▒ecompressing...done
CFE for R6300 version: v1.0.2
Build Date: Wed Apr 25 16:29:10 CST 2012
Init Arena
Init Devs.
Boot partition size = 262144(0x40000)
Found an ST compatible serial flash with 32 64KB blocks; total size 2MB
Found a Samsung NAND flash with 2048B pages or 128KB blocks; total size 128MB
et0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 5.100.138
CPU type 0x19749: 600MHz
Tot mem: 131072 KBytes
Device eth0: hwaddr 84-1B-5E-03-C0-F3, ipaddr 192.168.1.1, mask 255.255.255.0
gateway not set, nameserver not set
Checking crc...Loader:raw Filesys:raw Dev:nflash0.os File: Options:(null)
Loading: .... 1617032 bytes read
Entry at 0x80001000
Closing network.
Starting program at 0x80001000
[ 0.000000] Linux version 4.4.302 (root@linux) (gcc version 11.1.0 (OpenWrt GCC 11.1.0 r16896+6-3c46ba053d) ) #16020 Mon May 23 05:48:02 +07 2022
[ 0.000000] prom_init:194
[ 0.000000] CPU0 revision is: 00019749 (MIPS 74Kc)
[ 0.000000] Found ST compatible serial flash with 32 64KB blocks; total size 2MB
[ 0.000000] found nvram at 1F0000
[ 0.000000] something wrong here. do not remap
[ 0.000000] Using bcma bus
[ 0.000000] Determined physical RAM map:
[ 0.000000] memory: 07fff000 @ 00000000 (usable)
[ 0.000000] Primary instruction cache 32kB, 4-way, VIPT, I-cache aliases, linesize 32 bytes.
[ 0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
[ 0.000000] Zone ranges:
[ 0.000000] Normal [mem 0x0000000000000000-0x0000000007ffefff]
[ 0.000000] HighMem empty
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x0000000000000000-0x0000000007ffefff]
[ 0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x0000000007ffefff]
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32511
[ 0.000000] Kernel command line: console=ttyS0,115200 root=1f05 rootfstype=squashfs noinitrd init=/bin/sh
[ 0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[ 0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.000000] Writing ErrCtl register=80000d70
[ 0.000000] Readback ErrCtl register=80000d70
[ 0.000000] Cache parity protection enabled
[ 0.000000] Memory: 124396K/131068K available (3678K kernel code, 177K rwdata, 780K rodata, 216K init, 611K bss, 6672K reserved, 0K cma-reserved, 0K highmem)
[ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.000000] NR_IRQS:128
[ 0.000000] CPU: BCM5300 rev 1 at 600 MHz
[ 0.000000] clocksource: MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6370868154 ns
[ 0.000010] sched_clock: 32 bits at 300MHz, resolution 3ns, wraps every 7158278654ns
[ 0.195408] console [ttyS0] enabled
[ 0.199028] Calibrating delay loop... 299.82 BogoMIPS (lpj=1499136)
[ 0.268286] pid_max: default: 32768 minimum: 301
[ 0.273193] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.280063] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.288066] BRCM Errata: Disable CPU_WAIT
[ 0.294599] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.304829] futex hash table entries: 256 (order: -1, 3072 bytes)
[ 0.311864] NET: Registered protocol family 16
[ 0.317203] enable BCMA BUS Errata
[ 0.343615] boardflags are 110
[ 0.346818] PCI: Initializing host
[ 0.350329] PCI: Reset RC
[ 0.506053] boardflags are 110
[ 0.509240] PCI: Initializing host
[ 0.512747] PCI: Reset RC
[ 0.678625] PCI: scanning bus 0
[ 0.682034] PCI host bridge to bus 0000:00
[ 0.686284] pci_bus 0000:00: root bus resource [io 0x0000-0xffff]
[ 0.692715] pci_bus 0000:00: root bus resource [mem 0x00000000-0xffffffff]
[ 0.699825] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 0.705570] PCI: Fixing up bridge
[ 0.711929] PCI: Fixing up bus 0
[ 0.715298] pci 0000:00:05.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 0.723624] pci 0000:00:06.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 0.732026] PCI/PCIe coreunit 0 is set to bus 1.
[ 0.738502] PCI: Fixing up bus 1
[ 0.742047] PCI/PCIe coreunit 1 is set to bus 2.
[ 0.752079] PCI: Fixing up bus 2
[ 0.761523] clocksource: Switched to clocksource MIPS
[ 0.768421] NET: Registered protocol family 2
[ 0.773153] IP idents hash table entries: 2048 (order: 2, 16384 bytes)
[ 0.780674] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.787896] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.794526] TCP: Hash tables configured (established 1024 bind 1024)
[ 0.801189] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 0.807287] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 0.814021] NET: Registered protocol family 1
[ 0.819224] R6300 GPIO Init
[ 0.844220] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.852619] io scheduler noop registered (default)
[ 0.902644] HDLC line discipline maxframe=4096
[ 0.907241] N_HDLC line discipline registered.
[ 0.911895] serial8250_init
[ 0.914786] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[ 0.941600] serial8250: ttyS0 at MMIO 0x0 (irq = 8, base_baud = 1562500) is a U6_16550A
[ 0.970205] serial8250: ttyS1 at MMIO 0x0 (irq = 8, base_baud = 1562500) is a U6_16550A
[ 1.089952] brd: module loaded
[ 1.093513] pflash: found no supported devices
[ 1.098174] found WNDR4500 / R6300
[ 1.101690] try to find cfe size up to 2097152
[ 1.632348] no filesys. assume nflash devices
[ 1.636853] bootloader size: 2097152
[ 1.640566] nvram size: 65536
[ 1.643655] Creating 2 MTD partitions on "bcmsflash":
[ 1.648879] 0x000000000000-0x000000200000 : "cfe"
[ 1.656246] 0x0000001f0000-0x000000200000 : "nvram"
[ 1.663186] Found a Samsung NAND flash with 2048B pages or 128KB blocks; total size 128MB
[ 1.671739] nand: device found, Manufacturer ID: 0xec, Chip ID: 0xf1
[ 1.678303] nand: Samsung NAND 128MiB 3,3V 8-bit
[ 1.683105] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[ 1.692911] Bad block table found at page 65472, version 0x01
[ 1.701667] Bad block table found at page 65408, version 0x01
[ 1.707824] nand_read_bbt: bad block at 0x0000045c0000
[ 1.713273] Creating 2 MTD partitions on "brcmnand":
[ 1.718418] 0x000000000000-0x000002000000 : "linux"
[ 1.724995] 0x000002000000-0x000007f00000 : "ddwrt"
[ 1.799687] lookup_nflash_rootfs_offset: offset = 0x0
[ 1.805142] found trx at 0, len =26963968
[ 1.809278] scan filesys at 190000
[ 1.812923] nflash: squash filesystem with lzma found at offset 0
[ 1.819242] Creating 2 MTD partitions on "nflash":
[ 1.824198] 0x000000000000-0x000002000000 : "nandimage"
[ 1.831531] 0x000000190000-0x000002000000 : "rootfs"
[ 1.838537] mtd: partition "rootfs" set to be root filesystem
[ 1.844538] add netgear boarddata for pflash if exists
[ 1.849849] add netgear boarddata for sflash if exists
[ 1.855179] Creating 1 MTD partitions on "bcmsflash":
[ 1.860408] 0x0000001e0000-0x0000001f0000 : "board_data"
[ 1.867886] PPP generic driver version 2.4.2
[ 1.872539] PPP BSD Compression module registered
[ 1.877473] PPP Deflate Compression module registered
[ 1.882708] PPP MPPE Compression module registered
[ 1.887705] NET: Registered protocol family 24
[ 1.892449] Broadcom Watchdog Timer: 0.07 initialized.
[ 1.897884] GACT probability NOT on
[ 1.901508] Mirror/redirect action on
[ 1.905328] Simple TC action Loaded
[ 1.909902] netem: version 1.3
[ 1.913122] u32 classifier
[ 1.915918] Performance counters on
[ 1.919934] input device check on
[ 1.923714] Actions configured
[ 1.927291] Netfilter messages via NETLINK v0.30.
[ 1.932260] nf_conntrack version 0.5.0 (1943 buckets, 7772 max)
[ 1.938920] nf_conntrack_rtsp v0.7 loading
[ 1.943886] xt_time: kernel timezone is -0000
[ 1.948753] gre: GRE over IPv4 demultiplexor driver
[ 1.954203] nf_nat_rtsp v0.7 loading
[ 1.957944] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 1.963792] NET: Registered protocol family 17
[ 1.968543] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
[ 1.981683] Bridge firewalling registered
[ 1.985837] 8021q: 802.1Q VLAN Support v1.8
[ 1.990300] startup nvram driver
[ 1.993683] found nvram
[ 1.996241] max nvram space = 65536
[ 2.047734] VFS: Mounted root (squashfs filesystem) readonly on device 31:5.
[ 2.055746] Freeing unused kernel memory: 216K
[init] : starting devinit
cannot open /dev/nvram
udevtrigger[846]: parse_config_file: can't open '/etc/udev/udev.conf' as config file: No such file or directory
[init] : no previous bootfails detected! (all ok)
[init] : starting Architecture code for broadcom
boardnum 4536
boardtype 0xf52e
boardrev 0x1102
Booting device: Netgear R6300
Need reboot now .....
[watchdog] : daemon successfully started
get_wl_instance doesnt return the right value 0
No such device
Restoring Factory WIFI Pass: quickjade038
/etc/preinit: line 44: can't create /proc/sys/net/ipv4/ip_conntrack_max: nonexistent directory
cannot open /proc/sys/net/ipv4/ip_conntrack_max
/etc/preinit: line 44: can't create /proc/sys/net/ipv4/ip_conntrack_max: nonexistent directory
cannot open /proc/sys/net/ipv4/ip_conntrack_max
[resetbutton] : resetbutton daemon successfully started
get_wl_instance doesnt return the right value 0
wl: wl driver adapter not found
Write wireless mac fail : : No such device
wl: wl driver adapter not found
Failed to connect to the switch. Use the "list" command to see which switches are available.
Failed to connect to the switch. Use the "list" command to see which switches are available.
Failed to connect to the switch. Use the "list" command to see which switches are available.
Failed to connect to the switch. Use the "list" command to see which switches are available.
vconfig: ioctl error for add: No such device
vconfig: ioctl error for add: No such device
Failed to connect to the switch. Use the "list" command to see which switches are available.
[bridge] : bridge br0 successfully added
[ 11.964709] device br0 entered promiscuous mode
[ 11.985287] device br0 left promiscuous mode
[ 11.996223] device br0 entered promiscuous mode
ifconfig: ioctl 0x8913 failed: No such device[ 12.035089] device br0 left promiscuous mode
get_wl_instance doesnt return the right value 0
wl: wl driver adapter not found
get_wl_instance doesnt return the right value 0
wl: wl driver adapter not found
method udhcpd not found
method hwmon not found
ifconfig: ioctl 0x8913 failed: No such device
cannot open /proc/ctf
[sfe] : shortcut forwarding engine successfully stopped
sh: can't create /sys/class/ksmbd-control/kill_server: nonexistent directory
cp: can't stat '/tmp/mycron.d/*': No such file or directory
cp: can't stat '/jffs/mycron.d/*': No such file or directory
cp: can't stat '/mmc/mycron.d/*': No such file or directory
[ 14.124382] tun: Universal TUN/TAP device driver, 1.6
[ 14.129612] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
get_wl_instance doesnt return the right value 0
No such device
[wland] : daemon successfully started
[cron] : daemon successfully started
[dnsmasq] : daemon successfully started
cat: can't open '/proc/sys/net/netfilter/nf_conntrack_flush': No such file or directory
cannot open /proc/sys/net/ipv6/neigh/default/gc_thresh1
cannot open /proc/sys/net/ipv6/neigh/default/gc_thresh2
cannot open /proc/sys/net/ipv6/neigh/default/gc_thresh3
[httpd] : httpd server started at port 80
[httpd] : http daemon successfully started
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
[ 17.663996] fast-classifier (PBR safe v2.1.6b): starting up
[ 17.670019] fast-classifier: registered
[sfe] : shortcut forwarding engine successfully started
[ 18.099025] ip6_tables: (C) 2000-2006 Netfilter Core Team
ip6tables v1.8.5 (legacy): can't initialize ip6tables table `mangle': Address family not supported by protocol
Perhaps ip6tables or your kernel needs to be upgraded.
ip6tables v1.8.5 (legacy): can't initialize ip6tables table `mangle': Address family not supported by protocol
Perhaps ip6tables or your kernel needs to be upgraded.
ip6tables v1.8.5 (legacy): can't initialize ip6tables table `mangle': Address family not supported by protocol
Perhaps ip6tables or your kernel needs to be upgraded.
[sfe] : shortcut forwarding engine successfully started
ifconfig: ioctl 0x8913 failed: No such device
ifconfig: SIOCSIFTXQLEN: No such device
udhcpc: ioctl 0x8933 failed: No such device
[ttraff] : traffic counter daemon successfully started
get_wl_instance doesnt return the right value 0
wl: wl driver adapter not found
get_wl_instance doesnt return the right value 0
get_wl_instance doesnt return the right value 0
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
Radio: 0 currently turned off
[nas] : wait for network initmethod guest_nas not found
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
Radio: 0 currently turned off
[httpd] : daemon successfully stopped
[httpd] : httpd server shutdown[httpd] : httpd server started at port 80
[httpd] : http daemon successfully started
[resetbutton] : daemon successfully stopped
[resetbutton] : resetbutton daemon successfully started
[USB] checking...
/opt/etc/init.d/rcS: No such file or directory
/jffs/etc/init.d/rcS: No such file or directory
/mmc/etc/init.d/rcS: No such file or directory
killall: proxywatchdog.sh: no process killed
/mnt/smbshare
umount: can't unmount /mnt/smbshare: No such file or directory
rmmod: cifs: No such file or directory
rmmod: fscache: No such file or directory
killall: schedulerb.sh: no process killed
killall: wdswatchdog.sh: no process killed
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
[ 80.223361] random: nonblocking pool is initialized
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
get_wl_instance doesnt return the right value 0
No such device
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Tue May 24, 2022 7:46 Post subject: Re: Latest builds of ddwrt fail on Netgear r6300 v1
Duxa wrote:
Ive been running FreshTomato for the last 5 years or so. Decided to switch back to ddwrt. Loading latest couple of builds it looks like they fail on r6300v1.
Ive tried the 30/30/30, cant even get a link to the router via the RJ45 ports at all. Perhaps its the size of the kernel. I loaded older build (DD-WRT v3.0-r46788 giga (05/28/21)) and it works fine. Newer builds are in the ~26mb range and have this issue.
Hello.
First you dont do a 30/30/30 reset on Broadcom, according to experienced users here and my own experience with own Broadcom unit as per my signature, 30/30/30 can cause issues.
To nvram reset, you have 4 methods
1) At any time; Open a terminal and type nvram reset && reboot
2) (NOT recommended apparently soft brick as a result) When upgrading firmware via interface; On the Firmware Upgrade tab under After flashing reset to you select from dropdown -> Reset to default settings, select the upgrade firmware file below and click upgrade.
3) At any time; On the Factory Defaults tab you select Restore Factory Defaults and click the YES radio input and click the Apply Settings button.
4) Pressing the reset button on the router if present until the power led flashes or something like that, somewhere around 5 to 10 seconds.
Size of kernel is moot, you have 128MB flash, usable is around 30MB, which leaves you with exactly 35 free blocks when flashing the latest build.
The latest builds use swconfig now, older builds do not. Your serial log indicates the switch and wireless adapters cant be found.
Now I wonder if this is a known issue due to swconfig or because maybe you have flashed the wrong version of dd-wrt for v1 or maybe your config is wrong.
IDK how you went from fresh tomato to dd-wrt, you cant directly move between 3rd party firmwares it will screw your router.
Posted: Tue May 24, 2022 8:01 Post subject: Re: Latest builds of ddwrt fail on Netgear r6300 v1
the-joker wrote:
Duxa wrote:
Ive been running FreshTomato for the last 5 years or so. Decided to switch back to ddwrt. Loading latest couple of builds it looks like they fail on r6300v1.
Ive tried the 30/30/30, cant even get a link to the router via the RJ45 ports at all. Perhaps its the size of the kernel. I loaded older build (DD-WRT v3.0-r46788 giga (05/28/21)) and it works fine. Newer builds are in the ~26mb range and have this issue.
Hello.
First you dont do a 30/30/30 reset on Broadcom, according to experienced users here and my own experience with own Broadcom unit as per my signature, 30/30/30 can cause issues.
To nvram reset, you have 4 methods
1) At any time; Open a terminal and type nvram reset && reboot
2) (NOT recommended apparently soft brick as a result) When upgrading firmware via interface; On the Firmware Upgrade tab under After flashing, reset to you select from dropdown -> Reset to default settings, select the upgrade firmware file below and click upgrade.
3) At any time; On the Factory Defaults tab you select Restore Factory Defaults and click the YES radio input and click the Apply Settings button.
4) Pressing the reset button on the router if present until the power led flashes or something like that, somewhere around 5 to 10 seconds.
Size of kernel is moot, you have 128MB flash, usable is around 30MB, which leaves you with exactly 35 free blocks when flashing the latest build.
The latest builds use swconfig now, older builds do not. Your serial log indicates the switch and wireless adapters cant be found.
Now I wonder if this is a known issue due to swconfig or because maybe you have flashed the wrong version of dd-wrt for v1 or maybe your config is wrong.
IDK how you went from fresh tomato to dd-wrt, you cant directly move between 3rd party firmwares it will screw your router.
Yeah the router was in a weird state, I managed to flash it with build from 2019. Then slowly worked my way up updating from ddwrt to newer ddwrt builds selecting to clean VRAM with every upgrade. Last succesful build is dd-wrt.v24-48322_NEWD-2_K3.x_giga-R6300_.chk
Tried couple random ones after that including the latest 2, and all of them have this error:
No such device
get_wl_instance doesnt return the right value 0
one other thing I noticed. When flashing working builds returned 0 (no error) at the end of flashing.
But all troublesome builds did not. This is why I thought maybe its not fitting into flash:
Code:
[flash] : write block [26345472] at [0x01920000]
[flash] : write block [26476544] at [0x01940000]
[flash] : write block [26607616] at [0x01960000]
[flash] : write block [26738688] at [0x01980000]
[flash] : write block [26869760] at [0x019A0000]
[flash] :
done [27000832]
[init] : Terminated....................................
reboot: Restarting system
Please stand by while rebooting the system...
Decompressing...done
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Tue May 24, 2022 8:21 Post subject:
Brainslayer is clearly looking out for it, could be a bug slipped into some legacy Broadcom devices in recent builds, which have had quite a few changes to their code.
So bare with the slayer, if it caught his eye and he has your device to test and reproduce he will deal with it.
Quote:
But all troublesome builds did not. This is why I thought maybe its not fitting into flash:
No, I already said no and I know this for sure.
You can confirm this too, when you flash via CLI, look at the erased blocks and corresponding addresses.
Then compare with the written blocks and corresponding addresses.
if the last written block is write block [26869760] at [0x019A0000] and you compare with erased blocks, you will see there is 35 free blocks left after the corresponding erased block [26869760] at [0x019A0000] and the last possible block, which is A LOT of free blocks. SO its NOT what you think.
You last block is block 31457280 so between last written block 26869760 and last erased block 31457280 if you count them its exactly 35 blocks.
I keep an eye on this, newer firmware is using 4 blocks more than dd-wrt firmware from 10/03/2022 which last written block was block [26345472] at [0x01920000], it has mDNS a new feature related to samba and lots of new components that have been upgraded to their latest versions to mention a few.
35 free blocks though is still a great deal of buffer until you really cant fit anything.
Also note that this is around total 30MB for dd-wrt out of 128MB total flash, the rest was partitioned off to accommodate JFFS.
Joined: 08 May 2018 Posts: 14207 Location: Texas, USA
Posted: Tue May 24, 2022 15:22 Post subject: Re: Latest builds of ddwrt fail on Netgear r6300 v1
the-joker wrote:
2) When upgrading firmware via interface; On the Firmware Upgrade tab under After flashing, reset to you select from dropdown -> Reset to default settings, select the upgrade firmware file below and click upgrade.
This method usually results in a soft brick (still) and can cause other issues and is still not recommended by anyone but you. Let the thing reboot and either use Administration -> Factory Defaults or nvram erase && reboot or push the reset button after it's booted up for ~10 seconds. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Tue May 24, 2022 15:44 Post subject:
Marked as not recommended, I dont keep up with all the bugs off the top of my head.
to OP
Dont use method 2 its buggy
Edit: after speaking to BS about this soft brick issue on this menu he said
brainslayer wrote:
and no its not soft bricked if you reset to factory. its just reset to factory
so all is reset back to zero. on some devices the device will reboot 2 - 3 times if reset to defaults.
it doesnt soft brick. just clears all settings
so ip changes. wifi is default and of course some people loosing connection then cause of this
Brainslayer is clearly looking out for it, could be a bug slipped into some legacy Broadcom devices in recent builds, which have had quite a few changes to their code.
So bare with the slayer, if it caught his eye and he has your device to test and reproduce he will deal with it.
Quote:
But all troublesome builds did not. This is why I thought maybe its not fitting into flash:
No, I already said no and I know this for sure.
You can confirm this too, when you flash via CLI, look at the erased blocks and corresponding addresses.
Then compare with the written blocks and corresponding addresses.
if the last written block is write block [26869760] at [0x019A0000] and you compare with erased blocks, you will see there is 35 free blocks left after the corresponding erased block [26869760] at [0x019A0000] and the last possible block, which is A LOT of free blocks. SO its NOT what you think.
You last block is block 31457280 so between last written block 26869760 and last erased block 31457280 if you count them its exactly 35 blocks.
I keep an eye on this, newer firmware is using 4 blocks more than dd-wrt firmware from 10/03/2022 which last written block was block [26345472] at [0x01920000], it has mDNS a new feature related to samba and lots of new components that have been upgraded to their latest versions to mention a few.
35 free blocks though is still a great deal of buffer until you really cant fit anything.
Also note that this is around total 30MB for dd-wrt out of 128MB total flash, the rest was partitioned off to accommodate JFFS.
If shit came to shove and suddenly DD-WRT had that many newer features that needed more than 30MB flash, JFFS partition could be shrunk to offset the difference.
I get what you are saying, but I would expect return 0 regardless of what version of ddwrt is flashed. The fact that it instead gets Terminated on troublesome builds tells me flash is not completed successfully with those builds. Or at least that there is something wrong.
Joined: 08 May 2018 Posts: 14207 Location: Texas, USA
Posted: Tue May 24, 2022 17:02 Post subject:
the-joker wrote:
Edit: after speaking to BS about this soft brick issue on this menu he said
brainslayer wrote:
and no its not soft bricked if you reset to factory. its just reset to factory
so all is reset back to zero. on some devices the device will reboot 2 - 3 times if reset to defaults
So IDK, clear as mud.
I'd love to know the timing of it and on which devices because I've let one sit for an hour and it did not reboot 2-3 times; One got stuck in a boot loop that I had to get myself out of - that was pre-bootfail option functionality. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Tue May 24, 2022 17:11 Post subject:
Duxa wrote:
I get what you are saying, but I would expect return 0 regardless of what version of ddwrt is flashed. The fact that it instead gets Terminated on troublesome builds tells me flash is not completed successfully with those builds. Or at least that there is something wrong.
I cant discount some build being borked, but without actual serial output or output of said flash via cli then it nothing can be done.
You can flash via cli a bad build, grab output, then flash a good build (same as whatever is working) straight after without rebooting,then grab the good flash output and attach as text files to the reply.
Only by rebooting after a flash it tries to apply what was flashed, so really while in cli you can flash one after the other and collect outputs.
We need evidence, cause BS isnt gonna be trying all the builds.
Joined: 01 Dec 2021 Posts: 289 Location: Maryland, United States
Posted: Tue May 24, 2022 21:15 Post subject:
I have the R6300v1, and I am running the latest build without any problems. When I have GUI issues and can no longer use the GUI the 30/30/30 reset works for me.
Need to step forward one build at a time until it breaks so we know where to look.
I already mentioned that it breaks after build
dd-wrt.v24-48322_NEWD-2_K3.x_giga-R6300
Quote:
I have the R6300v1, and I am running the latest build without any problems. When I have GUI issues and can no longer use the GUI the 30/30/30 reset works for me.
Do you have serial access to see if you have those errors? Strange that you arent seeing the problem.
so they are slightly larger, but if size matters then Paul_go wouldnt be able to run them either.
I dont think its size related, your log and the wiki states this is a 128MB flash, in dd-wrt's case you have 30MB flash for the firmware (linux partition), which means the current builds should fit with plenty blocks to spare (35 free blocks to be precise, I counted)
I would ask you to shunt in the CHK file via TFTP as if you are recovering the router and then once it has completed and you can access a telnet or ssh run nvram erase && reboot.
Joined: 01 Dec 2021 Posts: 289 Location: Maryland, United States
Posted: Thu May 26, 2022 14:15 Post subject:
kernel-panic69 wrote:
@Duxa: Sorry, didn't see the info about 48322.
@PaulGo: 30/30/30 on Broadcom ARM is asking for trouble, especially on a Netgear. I refuse to address the webUI "issue" any longer.
My reply was moved to another thread:
PostPosted: Tue May 24, 2022 20:35
I believe the R6300v2 is ARM. I have the R6300V1 which is MIPS so 30-30-30 is permissible. I do not have the USB port enabled.
I found when I bricked my R6300 using Telnet, I loaded the original Netgear firmware and then did another 30/30/30 reset. From the Netgear firmware, I was then able to load the DD-WRT firmware.
