From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adam Van Ymeren Subject: bug#30847: Cannot upgrade GuixSD due to check-device-initrd-modules Date: Sun, 18 Mar 2018 12:32:18 -0400 Message-ID: <87zi351h0t.fsf@vany.ca> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:38045) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1exbF3-0003df-UV for bug-guix@gnu.org; Sun, 18 Mar 2018 12:33:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1exbF0-0001aZ-PC for bug-guix@gnu.org; Sun, 18 Mar 2018 12:33:05 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:60627) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1exbF0-0001aV-LB for bug-guix@gnu.org; Sun, 18 Mar 2018 12:33:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1exbF0-0001AH-Fc for bug-guix@gnu.org; Sun, 18 Mar 2018 12:33:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: Received: from eggs.gnu.org ([2001:4830:134:3::10]:37957) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1exbER-0003aW-2P for bug-guix@gnu.org; Sun, 18 Mar 2018 12:32:27 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1exbEN-0001Ik-UI for bug-guix@gnu.org; Sun, 18 Mar 2018 12:32:27 -0400 Received: from mail2.vany.ca ([142.54.190.254]:33768) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1exbEN-0001I5-Op for bug-guix@gnu.org; Sun, 18 Mar 2018 12:32:23 -0400 Received: from adamvy-laptop (CPEac202e0a8da3-CMac202e0a8da0.cpe.net.cable.rogers.com [174.115.45.4]) by mail2.vany.ca (Postfix) with ESMTPSA id EBA5DAC0144 for ; Sun, 18 Mar 2018 11:32:19 -0500 (CDT) List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: 30847@debbugs.gnu.org My root device is on NVMe. In my current kernel config CONFIG_NVME_CORE is set to a module, which is included in my initrd. However upstream defconfig has been changed to CONFIG_NVME_CORE=y When trying to guix reconfigure my system, building the operating system fails in check-device-initrd-modules with the following message vany/systems.scm:111:10: error: you may need these modules in the initrd for /dev/nvme0n1p2: nvme shpchp hint: Try adding them to the `initrd-modules' field of your `operating-system' declaration, along these lines: (operating-system ;; ... (initrd-modules (append (list "nvme" "shpchp") %base-initrd-modules))) If I add initrd-modules to my operating-system, then building the initrd fails because nvme module cannot be found (as it is not being build as a module). Fundamentally I think the problem is that check-device-initrd-modules is checking modules for the currently running kernel which is not necessarily the kernel that I will be installing. At the very least however it would be nice if I could override this check with a --i-know-what-im-doing flag of some sort. It seems odd that check-device-initrd-modules will not prevent your installation from continuing if it can't find modules.alias, but if it can find it and you didn't specify the initrd-modules it thinks you need then it becomes a hard error that you can't override. Perhaps it should always be a warning or prompt the user if they want to continue.