Hi all, adding the debian-kernel list due to issues with using debian-installer daily snapshot to install on my brand new laptop with an ath11k_pci supported wifi chip. It turns out that while d-i comes with the ath11k and ath11k_pci drivers, but misses the qrtr, qrtr-mki and michael_mic modules that are needed for the driver to actually work and not just load. On Wed, Dec 07, 2022 at 02:49:37PM +0200, Kalle Valo wrote: > Thanks. But this makes me wonder is it sensible to randomly install a > set of .ko files and drop the rest, like Debian's installer apparently > does? The dependency for drivers is pretty well documented in Kconfig > files, thanks to build testers testing with random configurations, but > if the installer omits all that there will be problems just like you are > experiencing. So for me MODULE_SOFTDEP() feels just like a band aid and > not a robust solution. I think a driver that a driver that has a runtime depedency on a certain module, but doesn't import symbols is always going to be somewhat problematic. But I also agree that the arbitrary splitting of kernel modules into separate packages for the installer, or in fact not packaging them at all for the installer is rather problematic. I'm not sure what the rationale is behind that, but I've added the debian-kernel and debian-boot lists. > Though I am happy to take your MODULE_SOFTDEP() patch, just wondering if > there is a better way to solve this. For example net/mac80211 (the > 802.11 stack) has a lot of crypto dependencies: > > select CRYPTO > select CRYPTO_LIB_ARC4 > select CRYPTO_AES > select CRYPTO_CCM > select CRYPTO_GCM > select CRYPTO_CMAC > select CRC32 > > And it's not using MODULE_SOFTDEP() at all. Yes. I'm not quite sure how the packages for d-i select which modules to include where, but given that other wifi hardware seems to work in the installer they must have figured this out somehow.
