00:15 <FergusL> Hi, is mainline kernel supposed to have the uImage target? I guess not, right?

09:30 <yollom> I'm getting "Wrong Ramdisk Image Format" when trying to load an Ubuntu initrd.img

09:31 <yollom> Oddly, I can use lsinitrd from dracut to list the files, but not lsinitramfs

09:31 <yollom> The initrd.img is a LZ4 archive

09:35 <yollom> What does U-Boot expect by default? Can I configure U-Boot to use this initrd.img?

09:48 <mps> hm, build bmp_logo is disabled now

10:24 <FergusL> Hi, trying to get more recent stuff to run on rk3326(rg351m), I have yet to solder serial headers but I'm wondering if there's a go-to root filesystem that one could recommend to at least get visual confirmation that it is working? I'll need that in the end anyway

10:25 <FergusL> also, google is no help for one thing: rg351m is based on odroid go advance which has this SPI reset button at the back -- is it known if the 351m has such a button as well? I opened it to check for the serial but didn't look at that

10:29 <shiz> yollom: uboot expects initrds to be in FIT format too

10:29 <shiz> from my experience

10:29 <shiz> you can wrap it in a FIT

10:31 <yollom> shiz: thanks, yah, realized that "legacy" was referring to FIT and not the initrd image/archive itself

10:31 <yollom> Was about to try to rebuild with legacy support enabled, but creating a fit image might be easier

10:32 <shiz> i can grab the fit script i used a few days ago if it helps

10:32 <yollom> shiz: That would be great!

10:33 <shiz> alright, now where did i stash that...

10:33 <yollom> Do I need to put everything in the FIT or can I get away with just the initrd?

10:33 <shiz> just the initrd and config section is fine

10:36 <shiz> https://txt.shiz.me/NTZkZGM3ZD

10:42 <yollom> shiz: Awesome! Thank you!

10:43 <shiz> if your initrd is really lzo compressed, be sure to change the comperssion flag :)

10:43 <shiz> it tells mkimage how it is currently compressed, not what to compress it with

11:01 <marex> yollom: you could also try bootz/booti command which does not expect uImage/fitImage iirc

11:02 <marex> FergusL: you can build one using OpenEmbedded or debootstrap one with debian , or just build simple one with busybox static build

11:03 <FergusL> marex oh okay thanks! I think debootstrap will work for that

11:05 <marex> FergusL: well in that case, look at systemd mkosi

11:06 <marex> FergusL: that is a wrapper around debootstrap which spits out fully configured image, which ... well ... might be useful if you dont want to do the manual dpkg --reconfigure -a on the target

11:09 <FergusL> marex that will help a lot! now it sounds like it's what systemd has for its containers, interesting!

11:18 <marex> FergusL: yes, they used it for VMs first, then containers and now they even seem to plan to use it for initrd generation too

11:19 <marex> FergusL: and the tool is rather simple, which is nice, its basically a wrapper around all those debootstraps and compatible tools for other distros

11:42 <yollom> shiz: unfortunately, I got the same error after running `mkimage -f custom.its custom.itb`, loading the itb into memory and then running bootm/booti

11:48 <shiz> it worked for bootm for me

11:48 <shiz> does yoru build have CONFIG_FIT?

14:12 <FergusL> I think things have started moving on my device, I reflashed u-boot onto a working ubuntu 20.04 sdcard for which I had slightly modified the boot.ini (their u-boot used that) by disabling a gpio and I could confirm after reflashing mainline u-boot that it didn't have the same effect. I'm still getting used to u-boot so next time is generating

14:12 <FergusL> boot.scr

14:15 <FergusL> next step

21:10 <sjg1_> Tartarus yes I see that error a lot. I sometimes even get it locally but not often. I am no sure what to do about it though.

23:08 <Tartarus> --lazy to umount seems to help for me