From: crodges <crodges@csphy.pw>
To: raingloom <raingloom@riseup.net>,
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: 55006@debbugs.gnu.org
Subject: bug#55006: First time boot hangs after "watchdog hardware is disabled"
Date: Tue, 19 Apr 2022 22:14:35 -0700 [thread overview]
Message-ID: <11963750.O9o76ZdvQC@sceadufaex> (raw)
In-Reply-To: <20220419202325.llvzfjsax74upigz@pelzflorian.localdomain>
[-- Attachment #1: Type: text/plain, Size: 929 bytes --]
On Tuesday, April 19, 2022 1:23:50 P.M. PDT pelzflorian (Florian Pelz) wrote:
> On Tue, Apr 19, 2022 at 06:55:11PM +0200, raingloom wrote:
> > Also IMHO this further proves my point that we need a "safe graphics
> > mode" boot option, see issue 54945.
>
> Well the uvesafb in the installer image worked for crodges, I suppose,
> so in the AMDGPU case there is no need for another boot option in the
> installer image.
>
> I’m not sure what to do about the installed system. There are
> multiple choices and all are bad. Currently by default after install
> you get a broken system unless nomodeset is added. The other libre
> options are not to use most of the expensive and powerful GPU.
>
> Regards,
> Florian
Well the issue was solved, I now have a bootable guix system. I'll consider my
options regarding the gpu. Thank you very much florian and raingloom. I
learned quite a few things!
crodges
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-04-20 5:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 17:32 bug#55006: First time boot hangs after "watchdog hardware is disabled" crodges
2022-04-19 8:50 ` pelzflorian (Florian Pelz)
2022-04-19 16:40 ` crodges
2022-04-19 16:55 ` raingloom
2022-04-19 20:23 ` pelzflorian (Florian Pelz)
2022-04-20 5:14 ` crodges [this message]
2022-04-19 19:54 ` 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=11963750.O9o76ZdvQC@sceadufaex \
--to=crodges@csphy.pw \
--cc=55006@debbugs.gnu.org \
--cc=pelzflorian@pelzflorian.de \
--cc=raingloom@riseup.net \
/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).