Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#60848 - [wireguard-dkms] 0.0.20181115-1 not working

Attached to Project: Community Packages
Opened by Alphazo (alphazo) - Sunday, 18 November 2018, 08:10 GMT
Last edited by Christian Hesse (eworm) - Tuesday, 20 November 2018, 09:56 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Christian Hesse (eworm)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

I installed Wireguard-dkms 0.0.20181115-1 on linux-4.19.2.arch1-1-x86_64 but it complained that some symbols were missing during startup. I then tried to manually start wireguard but it wouldn't. I then downgraded kernel to linux-4.19.1 but had the same result.
The only way I found to get Wireguard working again was to downgrade both wireguard-dksm and wireguard-tools to 0.0.20181018-1 (and reverted kernel back to latest one 4.19.2)
This task depends upon

Closed by  Christian Hesse (eworm)
Tuesday, 20 November 2018, 09:56 GMT
Reason for closing:  Fixed
Additional comments about closing:  wireguard 0.0.20181119-1
Comment by Doug Newgard (Scimmia) - Sunday, 18 November 2018, 15:38 GMT
Actual errors? Build log?
Comment by Alphazo (alphazo) - Sunday, 18 November 2018, 16:49 GMT
I didn't build it. Just installed it from the repo. Here is what I get with:
- community/wireguard-dkms 0.0.20181115-1
- community/wireguard-tools 0.0.20181115-1
- core/linux 4.19.2.arch1-1 (base)

# systemctl restart wg-quick@blueisland.service
# journalctl -xe
Nov 18 17:45:45 bluefly wg-quick[2828]: RTNETLINK answers: Operation not supported
Nov 18 17:45:45 bluefly kernel: wireguard: Unknown symbol poly1305_blocks_avx (err -2)
Nov 18 17:45:45 bluefly kernel: wireguard: Unknown symbol poly1305_emit_avx (err -2)
Nov 18 17:45:45 bluefly kernel: wireguard: Unknown symbol poly1305_blocks_avx512 (err -2)
Nov 18 17:45:45 bluefly kernel: wireguard: Unknown symbol chacha20_avx512vl (err -2)
Nov 18 17:45:45 bluefly kernel: wireguard: Unknown symbol chacha20_avx2 (err -2)
Nov 18 17:45:45 bluefly kernel: wireguard: Unknown symbol poly1305_blocks_avx2 (err -2)
Nov 18 17:45:45 bluefly kernel: wireguard: Unknown symbol chacha20_avx512 (err -2)
Nov 18 17:45:45 bluefly wg-quick[2828]: Unable to access interface: Protocol not supported
Nov 18 17:45:45 bluefly wg-quick[2828]: [#] ip link delete dev blueisland
Nov 18 17:45:45 bluefly wg-quick[2828]: Cannot find device "blueisland"
Nov 18 17:45:45 bluefly systemd[1]: wg-quick@blueisland.service: Main process exited, code=exited, status=1/FAILURE
Nov 18 17:45:45 bluefly systemd[1]: wg-quick@blueisland.service: Failed with result 'exit-code'.
Nov 18 17:45:45 bluefly systemd[1]: Failed to start WireGuard via wg-quick(8) for blueisland.
-- Subject: Unit wg-quick@blueisland.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit wg-quick@blueisland.service has failed.
--
-- The result is failed.


# systemctl status wg-quick@blueisland.service
● wg-quick@blueisland.service - WireGuard via wg-quick(8) for blueisland
Loaded: loaded (/usr/lib/systemd/system/wg-quick@.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sun 2018-11-18 17:43:50 CET; 17s ago
Docs: man:wg-quick(8)
man:wg(8)
https://www.wireguard.com/
https://www.wireguard.com/quickstart/
https://git.zx2c4.com/WireGuard/about/src/tools/man/wg-quick.8
https://git.zx2c4.com/WireGuard/about/src/tools/man/wg.8
Process: 1350 ExecStart=/usr/bin/wg-quick up blueisland (code=exited, status=1/FAILURE)
Main PID: 1350 (code=exited, status=1/FAILURE)

nov. 18 17:43:50 bluefly systemd[1]: Starting WireGuard via wg-quick(8) for blueisland...
nov. 18 17:43:50 bluefly wg-quick[1350]: [#] ip link add blueisland type wireguard
nov. 18 17:43:50 bluefly wg-quick[1350]: RTNETLINK answers: Operation not supported
nov. 18 17:43:50 bluefly wg-quick[1350]: Unable to access interface: Protocol not supported
nov. 18 17:43:50 bluefly wg-quick[1350]: [#] ip link delete dev blueisland
nov. 18 17:43:50 bluefly wg-quick[1350]: Cannot find device "blueisland"
nov. 18 17:43:50 bluefly systemd[1]: wg-quick@blueisland.service: Main process exited, code=exited, status=1/FAILURE
nov. 18 17:43:50 bluefly systemd[1]: wg-quick@blueisland.service: Failed with result 'exit-code'.
nov. 18 17:43:50 bluefly systemd[1]: Failed to start WireGuard via wg-quick(8) for blueisland.


Comment by Doug Newgard (Scimmia) - Sunday, 18 November 2018, 17:03 GMT
Read up on how DKMS works.
Comment by Alphazo (alphazo) - Sunday, 18 November 2018, 18:08 GMT
Sorry but I can't get this version to work even reinstalling kernel and trigger DKMS module refresh.

#sudo dkms status
exfat, 198.01c30ad, 4.19.2-arch1-1-ARCH, x86_64: installed
wireguard, 0.0.20181115, 4.19.2-arch1-1-ARCH, x86_64: installed
Comment by loqs (loqs) - Sunday, 18 November 2018, 19:22 GMT
https://wiki.archlinux.org/index.php/Dynamic_Kernel_Module_Support#Rebuild_modules
If the module fails to rebuild post the log for the build failure.
Edit:
wireguard, 0.0.20181115, 4.19.2-arch1-1-ARCH, x86_64: installed
Unless the kernel was changed then the module has built successfully. What is the service status and journal contents now?
Comment by surefire (surefire) - Sunday, 18 November 2018, 19:27 GMT
This is upstream bug
I rebuilt PKGBUILD from source=("git+https://git.zx2c4.com/WireGuard#branch=master") there's a bug fixed.
Comment by Daniel M. Capella (polyzen) - Monday, 19 November 2018, 19:11 GMT
There's a new snapshot out, 0.0.20181119.
Comment by Alphazo (alphazo) - Tuesday, 20 November 2018, 09:53 GMT
I confirm that wireguard 0.0.20181119-1 fixes the issue.

Loading...