From: Leo Famulari <leo@famulari.name>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: 24948@debbugs.gnu.org
Subject: bug#24948: Illegible GRUB menu
Date: Wed, 16 Nov 2016 12:52:14 -0500 [thread overview]
Message-ID: <20161116175214.GA1262@jasmine> (raw)
In-Reply-To: <87fumrv0xe.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2121 bytes --]
On Wed, Nov 16, 2016 at 08:34:21AM -0800, Chris Marusich wrote:
> Leo Famulari <leo@famulari.name> writes:
>
> > On my Thinkpad x200s running GuixSD, the graphical GRUB menu is
> > scrambled and illegible. I've attached a photograph of the problem.
>
> I also have an x200 running GuixSD (with Libreboot). I do not
> experience this issue; the GRUB menu looks correct to me.
I have an x200s, which is a slightly different machine.
> Are you using Libreboot with the GRUB payload? If so, what version of
> Libreboot [1]? What version of GuixSD? If you are using recent
> versions and the issue is still happening, I wonder if perhaps your
> hardware is different from mine.
I'm using the BIOS that came with the computer when I bought it
second-hand; it appears to be from Lenovo. I don't know whether or not
the differences in our hardware would cause this issue. And like I said
before, this used to work for me.
> For comparison, this is some of my video info (information obtained
> using the 'lspci' program):
>
> --8<---------------cut here---------------start------------->8---
> 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
> 00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
> --8<---------------cut here---------------end--------------->8---
I see the same:
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
> I am using Guix version "20161116.06". I am using Libreboot version
> "r20160907".
I keep the system up to date, but it's not usually "vanilla" `guix
pull`. I normally reconfigure the system from a Git checkout, and
sometimes it has custom patches, or I use the core-updates branch, or
other things like that.
However, the problem is consistent, and it persists when I try using
Guix straight from `guix pull`, version 20161114.22.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2016-11-16 17:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 21:54 bug#24948: Illegible GRUB menu Leo Famulari
2016-11-16 16:34 ` Chris Marusich
2016-11-16 17:52 ` Leo Famulari [this message]
2016-11-17 8:26 ` Chris Marusich
2016-11-21 6:54 ` Mark H Weaver
2016-11-21 17:43 ` Leo Famulari
2016-11-27 1:20 ` Leo Famulari
2019-02-04 23:38 ` Leo Famulari
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=20161116175214.GA1262@jasmine \
--to=leo@famulari.name \
--cc=24948@debbugs.gnu.org \
--cc=cmmarusich@gmail.com \
/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).