From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: bug#24948: Illegible GRUB menu Date: Sat, 26 Nov 2016 20:20:33 -0500 Message-ID: <20161127012033.GA10808@jasmine> References: <20161115215443.GA28213@jasmine> <8737ilnx11.fsf@netris.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:39157) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cAo9V-0006aU-Fw for bug-guix@gnu.org; Sat, 26 Nov 2016 20:21:10 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cAo9Q-0001XG-AH for bug-guix@gnu.org; Sat, 26 Nov 2016 20:21:09 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:55612) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cAo9P-0001X5-Sv for bug-guix@gnu.org; Sat, 26 Nov 2016 20:21:04 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1cAo9P-0000t1-Il for bug-guix@gnu.org; Sat, 26 Nov 2016 20:21:03 -0500 Sender: "Debbugs-submit" Resent-Message-ID: Content-Disposition: inline In-Reply-To: <8737ilnx11.fsf@netris.org> 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: Mark H Weaver Cc: 24948@debbugs.gnu.org On Mon, Nov 21, 2016 at 01:54:02AM -0500, Mark H Weaver wrote: > A few months ago we updated our grub from 2.00 to 2.02beta3, in commit > 4c7260011e219eb3ebf5da976ab107dbd5997829, dated June 16. Was that > roughly when this problem began? > > If so, I suggest reverting that commit in your local tree, to see if > downgrading to grub 2.00 fixes the problem. I reverted the following commits ... 4c7260011e21 (gnu: grub: Update to 2.02~beta3.) 358db0041f09 (gnu: grub: Make dependency on mdadm explicit.) ... on top of 1cd1d8a7ea43 (offload: Call 'machine-load' only once per machine.) I had to revert the second commit since it depended on changes in the first. I reconfigured and rebooted, but this didn't fix the problem for me.