From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: crodges <crodges@csphy.pw>
Cc: 55006@debbugs.gnu.org
Subject: bug#55006: First time boot hangs after "watchdog hardware is disabled"
Date: Tue, 19 Apr 2022 10:50:47 +0200 [thread overview]
Message-ID: <20220419085047.l34k7nnwtlj3mk74@pelzflorian.localdomain> (raw)
In-Reply-To: <4734468.31r3eYUQgx@sceadufaex>
On Mon, Apr 18, 2022 at 10:32:53AM -0700, crodges wrote:
> Hello,
>
> I'm installing guix in a recent desktop that I build (little more than a
> year). After being suggested to use latest iso on cuirass, I was able to
> install guix. The boot then hanged looking for iwlwifi firmware; someone in
> the help list suggested me to edit boot options and blacklist iwlwifi, then
> reconfigure guix once in.
>
> I did that and now booting process hangs in a new place, "Watchdog hardware is
> disabled". I include an image of the point.
>
> Thanks,
>
> crodges
Could you try to edit the boot options also to
- remove the `quiet`
- possibly you may need to add `nomodeset`.
What GPU is in this machine? On your Manjaro system, lspci or GNOME
Settings for example would show.
There are problems at least with some AMD GPUs, but this may not be
the issue.
(If it AMD turns out to be the issue, Denis 'GNUtoo' Carikli suggested
to partially fix them <https://issues.guix.gnu.org/36786#9>, while I
suggested to work around them <https://issues.guix.gnu.org/48343>.
Manjaro would not have these issues because it uses a nonfree linux
package. But your bug may be something completely different.)
Regards,
Florian
next prev parent reply other threads:[~2022-04-19 8:51 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) [this message]
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
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=20220419085047.l34k7nnwtlj3mk74@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=55006@debbugs.gnu.org \
--cc=crodges@csphy.pw \
/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).