Are you certain that the dkms rebuild was triggered?  Seems like like it was not.  Perhaps manually trigger it and reboot.

On Monday, November 19, 2018, Tosh <tosh@t0x0sh.org> wrote:
Hello,

I'm using Wireguard on ArchLinux since a long time, and today I have
some troubles to start my VPN. Here is the log of dmeg when I try to
'modprobe wireguard' :

wireguard: Unknown symbol poly1305_blocks_avx (err
-2)                                                               
wireguard: Unknown symbol poly1305_emit_avx (err
-2)                                                                 
wireguard: Unknown symbol poly1305_blocks_avx512 (err
-2)                                                            
wireguard: Unknown symbol chacha20_avx512vl (err
-2)                                                                 
wireguard: Unknown symbol chacha20_avx2 (err -2)
wireguard: Unknown symbol poly1305_blocks_avx2 (err
-2)                                                              
wireguard: Unknown symbol chacha20_avx512 (err -2)

I did a MAJ of my system yesterday, but wireguard wasn't upgraded, so I
don't know where the problem come from...Seems a LKM related to crypto
is missing, but I don't know which one is.

My kernel is 4.19.2-arch1-1-ARCH, and my wireguard packages are :

- community/wireguard-dkms 0.0.20181115-1

- community/wireguard-tools 0.0.20181115-1

Thanks for your work,

--
-TOSH-

If you need privacy you can encrypt your mails with my GPG key:
9B79 7754 00E2 23C7 FC90  E5C6 E5D9 1B2F 0BD5 3C6A



--
Sent from Gmail Mobile