From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ludovic =?UTF-8?Q?Court=C3=A8s?= Subject: bug#36753: The GUI installer throws an error Date: Fri, 23 Aug 2019 22:54:13 +0200 Message-ID: <875zmn38ne.fsf@gnu.org> References: <87o91it6fs.fsf@gnu.org> <20190815003001.5af31f4f@kompiuter> <87lfvkj2bf.fsf@gnu.org> <20190823020245.5b037a18@kompiuter> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:59659) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i1GaN-0008Ri-5v for bug-guix@gnu.org; Fri, 23 Aug 2019 16:55:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1i1GaM-0007Z1-AN for bug-guix@gnu.org; Fri, 23 Aug 2019 16:55:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:60704) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1i1GaM-0007Yt-7i for bug-guix@gnu.org; Fri, 23 Aug 2019 16:55:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1i1GaM-0000sD-5j for bug-guix@gnu.org; Fri, 23 Aug 2019 16:55:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <20190823020245.5b037a18@kompiuter> (Jan's message of "Fri, 23 Aug 2019 02:02:45 +0200") 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: Jan Cc: 36753@debbugs.gnu.org Hi, Jan skribis: >> That you were able to continue without networking looks like a bug. >> However, I just tried, and when networking is unavailable, I get the >> =E2=80=9CConnection error=E2=80=9D box that only allows me to go back to= the =E2=80=9CChecking >> connectivity=E2=80=9D dialog; there=E2=80=99s no way to skip that AFAICS. > > Okay, I now know what *probably* have happened. My proprietary > motherboard - MSI PC Mate B350 tricked me - after updating the firmware > and enabling the "UEFI mode" instead of "UEFI or legacy BIOS" I got a > higher resolution and network started to work normally. Before enabling > it, the GUI installer couldn't find network connection itself, so I had > to manually configure network connection by using ifconfig and dhclient, > then I just followed the GUI installer, and it somehow let me continue > with or without networking.=20 > Tried switching back to BIOS mode, but I can't reproduce the bug > anymore. None of this happens on my librebooted machine, tried hard to > break the installation :). Guess that's it, thanks for your time. I'm > probably going to sell this nonfree machine anyway. OK, thanks for explaining; closing the bug. Ludo=E2=80=99.