From: Christian Hesse <list@eworm.de>
To: lennart <lennart@hamburg.freifunk.net>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Similar Problem with ArchARM
Date: Wed, 18 Jan 2017 13:32:19 +0100 [thread overview]
Message-ID: <20170118133219.4e4c4625@leda> (raw)
In-Reply-To: <03b53159-927e-fa41-8fcd-544e914c7441@hamburg.freifunk.net>
[-- Attachment #1: Type: text/plain, Size: 1032 bytes --]
lennart <lennart@hamburg.freifunk.net> on Tue, 2017/01/17 10:22:
> Hi again,
>
> I'm now trying to get wireguard running on my raspberry pi with archARM
> [0]. I installed wireguard-dkms, wireguard-tools and
> linux-raspberrypi-headers and now get:
>
> alarm@alarmpi ~/wireguard ❯❯❯ sudo modprobe wireguard
> modprobe: FATAL: Module wireguard not found in directory
> /lib/modules/4.1.20-1-ARCH
>
> Any idea what could solve this problem?
>
> [0] https://archlinuxarm.org/
Works out of the box for me:
$ pacman -S wireguard-tools linux-raspberrypi-headers
[...]
(1/3) Install DKMS modules
==> dkms install wireguard/0.0.20170115 -k 4.4.43-1-ARCH
[...]
Have you booted the kernel that is actually installed? Version 4.1.20-1 is
pretty old in terms of Arch...
--
main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH"
"CX:;",b;for(a/* Best regards my address: */=0;b=c[a++];)
putchar(b-1/(/* Chris cc -ox -xc - && ./x */b/42*2-3)*42);}
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2017-01-18 12:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 9:22 lennart
2017-01-17 10:09 ` Jason A. Donenfeld
2017-01-17 10:11 ` Jason A. Donenfeld
2017-01-18 12:32 ` Christian Hesse [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=20170118133219.4e4c4625@leda \
--to=list@eworm.de \
--cc=lennart@hamburg.freifunk.net \
--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).