all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: help-guix@gnu.org
Subject: Re: GuixSD on a laptop with Heads
Date: Wed, 01 May 2019 13:19:12 +0200	[thread overview]
Message-ID: <87d0l24e33.fsf@nckx> (raw)
In-Reply-To: <f82e45f8-e40a-47dc-9129-3073cd066bf4@www.fastmail.com>

[-- Attachment #1: Type: text/plain, Size: 1346 bytes --]

Jonathan,

I haven't flashed Heads myself, but am passingly familiar with it 
since I do basically the same thing on my hardware including an 
X230 (and intend to recreate that on top of Guix, eventually).

Jonathan Frederickson wrote:
> However, I'm running into some issues when attempting to boot 
> into the new kernel - the moment I run kexec, I get no output 
> onscreen from the new kernel:
>
> https://imgur.com/a/r2lFD7k
>
> I've tried adding the usual debug flags to the kernel command 
> line for troubleshooting (debug, higher LOGLEVEL, earlyprintk to 
> vga) with no change.

That won't help if there's nowhere to print to.  From your 
screenshot, you're not in VGA mode, for example.  Is that 
screenshot from within Heads?  Which graphics driver is Heads 
using at that point?  Have you tried adding the same driver to the 
initrd?

  (initrd-modules (cons* "i915" %base-initrd-modules)))

It's also possible that Heads uses the Coreboot ‘simple’ 
framebuffer, for which you'll have to set at least the following 
kernel options:

  FB_SIMPLE=y
  GOOGLE_FIRMWARE=y
  GOOGLE_COREBOOT_TABLE=y
  GOOGLE_FRAMEBUFFER_COREBOOT=y

[Google isn't even being coy about stealing credit for others' 
work anymore.]

Unfortunately, that requires compiling a custom kernel.

Just some ideas,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  parent reply	other threads:[~2019-05-01 11:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-01  3:01 GuixSD on a laptop with Heads Jonathan Frederickson
2019-05-01  9:41 ` Mark H Weaver
2019-05-02  1:21   ` Mike Gerwitz
2019-05-01 11:19 ` Tobias Geerinckx-Rice [this message]
2019-05-02  2:07   ` Jonathan Frederickson

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d0l24e33.fsf@nckx \
    --to=me@tobias.gr \
    --cc=help-guix@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.