unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Niels Felsted <niels@pdlkrft.eu>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 40599@debbugs.gnu.org
Subject: bug#40599: 1.1.0rc2 i686 gui install unreadable
Date: Tue, 14 Apr 2020 20:20:09 +0200	[thread overview]
Message-ID: <87d08aszdy.fsf@ficus.lan> (raw)
In-Reply-To: <87a73evzu3.fsf@gnu.org> ("Ludovic Courtès"'s message of "Tue, 14 Apr 2020 17:42:12 +0200")

Hi Ludovic

Ludovic Courtès <ludo@gnu.org> writes:

> Hi Niels & Florian,
>
> "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:
>
>> On Tue, Apr 14, 2020 at 03:06:25PM +0200, Niels Felsted wrote:
>>> And testing Florians suggestions:
>>> 
>>> setting 'nomodeset' kernel parameter -> screen displays fine
>>> 
>>> setting 'modprobe.blacklist=i915' kernel parameter -> screen displays fine
>>> 
>>> As mentioned before, I did manage to install guix via tty3 (without
>>> setting any kernel parameters), and it boots up fine with
>>> gdm3/xfce4. So it is only the initial boot from the install iso that's
>>> distorted.
>>
>> Thank you for the testing!  Xorg working confirms that uvesafb really
>> is the source of the problem.  This is good to know.  I have hope that
>> this issue is fixed by commit 0ad60b2a89d6d387236466e0bcdd61ac489fca37
>> that loads uvesafb only if it cannot already detect a frame buffer
>> device.  I do not have a downloadable image for confirming the fix
>> though.
>
> Niels, here’s a new ISO image built from commit
> bd4c345ef7ddf3542662fe0872b06393b414a3fc, which includes Florian’s fix.
>
>   https://web.fdn.fr/~lcourtes/software/guix/1.1.0rc2.5/
>
> Could you simply boot that image, without any additional kernel
> arguments, and confirm that the installer now displays correctly?  (You
> don’t need to run the actual install.)

1.1.0rc2.5 works fine here!

br
Niels

  reply	other threads:[~2020-04-14 18:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-13 14:02 bug#40599: 1.1.0rc2 i686 gui install unreadable Niels Felsted
2020-04-13 20:36 ` Ludovic Courtès
2020-04-13 20:51   ` pelzflorian (Florian Pelz)
2020-04-13 20:56     ` Ludovic Courtès
2020-04-14  0:48       ` pelzflorian (Florian Pelz)
2020-04-14 13:06   ` Niels Felsted
2020-04-14 13:22     ` pelzflorian (Florian Pelz)
2020-04-14 15:42       ` Ludovic Courtès
2020-04-14 18:20         ` Niels Felsted [this message]
2020-04-14 18:48           ` pelzflorian (Florian Pelz)
2020-04-14 20:01             ` Ludovic Courtès
2020-04-13 21:06 ` pelzflorian (Florian Pelz)
2020-04-13 21:48   ` pelzflorian (Florian Pelz)

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=87d08aszdy.fsf@ficus.lan \
    --to=niels@pdlkrft.eu \
    --cc=40599@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    /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).