Joined: 16 Aug 2021 Posts: 81 Location: Oxford, UK.
Posted: Mon Aug 16, 2021 11:41 Post subject: WNDR4500v2 initial flash - Kernel panic unknown-block(31,5)
Hi, firstly a big thank you to the developers @ dd-wrt for their work. I have a Netgear WNDR4500v2 and have been using dd-wrt firmware for little over 2 weeks with only one regret; that I didn’t use it sooner!
After setting up & testing the firmware on my WNDR4500v2, I convinced my mother to move from stock to dd-wrt firmware on her identical router too. However, after following the procedure instructed on the dd-wrt website (as I did with mine) I ran into problems.
I have since connected a serial cable and reverted back to last Netgear stock firmware release. Although the stock firmware appears to work, I did notice a error flag on the console output.
I have tried several times to upgrade to dd-wrt firmware (as instructed) without success. I believe there may be corrupted block somewhere on the hardware.
This is the console output from uploading the initial dd-wrt firmware from Netgear stock:
CFE for WNDR4500 version: v1.0.4
Build Date: Mon Jan 14 16:04:19 CST 2013
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 C4-04-15-05-22-8B, 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: ....... 3871412 bytes read
Entry at 0x80001000
Closing network.
Starting program at 0x80001000
Linux version 3.10.67 (root@dd-wrt.buildserver) (gcc version 4.7.3 20121106 (prerelease)
(Linaro GCC 4.7-2012.11) ) #6269 Wed Feb 4 06:34:18 CET 2015
CPU revision is: 00019749 (MIPS 74Kc)
Found an ST compatible serial flash with 32 64KB blocks; total size 2MB
found nvram at 1F0000
something wrong here. do not remap
Determined physical RAM map:
memory: 07fff000 @ 00000000 (usable)
Zone ranges:
Normal [mem 0x00000000-0x07ffefff]
HighMem empty
Movable zone start for each node
Early memory node ranges
node 0: [mem 0x00000000-0x07ffefff]
Primary instruction cache 32kB, 4-way, VIPT, I-cache aliases, linesize 32 bytes.
Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32511
Kernel command line: console=ttyS0,115200 root=1f05 rootfstype=squashfs noinitrd init=/bin/sh
PID hash table entries: 512 (order: -1, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Writing ErrCtl register=80000ec0
Readback ErrCtl register=80000ec0
Cache parity protection enabled
Memory: 125336k/131068k available (3022k kernel code, 5732k reserved, 489k data, 324k init, 0k highmem)
NR_IRQS:128
CPU: BCM5300 rev 1 at 600 MHz
bcm947xx_clockevent_set_mode: 1
bcm947xx_clockevent_set_mode: 3
console [ttyS0] enabled
Calibrating delay loop... 299.82 BogoMIPS (lpj=1499136)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
NET: Registered protocol family 16
bio: create slab <bio-0> at 0
PCI: Initializing host
PCI: Reset RC
PCI: Initializing host
PCI: Reset RC
PCI: scanning bus 0
PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [io 0x0000-0xffff]
pci_bus 0000:00: root bus resource [mem 0x00000000-0xffffffff]
pci_bus 0000:00: root bus resource [bus 00-ff]
PCI: Fixing up bus 0
pci 0000:00:05.0: bridge configuration invalid ([bus 00-00]), reconfiguring
pci 0000:00:06.0: bridge configuration invalid ([bus 00-00]), reconfiguring
PCI/PCIe coreunit 0 is set to bus 1.
PCI: Fixing up bridge
cmd 6 new_cmd 6
PCI: Fixing up bridge
cmd 6 new_cmd 4
PCI: Enabling device 0000:01:00.1 (0004 -> 0006)
PCI: Fixing up bus 1
PCI/PCIe coreunit 1 is set to bus 2.
PCI: Fixing up bridge
cmd 6 new_cmd 6
PCI: Fixing up bridge
cmd 6 new_cmd 4
PCI: Enabling device 0000:02:00.1 (0004 -> 0006)
PCI: Fixing up bus 2
Switching to clocksource MIPS
NET: Registered protocol family 2
TCP established hash table entries: 1024 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 1024 bind 1024)
TCP: reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
R6300 GPIO Init
squashfs: version 3.0 (2006/03/15) Phillip Lougher
msgmni has been set to 244
io scheduler noop registered (default)
HDLC line discipline maxframe=4096
N_HDLC line discipline registered.
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250: ttyS0 at MMIO 0x0 (irq = is a U6_16550A
serial8250: ttyS1 at MMIO 0x0 (irq = is a U6_16550A
brd: module loaded
pflash: found no supported devices
found WNDR4500 / R6300
try to find cfe size up to 2097152
no filesys. assume nflash devices
bootloader size: 2097152
nvram size: 65536
Creating 2 MTD partitions on "bcmsflash":
0x000000000000-0x000000200000 : "cfe"
0x0000001f0000-0x000000200000 : "nvram"
Found a Samsung NAND flash with 2048B pages or 128KB blocks; total size 128MB
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit), 128MiB, page size: 2048, OOB size: 64
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01
nand_read_bbt: bad block at 0x000000060000
nand_read_bbt: bad block at 0x000004c40000
nand_read_bbt: bad block at 0x0000055a0000
Creating 2 MTD partitions on "brcmnand":
0x000000000000-0x000002000000 : "linux"
0x000002000000-0x000007f00000 : "ddwrt"
lookup_nflash_rootfs_offset: offset = 0x0
found trx at 0, len =23322624
scan filesys at 169000
Creating 2 MTD partitions on "nflash":
0x000000000000-0x000002000000 : "nandimage"
0x000002000000-0x000008000000 : "rootfs"
mtd: partition "rootfs" set to be root filesystem
add netgear boarddata for pflash if exists
add netgear boarddata for sflash if exists
Creating 1 MTD partitions on "bcmsflash":
0x0000001e0000-0x0000001f0000 : "board_data"
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
PPP generic driver version 2.4.2
PPP BSD Compression module registered
PPP Deflate Compression module registered
PPP MPPE Compression module registered
NET: Registered protocol family 24
Broadcom Watchdog Timer: 0.07 initialized.
GACT probability NOT on
Mirror/redirect action on
Failed to load ipt action
Simple TC action Loaded
netem: version 1.3
u32 classifier
Performance counters on
input device check on
Actions configured
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (1958 buckets, 7832 max)
nf_conntrack_rtsp v0.6.21 loading
xt_time: kernel timezone is -0000
ip_set: protocol 6
gre: GRE over IPv4 demultiplexor driver
nf_nat_rtsp v0.6.21 loading
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP: bic registered
TCP: cubic registered
TCP: westwood registered
TCP: highspeed registered
TCP: hybla registered
TCP: htcp registered
TCP: vegas registered
TCP: veno registered
TCP: scalable registered
TCP: lp registered
TCP: yeah registered
TCP: illinois registered
NET: Registered protocol family 17
Bridge firewalling registered
8021q: 802.1Q VLAN Support v1.8
startup nvram driver
found nvram
List of all partitions:
1f00 2048 mtdblock0 (driver?)
1f01 64 mtdblock1 (driver?)
1f02 32768 mtdblock2 (driver?)
1f03 97280 mtdblock3 (driver?)
1f04 32768 mtdblock4 (driver?)
1f05 98304 mtdblock5 (driver?)
1f06 64 mtdblock6 (driver?)
No filesystem could mount root, tried: squashfs
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,5)
Rebooting in 3 seconds..Please stand by while rebooting the system...
Decompressing...done
CFE for WNDR4500 version: v1.0.4
Build Date: Mon Jan 14 16:04:19 CST 2013
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 C4-04-15-05-22-8B, 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: ....... 3871412 bytes read
Entry at 0x80001000
Closing network.
Starting program at 0x80001000
Linux version 3.10.67 (root@dd-wrt.buildserver) (gcc version 4.7.3 20121106 (prerelease) (Linaro GCC 4.7-2012.11) ) #6269 Wed Feb 4 06:34:18 CET 2015
CPU revision is: 00019749 (MIPS 74Kc)
Found an ST compatible serial flash with 32 64KB blocks; total size 2MB
found nvram at 1F0000
something wrong here. do not remap
Determined physical RAM map:
memory: 07fff000 @ 00000000 (usable)
Zone ranges:
Normal [mem 0x00000000-0x07ffefff]
HighMem empty
Movable zone start for each node
Early memory node ranges
node 0: [mem 0x00000000-0x07ffefff]
Primary instruction cache 32kB, 4-way, VIPT, I-cache aliases, linesize 32 bytes.
Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32511
Kernel command line: console=ttyS0,115200 root=1f05 rootfstype=squashfs noinitrd init=/bin/sh
PID hash table entries: 512 (order: -1, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Writing ErrCtl register=80000ec0
Readback ErrCtl register=80000ec0
Cache parity protection enabled
Memory: 125336k/131068k available (3022k kernel code, 5732k reserved, 489k data, 324k init, 0k highmem)
NR_IRQS:128
CPU: BCM5300 rev 1 at 600 MHz
bcm947xx_clockevent_set_mode: 1
bcm947xx_clockevent_set_mode: 3
console [ttyS0] enabled
Calibrating delay loop... 299.82 BogoMIPS (lpj=1499136)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
NET: Registered protocol family 16
bio: create slab <bio-0> at 0
PCI: Initializing host
PCI: Reset RC
PCI: Initializing host
PCI: Reset RC
PCI: scanning bus 0
PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [io 0x0000-0xffff]
pci_bus 0000:00: root bus resource [mem 0x00000000-0xffffffff]
pci_bus 0000:00: root bus resource [bus 00-ff]
PCI: Fixing up bus 0
pci 0000:00:05.0: bridge configuration invalid ([bus 00-00]), reconfiguring
pci 0000:00:06.0: bridge configuration invalid ([bus 00-00]), reconfiguring
PCI/PCIe coreunit 0 is set to bus 1.
PCI: Fixing up bridge
cmd 6 new_cmd 6
PCI: Fixing up bridge
cmd 6 new_cmd 4
PCI: Enabling device 0000:01:00.1 (0004 -> 0006)
PCI: Fixing up bus 1
PCI/PCIe coreunit 1 is set to bus 2.
PCI: Fixing up bridge
cmd 6 new_cmd 6
PCI: Fixing up bridge
cmd 6 new_cmd 4
PCI: Enabling device 0000:02:00.1 (0004 -> 0006)
PCI: Fixing up bus 2
Switching to clocksource MIPS
NET: Registered protocol family 2
TCP established hash table entries: 1024 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 1024 bind 1024)
TCP: reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
R6300 GPIO Init
squashfs: version 3.0 (2006/03/15) Phillip Lougher
msgmni has been set to 244
io scheduler noop registered (default)
HDLC line discipline maxframe=4096
N_HDLC line discipline registered.
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250: ttyS0 at MMIO 0x0 (irq = is a U6_16550A
serial8250: ttyS1 at MMIO 0x0 (irq = is a U6_16550A
brd: module loaded
pflash: found no supported devices
found WNDR4500 / R6300
try to find cfe size up to 2097152
no filesys. assume nflash devices
bootloader size: 2097152
nvram size: 65536
Creating 2 MTD partitions on "bcmsflash":
0x000000000000-0x000000200000 : "cfe"
0x0000001f0000-0x000000200000 : "nvram"
Found a Samsung NAND flash with 2048B pages or 128KB blocks; total size 128MB
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit), 128MiB, page size: 2048, OOB size: 64
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01
nand_read_bbt: bad block at 0x000000060000
nand_read_bbt: bad block at 0x000004c40000
nand_read_bbt: bad block at 0x0000055a0000
Creating 2 MTD partitions on "brcmnand":
0x000000000000-0x000002000000 : "linux"
0x000002000000-0x000007f00000 : "ddwrt"
lookup_nflash_rootfs_offset: offset = 0x0
found trx at 0, len =23322624
scan filesys at 169000
Creating 2 MTD partitions on "nflash":
0x000000000000-0x000002000000 : "nandimage"
0x000002000000-0x000008000000 : "rootfs"
mtd: partition "rootfs" set to be root filesystem
add netgear boarddata for pflash if exists
add netgear boarddata for sflash if exists
Creating 1 MTD partitions on "bcmsflash":
0x0000001e0000-0x0000001f0000 : "board_data"
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
PPP generic driver version 2.4.2
PPP BSD Compression module registered
PPP Deflate Compression module registered
PPP MPPE Compression module registered
NET: Registered protocol family 24
Broadcom Watchdog Timer: 0.07 initialized.
GACT probability NOT on
Mirror/redirect action on
Failed to load ipt action
Simple TC action Loaded
netem: version 1.3
u32 classifier
Performance counters on
input device check on
Actions configured
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (1958 buckets, 7832 max)
nf_conntrack_rtsp v0.6.21 loading
xt_time: kernel timezone is -0000
ip_set: protocol 6
gre: GRE over IPv4 demultiplexor driver
nf_nat_rtsp v0.6.21 loading
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP: bic registered
TCP: cubic registered
TCP: westwood registered
TCP: highspeed registered
TCP: hybla registered
TCP: htcp registered
TCP: vegas registered
TCP: veno registered
TCP: scalable registered
TCP: lp registered
TCP: yeah registered
TCP: illinois registered
NET: Registered protocol family 17
Bridge firewalling registered
8021q: 802.1Q VLAN Support v1.8
startup nvram driver
found nvram
List of all partitions:
1f00 2048 mtdblock0 (driver?)
1f01 64 mtdblock1 (driver?)
1f02 32768 mtdblock2 (driver?)
1f03 97280 mtdblock3 (driver?)
1f04 32768 mtdblock4 (driver?)
1f05 98304 mtdblock5 (driver?)
1f06 64 mtdblock6 (driver?)
No filesystem could mount root, tried: squashfs
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,5)
Rebooting in 3 seconds..Please stand by while rebooting the system...
Decompressing...done
Is there a way to fix or workaround this? I am a linux noob, but I can follow instruction very well! Any help or insight would be very much appreciated.
Joined: 08 May 2018 Posts: 14246 Location: Texas, USA
Posted: Mon Aug 16, 2021 13:13 Post subject:
We have not one clue what version of DD-WRT you tried flashing, or what current build you are on, etc. Please refer to the forum rules and guidelines about providing ALL applicable information when you post asking for help. Thank you. _________________ "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: 16 Aug 2021 Posts: 81 Location: Oxford, UK.
Posted: Mon Aug 16, 2021 14:34 Post subject:
kernel-panic69 wrote:
We have not one clue what version of DD-WRT you tried flashing, or what current build you are on, etc. Please refer to the forum rules and guidelines about providing ALL applicable information when you post asking for help. Thank you.
But, just to clarify for you: I have used Netgear's UI to upload dd-wrt.v24-26138_NEWD-2_K3.x_mega-WNDR4500V2.chk as instructed (and which worked fine for the first device).
I am currently trying to learn how to verify the integrity of the hardware via busybox and serial connection. But search results are overwhelming me with non-related results.
Joined: 08 May 2018 Posts: 14246 Location: Texas, USA
Posted: Mon Aug 16, 2021 15:01 Post subject:
Looking at supported devices wiki, the v1 and v2 reference builds not published; The device wiki immediately pushes you to a build from 2015 which is larger than the 21676 build and likely larger than the original images that are attached somewhere in the device thread. While I spend time that I should be doing other things finding the original test .chk files, try using 21676 as your initial flash:
After sifting through the entire 96-page device thread, I believe 21676 is likely the best choice for initial flash, then
perhaps upgrade to the one in the wiki and then move forward from there to a current releae. What a wiki edit debacle
for whatever f*cking reason. The only thing I can think of is upgrading from 21676 may be problematic (from other
posts), but you can either use CLI upgrade or an old version of Firefox Portable to see if it is a weird glitch. FFS, that
f*cking hurt. What a waste of time and resources. _________________ "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: 16 Aug 2021 Posts: 81 Location: Oxford, UK.
Posted: Mon Aug 16, 2021 16:40 Post subject:
kernel-panic69 wrote:
Looking at supported devices wiki, the v1 and v2 reference builds not published; The device wiki immediately pushes you to a build from 2015 which is larger than the 21676 build and likely larger than the original images that are attached somewhere in the device thread. While I spend time that I should be doing other things finding the original test .chk files, try using 21676 as your initial flash:
I will take at look at these other options. But just so that you are aware... My mother & I have exactly the same model of router. I had no issues upgrading mine to DD-WRT, which is why I have suggested my mother follow suit.
Again, I'm a Linux noob. Maybe if anyone knows of any commands I can use to verify the integrity of the hardware, maybe this will be more helpful to everyone lol.
Joined: 08 May 2018 Posts: 14246 Location: Texas, USA
Posted: Mon Aug 16, 2021 16:49 Post subject:
Please ensure that they are both v2. That would be the only other factor, is if one is a v1 and the other is a v2. Update us on what you find, I have other tasks I should be focusing on. _________________ "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: 16 Aug 2021 Posts: 81 Location: Oxford, UK.
Posted: Mon Aug 16, 2021 16:56 Post subject:
kernel-panic69 wrote:
Please ensure that they are both v2. That would be the only other factor, is if one is a v1 and the other is a v2. Update us on what you find, I have other tasks I should be focusing on.
I understand. And again, I thank you greatly.
Both are indeed v2.
Look, there is no immediate need to resolve this issue. And although one never has enough time, and if no one else has jumped in on the thread to help, maybe you can come back to offer your support when you are less busy KP?
If I manage to pinpoint the problem, or find a resolution (besides using NG stock firmware) then I post to say so.
Joined: 16 Aug 2021 Posts: 81 Location: Oxford, UK.
Posted: Mon Aug 16, 2021 20:47 Post subject:
I have just stumbled upon this old thread: https://forum.dd-wrt.com/phpBB2/viewtopic.php?p=1092856
The fact that it appears to have been unresolved suggests that OEM is the only way forward
I have PM'd the author for any information. But I won't hold my breath.
Thanks anyway. You guys are by no means any less awesome!
Joined: 08 May 2018 Posts: 14246 Location: Texas, USA
Posted: Tue Aug 17, 2021 1:34 Post subject:
That post was likely during firmware image size issues or some other problem. There are several factors at play that could be causing issues. This is why I linked specific builds and such. You could likely try the ones I linked earlier, esp. the Kong PTB. That may get it going and then you should be able to upgrade via webUI or ssh / telnet to a more recent build. But if you wish to throw in the towel, by all means. _________________ "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: 16 Aug 2021 Posts: 81 Location: Oxford, UK.
Posted: Tue Aug 17, 2021 7:34 Post subject:
kernel-panic69 wrote:
That post was likely during firmware image size issues or some other problem. There are several factors at play that could be causing issues. This is why I linked specific builds and such. You could likely try the ones I linked earlier, esp. the Kong PTB. That may get it going and then you should be able to upgrade via webUI or ssh / telnet to a more recent build. But if you wish to throw in the towel, by all means.
I don't want to quit this endeavour without knowing for sure that it is indeed futile.
But because I had absolutely no issues following the guide to success on my router, I can't help but 'feel' that my mother's identical router is somehow faulty.
I also hate to rely on a 'feeling' when I'm sure there must be a puTTY, Busybox/linux tool to check storage & memory integrity, which eludes me.
I have tried the Kong .chk as suggested, but 'Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,5)' repeats and reboots the device still.
This is an old device, one which I know dd-wrt will load on in optimum conditions. And unless Devs can include hardware integrity checks & balances before loading firmware, I don't want to waste their time on this. Especially as I will be looking to switch out my new AX firmware to dd-wrt when it reaches it's EOL! lol.
My mother is refusing to spend the amount of money that I have on a new router, so a resolution would be more preferable than using the ISP router. If you have any more suggestions, I will gladly investigate KP.
Joined: 16 Aug 2021 Posts: 81 Location: Oxford, UK.
Posted: Tue Aug 17, 2021 8:28 Post subject:
egc wrote:
The bad blocks could be the problem.
So as @KP69 suggest try with an older smaller build or try with buildnumber 44809 or later that has some form of bad block handling
I haven't tried the later builds because I assumed they were too big for the initial flash. But you think this might work (by Netgear UI or serial tftp upload)?
Joined: 16 Aug 2021 Posts: 81 Location: Oxford, UK.
Posted: Tue Aug 17, 2021 10:03 Post subject:
egc wrote:
It is worth a try.
I jumped straight in using dd-wrt.v24-47146_NEWD-2_K3.x_giga-WNDR4500V2.chk via NG UI. And it's back to brick status.
I'm wondering if 'flash -offset' might be of any use. But I'm not confidant using this switch without guidance.
Also, isn't 'mtd ioctl MEMERASE error' more likely the root problem than 'Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,5)'. And if so, then no matter what I do there will be errors of some description, right?
I have tried the 30/30/30, 'cfe>nvram erase', 'cfe>nvram reset', 'cfe>nvram clear' and 'cfe>nvram bollox', all returned status=0 lol
is a U6_16550A
