Re: [gentoo-user] Re: switch from gnome/systemd to xfce/openrc borked my system - I GIVE UP
Nuno Silva wrote: On 2019-08-20, Raffaele Belardi wrote: Raffaele Belardi wrote: [...] - I grub-loaded a different kernel, one built for systemd. It stops in the exact same place as the openrc-built one. What are the kernel command lines for both kernels? I'm currently on a different system so, from the top of my head: For openrc something like "root=/dev/sda1 ro iommu=soft" For systemd "root=/dev/sda1 ro init=/path/to/systemd/init iommu=soft" iommu is required to workaround an USB3 issue on my motherboard. raffaele
Re: [gentoo-user] Re: switch from gnome/systemd to xfce/openrc borked my system
Daniel Frey wrote: On 8/19/19 5:24 AM, Raffaele Belardi wrote: 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. Did you update grub and remove the init= line that starts systemd? Yes. 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. Hmm, is it possible that it's waiting for entropy? Try moving the mouse like a madman for 20 seconds or so. I read on the internet about the crng delay issue. I don't think this is the case because it hangs after it has finished the random rc script, but I'll give it a try. raffaele
Re: [gentoo-user] Re: switch from gnome/systemd to xfce/openrc borked my system
On Monday, 19 August 2019 13:24:05 BST Raffaele Belardi wrote: > 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. It may be possible to hit CTRL-s to pause the scrolling, then CTRL-q to resume it. > > 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 -- Regards, Peter.
Re: [gentoo-user] Re: switch from gnome/systemd to xfce/openrc borked my system
On 8/19/19 5:24 AM, Raffaele Belardi wrote: 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. Did you update grub and remove the init= line that starts systemd? 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. Hmm, is it possible that it's waiting for entropy? Try moving the mouse like a madman for 20 seconds or so. Dan
Re: [gentoo-user] Re: switch from gnome/systemd to xfce/openrc borked my system
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
Re: [gentoo-user] Re: switch from gnome/systemd to xfce/openrc borked my system
On Monday, 19 August 2019 07:41:20 BST Raffaele Belardi wrote: > Raffaele Belardi wrote: > > One thing I notice from the boot log is that the root FS requires > > recovery. My live CDs did not let me because they are too old so I'll > > try to find a more up to date live CD. > Looking better at the kernel log, for sda1 (the root partition) it says: > "Recovery complete" so I don't think a new live CD will help. I'm really > out of ideas. > > raffaele 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. 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. 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. Make sure you are using a kernel set up for openrc. 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. ;-) I hope the above should allow you to boot, or at least arrive at some meaningful failure message to resolve. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
