From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from lists.zx2c4.com (lists.zx2c4.com [165.227.139.114]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 349D1C54E58 for ; Fri, 15 Mar 2024 23:44:37 +0000 (UTC) Received: by lists.zx2c4.com (ZX2C4 Mail Server) with ESMTP id b6a9f24c; Fri, 15 Mar 2024 23:44:36 +0000 (UTC) Received: from gandalf.ozlabs.org (mail.ozlabs.org [2404:9400:2221:ea00::3]) by lists.zx2c4.com (ZX2C4 Mail Server) with ESMTPS id ba3652cf (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO) for ; Fri, 15 Mar 2024 23:44:33 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ellerman.id.au; s=201909; t=1710546268; bh=DmvrUMNXUtpSZVzaitPWmDSNlpeFznZ95+rmUpDj/bk=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=pxiLr+G9wiG7ShCCGxO97nJBFeBRkNkYKBAmEE8oi7eDQyyASb3PwlGGzp405JCnD QOOs2fOMa+QktpaFLnFJV1dGPT+UMeapeG08ZRLGmeGrs3r/R2/7xxtVYZh6ZMA6m7 PzVqUyA9ej9kCGsSTqzUcMxRCIFvVlyi9sPVUcJd7/YQ+RE7p2KADSiCi1iyj+eXxn BrUMsmuRqyKEmfAIHa8X2efgR5B9RjkDMdDPVi/ltHJHb9bpe/nnqTnbZBBqWVJ1YL nltG8fh3063WnK4ywUhQmftbcikNAktd0Lq9ABQu2vAXiv8Ehhb3LsGaMXY61BhT4D dj9tVuTv980KA== Received: from authenticated.ozlabs.org (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.ozlabs.org (Postfix) with ESMTPSA id 4TxLSW4Rr9z4wbr; Sat, 16 Mar 2024 10:44:27 +1100 (AEDT) From: Michael Ellerman To: Michal =?utf-8?Q?Such=C3=A1nek?= , dtsen@linux.ibm.com Cc: linuxppc-dev@lists.ozlabs.org, wireguard@lists.zx2c4.com, "Jason A. Donenfeld" , netdev@vger.kernel.org Subject: Re: Cannot load wireguard module In-Reply-To: <20240315122005.GG20665@kitsune.suse.cz> References: <20240315122005.GG20665@kitsune.suse.cz> Date: Sat, 16 Mar 2024 10:44:25 +1100 Message-ID: <87jzm32h7q.fsf@mail.lhotse> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: wireguard@lists.zx2c4.com X-Mailman-Version: 2.1.30rc1 Precedence: list List-Id: Development discussion of WireGuard List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: wireguard-bounces@lists.zx2c4.com Sender: "WireGuard" Michal Such=C3=A1nek writes: > Hello, > > I cannot load the wireguard module. > > Loading the module provides no diagnostic other than 'No such device'. > > Please provide maningful diagnostics for loading software-only driver, > clearly there is no particular device needed. Presumably it's just bubbling up an -ENODEV from somewhere. Can you get a trace of it? Something like: # trace-cmd record -p function_graph -F modprobe wireguard That should probably show where it's bailing out. > jostaberry-1:~ # uname -a > Linux jostaberry-1 6.8.0-lp155.8.g7e0e887-default #1 SMP Wed Mar 13 09:02= :21 UTC 2024 (7e0e887) ppc64le ppc64le ppc64le GNU/Linux > jostaberry-1:~ # modprobe wireguard > modprobe: ERROR: could not insert 'wireguard': No such device > jostaberry-1:~ # modprobe -v wireguard > insmod /lib/modules/6.8.0-lp155.8.g7e0e887-default/kernel/arch/powerpc/cr= ypto/chacha-p10-crypto.ko.zst=20 > modprobe: ERROR: could not insert 'wireguard': No such device =20 What machine is this? A Power10? cheers