Hi,
Sorry for late replies ...
1 you don't need octoprint (so remove ti) to get modules
2 you can load all modules without risk, the kernel select the good one when the hardware is plugged.
... when you are sure of the correct one ... you can clean the launch to get only the module require.
3 you can get the tar attached here, to get the modules (3) with version for ADM before_4.1.0.RLQ1 and version for newest (after)
put in safe place, you can try by loading module using :
insmod /path/to/module.ko (module = ch431.ko or cp210x.ko)
4 if it works, you must add it in script to be loaded automatically
... if it's for a specific APKG, a good solution (but to be redo when APKG is updated in AppCentral) is to add the load of module in the start-stop.sh of the APKG and modules in APKG folder
for ex.
mkdir /usr/local/AppCentral/APKG_NAME/my_modules
cp -p /path/to/module.ko /usr/local/AppCentral/APKG_NAME/my_modules (replace module.ko bu correct name)
start-stop.sh is in : /usr/local/AppCentral/APKG_NAME/CONTROL/
... search for start and add a small shell code like :
Code: Select all
lsmod | grep -q module ## module can be replaced by cp210x or ch341 in your case
if [ $? -ne 0 ] ; then
insmod /usr/local/AppCentral/APKG_NAME/my_modules/module.ko
fi
do it for each module ch341.ko and/or cp210x.ko
... then restart the APKG
With this the module is loaded (if not already done) before your APKG start.
You can used other solution at A.D.M. level (so not attached to APKG) even the module can be loaded after APKG (not a problem in lot of case)
... using a start_up script or using Entware APKG init.d folder launched at each boot ...
file for x86_64 5.13.x kernel :
Philippe.
