lanefu changed the topic of #armbian-rockchip to: Armbian - Linux for ARM development boards | Rockchip SoC | www.armbian.com | This channel is relayed to the equivalent Discord channel | this channel is logged
<DC-IRC>
[Discord] <frankn.steroids> you know...that link you sent me for the community image, you're the maintainer right?
<DC-IRC>
[Discord] <frankn.steroids> image runs great not complaining
<DC-IRC>
[Discord] <frankn.steroids> just an user lost in the sea of information
<DC-IRC>
[Discord] <zwillx> I'm trying to get the patch in a workable format, my attempt here:
<DC-IRC>
[Discord] <zwillx> But I'm getting an error on the line holding "@@ -2665,6 +2665,59 @@ gpio4: gpio@fec50000 { "
<DC-IRC>
[Discord] <zwillx> which seems to be the dtsi patch unfortunately. I was trying to base it off the edge branch but there must be a discrepancy between the patch's dtsi attempt and the dtsi armbian is using
<DC-IRC>
[Discord] <fridtjof> yeah those packages look fine
<DC-IRC>
[Discord] <fridtjof> It's the same (only) kernel branch installed by the 5b+ config, going by the name
<DC-IRC>
[Discord] <fridtjof> What you mean then isn't a separate repo at this point but is just merged into the main armbian build system now
<DC-IRC>
[Discord] <fridtjof> Vendor kernel's the same package for both 5b and 5b+, and device trees for both are in the second package (which is just all the device trees from that kernel, i think?). So you should already have those installed if you used meco's 5b-plus config, just older (non-beta) versions
<DC-IRC>
[Discord] <frankn.steroids> i used the 5b one
<DC-IRC>
[Discord] <frankn.steroids> will i get these nice updates ppl are talking about through apt?
<DC-IRC>
[Discord] <fireman6740> How to move the U-boot build config to BuildRoot:
<DC-IRC>
[Discord] <Werner> We cannot support 3rd party frameworks
<DC-IRC>
[Discord] <fireman6740> ok
<DC-IRC>
[Discord] <mecoblock> yeah but that is Rock5B+ not Rock5B and that was just upstream armbian so nothing special. Please only use images that are made for the right board
<DC-IRC>
[Discord] <fridtjof> Eventually, yeah, i think
<DC-IRC>
[Discord] <fridtjof> Not really familiar with all the details though, im pretty new to the project
<DC-IRC>
[Discord] <fridtjof> but yeah, basically what meco said
<DC-IRC>
[Discord] <frankn.steroids> are these images using log2ram implementation of zram? i noticed omv install script disables armbian zram-config(bc both it and flashmemory plugin move files to /tmpfs) i would like to know what you think if disabling log2ram or whatever armbian uses currently would allow one to use flashmemory+ zram for compression only
<DC-IRC>
[Discord] <frankn.steroids> ZFS on a Nas can really benefit from some extra ram
<DC-IRC>
[Discord] <igorpec> we have our own zram config
<DC-IRC>
[Discord] <igorpec> zram is compressed anyway
<DC-IRC>
[Discord] <frankn.steroids> is it possible to disable the log2ram part of it?
<DC-IRC>
[Discord] <igorpec> and for logs it takes only 50Mb of RAM. not sure how would ZFS benefit from that ? 🙂
<DC-IRC>
[Discord] <frankn.steroids> I'd like to keep using flasmemory plugin
<DC-IRC>
[Discord] <frankn.steroids> we're talking different things, ZFS uses Arc for caching
<DC-IRC>
[Discord] <igorpec> yeah, you can disable it too if you like. Check /etc/defaults
<DC-IRC>
[Discord] <igorpec> yes, I know ZFS very well
<DC-IRC>
[Discord] <frankn.steroids> so you can see zram benefits it?
<DC-IRC>
[Discord] <igorpec> no, why would?
<DC-IRC>
[Discord] <igorpec> i mean, i understand that if you have ZFS storage and you put logs there
<DC-IRC>
[Discord] <igorpec> compression will do the job
<DC-IRC>
[Discord] <igorpec> automatically
<DC-IRC>
[Discord] <frankn.steroids> so zram is only for logs?
<DC-IRC>
[Discord] <igorpec> and for swap
<DC-IRC>
[Discord] <igorpec> there is no file swap but memory is getting compressed
<DC-IRC>
[Discord] <frankn.steroids> can't the Arc cache use zram compression?
<DC-IRC>
[Discord] <igorpec> but for logs, as i said, its so little that makes no point fiddling around
<DC-IRC>
[Discord] <igorpec> hmm, good question. i don't know
<DC-IRC>
[Discord] <frankn.steroids> i wad under the impression that anything could be moved to zram
<DC-IRC>
[Discord] <frankn.steroids> i was under the impression that anything could be moved to zram
<DC-IRC>
[Discord] <igorpec> yes. swap is pretty low level memory handler and zram replaces that
<DC-IRC>
[Discord] <igorpec> so in theory that is total memory
<DC-IRC>
[Discord] <igorpec> avail for applications
<DC-IRC>
[Discord] <frankn.steroids> so ZFS would obviously benefit
<DC-IRC>
[Discord] <igorpec> i think yes, but i am not aware how ZFS handles memory in details
<DC-IRC>
[Discord] <frankn.steroids> flashmemory plugin dev said it'd use double memory and maybe mess the moving bits
<DC-IRC>
[Discord] <igorpec> if you have compression on compresion is usually not a good idea. so that part is questionable
<DC-IRC>
[Discord] <igorpec> i am sure that flashmemory is not much different that what we have with zram / zlog / swap
<DC-IRC>
[Discord] <frankn.steroids> but back to question can one disable this log2ram behavior on armbian?
<DC-IRC>
[Discord] <igorpec> yes you can
<DC-IRC>
[Discord] <igorpec> look into /etc/defaults there is a switch
<DC-IRC>
[Discord] <igorpec> try and compare if you got time and you will see if there is any diff
<DC-IRC>
[Discord] <frankn.steroids> it does move logs back to disk on reboots, idea being to spare disk of micro operations and write amplification for many kinds of logs
<DC-IRC>
[Discord] <frankn.steroids> ok
<DC-IRC>
[Discord] <igorpec> now this flashmemory pluigin is probably better for OMV as it deal with probably other things
<DC-IRC>
[Discord] <frankn.steroids> yup, omv specific logs
<DC-IRC>
[Discord] <igorpec> i think they use this because they developed it ( i assume)
<DC-IRC>
[Discord] <frankn.steroids> so the idea is to keep using armbian zram-config for compression but let folder2ram/flashmemory plugin move things freely
<DC-IRC>
[Discord] <igorpec> omv intstaller anyway disabled it , i think
<DC-IRC>
[Discord] <frankn.steroids> so you can cache more nice things on your ZFS NAS
<DC-IRC>
[Discord] <igorpec> i have ZFS NAS but clean Armbian build, no OMV, nothing
<DC-IRC>
[Discord] <menu> you *can*, it's not a good idea
<DC-IRC>
[Discord] <frankn.steroids> oh i just read that ZFS is not able to use zram udev disk
<DC-IRC>
[Discord] <frankn.steroids> but the extra ram available could be used by ZFS Arc, and ZFS already compresses it anyway
<DC-IRC>
[Discord] <frankn.steroids> looks like a win win, but let's see it in practice
<DC-IRC>
[Discord] <menu> there's a reason nobody attempts to do this in practice, it won't have the performance benefit you're expecting
<DC-IRC>
[Discord] <frankn.steroids> you read it backwards
<DC-IRC>
[Discord] <frankn.steroids> if you utilize less ram via zram, what is left(uncompressed) can be used to increase Arc(ZFS cache) size
<DC-IRC>
[Discord] <frankn.steroids> you could max both like use 4GB for Arc and 4GB for zram say compression ratio is 2x for both you end up with 16GB effective ram which for these little boards with no upgrade option is quite cool, also you can tune ARC per dataset giving more control on what's cached or not
<DC-IRC>
[Discord] <frankn.steroids> i have set ARC for metadata only, will set it per dataset as needed, then leave armbian-zram-config enabled and armbian-ramlog disabled, leaving the flashmemory plugin do it's job with the logs
<DC-IRC>
[Discord] <frankn.steroids> also udev type disk like zram creates are not used by ZFS/ARC so nothing to worry there
<DC-IRC>
[Discord] <igorpec> @fridtjof rock5b+ i will merge that PR - even it might not be fully perfect.