From: Raffaele Belardi <raffaele.belardi@st.com>
To: <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Re: switch from gnome/systemd to xfce/openrc borked my system
Date: Mon, 19 Aug 2019 14:24:05 +0200 [thread overview]
Message-ID: <73c66f32-4026-561c-6f84-6d445b759b78@st.com> (raw)
In-Reply-To: <3492301.ddNJvlMHGk@localhost>
Mick wrote:
> On Monday, 19 August 2019 07:41:20 BST Raffaele Belardi wrote:
>
> You have 3 drives attached while you're trying to boot. The kernel seems to
> come to a stop after /dev/sdc. It may need some driver for this device/fs.
> I'd start by unplugging any drives which do not contain the system you're
> trying to boot, then go through a step by step process of installing/setting
> up openrc, DM and boot loader.
sdc is an external USB drive, I'll try to unplug that.
> The DM is not necessary to boot your system, but while you chrooted into it
> you might as well install and set up sddm as a DM - there are others but be
> careful they do not try to bring in 2/3 of Gnome and its dependencies too.
I'll do but first I want to see a working terminal, too much stuff to debug otherwise.
> Re-install GRUB or whichever boot manager you use and make sure it points to
> the correct kernel. If you're on an UEFI system and you boot directly using
> the kernel EFI stub, re-run efibootmgr to specify the kernel UEFI will boot
> with, but first run fsck.vfat on the EFI partition just in case this fs was
> messed up too.
It's grub2, non-UEFI. I don't normally reinstall it when I update the kernel, I only run
grub-mkconfig. I did the same this time.
> Make sure you are using a kernel set up for openrc.
Good catch, although I'm not sure where to find that info in the available kernel log.
I'll look better, I need to stop it from scrolling.
> In /etc/rc.conf set up a log file and temporarily enable logging. If any
> openrc scripts fail and can't boot, you will able to look at the logs when you
> chroot back into it - using less/cat/plain text editor. ;-)
Good idea.
> I hope the above should allow you to boot, or at least arrive at some
> meaningful failure message to resolve.
>
One of the last things printed in the kernel log is "random: crng init done". The random
service is part (possibly the last service) of the boot runlevel which is entered after
the sysinit runlevel. So apparently a lot of openrc stuff has already started
successfully. Instead, nothing from the default runlevel is output. I'll re-check those
services.
raffaele
next prev parent reply other threads:[~2019-08-19 12:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 6:29 [gentoo-user] switch from gnome/systemd to xfce/openrc borked my system Raffaele Belardi
2019-08-19 6:41 ` [gentoo-user] " Raffaele Belardi
2019-08-19 11:19 ` Mick
2019-08-19 12:24 ` Raffaele Belardi [this message]
2019-08-19 14:20 ` Daniel Frey
2019-08-19 14:25 ` Raffaele Belardi
2019-08-19 14:24 ` Peter Humphrey
2019-08-19 11:51 ` [gentoo-user] " David Haller
2019-08-19 12:32 ` Raffaele Belardi
2019-08-19 13:52 ` Rich Freeman
2019-08-19 14:42 ` Raffaele Belardi
2019-08-19 15:39 ` Rich Freeman
2019-08-20 6:26 ` [gentoo-user] switch from gnome/systemd to xfce/openrc borked my system - I GIVE UP Raffaele Belardi
2019-08-20 13:56 ` [gentoo-user] " Nuno Silva
2019-08-21 7:26 ` Raffaele Belardi
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=73c66f32-4026-561c-6f84-6d445b759b78@st.com \
--to=raffaele.belardi@st.com \
--cc=gentoo-user@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox