[arch-general] Kernel modules not loaded after Linux update

[Peter Nabbefeld]

Am 23.07.2018 um 10:53 schrieb Levente Polyak via arch-general:
> On 07/23/2018 10:43 AM, Ralf Mardorf wrote:
>> [1]
>> 4.17.8 still in Core allegedly also contains it.
>>
>> $ grep pkg.e.= linux/repos/core-x86_64/PKGBUILD
>> pkgver=4.17.8
>> pkgrel=1
>> $ grep SALSA linux/repos/core-x86_64/config
>> CONFIG_CRYPTO_SALSA20=m
>> CONFIG_CRYPTO_SALSA20_X86_64=m
>>
>> I uninstalled
>>
>> $ uname -a
>> Linux archlinux 4.17.9-1-ARCH #1 SMP PREEMPT Sun Jul 22 20:23:36 UTC 2018 x86_64 GNU/Linux
>>
>> from Staging and removed it from the cache and then installed it from
>> Testing and rebooted.
>>
>> It remains
>>
>> $ uname -a
>> Linux archlinux 4.17.9-1-ARCH #1 SMP PREEMPT Sun Jul 22 20:23:36 UTC 2018 x86_64 GNU/Linux
>> $ zgrep SALSA /proc/config.gz
>> CONFIG_CRYPTO_SALSA20=m
>> $ grep SALSA /lib/modules/4.17.9-1-ARCH/build/.config
>> CONFIG_CRYPTO_SALSA20=m
>>
>> so it differs from config provided by the asp checkout
>>
>> grep SALSA linux/repos/testing-x86_64/config
>> CONFIG_CRYPTO_SALSA20=m
>> CONFIG_CRYPTO_SALSA20_X86_64=m
>>
>> FWIW
>>
>> $ grep SALSA linux/repos/core-i686/config.i686
>> CONFIG_CRYPTO_SALSA20=m
>> CONFIG_CRYPTO_SALSA20_586=m
>>
> No, it won't come back. The reason for the mismatch is that the config
> in the checkout is not regularly updated/synced for every minor kernel
> bump and removed options will remain there while the effective config at
> the end (which you can observe via config.gz) of cause won't have it.
>
> CRYPTO_SALSA20_X86_64 was removed in 4.17.7
>
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=49c8ef6d52ed6dacbca5a731ebe253bfb44e0ea9
>
Okay, thank You. But it seems, bluetooth is depending on that module, so 
probably it needs a patch, then.  :-/

Currently, I'll have to set my installation to not upgrade to a version 
 > 4.17.6.

Regards
Peter