bug#48343: Cannot boot after installation

bug#48343: Cannot boot after installation

[Sergey Petrov]

Hi! I've installed ordinary guix system following graphical installer, 
but can't boot it, here what I got after installation complete:

GC Warning: pthread_getattr_pp or pthread_attr_getstack failed for main 
thread GC Warning:
Couldn't read /proc/stat
Welcome, this is GMU's early boot Guile.
Use '--repl' for an initrd REPL.

loading kernel modules...
/dev/nvme0n1p8: clean,
134898/5169152 files, 1320485/20649216 blocks
loading '/gnu/store/519yr5adx95d26s3nu65mjOcc9731630-system/boot...
making '/gnu/store/519yr5adx95d26s3nu65mj0cc9731630-system' the current 
system...
setting up setuid programs in '/run/setuid-programs'...
populating /etc from /gnu/store/d6k3c7p2s6ji0ix2g3lafx4iwOd43a98-etc...
error in finalization thread: Success
[   3.049660] udevd[272]: no sender credentials received, message ignored
[   3.098019] sp5100-tco sp5100-tco: Watchdog hardware is disabled
[   3.104103] Error: Driver 'pcspkr' is already registered, aborting...
[   3.180575] kvm: disabled by bios

At this point computer hangs infinitely, and if I enable CPU 
virtualization in BIOS it starts to hang at line "[   3.104103] Error: 
Driver 'pcspkr' is already registered, aborting..."

bug#48343: Cannot boot after installation

[Bone Baboon via Bug reports for GNU Guix]

Sergey Petrov writes:

> Hi! I've installed ordinary guix system following graphical installer,
> but can't boot it, here what I got after installation complete:
>
> GC Warning: pthread_getattr_pp or pthread_attr_getstack failed for
> main thread GC Warning:
> Couldn't read /proc/stat
> Welcome, this is GMU's early boot Guile.
> Use '--repl' for an initrd REPL.
>
> loading kernel modules...
> /dev/nvme0n1p8: clean,
> 134898/5169152 files, 1320485/20649216 blocks
> loading '/gnu/store/519yr5adx95d26s3nu65mjOcc9731630-system/boot...
> making '/gnu/store/519yr5adx95d26s3nu65mj0cc9731630-system' the
> current system...
> setting up setuid programs in '/run/setuid-programs'...
> populating /etc from /gnu/store/d6k3c7p2s6ji0ix2g3lafx4iwOd43a98-etc...
> error in finalization thread: Success
> [   3.049660] udevd[272]: no sender credentials received, message ignored
> [   3.098019] sp5100-tco sp5100-tco: Watchdog hardware is disabled
> [   3.104103] Error: Driver 'pcspkr' is already registered, aborting...
> [   3.180575] kvm: disabled by bios
>
> At this point computer hangs infinitely, and if I enable CPU
> virtualization in BIOS it starts to hang at line "[   3.104103] Error: 
> Driver 'pcspkr' is already registered, aborting..."

I ran into a similar issue with a computer I installed Guix on.  It
would not complete the boot up process.  I am not sure if I was
experiencing the same issue you are as I did not submit it to a Guix
mailing list.  I got help solving it on #guix.  What worked for me was
to add the Linux kernel argument `nomodeset` to my system configuration.
In the operating system declaration of the system configuration I added:

```
  (kernel-arguments
   (append
    (list "nomodeset")
    %default-kernel-arguments))
```

bug#48343: Cannot boot after installation

[Sergey Petrov]

Hm, I've added these lines to the etc/config.scm, tried to boot again 
and it doesn't seem to change anything...

On 5/11/21 8:48 PM, Bone Baboon wrote:
> Sergey Petrov writes:
>
>> Hi! I've installed ordinary guix system following graphical installer,
>> but can't boot it, here what I got after installation complete:
>>
>> GC Warning: pthread_getattr_pp or pthread_attr_getstack failed for
>> main thread GC Warning:
>> Couldn't read /proc/stat
>> Welcome, this is GMU's early boot Guile.
>> Use '--repl' for an initrd REPL.
>>
>> loading kernel modules...
>> /dev/nvme0n1p8: clean,
>> 134898/5169152 files, 1320485/20649216 blocks
>> loading '/gnu/store/519yr5adx95d26s3nu65mjOcc9731630-system/boot...
>> making '/gnu/store/519yr5adx95d26s3nu65mj0cc9731630-system' the
>> current system...
>> setting up setuid programs in '/run/setuid-programs'...
>> populating /etc from /gnu/store/d6k3c7p2s6ji0ix2g3lafx4iwOd43a98-etc...
>> error in finalization thread: Success
>> [   3.049660] udevd[272]: no sender credentials received, message ignored
>> [   3.098019] sp5100-tco sp5100-tco: Watchdog hardware is disabled
>> [   3.104103] Error: Driver 'pcspkr' is already registered, aborting...
>> [   3.180575] kvm: disabled by bios
>>
>> At this point computer hangs infinitely, and if I enable CPU
>> virtualization in BIOS it starts to hang at line "[   3.104103] Error:
>> Driver 'pcspkr' is already registered, aborting..."
> I ran into a similar issue with a computer I installed Guix on.  It
> would not complete the boot up process.  I am not sure if I was
> experiencing the same issue you are as I did not submit it to a Guix
> mailing list.  I got help solving it on #guix.  What worked for me was
> to add the Linux kernel argument `nomodeset` to my system configuration.
> In the operating system declaration of the system configuration I added:
>
> ```
>    (kernel-arguments
>     (append
>      (list "nomodeset")
>      %default-kernel-arguments))
> ```

