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>
<lanefu> look at all this promise of a bright mainline future for rk3588(s)
<DC-IRC>
<RichN> to the kernelel tree you built with
<DC-IRC>
<RichN> see if it will get or new board going some
<DC-IRC>
<RichN> sorry working to finish off desktops and push by tomorrow
<DC-IRC>
<RichN> so new bookworm imgs can be built
<DC-IRC>
<lanefu> yeah hang tight on going to crazy with this link.. ricardo's got cherry-picks form my branch to tee up the collabora kernel stuff .. house keeping required still 😛 (this brnach got messy cuz i'm doing unlreated stuff as well)
<DC-IRC>
<ossuaries> Rock Pi 4b (RK3399) has a failing ram chip (first 2GB/4GB total) that I'm trying to blacklist. Passing memmap=2G$0M (or memmap=2G\\\$0M) to /boot/boot.cmd (then compiling with sudo mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr) causes dmesg on boot to spit out "Unknown kernel command line parameters "memmap=2G$0M" will be passed to user space." Should I be pas <clipped message>
<DC-IRC>
<ossuaries> sing this parameter to /boot/armbianEnv.txt instead? Are any of my commands wrong? OS: Armbian (23.02.2). Kernel: 5.15.93-rockchip64.
<DC-IRC>
<ossuaries> If anyone could help that'd be incredible.
<DC-IRC>
<ossuaries> Hey everyone.
<DC-IRC>
<ossuaries> Rock Pi 4b (RK3399) has a failing ram chip (first 2GB/4GB total) that I'm trying to blacklist. Passing memmap=2G$0M (or memmap=2G\\\$0M) to /boot/boot.cmd (then compiling with sudo mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr) causes dmesg on boot to spit out "Unknown kernel command line parameters "memmap=2G$0M" will be passed to user space." Should I be pas <clipped message>
<DC-IRC>
<ossuaries> sing this parameter to /boot/armbianEnv.txt instead? Are any of my commands wrong? OS: Armbian (23.02.2). Kernel: 5.15.93-rockchip64.
<DC-IRC>
<ossuaries> If anyone could help that'd be incredible. If this is the wrong place to post this, let me know.
<DC-IRC>
<ossuaries> Cryptrooted and booting off NVME, if that changes anything. Only line that's been altered is setenv bootargs.
<DC-IRC>
<lanefu> at a glance it looks okay what you're doing.. but that error message is probably being truthful.. which is kernel doesnt thing htat's a valid argument
<DC-IRC>
<ossuaries> Oh dear. Thanks for the help. Is there an equivalent command for arm?
<DC-IRC>
<lanefu> dunno you're playing in territory beyond my 🧠
<DC-IRC>
<Tenkawa> Its not really blacklisting
<DC-IRC>
<Tenkawa> its used for DAX
<DC-IRC>
<Tenkawa> Its actually the opposite
<DC-IRC>
<Tenkawa> it is used for persistemt memory pseudo allocatiom
<DC-IRC>
<Tenkawa> it is used for persistemt memory pseudo allocation
<DC-IRC>
<Tenkawa> it is used for persistent memory pseudo allocation
<DC-IRC>
<Tenkawa> You can use a segment of memory in the os layer..
<DC-IRC>
<Tenkawa> The Linux pmem driver allows application developers to begin developing persistent memory enabled applications using memory mapped files residing on Direct Access Filesystems (DAX) such as EXT4 and XFS. A memmap kernel option was added that supports reserving one or more ranges of unassigned memory for use with emulated persistent memory.
<DC-IRC>
<Tenkawa> Not sure that would have quite the effect you are looking for however check out this document and see what you think:
<DC-IRC>
<ossuaries> Huh. Interesting. Thank you for the help!
<DC-IRC>
<Tenkawa> np
<DC-IRC>
<Tenkawa> I'm finding conflicting information that memmap "in theory" can be used... but you have to find and adjust addresses (on x86 at leest).. I still haven't found anything in any other architecture
<DC-IRC>
<Tenkawa> It seems to be a very "unstable" workaround