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

[Ralf Mardorf]

On Mon, 23 Jul 2018 10:27:45 +0200, Peter Nabbefeld wrote:
>Tried to get that file from testing but couldn't find out how. Just
>activating the repo didn't help, probably I'd have to use some other
>mirror.

Did you run pacman -Syu?
If so, then the mirror perhaps isn't already synced, since it just moved
from Staging to Testing. 

You could install it by running

sudo pacman -U https://jpn.mirror.pkgbuild.com/testing/os/x86_64/linux{,-headers,-docs}-4.17.9-1-x86_64.pkg.tar.xz

but it doesn't solve this issue, see [1].

>It seems, CONFIG_CRYPTO_SALSA20 activates the external API (to be used 
>by modules and/or applications) while CONFIG_CRYPTO_SALSA20_X86_64 
>provides the implementation, so it *should* help (if this is the
>stream cipher used by bluez).

I don't have knowledge about this.

[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