bug#48343: Cannot boot after installation

[Ludovic Courtès]

Hi Sergey,

Sergey Petrov <sekk1e@yandex.ru> skribis:

> Hm, I've added these lines to the etc/config.scm, tried to boot again
> and it doesn't seem to change anything...

Note that /etc/config.scm doesn’t have any effect in itself.  You need
to run ‘guix system reconfigure /etc/config.scm’ to deploy the changes
you made.

HTH,
Ludo’.

bug#48343: Cannot boot after installation

[Sergey Petrov]

Thanks, I've planned to read docs about it right after I can boot to guix :)

On 5/12/21 4:24 AM, Ludovic Courtès wrote:
> Hi Sergey,
>
> Sergey Petrov <sekk1e@yandex.ru> skribis:
>
>> Hm, I've added these lines to the etc/config.scm, tried to boot again
>> and it doesn't seem to change anything...
> Note that /etc/config.scm doesn’t have any effect in itself.  You need
> to run ‘guix system reconfigure /etc/config.scm’ to deploy the changes
> you made.
>
> HTH,
> Ludo’.

bug#48343: Cannot boot after installation

[Brendan Tildesley via Bug reports for GNU Guix]

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

If setting nomodeset is the answer, there is a trick you can use in GRUB to set it before boot.
Apparently in GRUB, you:

1. Press e
2. Edit the linux ... line to add nomodeset as an option
3. Press ctrl X

I just found the instructions here https://duckduckgo.com/?q=grub+nomode+set

At least give that a go and report back if it works.

[-- Attachment #2: Type: text/html, Size: 1063 bytes --]

bug#48343: Cannot boot after installation

[Sergey Petrov]

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

Hi Brendan! It works, I can proceed to system now, but terminal only, my 
WM (Enlightenment) cannot initialize. I think I can give a try to some 
other WMs and check how it goes.

On 5/12/21 10:17 PM, Brendan Tildesley wrote:
> If setting nomodeset is the answer, there is a trick you can use in 
> GRUB to set it before boot.
> Apparently in GRUB, you:
>
> 1. Press e
> 2. Edit the linux ... line to add nomodeset as an option
> 3. Press ctrl X
>
> I just found the instructions here 
> https://duckduckgo.com/?q=grub+nomode+set 
> <https://duckduckgo.com/?q=grub+nomode+set>
>
> At least give that a go and report back if it works.

[-- Attachment #2: Type: text/html, Size: 1598 bytes --]

bug#48343: Cannot boot after installation

[Bone Baboon via Bug reports for GNU Guix]

Looks like you are running into many of the problems I had when I
installed Guix on a computer.

Sergey Petrov writes:
> Hi Brendan! It works, I can proceed to system now
>
> On 5/12/21 10:17 PM, Brendan Tildesley wrote:
>> If setting nomodeset is the answer, there is a trick you can use in
>> GRUB to set it before boot.
>> Apparently in GRUB, you:
>>
>> 1. Press e
>> 2. Edit the linux ... line to add nomodeset as an option
>> 3. Press ctrl X
>>
>> I just found the instructions here
>> https://duckduckgo.com/?q=grub+nomode+set 
>> <https://duckduckgo.com/?q=grub+nomode+set>

If you were able to manually use nomodeset in Grub then you should be
able to add that snippet for the Linux kernel argument nomodeset that I
shared and reconfigure your system.  Then you will not need to manually
enter nomodeset in Grub each time you boot.

> but terminal only, my WM (Enlightenment) cannot initialize. I think I
> can give a try to some other WMs and check how it goes.

You may find this has useful information in regards to getting a
graphical environment working:
https://lists.gnu.org/archive/html/help-guix/2021-04/msg00220.html

bug#48343: Cannot boot after installation

[pelzflorian (Florian Pelz)]

On Wed, May 12, 2021 at 03:33:51PM -0400, Bone Baboon via Bug reports for GNU Guix wrote:
> Sergey Petrov writes:
> > but terminal only, my WM (Enlightenment) cannot initialize. I think I
> > can give a try to some other WMs and check how it goes.
> 
> You may find this has useful information in regards to getting a
> graphical environment working:
> https://lists.gnu.org/archive/html/help-guix/2021-04/msg00220.html

Another WM would be the leaner solution, however maybe uvesafb (which
is also used in the installer image) can help you set up GNOME etc.:

https://lists.gnu.org/archive/html/bug-guix/2020-04/msg00320.html

Regards,
Florian

bug#48343: Cannot boot after installation

[Sergey Petrov]

I've read it, and I guess that my graphics is not supported because 
there is no /dev/dri directory. Thank you!

On 5/13/21 2:33 AM, Bone Baboon wrote:
> You may find this has useful information in regards to getting a
> graphical environment working:
> https://lists.gnu.org/archive/html/help-guix/2021-04/msg00220.html