Reza Alizadeh Majd <[email protected]> writes:
> On Mon, 21 Feb 2022 12:14:50 +0100 > Ricardo Wurmus <[email protected]> wrote: > > >> >>mmc-block or mmc_block? > > based on the following thread I thought that it might be the issue with > module name, so I tested with both mmc_block an mmc-block. > > https://debbugs.gnu.org/cgi/bugreport.cgi?bug=34902 > > unfortunately neither of those worked for me and I received the error > message I mentioned before. > >> >>What does the directory contain? If the module doesn’t exist you’ll >>have to build a kernel with a configuration that enables this module. >> > > $ find /gnu/store/*-linux-libre-arm64-generic-5.14.15/lib/modules -name > '*mmc*' > /gnu/store/gjm8fcl4z9zl7qql5d3cvpbrdlkfjx27-linux-libre-arm64-generic-5.14.15/lib/modules/5.14.15-gnu-v7l/kernel/drivers/mmc > /gnu/store/gjm8fcl4z9zl7qql5d3cvpbrdlkfjx27-linux-libre-arm64-generic-5.14.15/lib/modules/5.14.15-gnu-v7l/kernel/drivers/mmc/host/mmc_spi.ko > /gnu/store/gjm8fcl4z9zl7qql5d3cvpbrdlkfjx27-linux-libre-arm64-generic-5.14.15/lib/modules/5.14.15-gnu-v7l/kernel/drivers/mmc/host/of_mmc_spi.ko > > so it seems that the module is actually not available. is that because > of the the libre kernel restrictions? What restrictions? The list of modules depends largely on the kernel configuration. I encourage you to check if you need to add something to the kernel configuration and build your own kernel. -- Ricardo
