From: Tom Willemse <tom@ryuslash.org>
To: Joshua Branson <jbranso@dismail.de>
Cc: help-guix@gnu.org
Subject: Re: Trouble booting Guix System
Date: Mon, 09 Nov 2020 22:45:52 -0800 [thread overview]
Message-ID: <87d00laevz.fsf@ryuslash.org> (raw)
In-Reply-To: <87d00ryiow.fsf@dismail.de> (Joshua Branson's message of "Thu, 05 Nov 2020 09:36:15 -0500")
Joshua Branson <jbranso@dismail.de> writes:
> I actually couldn't get encryption to work for my on my librebooted
> machine. I re-installed with just 1 unencrypted ext4 machine, and now I
> can use guix system. Not really a fix I know, but you might give that a try.
I've tried installing without encryption, but I still get the same
behavior. I did notice these lines in my messages log, I'm guessing this
certainly isn't good. I don't have any experience with the linux-libre
kernel, but I'm guessing it's a problem with my video card needing
non-free firmware?
amdgpu: mc: Failed to load firmware "/*(DEBLOBBED)*/"
[drm:gmc_v8_0_sw_init [amdgpu]] *ERROR* Failed to load mc firmware!
[drm:amdgpu_device_init [amdgpu]] *ERROR* sw_init of IP block <gmc_v8_0> failed -2
amdgpu 0000:03:00.0: amdgpu: amdgpu_device_ip_init failed
amdgpu 0000:03:00.0: amdgpu: Fatal error during GPU init
[drm] amdgpu: finishing device.
amdgpu: probe of 0000:03:00.0 failed with error -2
next prev parent reply other threads:[~2020-11-10 6:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 6:21 Trouble booting Guix System Tom Willemse
2020-11-05 14:36 ` Joshua Branson
2020-11-09 17:48 ` Tom Willemse
2020-11-10 6:45 ` Tom Willemse [this message]
2020-11-10 21:26 ` Joshua Branson
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=87d00laevz.fsf@ryuslash.org \
--to=tom@ryuslash.org \
--cc=help-guix@gnu.org \
--cc=jbranso@dismail.de \
/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.
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).