Cannot boot after installation

  • Open
  • quality assurance status badge
Details
5 participants
  • Bone Baboon
  • Brendan Tildesley
  • Ludovic Courtès
  • pelzflorian (Florian Pelz)
  • Sergey Petrov
Owner
unassigned
Submitted by
Sergey Petrov
Severity
normal
Merged with
S
S
Sergey Petrov wrote on 11 May 2021 08:43
(address . bug-guix@gnu.org)
674973b5-c35e-5a4e-0f3f-de2f3b6e782d@yandex.ru
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..."
B
B
Bone Baboon wrote on 11 May 2021 15:48
(name . Sergey Petrov)(address . sekk1e@yandex.ru)
87im3pfkjr.fsf@disroot.org
Sergey Petrov writes:

Toggle quote (27 lines)
> 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))
```
S
S
Sergey Petrov wrote on 11 May 2021 16:14
(name . Bone Baboon)(address . bone.baboon@disroot.org)
6042e78b-15ba-08d4-22e5-69290e8753c8@yandex.ru
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:
Toggle quote (41 lines)
> 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))
> ```
L
L
Ludovic Courtès wrote on 11 May 2021 23:24
(name . Sergey Petrov)(address . sekk1e@yandex.ru)
878s4lufpd.fsf@gnu.org
Hi Sergey,

Sergey Petrov <sekk1e@yandex.ru> skribis:

Toggle quote (3 lines)
> 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’.
B
B
Brendan Tildesley wrote on 12 May 2021 17:17
Cannot boot after installation
(name . 48343@debbugs.gnu.org)(address . 48343@debbugs.gnu.org)(name . Sergey Petrov)(address . sekk1e@yandex.ru)
1979417313.259515.1620832627276@office.mailbox.org
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: file
S
S
Sergey Petrov wrote on 12 May 2021 19:01
bde404b2-a75e-810f-96ee-5bc9cf029623@yandex.ru
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:
Toggle quote (13 lines)
> 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: file
S
S
Sergey Petrov wrote on 12 May 2021 19:09
Re: bug#48343: Cannot boot after installation
(name . Ludovic Courtès)(address . ludo@gnu.org)
673f50f6-7393-d6d6-eae4-d4b506635bfd@yandex.ru
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:
Toggle quote (12 lines)
> 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’.
B
B
Bone Baboon wrote on 12 May 2021 21:33
(name . Sergey Petrov)(address . sekk1e@yandex.ru)
87zgwzeogw.fsf@disroot.org
Looks like you are running into many of the problems I had when I
installed Guix on a computer.

Sergey Petrov writes:
Toggle quote (15 lines)
> 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.

Toggle quote (3 lines)
> 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:
P
P
pelzflorian (Florian Pelz) wrote on 12 May 2021 23:04
(name . Bone Baboon)(address . bone.baboon@disroot.org)
20210512210430.wgi3dvh4n3py2m5z@pelzflorian.localdomain
On Wed, May 12, 2021 at 03:33:51PM -0400, Bone Baboon via Bug reports for GNU Guix wrote:
Toggle quote (8 lines)
> 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.:


Regards,
Florian
S
S
Sergey Petrov wrote on 13 May 2021 19:28
(name . Bone Baboon)(address . bone.baboon@disroot.org)
ee9ecd75-0afd-8b32-ff3c-2bb3ede223a2@yandex.ru
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:
Toggle quote (3 lines)
> 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
P
P
pelzflorian (Florian Pelz) wrote on 19 Apr 2022 21:56
merge 55006 48343
(address . request@debbugs.gnu.org)
20220419195600.5gisfzgc6yhzpte6@pelzflorian.localdomain
merge 55006 48343
quit
?
Your comment

Commenting via the web interface is currently disabled.

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

To respond to this issue using the mumi CLI, first switch to it
mumi current 48343
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