Increasing mamba and venom kernel partition to 6MB

Compiled 5.4.x with the bot default config.seed

3212994 Feb  8 15:15 linksys_wrt1900ac-v1-kernel.bin

as it is smaller than the above 5.10.x I did not bother flashing. I tried the same with 5.10.x but it fails to compile. Issues above and beyond what I have run into with my personal config.seed on 5.10.x. So 5.10.x has a way to go yet. Using the above numbers from 5.4.x, I would guesstimate ~3.4+M on a bot build of a 5.10.x for mamba. Some room to breathe at any rate.

I took a look back to see if there was any indication in the git log as to the rational behind the decisions made regarding the kernel size numbers of the two targets of interest, did not find much; @lantis1008, do you have any insight on this.

@ghoffman , I don't think the uboot source(s) have ever been released for the wrtpac targets, at least I have never come across them in my travels. People are just pushing a BLOB of unknown origin to their device. Unless they took the time to pull the BLOB from their own device, in which case they are pushing their own unknown origin BLOB, well...

1 Like

Right, I have compile and flashed the resized patch firmware for Venom (WRT32x), here is my kernel log

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 5.4.96 (emy@dcg.v1) (gcc version 8.4.0 (OpenWrt GCC 8.4.0 r15540+5-20a7c9d5c9)) #0 SMP Mon Feb 8 16:58:29 2021
[    0.000000] CPU: ARMv7 Processor [414fc091] revision 1 (ARMv7), cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] OF: fdt: Machine model: Linksys WRT32X
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] On node 0 totalpages: 131072
[    0.000000]   Normal zone: 1152 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 131072 pages, LIFO batch:31
[    0.000000] percpu: Embedded 11 pages/cpu s15564 r8192 d21300 u45056
[    0.000000] pcpu-alloc: s15564 r8192 d21300 u45056 alloc=11*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 129920
[    0.000000] Kernel command line: console=ttyS0,115200 root=/dev/mtdblock8
[    0.000000] Bootloader command line (ignored): console=ttyS0,115200 root=/dev/mtdblock8
[    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes, linear)
[    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes, linear)
[    0.000000] mem auto-init: stack:off, heap alloc:on, heap free:on
[    0.000000] mem auto-init: clearing system memory may take some time...
[    0.000000] Memory: 508384K/524288K available (7168K kernel code, 231K rwdata, 884K rodata, 1024K init, 234K bss, 15904K reserved, 0K cma-reserved, 0K highmem)
[    0.000000] random: get_random_u32 called from 0xc0238e38 with crng_init=0
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[    0.000000] rcu: Hierarchical RCU implementation.
[    0.000000] rcu: 	RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] L2C: DT/platform modifies aux control register: 0x06070000 -> 0x16070000
[    0.000000] L2C-310 enabling early BRESP for Cortex-A9
[    0.000000] L2C-310 full line of zeros enabled for Cortex-A9
[    0.000000] L2C-310 D prefetch enabled, offset 1 lines
[    0.000000] L2C-310 dynamic clock gating enabled, standby mode enabled
[    0.000000] L2C-310 Coherent cache controller enabled, 16 ways, 1024 kB
[    0.000000] L2C-310 Coherent: CACHE_ID 0x410054c9, AUX_CTRL 0x56070001
[    0.000000] Switching to timer-based delay loop, resolution 40ns
[    0.000002] sched_clock: 32 bits at 25MHz, resolution 40ns, wraps every 85899345900ns
[    0.000008] clocksource: armada_370_xp_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 76450417870 ns
[    0.000105] Calibrating delay loop (skipped), value calculated using timer frequency.. 50.00 BogoMIPS (lpj=250000)
[    0.000110] pid_max: default: 32768 minimum: 301
[    0.000246] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    0.000249] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    0.000595] CPU: Testing write buffer coherency: ok
[    0.000607] CPU0: Spectre v2: using BPIALL workaround
[    0.000703] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.000861] Setting up static identity map for 0x100000 - 0x100060
[    0.000923] mvebu-soc-id: MVEBU SoC ID=0x6820, Rev=0x4
[    0.000989] mvebu-pmsu: Initializing Power Management Service Unit
[    0.001036] rcu: Hierarchical SRCU implementation.
[    0.001138] smp: Bringing up secondary CPUs ...
[    0.001255] Booting CPU 1
[    0.001391] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.001393] CPU1: Spectre v2: using BPIALL workaround
[    0.001436] smp: Brought up 1 node, 2 CPUs
[    0.001439] SMP: Total of 2 processors activated (100.00 BogoMIPS).
[    0.001442] CPU: All CPU(s) started in SVC mode.
[    0.002868] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[    0.002912] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.002919] futex hash table entries: 512 (order: 3, 32768 bytes, linear)
[    0.003000] pinctrl core: initialized pinctrl subsystem
[    0.003339] NET: Registered protocol family 16
[    0.003795] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.004313] cpuidle: using governor ladder
[    0.004436] mvebu-pmsu: CPU hotplug support is currently broken on Armada 38x: disabling
[    0.004442] mvebu-pmsu: CPU idle is currently broken on Armada 38x: disabling
[    0.010816] cryptd: max_cpu_qlen set to 1000
[    0.011550] SCSI subsystem initialized
[    0.011701] libata version 3.00 loaded.
[    0.011785] usbcore: registered new interface driver usbfs
[    0.011810] usbcore: registered new interface driver hub
[    0.011828] usbcore: registered new device driver usb
[    0.012003] workqueue: max_active 576 requested for napi_workq is out of range, clamping between 1 and 512
[    0.012448] clocksource: Switched to clocksource armada_370_xp_clocksource
[    0.012712] thermal_sys: Registered thermal governor 'step_wise'
[    0.012836] NET: Registered protocol family 2
[    0.013145] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes, linear)
[    0.013163] TCP established hash table entries: 4096 (order: 2, 16384 bytes, linear)
[    0.013182] TCP bind hash table entries: 4096 (order: 3, 32768 bytes, linear)
[    0.013210] TCP: Hash tables configured (established 4096 bind 4096)
[    0.013238] UDP hash table entries: 256 (order: 1, 8192 bytes, linear)
[    0.013252] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes, linear)
[    0.013333] NET: Registered protocol family 1
[    0.013345] PCI: CLS 0 bytes, default 64
[    0.014334] workingset: timestamp_bits=14 max_order=17 bucket_order=3
[    0.017176] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.017182] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    0.018295] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)
[    0.019677] armada-38x-pinctrl f1018000.pinctrl: registered pinctrl driver
[    0.020574] mvebu-pcie soc:pcie: PCI host bridge to bus 0000:00
[    0.020582] pci_bus 0000:00: root bus resource [bus 00-ff]
[    0.020587] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xe7ffffff]
[    0.020591] pci_bus 0000:00: root bus resource [io  0x1000-0xeffff]
[    0.020658] pci 0000:00:01.0: [11ab:6820] type 01 class 0x060400
[    0.020672] pci 0000:00:01.0: reg 0x38: [mem 0x00000000-0x000007ff pref]
[    0.020781] pci 0000:00:02.0: [11ab:6820] type 01 class 0x060400
[    0.020791] pci 0000:00:02.0: reg 0x38: [mem 0x00000000-0x000007ff pref]
[    0.021451] PCI: bus0: Fast back to back transfers disabled
[    0.021456] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    0.021462] pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    0.021510] pci 0000:01:00.0: [11ab:2b40] type 00 class 0x020000
[    0.021534] pci 0000:01:00.0: reg 0x10: [mem 0x40000000-0x401fffff 64bit pref]
[    0.021544] pci 0000:01:00.0: reg 0x18: [mem 0x40200000-0x402fffff 64bit pref]
[    0.021609] pci 0000:01:00.0: supports D1 D2
[    0.021613] pci 0000:01:00.0: PME# supported from D0 D1 D3hot D3cold
[    0.022273] PCI: bus1: Fast back to back transfers disabled
[    0.022279] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[    0.022329] pci 0000:02:00.0: [11ab:2b40] type 00 class 0x020000
[    0.022357] pci 0000:02:00.0: reg 0x10: [mem 0x42000000-0x421fffff 64bit pref]
[    0.022369] pci 0000:02:00.0: reg 0x18: [mem 0x42200000-0x422fffff 64bit pref]
[    0.022468] pci 0000:02:00.0: supports D1 D2
[    0.022472] pci 0000:02:00.0: PME# supported from D0 D1 D3hot D3cold
[    0.022496] pci 0000:02:00.0: 2.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s x1 link at 0000:00:02.0 (capable of 4.000 Gb/s with 5 GT/s x1 link)
[    0.023229] PCI: bus2: Fast back to back transfers disabled
[    0.023243] pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02
[    0.023276] pci 0000:00:01.0: BAR 8: assigned [mem 0xe0000000-0xe02fffff]
[    0.023281] pci 0000:00:02.0: BAR 8: assigned [mem 0xe0400000-0xe06fffff]
[    0.023286] pci 0000:00:01.0: BAR 6: assigned [mem 0xe0300000-0xe03007ff pref]
[    0.023291] pci 0000:00:02.0: BAR 6: assigned [mem 0xe0700000-0xe07007ff pref]
[    0.023298] pci 0000:01:00.0: BAR 0: assigned [mem 0xe0000000-0xe01fffff 64bit pref]
[    0.023307] pci 0000:01:00.0: BAR 2: assigned [mem 0xe0200000-0xe02fffff 64bit pref]
[    0.023315] pci 0000:00:01.0: PCI bridge to [bus 01]
[    0.023320] pci 0000:00:01.0:   bridge window [mem 0xe0000000-0xe02fffff]
[    0.023326] pci 0000:02:00.0: BAR 0: assigned [mem 0xe0400000-0xe05fffff 64bit pref]
[    0.023336] pci 0000:02:00.0: BAR 2: assigned [mem 0xe0600000-0xe06fffff 64bit pref]
[    0.023344] pci 0000:00:02.0: PCI bridge to [bus 02]
[    0.023348] pci 0000:00:02.0:   bridge window [mem 0xe0400000-0xe06fffff]
[    0.023615] mv_xor f1060800.xor: Marvell shared XOR driver
[    0.083282] mv_xor f1060800.xor: Marvell XOR (Descriptor Mode): ( xor cpy intr )
[    0.083426] mv_xor f1060900.xor: Marvell shared XOR driver
[    0.143032] mv_xor f1060900.xor: Marvell XOR (Descriptor Mode): ( xor cpy intr )
[    0.143183] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
[    0.143807] printk: console [ttyS0] disabled
[    0.163884] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 22, base_baud = 12500000) is a 16550A
[    0.989354] printk: console [ttyS0] enabled
[    0.995037] loop: module loaded
[    0.998192] Loading iSCSI transport class v2.0-870.
[    1.003496] ahci-mvebu f10a8000.sata: f10a8000.sata supply ahci not found, using dummy regulator
[    1.012354] ahci-mvebu f10a8000.sata: f10a8000.sata supply phy not found, using dummy regulator
[    1.021117] ahci-mvebu f10a8000.sata: f10a8000.sata supply target not found, using dummy regulator
[    1.030177] ahci-mvebu f10a8000.sata: AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl platform mode
[    1.039267] ahci-mvebu f10a8000.sata: flags: 64bit ncq sntf led only pmp fbs pio slum part sxs 
[    1.048392] scsi host0: ahci-mvebu
[    1.051993] scsi host1: ahci-mvebu
[    1.055515] ata1: SATA max UDMA/133 mmio [mem 0xf10a8000-0xf10a9fff] port 0x100 irq 41
[    1.063471] ata2: SATA max UDMA/133 mmio [mem 0xf10a8000-0xf10a9fff] port 0x180 irq 41
[    1.071908] nand: device found, Manufacturer ID: 0xc2, Chip ID: 0xda
[    1.078297] nand: Macronix MX30LF2G18AC
[    1.082147] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[    1.090086] Bad block table found at page 131008, version 0x01
[    1.096569] Bad block table found at page 130944, version 0x01
[    1.102742] nand_read_bbt: bad block at 0x000008d80000
[    1.107901] nand_read_bbt: bad block at 0x00000d720000
[    1.113188] 10 fixed-partitions partitions found on MTD device pxa3xx_nand-0
[    1.120265] Creating 10 MTD partitions on "pxa3xx_nand-0":
[    1.125783] 0x000000000000-0x000000200000 : "u-boot"
[    1.131053] 0x000000200000-0x000000220000 : "u_env"
[    1.136218] 0x000000220000-0x000000260000 : "s_env"
[    1.141325] 0x000000260000-0x000000820000 : "unused_area"
[    1.146973] 0x0000007e0000-0x000000820000 : "devinfo"
[    1.152261] 0x000000900000-0x000008400000 : "kernel1"
[    1.157685] 0x000000f00000-0x000008400000 : "rootfs1"
[    1.163107] 0x000008400000-0x00000ff00000 : "kernel2"
[    1.168525] 0x000008a00000-0x00000ff00000 : "ubi"
[    1.173609] 0x00000ff00000-0x000010000000 : "BBT"
[    1.178827] libphy: Fixed MDIO Bus: probed
[    1.183161] orion-mdio f1072004.mdio: IRQ index 0 not found
[    1.188791] libphy: orion_mdio_bus: probed
[    1.193034] mv88e6085 f1072004.mdio-mii:00: switch 0x3520 detected: Marvell 88E6352, revision 1
[    1.357774] libphy: mv88e6xxx SMI: probed
[    1.363612] mvneta_bm f10c8000.bm: Buffer Manager for network controller enabled
[    1.372301] mvneta f1070000.ethernet eth0: Using hardware mac address 60:38:e0:ce:37:58
[    1.380424] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.386984] ehci-pci: EHCI PCI platform driver
[    1.391469] ehci-platform: EHCI generic platform driver
[    1.396779] ehci-orion: EHCI orion driver
[    1.400876] orion-ehci f1058000.usb: EHCI Host Controller
[    1.406311] orion-ehci f1058000.usb: new USB bus registered, assigned bus number 1
[    1.407873] ata2: SATA link down (SStatus 0 SControl 300)
[    1.413957] orion-ehci f1058000.usb: irq 38, io mem 0xf1058000
[    1.419363] ata1: SATA link down (SStatus 0 SControl 300)
[    1.452460] orion-ehci f1058000.usb: USB 2.0 started, EHCI 1.00
[    1.458648] hub 1-0:1.0: USB hub found
[    1.462484] hub 1-0:1.0: 1 port detected
[    1.466913] usbcore: registered new interface driver usb-storage
[    1.473088] i2c /dev entries driver
[    1.479003] watchdog: f1020300.watchdog: driver supplied timeout (4294967295) out of range
[    1.487315] watchdog: f1020300.watchdog: falling back to default timeout (171)
[    1.494654] orion_wdt: Initial timeout 171 sec
[    1.499469] debugfs: Directory 'cpu1' with parent 'opp' already present!
[    1.518718] sdhci: Secure Digital Host Controller Interface driver
[    1.524924] sdhci: Copyright(c) Pierre Ossman
[    1.562455] mmc0: SDHCI controller on f10d8000.sdhci [f10d8000.sdhci] using ADMA
[    1.575149] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.588343] marvell-cesa f1090000.crypto: CESA device successfully registered
[    1.595955] NET: Registered protocol family 10
[    1.600881] Segment Routing with IPv6
[    1.604606] NET: Registered protocol family 17
[    1.609105] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[    1.622180] 8021q: 802.1Q VLAN Support v1.8
[    1.626424] Registering SWP/SWPB emulation handler
[    1.633197] mv88e6085 f1072004.mdio-mii:00: switch 0x3520 detected: Marvell 88E6352, revision 1
[    1.661539] random: fast init done
[    1.666446] mmc0: new high speed SDIO card at address 0001
[    1.942181] libphy: mv88e6xxx SMI: probed
[    2.283589] mv88e6085 f1072004.mdio-mii:00 lan4 (uninitialized): PHY [mv88e6xxx-1:00] driver [Marvell 88E1540]
[    2.314260] mv88e6085 f1072004.mdio-mii:00 lan3 (uninitialized): PHY [mv88e6xxx-1:01] driver [Marvell 88E1540]
[    2.343725] mv88e6085 f1072004.mdio-mii:00 lan2 (uninitialized): PHY [mv88e6xxx-1:02] driver [Marvell 88E1540]
[    2.373182] mv88e6085 f1072004.mdio-mii:00 lan1 (uninitialized): PHY [mv88e6xxx-1:03] driver [Marvell 88E1540]
[    2.404290] mv88e6085 f1072004.mdio-mii:00 wan (uninitialized): PHY [mv88e6xxx-1:04] driver [Marvell 88E1540]
[    2.452937] mv88e6085 f1072004.mdio-mii:00: configuring for fixed/ link mode
[    2.463095] DSA: tree 0 setup
[    2.466391] xhci-hcd f10f8000.usb3: xHCI Host Controller
[    2.471741] xhci-hcd f10f8000.usb3: new USB bus registered, assigned bus number 2
[    2.479352] xhci-hcd f10f8000.usb3: hcc params 0x0a000990 hci version 0x100 quirks 0x0000000000010010
[    2.488660] xhci-hcd f10f8000.usb3: irq 44, io mem 0xf10f8000
[    2.495663] hub 2-0:1.0: USB hub found
[    2.499449] hub 2-0:1.0: 1 port detected
[    2.503508] xhci-hcd f10f8000.usb3: xHCI Host Controller
[    2.508845] xhci-hcd f10f8000.usb3: new USB bus registered, assigned bus number 3
[    2.516385] xhci-hcd f10f8000.usb3: Host supports USB 3.0 SuperSpeed
[    2.522816] usb usb3: We don't know the algorithms for LPM for this host, disabling LPM.
[    2.531104] hub 3-0:1.0: USB hub found
[    2.534891] hub 3-0:1.0: 1 port detected
[    2.539403] UBI: auto-attach mtd8
[    2.542741] ubi0: attaching mtd8
[    2.552637] mv88e6085 f1072004.mdio-mii:00: Link is Up - 1Gbps/Full - flow control off
[    3.144740] ubi0: scanning is finished
[    3.156391] ubi0: attached mtd8 (name "ubi", size 117 MiB)
[    3.161900] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    3.168809] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    3.175627] ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
[    3.182623] ubi0: good PEBs: 934, bad PEBs: 2, corrupted PEBs: 0
[    3.188652] ubi0: user volume: 2, internal volumes: 1, max. volumes count: 128
[    3.195907] ubi0: max/mean erase counter: 2/0, WL threshold: 4096, image sequence number: 1612803509
[    3.205079] ubi0: available PEBs: 0, total reserved PEBs: 934, PEBs reserved for bad PEB handling: 38
[    3.214344] ubi0: background thread "ubi_bgt0d" started, PID 935
[    3.214897] block ubiblock0_0: created from ubi0:0(rootfs)
[    3.225892] ubiblock: device ubiblock0_0 (rootfs) set to be root filesystem
[    3.232887] hctosys: unable to open rtc device (rtc0)
[    3.241343] VFS: Mounted root (squashfs filesystem) readonly on device 254:0.
[    3.249166] Freeing unused kernel memory: 1024K
[    3.272735] Checked W+X mappings: passed, no W+X pages found
[    3.278417] Run /sbin/init as init process
[    3.514637] init: Console is alive
[    3.518123] init: - watchdog -
[    4.169338] kmodloader: loading kernel modules from /etc/modules-boot.d/*
[    4.206564] ehci-fsl: Freescale EHCI Host controller driver
[    4.213065] uhci_hcd: USB Universal Host Controller Interface driver
[    4.220005] usbcore: registered new interface driver uas
[    4.225471] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
[    4.239663] init: - preinit -
[    4.590815] random: jshn: uninitialized urandom read (4 bytes read)
[    4.611172] random: jshn: uninitialized urandom read (4 bytes read)
[    4.727289] random: jshn: uninitialized urandom read (4 bytes read)
[    8.126915] UBIFS (ubi0:1): Mounting in unauthenticated mode
[    8.132680] UBIFS (ubi0:1): background thread "ubifs_bgt0_1" started, PID 1055
[    8.172738] UBIFS (ubi0:1): recovery needed
[    8.260646] UBIFS (ubi0:1): recovery completed
[    8.265149] UBIFS (ubi0:1): UBIFS: mounted UBI device 0, volume 1, name "rootfs_data"
[    8.273021] UBIFS (ubi0:1): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    8.282981] UBIFS (ubi0:1): FS size: 89137152 bytes (85 MiB, 702 LEBs), journal size 4444160 bytes (4 MiB, 35 LEBs)
[    8.293461] UBIFS (ubi0:1): reserved for root: 4210167 bytes (4111 KiB)
[    8.300102] UBIFS (ubi0:1): media format: w5/r0 (latest is w5/r0), UUID 08DFC233-576C-41F4-88A4-DE0FC1E68F62, small LPT model
[    8.315454] mount_root: switching to ubifs overlay
[    8.387524] urandom-seed: Seeding with /etc/urandom.seed
[    8.487046] procd: - early -
[    8.489963] procd: - watchdog -
[    9.027722] procd: - watchdog -
[    9.032462] procd: - ubus -
[    9.078686] urandom_read: 5 callbacks suppressed
[    9.078689] random: ubusd: uninitialized urandom read (4 bytes read)
[    9.090204] random: ubusd: uninitialized urandom read (4 bytes read)
[    9.100351] procd: - init -
[    9.758200] urngd: v1.0.2 started.
[    9.791998] random: crng init done
[   10.034650] kmodloader: loading kernel modules from /etc/modules.d/*
[   10.066348] zram: Added device: zram0
[   10.071059] tun: Universal TUN/TAP device driver, 1.6
[   10.078616] ipip: IPv4 and MPLS over IPv4 tunneling driver
[   10.126536] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[   10.280651] cryptodev: driver 1.11 loaded.
[   10.300670] Loading modules backported from Linux version v5.8.18-0-gab435ce49bd1
[   10.308222] Backport generated by backports.git v5.8.18-1-0-ga630fd46
[   10.369968] <<Marvell Mac80211 Wireless PCIE Network Driver version 10.3.8.0-20181210>>
[   10.378057] pci 0000:00:01.0: enabling device (0140 -> 0142)
[   10.383833] ieee80211 phy0: priv->pcmd_buf = 0a81334f  priv->pphys_cmd_buf = 81887cbc
[   10.482483] ieee80211 phy0: fw download start
[   10.482488] ieee80211 phy0: ddr init: download start
[   10.482868] ieee80211 phy0: ddr init: download complete
[   10.621427] ieee80211 phy0: FwSize = 451040 downloaded Size = 451040 curr_iteration 65521
[   13.496743] ieee80211 phy0: fw download complete
[   13.496918] ieee80211 phy0: device node: pcie@1,0
[   13.537486] ieee80211 phy0: pcmd = 0a81334f
[   13.555557] ieee80211 phy0: firmware version: 0x903020c
[   14.124420] ieee80211 phy0: firmware region code: 30
[   14.188247] ieee80211 phy0: 2G disabled, 5G enabled
[   14.193150] ieee80211 phy0: 4 TX antennas, 4 RX antennas
[   14.198725] pci 0000:00:02.0: enabling device (0140 -> 0142)
[   14.204509] ieee80211 phy1: priv->pcmd_buf = 1d25ca4c  priv->pphys_cmd_buf = fae4049a
[   14.218530] ieee80211 phy1: fw download start
[   14.218537] ieee80211 phy1: ddr init: download start
[   14.218922] ieee80211 phy1: ddr init: download complete
[   14.360953] ieee80211 phy1: FwSize = 451040 downloaded Size = 451040 curr_iteration 65527
[   15.556839] ieee80211 phy1: fw download complete
[   15.557026] ieee80211 phy1: device node: pcie@2,0
[   15.597464] ieee80211 phy1: pcmd = 1d25ca4c
[   15.615537] ieee80211 phy1: firmware version: 0x903020c
[   16.178856] ieee80211 phy1: firmware region code: 30
[   16.225490] ieee80211 phy1: 2G enabled, 5G disabled
[   16.230400] ieee80211 phy1: 4 TX antennas, 4 RX antennas
[   16.274333] hidraw: raw HID events driver (C) Jiri Kosina
[   16.280609] Mirror/redirect action on
[   16.288743] u32 classifier
[   16.291464]     input device check on
[   16.295166]     Actions configured
[   16.303972] GACT probability on
[   16.308733] Simple TC action Loaded
[   16.319537] fuse: init (API version 7.31)
[   16.333139] Bluetooth: Core ver 2.22
[   16.336789] NET: Registered protocol family 31
[   16.341256] Bluetooth: HCI device and connection manager initialized
[   16.347698] Bluetooth: HCI socket layer initialized
[   16.352616] Bluetooth: L2CAP socket layer initialized
[   16.357708] Bluetooth: SCO socket layer initialized
[   16.363459] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   16.368805] Bluetooth: BNEP filters: protocol multicast
[   16.374251] Bluetooth: BNEP socket layer initialized
[   16.379869] Bridge firewalling registered
[   16.389237] Bluetooth: vendor=0x2df, device=0x9136, class=255, fn=2
[   17.260156] Bluetooth: FW download over, size 616840 bytes
[   17.858334] btmrvl_sdio mmc0:0001:2: sdio device tree data not available
[   17.867015] usbcore: registered new interface driver btusb
[   17.873952] Bluetooth: HCI UART driver ver 2.3
[   17.878437] Bluetooth: HCI UART protocol H4 registered
[   17.883597] Bluetooth: HCI UART protocol BCSP registered
[   17.888936] Bluetooth: HCI UART protocol ATH3K registered
[   17.895195] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[   17.901173] Bluetooth: HIDP socket layer initialized
[   18.064588] nf_conntrack_rtsp v0.7 loading
[   18.069928] mwifiex_sdio mmc0:0001:1: WLAN FW already running! Skip FW dnld
[   18.076963] mwifiex_sdio mmc0:0001:1: WLAN FW is active
[   18.089734] nf_nat_rtsp v0.7 loading
[   18.105778] Bluetooth: RFCOMM TTY layer initialized
[   18.110697] Bluetooth: RFCOMM socket layer initialized
[   18.115883] Bluetooth: RFCOMM ver 1.11
[   18.121226] usbcore: registered new interface driver ums-alauda
[   18.127566] usbcore: registered new interface driver ums-cypress
[   18.134424] usbcore: registered new interface driver ums-datafab
[   18.141004] usbcore: registered new interface driver ums-freecom
[   18.147946] usbcore: registered new interface driver ums-isd200
[   18.154794] usbcore: registered new interface driver ums-jumpshot
[   18.161260] usbcore: registered new interface driver ums-karma
[   18.167524] usbcore: registered new interface driver ums-sddr09
[   18.173808] usbcore: registered new interface driver ums-sddr55
[   18.180128] usbcore: registered new interface driver ums-usbat
[   18.187406] wireguard: WireGuard 1.0.20201112 loaded. See www.wireguard.com for information.
[   18.195944] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld <Jason@zx2c4.com>. All Rights Reserved.
[   18.233580] xt_time: kernel timezone is -0000
[   18.242320] PPP generic driver version 2.4.2
[   18.247746] NET: Registered protocol family 24
[   18.271262] mwifiex_sdio mmc0:0001:1: info: MWIFIEX VERSION: mwifiex 1.0 (15.68.7.p189) 
[   18.279428] mwifiex_sdio mmc0:0001:1: driver_version = mwifiex 1.0 (15.68.7.p189) 
[   18.282592] kmodloader: done loading kernel modules from /etc/modules.d/*
[   18.884105] zram0: detected capacity change from 0 to 33554432
[   21.340070] mvneta f1070000.ethernet eth0: configuring for fixed/rgmii-id link mode
[   21.348551] mvneta f1070000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[   21.351014] mv88e6085 f1072004.mdio-mii:00 lan1: configuring for phy/gmii link mode
[   21.365886] 8021q: adding VLAN 0 to HW filter on device lan1
[   21.374539] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   21.381092] br-lan: port 1(lan1) entered blocking state
[   21.386405] br-lan: port 1(lan1) entered disabled state
[   21.397405] device lan1 entered promiscuous mode
[   21.402044] device eth0 entered promiscuous mode
[   21.517076] mv88e6085 f1072004.mdio-mii:00 lan3: configuring for phy/gmii link mode
[   21.529194] 8021q: adding VLAN 0 to HW filter on device lan3
[   21.538567] br-lan: port 2(lan3) entered blocking state
[   21.543880] br-lan: port 2(lan3) entered disabled state
[   21.569133] device lan3 entered promiscuous mode
[   21.583477] mv88e6085 f1072004.mdio-mii:00: p6: already a member of VLAN 1
[   21.602543] mv88e6085 f1072004.mdio-mii:00 lan4: configuring for phy/gmii link mode
[   21.625005] 8021q: adding VLAN 0 to HW filter on device lan4
[   21.631409] br-lan: port 3(lan4) entered blocking state
[   21.636699] br-lan: port 3(lan4) entered disabled state
[   21.646066] device lan4 entered promiscuous mode
[   21.659018] mv88e6085 f1072004.mdio-mii:00: p6: already a member of VLAN 1
[   21.691646] mv88e6085 f1072004.mdio-mii:00 wan: configuring for phy/gmii link mode
[   21.715181] 8021q: adding VLAN 0 to HW filter on device wan
[   22.768592] ieee80211 phy0: change: 0xffffffff
[   22.884204] br-lan: port 4(wlan0) entered blocking state
[   22.889551] br-lan: port 4(wlan0) entered disabled state
[   22.895301] device wlan0 entered promiscuous mode
[   22.900129] br-lan: port 4(wlan0) entered blocking state
[   22.905501] br-lan: port 4(wlan0) entered forwarding state
[   22.917467] br-lan: port 4(wlan0) entered disabled state
[   23.119548] ieee80211 phy1: change: 0xffffffff
[   23.213300] br-lan: port 5(wlan1) entered blocking state
[   23.218639] br-lan: port 5(wlan1) entered disabled state
[   23.224266] device wlan1 entered promiscuous mode
[   23.229097] br-lan: port 5(wlan1) entered blocking state
[   23.234467] br-lan: port 5(wlan1) entered forwarding state
[   23.254697] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
[   23.464975] mv88e6085 f1072004.mdio-mii:00 wan: Link is Up - 100Mbps/Full - flow control off
[   23.476205] IPv6: ADDRCONF(NETDEV_CHANGE): wan: link becomes ready
[   23.923021] br-lan: port 5(wlan1) entered disabled state
[   24.787308] mv88e6085 f1072004.mdio-mii:00 lan1: Link is Up - 1Gbps/Full - flow control rx/tx
[   24.800751] br-lan: port 1(lan1) entered blocking state
[   24.806030] br-lan: port 1(lan1) entered forwarding state
[   25.233783] mv88e6085 f1072004.mdio-mii:00 lan3: Link is Up - 1Gbps/Full - flow control rx/tx
[   25.242806] br-lan: port 2(lan3) entered blocking state
[   25.248067] br-lan: port 2(lan3) entered forwarding state
[   27.939497] ieee80211 phy0: change: 0x100
[   27.957382] ieee80211 phy0: change: 0x40
[   28.244060] ieee80211 phy0: change: 0x40
[   28.268108] ieee80211 phy1: change: 0x100
[   28.285580] ieee80211 phy1: change: 0x40
[   28.533302] ieee80211 phy0: change: 0x40
[   28.540559] ieee80211 phy1: change: 0x40
[   28.689326] ieee80211 phy0: change: 0x100
[   28.707401] ieee80211 phy0: change: 0x100
[   28.723703] ieee80211 phy0: change: 0x42
[   28.777549] ieee80211 phy1: change: 0x40
[   29.020821] br-lan: port 4(wlan0) entered blocking state
[   29.026173] br-lan: port 4(wlan0) entered forwarding state
[   29.026957] ieee80211 phy1: change: 0x40
[   29.032215] pppoe-wan: renamed from ppp0
[   29.232499] ieee80211 phy1: change: 0x40
[   29.447510] ieee80211 phy1: change: 0x40
[   29.662510] ieee80211 phy1: change: 0x40
[   29.862499] ieee80211 phy1: change: 0x40
[   30.052494] ieee80211 phy1: change: 0x40
[   30.263419] ieee80211 phy1: change: 0x40
[   30.452480] ieee80211 phy1: change: 0x40
[   30.662409] ieee80211 phy1: change: 0x40
[   30.912506] ieee80211 phy1: change: 0x40
[   31.112538] ieee80211 phy1: change: 0x40
[   31.226645] ieee80211 phy1: change: 0x100
[   31.235729] ieee80211 phy1: change: 0x100
[   31.252789] ieee80211 phy1: change: 0x42
[   31.433213] br-lan: port 5(wlan1) entered blocking state
[   31.438565] br-lan: port 5(wlan1) entered forwarding state
[  446.238026] mv88e6085 f1072004.mdio-mii:00 lan3: Link is Down
[  446.243844] br-lan: port 2(lan3) entered disabled state
[  447.893889] mv88e6085 f1072004.mdio-mii:00 lan3: Link is Up - 10Mbps/Full - flow control rx/tx
[  447.902557] br-lan: port 2(lan3) entered blocking state
[  447.907807] br-lan: port 2(lan3) entered forwarding state
[  449.006857] mv88e6085 f1072004.mdio-mii:00 lan3: Link is Down
[  449.012675] br-lan: port 2(lan3) entered disabled state

How ever checking the sysupgrade image shows a 3mb kernel in it.
How do i check the .img file's kernel size or how do i findout on the router.

Just blindly followed the GPL because it was my first device support patch, I didn't know any better, and it worked ok :upside_down_face:

1 Like

@solidus1983

[    1.125783] 0x000000000000-0x000000200000 : "u-boot"
[    1.131053] 0x000000200000-0x000000220000 : "u_env"
[    1.136218] 0x000000220000-0x000000260000 : "s_env"
[    1.141325] 0x000000260000-0x000000820000 : "unused_area"
[    1.146973] 0x0000007e0000-0x000000820000 : "devinfo"
[    1.152261] 0x000000900000-0x000008400000 : "kernel1"
[    1.157685] 0x000000f00000-0x000008400000 : "rootfs1"
[    1.163107] 0x000008400000-0x00000ff00000 : "kernel2"
[    1.168525] 0x000008a00000-0x00000ff00000 : "ubi"
[    1.173609] 0x00000ff00000-0x000010000000 : "BBT"

That indeed looks correct, awesome to hear that venom too works!

How ever checking the sysupgrade image shows a 3mb kernel in it.

That is expected, the kernel will only be as big as it needs to.

How do i check the .img file's kernel size

Extracting the sysupgrade and running ls -la kernel or file kernel will give you the sizes.

If you are using the above two config settings, you presumably have patches in your tree to shrink things, otherwise your build presumably would have failed for the wrt32x (prior to these patches). At least the bots currently fail due to the size exception with similar setting. Some kmod removals maybe?

Thats the thing i haven't removed the kmods, infact i have added a load to both this image and to the one before it.

However i have noticed the size (using the same config) has changed.

Pre-Resize Patch r15697:

Post-Resize Patch r15710:

As you can see the factory img has grown for the wrt32x by 3mb but the sysupgrade stayed the same. However it boots so thats a start.

If you DM me i will give you the link to the webserver so you can check the mainfest file and config file.

You can just push'em to a bit bucket and post the link(s)

cat file | nc termbin.com 9999

but a git status indicates a clean tree, colour me confused.

Here you go, completely forgot about termbin.com

R15710:

config.buildinfo : https://termbin.com/7o3v
openwrt-mvebu-cortexa9.manifest : https://termbin.com/2uj2

R15697:

config.buildinfo :  https://termbin.com/c91b
openwrt-mvebu-cortexa9.manifest :  https://termbin.com/u57c

git status shows

        mvebu-frequency-scaling-kernel5.4.patches
        target/linux/mvebu/patches-5.4/800-Add_Armada_38x_support_for_clk-cpu.patch
        target/linux/mvebu/patches-5.4/801-Use_shorter_register_definition_in_pmsu_c.patch
        target/linux/mvebu/patches-5.4/802-Made_the_dynamic_frequency_scaling_support_more_generic.patch
        target/linux/mvebu/patches-5.4/803-Armada_38x_Add_dynamic_frequency_scaling_support_in_pmsu.patch
        target/linux/mvebu/patches-5.4/804-Update_Armada_38x_DT_for_dynamic_frequency_scaling.patch
        target/linux/mvebu/patches-5.4/806-disable-clocksource.patch

However its not showing any of the git am patches at all

however if i look in target/linux/mvebu/image/cortexa9.mk :

define Device/linksys_wrt32x
  $(call Device/linksys)
  $(Device/dsa-migration)
  DEVICE_MODEL := WRT32X
  DEVICE_ALT0_VENDOR := Linksys
  DEVICE_ALT0_MODEL := Venom
  DEVICE_DTS := armada-385-linksys-venom
  DEVICE_PACKAGES += kmod-btmrvl kmod-mwifiex-sdio mwlwifi-firmware-88w8964
  KERNEL_SIZE := 6144k
  KERNEL := kernel-bin | append-dtb
  SUPPORTED_DEVICES += armada-385-linksys-venom linksys,venom
  DEFAULT := n

I don't use git am, but if memory serves something like

git log --oneline

should show what you have added. You would have to have changed something relative to target/linux/mvebu/config-5.4...

To make a 5.10.x build work I was changing some kmods to loadable by way of adding file

target/linux/mvebu/cortexa9/config-5.10
# CONFIG_ATA is not set
# CONFIG_EXT4_FS is not set
# CONFIG_SATA_PMP is not set
# CONFIG_SCSI is not set

The merge request:

2 Likes

I have been in contact with Linksys and Marvell a long time ago, asking them to release the code for the 3200 u-boot. I even asked for support from Wolfgang Denk, one of the founders of u-boot project. They failed to provide the code, although their generic modified code is available on github: https://github.com/MarvellEmbeddedProcessors/u-boot-marvell

nitroshift

1 Like

@anomeome
hmm? are you sure that is intended for me?

Wondering if you intend on submitting your 5.10.x patchset for mvebu now that the 5.10 generic patchset is in master

1 Like

It is available on github but will submit it to master today.

nitroshift

LE: submitted.

3 Likes

@nitroshift
Your mvebu 5.10 patch that you sent to the mailing list includes numerous issues:

  • It has no subject and no description.
  • It wasn't picked up by Patchwork.
  • It doesn't successfully apply on master. Immediately fails at 002-add_powertables.patch user error here
  • It seems to be missing patches compared to 5.4, if they aren't needed anymore they should be noted in the description.
  • The patches don't appear to be numbered correctly. eg 002-add_powertables.patch vs 302-add_powertables.patch.
  • 999-DNM-dts-mamba-resize-3MB_to_4MB.patch needs to be dropped.
  • You removed the SPDX identifier from target/linux/mvebu/Makefile.
  • KERNEL_PATCHVER should be left and have KERNEL_TESTING_PATCHVER bumped instead.

Thanks for the heads-up! Will look into it today and create a pull request. Patch 999 was dropped in the next message in list. Forgot about it when sent the message.

nitroshift

LE:

2 Likes

I see that they are cutting openwrt-21.02 branch already, do you (or anyone) know if 5.10/larger kernel partition will make it to 21.02?

Also, thank you for all your work on mvebu/WRT AC series!

Until one of the methods being tried makes it into master there is no chance, with PR3852 most likely. Subscribe to the PR to get notification should something develop.

1 Like

Sorry let me rephrase my questions:

Hopefully the 4/6MB kernel partition patch get merged soon. (I got a rango a few weeks back before this PR was opened, to just play with snapshot)
If none of the kernel partition increase PR makes through, does that mean there won't be official images for mamba/venom in either master/snapshot or 21.02?

The 5.10 patch (or any patch for this matter), when/if it makes it into master within the next few days, who/what decides if they are going to cherry-pick that to the 21.02 branch?

One of the reasons given for branching 21.02 now is to be able to merge 5.10 patches into master without affecting the next release: http://lists.openwrt.org/pipermail/openwrt-devel/2021-February/033804.html

Stabilizing a new kernel version and moving all or a significant number of targets to it takes a lot of time.

So I believe it's unlikely that any 5.10 patches will end up in 21.02.

3 Likes