From: Michael Gerlach <n3ph@terminal21.de>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>,
Jens Viisauksena <viisauksena@posteo.de>
Subject: Re: [WireGuard] wireguard on gentoo (4.6.3)
Date: Tue, 5 Jul 2016 02:19:08 +0200 [thread overview]
Message-ID: <20160705001908.GA9395@c3po> (raw)
In-Reply-To: <CAHmME9r8cNHAnuqMuP93YAhe77VUy=sX5NVS4kB+5U7tpF59Sg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1346 bytes --]
Everythings fine - thanks for the hints.. I really do not know what went
wrong but now i have the kernel running without MOD_VERSIONING.
I recompiled the module and its working fine now..
[ 277.546618] wireguard: WireGuard loaded. See www.wireguard.io for
information.
[ 277.546622] wireguard: (C) Copyright 2015-2016 Jason A. Donenfeld
<Jason@zx2c4.com>. All Rights Reserved.
I will now retry this with MOD_VERSIONING - i guess i just forget to
recompile the module after altering the kernel accordingly for the
dependencies..
best regards,
n3ph
On Tue, Jul 05, 2016 at 02:14:18AM +0200, Jason A. Donenfeld wrote:
> Hey Michael,
>
> There might be some other weirdness happening, then, with your kernel
> tree. Perhaps the compiler changed in curious ways, or sources got
> mixed around.
>
> You might benefit from running something like:
>
> # cd /usr/src/linux
> # mount /boot
> # cp .config ../backup-config
> # make mrproper
> # mv ../backup-config .
> # make oldconfig
> # make -j$(nproc)
> # make -j$(nproc) modules
> # make install
> # make modules_install
> # reboot
>
> That should give you something perhaps a bit more clean. Then, once
> that's running, try emerging wireguard again.
>
> Jason
--
Please use PGP - https://en.wikipedia.org/wiki/Pretty_Good_Privacy
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-07-05 0:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 22:53 [WireGuard] wireguard on gentoo (4.6.3) Michael Gerlach
2016-07-04 23:45 ` Jason A. Donenfeld
2016-07-04 23:50 ` Jens Viisauksena
2016-07-04 23:54 ` Jason A. Donenfeld
2016-07-05 0:06 ` Michael Gerlach
2016-07-05 0:14 ` Jason A. Donenfeld
2016-07-05 0:14 ` Jason A. Donenfeld
2016-07-05 0:19 ` Michael Gerlach [this message]
2016-07-05 0:20 ` Jason A. Donenfeld
2016-07-05 0:40 ` Michael Gerlach
2016-07-05 0:41 ` 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=20160705001908.GA9395@c3po \
--to=n3ph@terminal21.de \
--cc=Jason@zx2c4.com \
--cc=viisauksena@posteo.de \
--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