The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped automatically by the mailing list software.
--- Begin Message ---Hi, I'm working on porting a second MikroTik device, the RouterBOARD 922UAGS-5HPacD, from ar71xx to ath79 and I'm having trouble with the NAND storage. The chip is detected, but bad eraseblocks are reported when booting an initramfs image via TFTP (haven't tried sysupgrade yet): [ 0.791848] Creating 4 MTD partitions on "spi0.0": [ 0.796717] 0x000000000000-0x00000000c000 : "routerboot" [ 0.802857] 0x00000000c000-0x00000000d000 : "art" [ 0.808379] 0x00000000d000-0x00000000e000 : "bios" [ 0.813924] 0x00000000e000-0x00000000f000 : "soft_config" [ 0.823549] nand: device found, Manufacturer ID: 0xec, Chip ID: 0xf1 [ 0.830034] nand: Samsung NAND 128MiB 3,3V 8-bit [ 0.834717] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64 [ 0.842435] Scanning device for bad blocks [ 0.846909] Bad eraseblock 2 at 0x000000040000 [ 0.851500] Bad eraseblock 3 at 0x000000060000 [...] eraseblocks continue on all blocks, from 4 to 15 [ 0.911492] Bad eraseblock 16 at 0x000000200000 [ 1.036624] 3 fixed-partitions partitions found on MTD device ar934x-nand [ 1.043531] Creating 3 MTD partitions on "ar934x-nand": [ 1.048844] 0x000000000000-0x000000040000 : "booter" [ 1.054605] 0x000000040000-0x000000400000 : "kernel" [ 1.060369] 0x000000400000-0x000000800000 : "ubi" [ 1.477206] UBI error: unable to read from mtd6 The current 19.07.0 or snapshot ar71xx initramfs images do not complain about any bad eraseblocks, and can properly managa the UBI fs at mtd6: [ 3.402365] nand: device found, Manufacturer ID: 0xec, Chip ID: 0xf1 [ 3.408818] nand: Samsung NAND 128MiB 3,3V 8-bit [ 3.413534] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64 [ 3.421239] Scanning device for bad blocks [ 3.579454] Creating 3 MTD partitions on "ar934x-nfc": [ 3.584716] 0x000000000000-0x000000040000 : "booter" [ 3.607604] 0x000000040000-0x000000400000 : "kernel" [ 3.630593] 0x000000400000-0x000008000000 : "ubi" It looks like the NAND chip is correctly detected, but I don't know what I'm missing that causes the [wrong] bad eraseblocks to appear. Any suggestions? The tree with the commit adding support is at https://github.com/rogerpueyo/openwrt/tree/ath79-mikrotik-rb-922uags-5hpacd_badblocks Thanks! Roger
--- End Message ---
_______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
