broadcom-k26 builds >43136 is bricking Linksys E* series

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware
Author Message
Simba7
DD-WRT User


Joined: 09 Oct 2007
Posts: 51

PostPosted: Sun Jun 21, 2020 1:11    Post subject: broadcom-k26 builds >43136 is bricking Linksys E* series Reply with quote
I've noticed this with a stack of E1200v2's, E1500's, and E1550's lately. I'm wondering if broadcom-k26 series is broken for these specific devices. I then tried them on broadcom-k3x and they work great, even with the most recent build. The E1200v1 wasn't so lucky (4MB of flash) and had to go back to 43136.

EDIT: The only way I could reflash them is through serial console and entering "flash -ctheader : flash1.trx" and tftp upload.

Code:
Image 1 is OK
Try to load image 1.
Waiting for 3 seconds to upgrade ...
CMD: [load -raw -addr=0x807b0a10 -max=0x184f5f0 :]
Loader:raw Filesys:tftp Dev:eth0 File:: Options:(null)
Loading: _tftpd_open(): retries=0/3
_tftpd_open(): retries=1/3
_tftpd_open(): retries=2/3

### Start=424234975 E=750309668 Delta=326074693 ###
Failed.
Could not load :: Timeout occured
CMD: [boot -raw -z -addr=0x80001000 -max=0x6ff000 flash0.os:]
Loader:raw Filesys:raw Dev:flash0.os File: Options:(null)
Loading: .. 3916 bytes read

### Start=753388859 E=754028040 Delta=639181 ###
Entry at 0x80001000
Closing network.
Starting program at 0x80001000
Linux version 2.6.24.111 (root@linux) (gcc version 4.1.2) #15653 Wed Jun 17 07:08:53 +04 2020
CPU revision is: 00019749
Found a 8MB ST compatible serial flash
Determined physical RAM map:
 memory: 02000000 @ 00000000 (usable)
Zone PFN ranges:
  Normal          0 ->     8192
  HighMem      8192 ->     8192
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
    0:        0 ->     8192
Built 1 zonelists in Zone order.  Total pages: 8192
Kernel command line: console=ttyS0,115200 root=1f02 rootfstype=squashfs noinitrd
Primary instruction cache 32kB, physically tagged, 4-way, linesize 32 bytes.
Primary data cache 32kB, 4-way, linesize 32 bytes.
Synthesized TLB refill handler (20 instructions).
Synthesized TLB load handler fastpath (32 instructions).
Synthesized TLB store handler fastpath (32 instructions).
Synthesized TLB modify handler fastpath (31 instructions).
PID hash table entries: 256 (order: 8, 1024 bytes)
CPU: BCM5357 rev 2 at 300 MHz
Using 150.000 MHz high precision timer.
console [ttyS0] enabled
Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Memory: 25924k/32768k available (3486k kernel code, 6828k reserved, 1374k data, 220k init, 0k highmem)
Mount-cache hash table entries: 512
NET: Registered protocol family 16
Generic PHY: Registered new driver
PCI: no core
PCI: no core
PCI: Fixing up bus 0
NET: Registered protocol family 2
Time: MIPS clocksource has been installed.
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
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
devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
squashfs: version 3.0 (2006/03/15) Phillip Lougher
io scheduler noop registered
io scheduler deadline registered (default)
HDLC line discipline: version $Revision: 4.8 $, maxframe=4096
N_HDLC line discipline registered.
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250: ttyS0 at MMIO 0x0 (irq = 8) is a 16550A
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
PPP BSD Compression module registered
MPPE/MPPC encryption/compression module registered
NET: Registered protocol family 24
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
et_module_init: passivemode set to 0x0
eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 5.100.138.9
pflash: found no supported devices
bootloader size: 262144
nvram size: 65536
sflash: Filesystem type: squashfs, size=0x61c2cf
partition size = 6433792
Creating 5 MTD partitions on "sflash":
0x00000000-0x00040000 : "cfe"
0x00040000-0x007f0000 : "linux"
0x0019d400-0x007c0000 : "rootfs"
mtd: partition "rootfs" doesn't start on an erase block boundary -- force read-only
0x007f0000-0x00800000 : "nvram"
0x007c0000-0x007f0000 : "ddwrt"
Broadcom Watchdog Timer: 0.07 initialized.
u32 classifier
    Performance counters on
    Actions configured
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (1024 buckets, 4096 max)
ctnetlink v0.93: registering with nfnetlink.
IPv4 over IPv4 tunneling driver
GRE over IPv4 tunneling driver
ip_tables: (C) 2000-2006 Netfilter Core Team
ClusterIP Version 0.8 loaded successfully
TCP bic registered
TCP cubic registered
TCP westwood registered
TCP highspeed registered
TCP hybla registered
TCP htcp registered
TCP vegas registered
TCP scalable registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Welcome to PF_RING 3.2.1
(C) 2004-06 L.Deri <deri@ntop.org>
NET: Registered protocol family 27
PF_RING: bucket length    128 bytes
PF_RING: ring slots       4096
PF_RING: sample rate      1 [1=no sampling]
PF_RING: capture TX       No [RX only]
PF_RING: transparent mode Yes
PF_RING initialized correctly.
PF_RING: registered /proc/net/pf_ring/
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
decode 1f02
SQUASHFS error: Failed to allocate read_data block
List of all partitions:
1f00        256 mtdblock0 (driver?)
1f01       7872 mtdblock1 (driver?)
1f02       6283 mtdblock2 (driver?)
1f03         64 mtdblock3 (driver?)
1f04        192 mtdblock4 (driver?)
No filesystem could mount root, tried:  squashfs
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2)
Sponsor
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 7246
Location: Texas, USA

