From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:470:142:3::10]:32944) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jJz9b-0003Mz-7t for guix-patches@gnu.org; Thu, 02 Apr 2020 08:41:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jJz9a-00075T-2G for guix-patches@gnu.org; Thu, 02 Apr 2020 08:41:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:56036) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1jJz9Z-00075P-VX for guix-patches@gnu.org; Thu, 02 Apr 2020 08:41:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1jJz9Z-0007z0-Tk for guix-patches@gnu.org; Thu, 02 Apr 2020 08:41:01 -0400 Subject: [bug#40274] [PATCH v4] gnu: Add kernel-module-loader-service. Resent-Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Thu, 02 Apr 2020 12:40:00 +0000 From: Brice Waegeneire In-Reply-To: <20200401193458.evg46ygamtniby7k@pelzflorian.localdomain> References: <20200328135908.2540-1-brice@waegenei.re> <20200331202340.10054-1-brice@waegenei.re> <20200401193458.evg46ygamtniby7k@pelzflorian.localdomain> Message-ID: <64e7eade2865209e84940a1cbca3313a@waegenei.re> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: "pelzflorian (Florian Pelz)" Cc: 40274@debbugs.gnu.org Hello Florian, Thank you for trying out this new service. On 2020-04-01 19:34, pelzflorian (Florian Pelz) wrote: > I tried with your patch to make the Guix install image load the > uvesafb kernel module, but it fails and I get no log. Is it possible > to make the service log failures? > > I just get: > > failed to load service: kernel-module-loader > > printed on the console (but not to /var/log/messages). This a message saying it can't load that service, in this case because it's parameters weren't formatted correctly, this is not specific to this service that's how shepherd handle failing to load a service. Please open a new issue about it if you think (as I do) that shepherd should be more explicit when it fails to load a service. Regarding this service, logging has been implemented in v5; the output of modprobe will be logged if it fails, for example when trying to load an invalid kernel module like “foo”. - Brice