From: Sergey Petrov <sekk1e@yandex.ru>
To: 48343@debbugs.gnu.org
Subject: bug#48343: Cannot boot after installation
Date: Tue, 11 May 2021 13:43:28 +0700 [thread overview]
Message-ID: <674973b5-c35e-5a4e-0f3f-de2f3b6e782d@yandex.ru> (raw)
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..."
next reply other threads:[~2021-05-11 12:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 6:43 Sergey Petrov [this message]
2021-05-11 13:48 ` bug#48343: Cannot boot after installation Bone Baboon via Bug reports for GNU Guix
2021-05-11 14:14 ` Sergey Petrov
2021-05-11 21:24 ` Ludovic Courtès
2021-05-12 17:09 ` Sergey Petrov
2021-05-12 15:17 ` Brendan Tildesley via Bug reports for GNU Guix
2021-05-12 17:01 ` Sergey Petrov
2021-05-12 19:33 ` Bone Baboon via Bug reports for GNU Guix
2021-05-12 21:04 ` pelzflorian (Florian Pelz)
2021-05-13 17:28 ` Sergey Petrov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=674973b5-c35e-5a4e-0f3f-de2f3b6e782d@yandex.ru \
--to=sekk1e@yandex.ru \
--cc=48343@debbugs.gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.