From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2.migadu.com ([2001:41d0:403:58f0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms1.migadu.com with LMTPS id oPs2KDRIT2bdTAEAe85BDQ:P1 (envelope-from ) for ; Thu, 23 May 2024 15:44:20 +0200 Received: from aspmx1.migadu.com ([2001:41d0:403:58f0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2.migadu.com with LMTPS id oPs2KDRIT2bdTAEAe85BDQ (envelope-from ) for ; Thu, 23 May 2024 15:44:20 +0200 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=none ("invalid DKIM record") header.d=freakingpenguin.com header.s=x header.b=U7qbNDVy; dmarc=none; spf=pass (aspmx1.migadu.com: domain of "bug-guix-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="bug-guix-bounces+larch=yhetil.org@gnu.org" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1716471860; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding:resent-cc: resent-from:resent-sender:resent-message-id:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=RiDPCpLWCnGKPyRqXTF7rMVhBlf+2R6dZNVv/0XnH7w=; b=EXqToxJrvvUL2MEo0IITgN+BL18fgYMMhO9aPMwbC1pKQAsdmeDervHBqc5lMHP6n28J5U 9D3YAj5kDM+16e5PUtFATeqesDpaXKey82lvda/7vHcI6ufhc9OkYETeXjuOFSCWAfoA2+ pq/GTEt/oUAC0AiKrHgp23uEwhPnGl9jQiX5z1LLMVUrwHfnthcWtP9Wsu/CJEURNOBgCs 4KN5so5argFAn4D49lVtqoQn8iBl7TwTuukc6Fl98OlShQpOYIA38P1Hft8F8jqidKFQCT w95UQ+bpd2226ZnRMk4lAVl5wSFRrGC4yZA0eaP3pFCuzEeQ4iLsT9ffPmyajw== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1716471860; a=rsa-sha256; cv=none; b=udVL/br4KMwl6+VMXaQ3Y+7RgN85dq7lNJrX/FyIvHyVv9ko0bVMCTyLGW63hanyQVbMPf 5Kqn0B3C/GIwtyKpiOtaVeDW/B77TtSRfysTMwpTHdEU7VgmcVnh3cUMTxJkSJDXoReQX+ Bkdn7S6E10Y5rS0hSgcJZq9cJmTzWg5ijeiBkrw0TRR/8e2toNDor8/e5GGrA+/hhoKjmK cpJForbofu8Dr2YTtGQVM/HxdIKbKM61piXaNRrw3nUNu13+6r5OIYr0z69ANijU4sVF6R J/5hckuEZX2ba2BheibV5DzkqqfXAn5VIX2qWVLzW16uFeIQJ0G7axXjNS6B4Q== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=none ("invalid DKIM record") header.d=freakingpenguin.com header.s=x header.b=U7qbNDVy; dmarc=none; spf=pass (aspmx1.migadu.com: domain of "bug-guix-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="bug-guix-bounces+larch=yhetil.org@gnu.org" Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 770333CCAE for ; Thu, 23 May 2024 15:44:20 +0200 (CEST) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sA8je-0003cb-Dk; Thu, 23 May 2024 09:43:58 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sA8jb-0003bc-O5 for bug-guix@gnu.org; Thu, 23 May 2024 09:43:56 -0400 Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1sA8jb-0004zL-Fq for bug-guix@gnu.org; Thu, 23 May 2024 09:43:55 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1sA8jh-0002xH-Pv for bug-guix@gnu.org; Thu, 23 May 2024 09:44:01 -0400 X-Loop: help-debbugs@gnu.org Subject: bug#61173: Wireguard and NF Tables service broken on aarch64 Resent-From: Richard Sent Original-Sender: "Debbugs-submit" Resent-CC: bug-guix@gnu.org Resent-Date: Thu, 23 May 2024 13:44:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 61173 X-GNU-PR-Package: guix X-GNU-PR-Keywords: To: elais@fastmail.com Cc: 61173@debbugs.gnu.org Received: via spool by 61173-submit@debbugs.gnu.org id=B61173.171647183111346 (code B ref 61173); Thu, 23 May 2024 13:44:01 +0000 Received: (at 61173) by debbugs.gnu.org; 23 May 2024 13:43:51 +0000 Received: from localhost ([127.0.0.1]:59104 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1sA8jW-0002ww-Nq for submit@debbugs.gnu.org; Thu, 23 May 2024 09:43:51 -0400 Received: from mail-108-mta20.mxroute.com ([136.175.108.20]:46565) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1sA8jR-0002wl-Cv for 61173@debbugs.gnu.org; Thu, 23 May 2024 09:43:49 -0400 Received: from filter006.mxroute.com ([136.175.111.3] filter006.mxroute.com) (Authenticated sender: mN4UYu2MZsgR) by mail-108-mta20.mxroute.com (ZoneMTA) with ESMTPSA id 18fa5b158d0000efce.001 for <61173@debbugs.gnu.org> (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384); Thu, 23 May 2024 13:43:34 +0000 X-Zone-Loop: 9fb3f4534e3c936c1a666301b64e8cbaf6e079473b77 X-Originating-IP: [136.175.111.3] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=freakingpenguin.com; s=x; h=Content-Transfer-Encoding:Content-Type: MIME-Version:Message-ID:Date:References:In-Reply-To:Subject:Cc:To:From:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=RiDPCpLWCnGKPyRqXTF7rMVhBlf+2R6dZNVv/0XnH7w=; b=U7qbNDVyy4FIWbkS1pQNJV9trD CGb2XKpvStjYk8K/5/abLQFwsU/2smdSLCBxvpgY45vvkpEWv34K2ksdGT3DN41v849HMdntBDNVw YGile19iEOcV+J+2yFQD7vDToFqtAZNSc5GQ4LAavDHWHBAdSRKRzAGYNsikDWEPgNwze2yxZ7mb9 rW1G4RFIhbnyziODJ+GDz1zYea3bFdmdcPmTwi0RHi90cLqecBgkOjKXMIje58MnfSUbeZ/s3k+oP XUai7Dcn8W4cjsBTutO3V3HagpqpIuuh1c8lbfPFhnwqS1IgjoE3GmvBMdoTmdoMi3acyBoDlmXUY A4ecybhg==; From: Richard Sent In-Reply-To: (elais@fastmail.com's message of "Wed, 22 May 2024 21:48:06 -0700") References: <36296851-3bbf-4f7e-92d0-dd7006fd28fe@Spark> <7b54ca8e-5886-4a5b-8a5c-819a646b6bc9@Spark> <878r02f2g6.fsf@freakingpenguin.com> Date: Thu, 23 May 2024 09:43:25 -0400 Message-ID: <87zfsgve2q.fsf@freakingpenguin.com> User-Agent: Gnus/5.13 (Gnus v5.13) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Authenticated-Id: richard@freakingpenguin.com X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-guix@gnu.org List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+larch=yhetil.org@gnu.org Sender: bug-guix-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US X-Migadu-Spam-Score: -3.36 X-Spam-Score: -3.36 X-Migadu-Queue-Id: 770333CCAE X-Migadu-Scanner: mx11.migadu.com X-TUID: D2Q9p+mCK9D5 > Hi. It turns out you should use a `linux-libre` kernel same as you > would in x64. If you=E2=80=99re running arm64 then it will still build and > have all the features you expect. I forgot I filed a bug for this but > it=E2=80=99s resolved on my end now. Thanks for the tip. In my case I'm using a certain SBC and am in a catch-22 situation, so I still think there's a bug here: 1. Use linux-libre so kernel config options for various Guix services are set, but not have all the config options required to boot and run the board. 1. Adding config options with dependencies via customize-linux can best be described as a pain. [1] =20=20 2. Use linux-libre-arm64-generic to boot the board, but need to manually enable additional config options for every service that requires them. I can eventually either power through 1 or piece together the options I need for 2, but this behavior is definitely surprising. I have three proposed solutions in order of complexity: 1. The documentation for -generic kernels can be improved so their meaning is clearer. -generic as in "as close to upstream as possible". See [2]. 2. Add more entries to %default-extra-linux-options using config options required by various services. 3. A "linux-config-service" or similar could be created that other services extend with their required kernel support, if any. Of the 3, 3 seems the most elegant. It could easily complicate the substitutability of the kernel however. Perhaps it could simply be a system build-time check to confirm that the kernel's .config file does in fact have those options set. [1]: https://issues.guix.gnu.org/66355 [2]: https://issues.guix.gnu.org/43078#2 --=20 Take it easy, Richard Sent Making my computer weirder one commit at a time.