From: Samu Voutilainen <wireguard@smar.fi>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Cc: faustin@fala.red
Subject: Re: Build wireguard-linux-compat on SLES15 (s390x)
Date: Thu, 21 Oct 2021 11:07:44 +0300 [thread overview]
Message-ID: <4688156.31r3eYUQgx@marie> (raw)
In-Reply-To: <YXEaXIkYfcSPO+tR@falared>
[-- Attachment #1: Type: text/plain, Size: 968 bytes --]
Faustin Lammler kirjoitti torstaina 21. lokakuuta 2021 10.44.28 EEST:
> Samu Voutilainen <wireguard@smar.fi>,
>
> 20/10/2021 – 19:25:49 (+0300):
> > At least on x86_64 SLE, the module is in kernel-*-extra package, for
> > example in kernel-default-extra.
>
> Zypper does show kernel-default-extra but:
> | kernel-default-base | The Standard Kernel - base modules | package
>
> That is not installed, maybe this is where the wireguard module is?
kernel-default-base is kind of minimal version of default kernel, usable in
certain virtualization setups, for example.
Actually it looks like in SLE-15-SP3 wireguard.ko is in kernel-default rather
in -extra. That was case in SP2.
$ rpm -ql kernel-default | ag wireguard.ko
/lib/modules/5.3.18-59.27-default/kernel/drivers/net/wireguard/wireguard.ko.xz
If the module is not present, maybe it is not compiled for s390x. Maybe SUSE’s
support could enlighten why such choice has been made?
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-10-21 8:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-09 10:26 Faustin Lammler
2021-10-19 11:01 ` Faustin Lammler
2021-10-19 12:18 ` CW
2021-10-19 23:51 ` Jason A. Donenfeld
2021-10-20 9:00 ` Faustin Lammler
2021-10-20 16:25 ` Samu Voutilainen
2021-10-21 7:44 ` Faustin Lammler
2021-10-21 8:07 ` Samu Voutilainen [this message]
2021-10-21 8:52 ` Faustin Lammler
2021-10-20 17:56 ` Jason A. Donenfeld
2021-10-21 12:37 ` Daniel Wagner
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=4688156.31r3eYUQgx@marie \
--to=wireguard@smar.fi \
--cc=faustin@fala.red \
--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).