First time boot hangs after "watchdog hardware is disabled"

Open

Details

3 participants

crodges
pelzflorian (Florian Pelz)
raingloom

Owner: unassigned

Submitted by: crodges

Severity: normal

Merged with

48343

crodges wrote on 18 Apr 2022 19:32

Recipients:(address . bug-guix@gnu.org)

Message-ID:4734468.31r3eYUQgx@sceadufaex

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

Attachment: guix-watchdog-booting-bug.jpeg

pelzflorian (Florian Pelz) wrote on 19 Apr 2022 10:50

Recipients:(name . crodges)(address . crodges@csphy.pw)(address . 55006@debbugs.gnu.org)

Message-ID:20220419085047.l34k7nnwtlj3mk74@pelzflorian.localdomain

On Mon, Apr 18, 2022 at 10:32:53AM -0700, crodges wrote:

Toggle quote (15 lines)> 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

crodges wrote on 19 Apr 2022 18:40

Recipients:(name . pelzflorian (Florian Pelz))(address . pelzflorian@pelzflorian.de)(address . 55006@debbugs.gnu.org)

Message-ID:1813795.tdWV9SEqCh@sceadufaex

On Tuesday, April 19, 2022 1:50:47 A.M. PDT pelzflorian (Florian Pelz) wrote:

Toggle quote (38 lines)> 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

Florian,

Removing quiet and adding nomodeset, I was able to boot for the first time!

low resolution, but I was able to edit config.scm to add

(kernel-arguments

'(; https://issues.guix.gnu.org/53712#12

"modprobe.blacklist=pcspkr,snd_pcsp,iwlwifi"))

as referenced in https://issues.guix.gnu.org/53712#13

then did guix pull and sudo guix system reconfigure /etc/config.scm

Noticed that the kernel was updated to linux-libre 5.16.20. Tried to reboot

without editing arguments in the kernel. I got to another freeze, and clearly

it seems to be the amd gpu, as in the new attached image. Is it possible,

considering that this gpu has free software drivers?

The GPU is a Radeon RX 6800 XT, which manjaro lists as using open source

drivers.

Attachment: guix-amd-bug-boot.jpeg

raingloom wrote on 19 Apr 2022 18:55

Recipients:(name . crodges)(address . crodges@csphy.pw)

Message-ID:20220419185508.6066aa73@riseup.net

On Tue, 19 Apr 2022 09:40:20 -0700

crodges <crodges@csphy.pw> wrote:

Toggle quote (65 lines)> On Tuesday, April 19, 2022 1:50:47 A.M. PDT pelzflorian (Florian
> Pelz) wrote:
> > 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  
> Florian, 
> 
> Removing quiet and adding nomodeset, I was able to boot for the first
> time! low resolution, but I was able to edit config.scm to add 
> 
> (kernel-arguments
>  '(; https://issues.guix.gnu.org/53712#12
>    "modprobe.blacklist=pcspkr,snd_pcsp,iwlwifi"))
> 
> as referenced in https://issues.guix.gnu.org/53712#13
> 
> then did guix pull and sudo guix system reconfigure /etc/config.scm
> 
> Noticed that the kernel was updated to linux-libre 5.16.20. Tried to
> reboot without editing arguments in the kernel. I got to another
> freeze, and clearly it seems to be the amd gpu, as in the new
> attached image. Is it possible, considering that this gpu has free
> software drivers?  
> 
> The GPU is a Radeon RX 6800 XT, which manjaro lists as using open
> source drivers.
> 
> 

The funny thing is that AMDGPU is not really entirely free software,
only the kernel component is, but the firmwares are not. Guix doesn't
actually package AMDGPU as far as I know, you have to use The Forbidden
Channel if you have an AMD card and want to actually use it. But also
yes, it's super buggy for me as well, sometimes it freezes, sometimes
it just glitches out.

Also IMHO this further proves my point that we need a "safe graphics
mode" boot option, see issue 54945.

pelzflorian (Florian Pelz) wrote on 19 Apr 2022 21:54

Recipients:(name . crodges)(address . crodges@csphy.pw)(address . 55006@debbugs.gnu.org)

Message-ID:20220419195404.hjwve7q7eb272kby@pelzflorian.localdomain

Hi crodges,

On Tue, Apr 19, 2022 at 09:40:20AM -0700, crodges wrote:

Toggle quote (5 lines)

> Noticed that the kernel was updated to linux-libre 5.16.20. Tried to reboot

> without editing arguments in the kernel. I got to another freeze, and clearly

> it seems to be the amd gpu, as in the new attached image. Is it possible,

> considering that this gpu has free software drivers?

I proposed removing quiet so more messages would get printed to the

screen, but your photo already shows everything.

So this is bad news. Technically the amdgpu drivers themselves are

free software, but they require nonfree firmware, and linux-libre

removes it.

With linux-libre, there is therefore no way to use the GPU for 3D

acceleration, I believe.

In your original post, you said you succeeded in installing Guix

System with the installer image. The installer image uses

uvesafb-service-type when amdgpu fails, so you could do the same.

See the installer’s configuration file at:

~/.config/guix/current/share/guile/site/3.0/gnu/system/install.scm

The workaround I suggested at

On Tue, Apr 19, 2022 at 10:50:47AM +0200, pelzflorian (Florian Pelz) wrote:

Toggle quote (6 lines)

> (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.)

is a more concise way to unconditionally load uvesafb, even for

graphical desktops. Denis’ suggestion to fix the driver is a more

proper solution but more work, if it works. Either way you won’t be

able to use accelerated 3D with linux-libre.

I’m merging this bug with 48343.

Regards,

Florian

pelzflorian (Florian Pelz) wrote on 19 Apr 2022 21:56

merge 55006 48343

Recipients:(address . request@debbugs.gnu.org)

Message-ID:20220419195600.5gisfzgc6yhzpte6@pelzflorian.localdomain

merge 55006 48343

quit

pelzflorian (Florian Pelz) wrote on 19 Apr 2022 22:23

Re: bug#55006: First time boot hangs after "watchdog hardware is disabled"

Recipients:(name . raingloom)(address . raingloom@riseup.net)

Message-ID:20220419202325.llvzfjsax74upigz@pelzflorian.localdomain

On Tue, Apr 19, 2022 at 06:55:11PM +0200, raingloom wrote:

Toggle quote (3 lines)

> 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

crodges wrote on 20 Apr 2022 07:14

Recipients:(address . 55006@debbugs.gnu.org)

Message-ID:11963750.O9o76ZdvQC@sceadufaex

On Tuesday, April 19, 2022 1:23:50 P.M. PDT pelzflorian (Florian Pelz) wrote:

Toggle quote (15 lines)> 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

Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 55006@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it

mumi current 55006

Then, you may apply the latest patchset in this issue (with sign off)

mumi am -- -s

Or, compose a reply to this issue

mumi compose

Or, send patches to this issue

mumi send-email *.patch

is:open	open issues
is:done	closed issues
submitter:<who>	search issue submitter
author:<who>	search by message author
date:yesterday..now	search by issue date
mdate:3m..2d	search by message date