View Single Post
Old 05-12-2022, 05:59 PM   #3
katadelos
rm -rf /
katadelos ought to be getting tired of karma fortunes by now.katadelos ought to be getting tired of karma fortunes by now.katadelos ought to be getting tired of karma fortunes by now.katadelos ought to be getting tired of karma fortunes by now.katadelos ought to be getting tired of karma fortunes by now.katadelos ought to be getting tired of karma fortunes by now.katadelos ought to be getting tired of karma fortunes by now.katadelos ought to be getting tired of karma fortunes by now.katadelos ought to be getting tired of karma fortunes by now.katadelos ought to be getting tired of karma fortunes by now.katadelos ought to be getting tired of karma fortunes by now.
 
Posts: 219
Karma: 3333683
Join Date: Nov 2019
Location: United Kingdom
Device: K5, KT, KT2, KT3, KT4, KV, PW2, PW3, PW4, PW5
I vaguely remember running into a issue like this when attempting to bring up the WLAN interface using Alpine/Buildroot images on KT2/PW3; IIRC it was because the firmware loading relies upon hotplug/udev and non-Amazon images lack the script used to handle this (usr/libexec/firmware.sh on KT2)?

The actual mechanism used is covered in the kernel docs under the section "Firmware kobject uevent fallback mechanism".

I think the same mechanism is used to load the waveform, come to think of it...
katadelos is offline   Reply With Quote