10:32 <ynezz> nbd: ok, thanks, so I'll mark this as wanted state then

11:42 <SpectreDev_01> Ansuel: https://pastebin.com/LafWm9aX

11:42 <SpectreDev_01> You got any clue I can't get past this

11:45 <PaulFertser> SpectreDev_01: why do you hardcode root= twice and why at all? OpenWrt kernel patches automatically use whatever partition is called "rootfs" as root.

11:46 <PaulFertser> SpectreDev_01: basically you have unsuitable explicit root specification and "rootwait" so the kernel just waits for the wrong device to appear.

11:47 <SpectreDev_01> It's appended because ubiblock0_0 doesn't boot on mtd24 (rootfs_1/alt_rootfs) iirc

11:47 <SpectreDev_01> And rootwait is done by uboot by default

11:50 <PaulFertser> SpectreDev_01: whatever the reason is, that's not how OpenWrt normally boots. rootwait is not harmful, don't worry about it. Without rootwait you'd just get kernel panic unable to mount root instead of hanging/waiting.

11:51 <PaulFertser> SpectreDev_01: btw, what's in your "rootfs" partition, how do you generated the image for it and flashed it?

11:52 <PaulFertser> SpectreDev_01: is it actually a ubi container? Then do not call it rootfs because the kernel can get confused.

11:52 <PaulFertser> If it's ubi just call it "ubi".

11:53 <PaulFertser> And there should be a volume named "rootfs" inside of it.

11:55 <PaulFertser> SpectreDev_01: here's an example from mir3g-v1 how a NAND device is normally handled: https://paste.debian.net/1292120/

11:56 <PaulFertser> SpectreDev_01: see, everything is automatic, ubi is auto-attached, rootfs is automatically selected etc.

11:57 <SpectreDev_01> PaulFertser: Nah factory is .bin, and flashed it fine via stock gui but sysupgrading doesn't work, rootfs contains rootfs_data iirc, I'll try finding the volumes in rootfs

11:58 <PaulFertser> SpectreDev_01: the partition containing ubi shouldn't be called rootfs.

11:58 <PaulFertser> SpectreDev_01: OpenWrt on NAND targets usually expects two ubi volumes inside "ubi" partition: rootfs and rootfs_data.

12:00 <PaulFertser> SpectreDev_01: nand.sh first removes rootfs_data volume, flashes new squashfs image to rootfs ubi volume, then creates rootfs_data ubifs volume to be used as r/w overlay and unpacks configuration archive.

12:01 <SpectreDev_01> PaulFertser: here it is ubiinfo https://pastebin.com/haUwxguH

12:02 <PaulFertser> SpectreDev_01: it says name squashfs and not "rootfs" as OpenWrt expects it.

12:03 <PaulFertser> And why is the volume so big?

12:04 <SpectreDev_01> I really don't know why, that's stock, Linksys has done that

12:04 <PaulFertser> SpectreDev_01: you're porting OpenWrt there right?

12:04 <PaulFertser> So you need to follow OpenWrt conventions, not whateve Linksys has invented.

12:05 <SpectreDev_01> Yeah I'm porting Openwrt

12:07 <PaulFertser> So OpenWrt expects no bullshit root= arguments, no ubi.mtd=22,2048 ubi.block=0,0 . It just wants the partition that holds ubi container to be called "ubi" and the volume that has squashfs root filesystem inside of it called "rootfs".

12:10 <SpectreDev_01> Ok hmm

12:30 <tmn505> I'm curious, why is there a need to append root=/dev/ubiblock0_1, bootloader mangles the boot arguments and they seem to clash with whatever You're adding, and I don't think there can be two root. Doesn't ipq40xx recipe (and kernel arguments) work for Your device? Looking at bootlog for Linksys EA8300 on OpenWrt wiki, the bootloader sets similar arguments except ubi.block=.

12:40 <SpectreDev_01> Hmm could work never tried