PostPosted: Sun Jun 21, 2020 2:14    Post subject: Reply with quote
I presume you are flashing the generic mini k2.6 nv64k build on your 4MB flash devices. Trailed build should only be used for initial flash. Thanks for the report!
_________________
Official Forum Rules, Guidelines, and Helpful InformationFirmware FAQInstallation WikiWhere Do I Download Firmware?
DON'T use Chromium-based browsersRTFM/STFW - TL;DR is NOT an excuse. • Why Should I Care What Color the Bikeshed Is?
Please DO NOT PM me with questions; Ask in the forum.

---------------------------------------------------------

Linux User #377467 counter.li.org / linuxcounter.net
Simba7
DD-WRT User


Joined: 09 Oct 2007
Posts: 51

PostPosted: Sun Jun 21, 2020 3:48    Post subject: Reply with quote
kernel-panic69 wrote:
I presume you are flashing the generic mini k2.6 nv64k build on your 4MB flash devices. Trailed build should only be used for initial flash. Thanks for the report!

Actually, no. This was doing an upgrade on an existing device already running dd-wrt. It was running a rather old build from 2018 and went to upgrade it. This was the result.

I tried flashing through upgrade, along with going straight through the CFE using a trailed build. Same result. I ended up switching them to the K3x build, except for the lone E1200v1.
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 7246
Location: Texas, USA

PostPosted: Sun Jun 21, 2020 4:44    Post subject: Reply with quote
The E1200v1 is the one I was referring to as far as mini nv64k upgrades (ref: E1200 Wiki). After initial flash, you need to be on at least 40723 for all the shell-related patches (ref: #6373)

Also:
jwh7 wrote:
All I can say is not to use any build older than 41664, to have SFE NAT (for k3.2+ builds), KRACK (k24+), PBR+SFE, CAKE / FQ_CODEL_FAST, and GTK Rekey wireless timer fixes. For Wireguard, one should use at least 42872.


There may be some builds in bewteen the wiki inital flash and present that may not play nice as far as webflash upgrade, tftp, or serial, as you've found out.

I have forwarded the report to the developer, but not sure how quickly this will get resolved. Again, thank you for reporting!

_________________
Official Forum Rules, Guidelines, and Helpful InformationFirmware FAQInstallation WikiWhere Do I Download Firmware?
DON'T use Chromium-based browsersRTFM/STFW - TL;DR is NOT an excuse. • Why Should I Care What Color the Bikeshed Is?
Please DO NOT PM me with questions; Ask in the forum.

---------------------------------------------------------

Linux User #377467 counter.li.org / linuxcounter.net
Display posts from previous:    Page 1 of 1
Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum