From: "Ludovic Courtès" <ludo@gnu.org>
To: Jan <tona_kosmicznego_smiecia@interia.pl>
Cc: 36753@debbugs.gnu.org
Subject: bug#36753: The GUI installer throws an error
Date: Fri, 23 Aug 2019 22:54:13 +0200 [thread overview]
Message-ID: <875zmn38ne.fsf@gnu.org> (raw)
In-Reply-To: <20190823020245.5b037a18@kompiuter> (Jan's message of "Fri, 23 Aug 2019 02:02:45 +0200")
Hi,
Jan <tona_kosmicznego_smiecia@interia.pl> 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
>> “Connection error” box that only allows me to go back to the “Checking
>> connectivity” dialog; there’s 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.
> 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’.
next prev parent reply other threads:[~2019-08-23 20:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tvkprtjlzlkrwomzieth@apau>
2019-07-25 16:39 ` bug#36753: The GUI installer throws an error Ludovic Courtès
2019-08-14 22:30 ` Jan
2019-08-22 21:52 ` Ludovic Courtès
2019-08-23 0:02 ` Jan
2019-08-23 20:54 ` Ludovic Courtès [this message]
2019-08-14 11:52 ` Jan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875zmn38ne.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=36753@debbugs.gnu.org \
--cc=tona_kosmicznego_smiecia@interia.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).