From: John <graysky@archlinux.us>
To: Tosh <tosh@t0x0sh.org>
Cc: "wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: Re: Problem to load wireguard LKM in Archlinux
Date: Mon, 19 Nov 2018 10:04:58 -0500 [thread overview]
Message-ID: <CAO_nJAb5zoW+YRtt4BvB9YJzBm9w3DmXnuyGZ=362E3G7ofcQA@mail.gmail.com> (raw)
In-Reply-To: <41797799-8633-d195-54cb-ca3f38fbd371@t0x0sh.org>
[-- Attachment #1.1: Type: text/plain, Size: 1316 bytes --]
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
[-- Attachment #1.2: Type: text/html, Size: 2324 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
prev parent reply other threads:[~2018-11-19 15:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-18 18:55 Traffic on port 53 fails on LTE but works on WiFi John
2018-11-19 4:26 ` Quan Zhou
2018-11-19 7:32 ` M. Dietrich
2018-11-19 8:40 ` John
2018-11-19 8:54 ` Matthias Urlichs
2018-11-19 16:02 ` Roman Mamedov
2018-11-19 9:57 ` Problem to load wireguard LKM in Archlinux Tosh
2018-11-19 15:04 ` John [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAO_nJAb5zoW+YRtt4BvB9YJzBm9w3DmXnuyGZ=362E3G7ofcQA@mail.gmail.com' \
--to=graysky@archlinux.us \
--cc=tosh@t0x0sh.org \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).