Open gociii opened 1 year ago
@gociii - this warning is harmless - it looks like the kernel does not find a firmware it would like to load - most probably the filename it searches does not match the installed firmware files ... i just have a debian bookworm at hand right now and there are at least some files /lib/firmware/s5p-mfc* - maybe a "dmesg | grep -i firmware" will bring up which filename the kernel is searching for ... this firmware is for video encoding and decoding and is not really well supported on a mainline system (but maybe i'm wrong with this assumption), so it should be no drama if it is not found ...
looks like this is it maybe: https://forum.odroid.com/viewtopic.php?p=296928#p296928
Thanks for the info hexdump0815. Appears on 5.19.1 too, but doesn't seem to hinder it's headless functionality.
dmesg output:
[ 0.000000] Running under secure firmware. [ 18.845073] s5p-mfc 13400000.codec: preallocated 8 MiB buffer for the firmware and context buffers [ 18.854848] s5p-mfc 13400000.codec: Direct firmware load for s5p-mfc.fw failed with error -2 [ 18.858242] s5p_mfc_load_firmware:69: Firmware is not present in the /lib/firmware directory nor compiled in kernel [ 20.098033] s5p-mfc 13400000.codec: Direct firmware load for s5p-mfc.fw failed with error -2 [ 20.110106] s5p_mfc_load_firmware:69: Firmware is not present in the /lib/firmware directory nor compiled in kernel [ 20.147639] s5p-mfc 13400000.codec: Direct firmware load for s5p-mfc.fw failed with error -2 [ 20.155647] s5p_mfc_load_firmware:69: Firmware is not present in the /lib/firmware directory nor compiled in kernel
I'm running cockpit on Odroid-U3 with diet-pi 'installed' on top of debian image with kernel version 5.18.1-stb-exy+ I noticed the error below under kernel logs within cockpit.
kernel: s5p_mfc_load_firmware:69: Firmware is not present in the /lib/firmware directory nor compiled in kernel PRIORITY 3 SYSLOG_FACILITY 0 SYSLOG_IDENTIFIER kernel _BOOT_ID 20f377c1a3034849b15e5c5473a9bf2a _HOSTNAME linuxhost _MACHINE_ID 7d93fb82b0cc4679aabb6490d31ab16b _SOURCE_MONOTONIC_TIMESTAMP 22418106 _TRANSPORT kernel CURSOR s=7ce1e9b15bb84367bb1baa1756530e9b;i=29d;b=20f377c1a3034849b15e5c5473a9bf2a;m=1564748;t=5e75d6bfb5063;x=74eb62502a38bddc MONOTONIC_TIMESTAMP 22431560 __REALTIME_TIMESTAMP 1661763313160291
Will be using image with kernel 5.19 soon and will report if issue is fixed in the coming days.