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] <jonh7776> I don't run the edge kernel but perhaps it is a built-in module? It would then be loaded with the kernel and not be compiled as a separate module. It would be in the /lib/modules/linux-*your version*/modules.builtin file.
<DC-IRC>
[Discord] <jonh7776> I don't run the edge kernel but perhaps it is a built-in module? It would then be loaded with the kernel and not be compiled as a separate module. It would be in the /lib/modules/linux-*your version*/modules.builtin file.
<DC-IRC>
[Discord] <jonh7776> I mean listed in this file which is a text file.
<DC-IRC>
[Discord] <t1msu_87222> it is not listed there
DC-IRC has quit [Remote host closed the connection]
DC-IRC has joined #armbian-rockchip
<DC-IRC>
[Discord] <t1msu_87222> i think my mesa version is too old (22.3)
<DC-IRC>
[Discord] <amazingfate> You need mesa 24.1 or later for panthor.
<DC-IRC>
[Discord] <Werner> If you have ubuntu as userspace you can use oibaf ppa to install latest mesa packages
lanefu has quit [Ping timeout: 272 seconds]
<DC-IRC>
[Discord] <alexl83> Hi Guys! I'd like to keep my orangepi5-plus builds on kernel 6.8 - is it safe to enable target current in your opinion or am I bound to find issues? When 6.8.12 was edge, I had no issues with it
<DC-IRC>
[Discord] <alexl83> also, is there any compile-time flag or variable for vendor kernel, to enable usage of trace_printk?
<DC-IRC>
[Discord] <t1msu_87222> I switched to debian sid and it works now. But is it even useful to enable it for these older distributions?
<DC-IRC>
[Discord] <alexl83> also, is there any compile-time flag or variable for vendor kernel, to remove usage of trace_printk?
<DC-IRC>
[Discord] <narga_64> It's safe, but keep in mind that `current` 6.8 is EOL and will be switched to 6.10 soon, when `edge` switches to 6.11-rc.
<DC-IRC>
[Discord] <narga_64> Current will stay on the next LTS kernel once released
<DC-IRC>
[Discord] <narga_64> So if you want to stay on 6.8 you need to enable kernel update freeze
<DC-IRC>
[Discord] <alexl83> frozen for the time being as kali hasn't yet imported 6.10 and refreshed its patches
<DC-IRC>
[Discord] <alexl83> I enabled current for orangepi5-plus via userpatches but got a green led with no boot - it seems to be related to a change in initramfs.conf I made. I set MODULE=dep (was 'most') to trim down image size: it works with rk35xx-vendor but seems 6.8 wants a bigger set of modules to boot on 6.8 - will run some tests
<DC-IRC>
[Discord] <alexl83> MODULES=dep works also for other boards, and saves up to 20megs of space
<DC-IRC>
[Discord] <alexl83> frozen for the time being as kali hasn't yet imported 6.10 and refreshed its patches
<DC-IRC>
[Discord] <alexl83> I enabled current for orangepi5-plus via userpatches but got a green led with no boot - it seems to be related to a change in initramfs.conf I made. I set MODULES=dep (was 'most') to trim down image size: it works with rk35xx-vendor but seems 6.8 wants a bigger set of modules to boot on 6.8 - will run some tests
<DC-IRC>
[Discord] <narga_64> I have never touched that option, but if it does what I assume it does, then you could change some kernel configs to disable some modules you don't need
<DC-IRC>
[Discord] <alexl83> MODULES=dep states that update-initramfs will try to guess which modules are needed instead of pulling everything and its dog
<DC-IRC>
[Discord] <alexl83> but how to guess in a chrooted env? nevertheless it works for most of my boards
<DC-IRC>
[Discord] <alexl83> in current test image I kept MODULES=most and rebuilt everything from scratch using ARTIFACT_IGNORE_CACHE=yes - maybe cached rootfs has some issues
<DC-IRC>
[Discord] <alexl83> will play around
<DC-IRC>
[Discord] <narga_64> There's plenty of "useless" modules, as in totally not needed for the hardware. But then there's modules for filesystems for example. Does modules=deps disable the btrfs module for example if it doesn't detect a btrfs partition?
<DC-IRC>
[Discord] <alexl83> Cannot say, it's kinda lacking documentation - criteria for choosing modules are not specified, I'd suppose it looks at /proc/modules - but again, while building in framework it'd useless
<DC-IRC>
[Discord] <alexl83> I was probably not really wise in changing that option at build time
<DC-IRC>
[Discord] <alexl83> will see if doing it on a live system has the same effect (not booting)
<DC-IRC>
[Discord] <narga_64> Sounds interesting!
<DC-IRC>
[Discord] <alexl83> I have my nanopi-r5c with literally 0 modules into initramfs and booting fine, but let me check live
<DC-IRC>
[Discord] <alexl83> this is the only module cached in initramfs on my nanopi-r5c using MODULES=dep