Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Alexander Morlang <alx@dd19.de>
To: Egbert Verhage <egbert@eggiecode.org>
Cc: wireguard@lists.zx2c4.com
Subject: Re: wg binary in armhf deb from ppa missing
Date: Sun, 19 Feb 2017 17:29:59 +0100	[thread overview]
Message-ID: <E8A0979F-E0B0-4614-801C-A56F94039F4B@dd19.de> (raw)
In-Reply-To: <37c21d07-0153-7fa2-8fe3-c852704e53b9@eggiecode.org>

Hi,
building on armhf reveals some effects i don=E2=80=99t understand:
On my raspi3 with raspian and kernel
uname -a
Linux raspberrypi 4.4.38-v7+ #938 SMP Thu Dec 15 15:22:21 GMT 2016 =
armv7l GNU/Linux
kernelmodule&wg are building just fine an the module loads. i had no =
time for testing it, but it builds.

On Banana Pro with armbian an kernel
uname -a
Linux bananapipro 4.9.7-sunxi #1 SMP Thu Feb 2 01:52:06 CET 2017 armv7l =
armv7l armv7l GNU/Linux
it=E2=80=99s building, but the module will not load:

sudo modprobe wireguard=20
modprobe: ERROR: could not insert 'wireguard': Exec format error

modinfo wireguard=20
filename:       /lib/modules/4.9.7-sunxi/extra/wireguard.ko
alias:          rtnl-link-wireguard
author:         Jason A. Donenfeld <Jason@zx2c4.com>
description:    Fast, secure, and modern VPN tunnel
license:        GPL v2
depends:        udp_tunnel,ip6_udp_tunnel,x_tables
vermagic:       4.9.7-sunxi SMP mod_unload ARMv7 thumb2 p2v8=20

In dmesg, it shows:
[ 1404.917772] wireguard: loading out-of-tree module taints kernel.
[ 1404.919392] wireguard: unknown relocation: 102

Next i will try with bananian and 4.4 kernel.

Gru=C3=9F, Alex

> Am 19.02.2017 um 15:51 schrieb Egbert Verhage <egbert@eggiecode.org>:
>=20
> Hey Alex,
>=20
> Ow, I never tested the package on armhf. I will give test it tomorrow =
on
> my own Banana Pi 2 and Raspberry pi 2.
>=20
> If you are running the image of lemaker on your banana pi, maybe try
> first to build the package from the git repo.
>=20
> Greetz,
> Egbert
>=20
>=20
> On 2017-02-19 02:14, Alexander Morlang wrote:
>> Hi,
>> used the launchpad ppa in xenial on armhf (Banana Pro).=20
>> The wireguard-tools packet installed only /usr/share/doc
>>=20
>> Is this a known problem?
>>=20
>> I downloaded the
>> =
https://launchpad.net/~wireguard/+archive/ubuntu/wireguard/+files/wireguar=
d-tools_0.0.20170214-wg1~xenial_armhf.deb
>> and hat a look with dpkg -c <file>, getting the same result of no =
binary in the packet.
>>=20
>> regards, Alex
>> _______________________________________________
>> WireGuard mailing list
>> WireGuard@lists.zx2c4.com
>> https://lists.zx2c4.com/mailman/listinfo/wireguard
>=20
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard

  parent reply	other threads:[~2017-02-19 16:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-19  1:14 Alexander Morlang
2017-02-19 14:51 ` Egbert Verhage
2017-02-19 16:27   ` Egbert Verhage
2017-02-19 16:29   ` Alexander Morlang [this message]
2017-02-19 18:21     ` wg binary in armhf deb from ppa missing; armbian with Allwinner A20 chip modprobe wg not working Egbert Verhage
     [not found]       ` <CAHmME9ossQJ3U54yOmY98dcdG239xm6KeHQt+n8zb6R0x4yUZA@mail.gmail.com>
2017-02-19 19:02         ` Jason A. Donenfeld

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=E8A0979F-E0B0-4614-801C-A56F94039F4B@dd19.de \
    --to=alx@dd19.de \
    --cc=egbert@eggiecode.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).