Skip to main content
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: X won't start after cold reboot, but starts after rebooting out of Ubuntu (Read 1776 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: X won't start after cold reboot, but starts after rebooting out of Ubuntu

Reply #15
Yeah parallel mode in openrc still isn't 100% guaranteed yet. It probably works fine for most people, but OP could just be an unlucky fellow. Adjusting the depends and stuff around, it should be fixable though.


Re: X won't start after cold reboot, but starts after rebooting out of Ubuntu

Reply #17
Still looks like a synchronization problem to me. If you want, boot the system twice, one with rc_parallel="YES" and another one without and check /var/log/rc.log to see the order of services brought up. Interesting comments from rc.conf.

# Set to "YES" if you want the rc system to try and start services
# in parallel for a slight speed improvement. When running in parallel we
# prefix the service output with its name as the output will get
# jumbled up.
# WARNING: whilst we have improved parallel, it can still potentially lock
# the boot process. Don't file bugs about this unless you can supply
# patches that fix it without breaking other things!


To play safe, maybe you should leave parallel option to "NO".
Here is the section from rc.log when I did a cold boot with parallel = YES, and X did not start:
Code: [Select]
rc boot logging started at Thu Nov  4 09:13:54 2021

modules           | * Loading module crypto_user ...
termencoding      | * Setting terminal encoding [UTF-8] ...
 [ ok ]
keymaps           | * Setting keyboard mode [UTF-8] ...
 [ ok ]
 [ ok ]
keymaps           | * Loading key mappings [us] ...
 [ ok ]
hwclock           | * Setting system clock using the hardware clock [UTC] ...
 [ ok ]
hostname          | * Setting hostname to x360 from /etc/hostname ...
 [ ok ]
loopback          | * Bringing up network interface lo ...
sysctl            | * Configuring kernel parameters ...
 [ ok ]
 [ ok ]
procfs            | * Mounting misc binary format filesystem ...
fsck              | * Checking local filesystems  ...
 [ ok ]
fsck              |fsck.fat 4.2 (2021-01-31)
fsck              |/dev/nvme0n1p1: 348 files, 22938/65536 clusters
fsck              |/dev/nvme0n1p8: clean, 282242/1966080 files, 2493814/7864320 blocks
binfmt            | * Loading custom binary format handlers ...
fsck              |/dev/nvme0n1p12: clean, 612/5898240 files, 2674770/23592960 blocks
 [ ok ]
fsck              |/dev/nvme0n1p6: clean, 11/1966080 files, 167453/7864320 blocks
fsck              |/dev/nvme0n1p9: clean, 12680/6553600 files, 731524/26214400 blocks
fsck              |fsck.ext4: No such file or directory while trying to open /dev/mapper/home
fsck              |Possibly non-existent device?
fsck              |/dev/nvme0n1p11: clean, 951102/23789568 files, 17073022/95145728 blocks
fsck              | * Operational error
 [ !! ]
root              | * Remounting filesystems ...
 [ ok ]
mtab              | * Updating /etc/mtab ...
mtab              | * Creating mtab symbolic link
 [ ok ]
swap              | * Activating swap devices ...
 [ ok ]
localmount        | * Mounting local filesystems ...
 [ ok ]
opensysusers      | * Setting up sysusers.d entries ...
urandom           | * Initializing random number generator ...
 [ ok ]
opentmpfiles-setup| * Setting up tmpfiles.d entries ...
 [ ok ]
 [ ok ]
bootmisc          | * Creating user login records ...
 [ ok ]
bootmisc          | * Wiping /tmp directory ...
 [ ok ]
consolefont       | * Setting console font [default8x16] ...
save-keymaps      | * Saving key mapping ...
save-termencoding | * Saving terminal encoding ...
dbus              | * Starting dbus ...
 [ ok ]
 [ ok ]
 [ ok ]
net.lo            | * Bringing up interface lo
net.lo            | *   Caching network module dependencies
 [ ok ]
consolefont       |setfont: INFO setfont.c:627 save_font: Found nothing to save
elogind           | * Starting elogind ...
 [ ok ]
net.lo            | *   127.0.0.1/8 ...
 [ ok ]
net.lo            | *   Adding routes
net.lo            | *     127.0.0.0/8 via 127.0.0.1 ...
 [ ok ]
 [ ok ]

rc boot logging stopped at Thu Nov  4 09:13:55 2021


rc default logging started at Thu Nov  4 09:13:55 2021

syslog-ng         | * Checking your configfile (/etc/syslog-ng/syslog-ng.conf) ...
connmand          | * Starting connmand ...
 [ ok ]
netmount          | * Mounting network filesystems ...
 [ ok ]
avahi-daemon      | * Starting avahi-daemon ...
 [ ok ]
 [ ok ]
syslog-ng         | * Starting syslog-ng ...
 [ ok ]
cronie            | * Starting cronie ...
 [ ok ]
cupsd             | * Starting cupsd ...
acpid             | * Starting acpid ...
 [ ok ]
 [ ok ]
lightdm           | * Starting lightdm ...
 [ ok ]
sshd              | * Starting sshd ...
 [ ok ]
local             | * Starting local ...
 [ ok ]

rc default logging stopped at Thu Nov  4 09:13:56 2021


rc default logging started at Thu Nov  4 09:13:55 2021

syslog-ng         | * Checking your configfile (/etc/syslog-ng/syslog-ng.conf) ...
connmand          | * Starting connmand ...
 [ ok ]
netmount          | * Mounting network filesystems ...
 [ ok ]
avahi-daemon      | * Starting avahi-daemon ...
 [ ok ]
 [ ok ]
syslog-ng         | * Starting syslog-ng ...
 [ ok ]
cronie            | * Starting cronie ...
 [ ok ]
cupsd             | * Starting cupsd ...
acpid             | * Starting acpid ...
 [ ok ]
 [ ok ]
lightdm           | * Starting lightdm ...
 [ ok ]
sshd              | * Starting sshd ...
 [ ok ]
local             | * Starting local ...
 [ ok ]

rc default logging stopped at Thu Nov  4 09:13:56 2021

And here is with parallel = NO:
Code: [Select]
rc boot logging started at Thu Nov  4 09:16:04 2021

 * Loading module crypto_user ...
 [ ok ]
 * Setting system clock using the hardware clock [UTC] ...
 [ ok ]
 * Mounting misc binary format filesystem ...
 [ ok ]
 * Loading custom binary format handlers ...
 [ ok ]
 * Checking local filesystems  ...
fsck.fat 4.2 (2021-01-31)
/dev/nvme0n1p1: 348 files, 22938/65536 clusters
/dev/nvme0n1p8: clean, 282242/1966080 files, 2493814/7864320 blocks
/dev/nvme0n1p12: clean, 612/5898240 files, 2674770/23592960 blocks
/dev/nvme0n1p6: clean, 11/1966080 files, 167453/7864320 blocks
/dev/nvme0n1p9: clean, 12680/6553600 files, 731524/26214400 blocks
fsck.ext4: No such file or directory while trying to open /dev/mapper/home
Possibly non-existent device?
/dev/nvme0n1p11: clean, 951102/23789568 files, 17073022/95145728 blocks
 * Operational error
 [ !! ]
 * Remounting filesystems ...
 [ ok ]
 * Updating /etc/mtab ...
 * Creating mtab symbolic link
 [ ok ]
 * Activating swap devices ...
 [ ok ]
 * Mounting local filesystems ...
 [ ok ]
 * Configuring kernel parameters ...
 [ ok ]
 * Creating user login records ...
 [ ok ]
 * Wiping /tmp directory ...
 [ ok ]
 * Setting terminal encoding [UTF-8] ...
 [ ok ]
 * Setting console font [default8x16] ...
 [ ok ]
setfont: INFO setfont.c:627 save_font: Found nothing to save
 * Starting dbus ...
 [ ok ]
 * Starting elogind ...
 [ ok ]
 * Setting hostname to x360 from /etc/hostname ...
 [ ok ]
 * Setting keyboard mode [UTF-8] ...
 [ ok ]
 * Loading key mappings [us] ...
 [ ok ]
 * Bringing up network interface lo ...
 [ ok ]
 * Bringing up interface lo
 *   Caching network module dependencies
 *   127.0.0.1/8 ...
 [ ok ]
 *   Adding routes
 *     127.0.0.0/8 via 127.0.0.1 ...
 [ ok ]
 [ ok ]
 * Setting up sysusers.d entries ...
 [ ok ]
 * Setting up tmpfiles.d entries ...
 [ ok ]
 * Saving key mapping ...
 [ ok ]
 * Saving terminal encoding ...
 [ ok ]
 * Initializing random number generator ...
 [ ok ]

rc boot logging stopped at Thu Nov  4 09:16:07 2021


rc default logging started at Thu Nov  4 09:16:07 2021

 * Checking your configfile (/etc/syslog-ng/syslog-ng.conf) ...
 [ ok ]
 * Starting syslog-ng ...
 [ ok ]
 * Starting acpid ...
 [ ok ]
 * Starting connmand ...
 [ ok ]
 * Starting cronie ...
 [ ok ]
 * Starting avahi-daemon ...
 [ ok ]
 * Starting cupsd ...
 [ ok ]
 * Mounting network filesystems ...
 [ ok ]
 * Starting lightdm ...
 [ ok ]
 * Starting sshd ...
 [ ok ]
 * Starting local ...
 [ ok ]

rc default logging stopped at Thu Nov  4 09:16:08 2021

Although I am still disturbed by the warm-vs-cold boot differences, I am in agreement that there is some synchronization / race condition.  However, since I am not troubled by the extra 2 seconds (+/-) required by parallel = NO, I'm completely happy to go that route.

I don't tend to reboot often... the number of times I rebooted yesterday made me feel like I was using windows, which I avoid like the plague.  Hopefully it won't take me long to figure out how to mount an encrypted partition at boot time (but that's another story) and then I should be good to go.  Having said that, if the above rc.log information causes anyone to have a brilliant idea and they would like another test or more information, just let me know.

Cheers.

Re: X won't start after cold reboot, but starts after rebooting out of Ubuntu

Reply #18
Yeah parallel mode in openrc still isn't 100% guaranteed yet. It probably works fine for most people, but OP could just be an unlucky fellow.
But how did OpenRC know that?   :D

Re: X won't start after cold reboot, but starts after rebooting out of Ubuntu

Reply #19
Since the OP is still trying out Artix, he could also try another init system as well. Currently Artix supports runit, s6 and 66, with dinit being in testing.

I'm using 66. :)
Thanks for the thoughts.  If/when I figure out how to mount an encrypted /home at boot, I'll probably stick with OpenRC, to get some return on the investment of time I've put into it so far.  But it's good to have some choice.


Re: X won't start after cold reboot, but starts after rebooting out of Ubuntu

Reply #21
Here is the section from rc.log when I did a cold boot with parallel = YES, and X did not start:
Code: [Select]
rc boot logging started at Thu Nov  4 09:13:54 2021

modules           | * Loading module crypto_user ...
termencoding      | * Setting terminal encoding [UTF-8] ...
 [ ok ]
keymaps           | * Setting keyboard mode [UTF-8] ...
 [ ok ]
 [ ok ]
keymaps           | * Loading key mappings [us] ...
 [ ok ]
hwclock           | * Setting system clock using the hardware clock [UTC] ...
 [ ok ]
hostname          | * Setting hostname to x360 from /etc/hostname ...
 [ ok ]
loopback          | * Bringing up network interface lo ...
sysctl            | * Configuring kernel parameters ...
 [ ok ]
 [ ok ]
procfs            | * Mounting misc binary format filesystem ...
fsck              | * Checking local filesystems  ...
 [ ok ]
fsck              |fsck.fat 4.2 (2021-01-31)
fsck              |/dev/nvme0n1p1: 348 files, 22938/65536 clusters
fsck              |/dev/nvme0n1p8: clean, 282242/1966080 files, 2493814/7864320 blocks
binfmt            | * Loading custom binary format handlers ...
fsck              |/dev/nvme0n1p12: clean, 612/5898240 files, 2674770/23592960 blocks
 [ ok ]
fsck              |/dev/nvme0n1p6: clean, 11/1966080 files, 167453/7864320 blocks
fsck              |/dev/nvme0n1p9: clean, 12680/6553600 files, 731524/26214400 blocks
fsck              |fsck.ext4: No such file or directory while trying to open /dev/mapper/home
fsck              |Possibly non-existent device?
fsck              |/dev/nvme0n1p11: clean, 951102/23789568 files, 17073022/95145728 blocks
fsck              | * Operational error
 [ !! ]
root              | * Remounting filesystems ...
 [ ok ]
mtab              | * Updating /etc/mtab ...
mtab              | * Creating mtab symbolic link
 [ ok ]
swap              | * Activating swap devices ...
 [ ok ]
localmount        | * Mounting local filesystems ...
 [ ok ]
opensysusers      | * Setting up sysusers.d entries ...
urandom           | * Initializing random number generator ...
 [ ok ]
opentmpfiles-setup| * Setting up tmpfiles.d entries ...
 [ ok ]
 [ ok ]
bootmisc          | * Creating user login records ...
 [ ok ]
bootmisc          | * Wiping /tmp directory ...
 [ ok ]
consolefont       | * Setting console font [default8x16] ...
save-keymaps      | * Saving key mapping ...
save-termencoding | * Saving terminal encoding ...
dbus              | * Starting dbus ...
 [ ok ]
 [ ok ]
 [ ok ]
net.lo            | * Bringing up interface lo
net.lo            | *   Caching network module dependencies
 [ ok ]
consolefont       |setfont: INFO setfont.c:627 save_font: Found nothing to save
elogind           | * Starting elogind ...
 [ ok ]
net.lo            | *   127.0.0.1/8 ...
 [ ok ]
net.lo            | *   Adding routes
net.lo            | *     127.0.0.0/8 via 127.0.0.1 ...
 [ ok ]
 [ ok ]

rc boot logging stopped at Thu Nov  4 09:13:55 2021


rc default logging started at Thu Nov  4 09:13:55 2021

syslog-ng         | * Checking your configfile (/etc/syslog-ng/syslog-ng.conf) ...
connmand          | * Starting connmand ...
 [ ok ]
netmount          | * Mounting network filesystems ...
 [ ok ]
avahi-daemon      | * Starting avahi-daemon ...
 [ ok ]
 [ ok ]
syslog-ng         | * Starting syslog-ng ...
 [ ok ]
cronie            | * Starting cronie ...
 [ ok ]
cupsd             | * Starting cupsd ...
acpid             | * Starting acpid ...
 [ ok ]
 [ ok ]
lightdm           | * Starting lightdm ...
 [ ok ]
sshd              | * Starting sshd ...
 [ ok ]
local             | * Starting local ...
 [ ok ]

rc default logging stopped at Thu Nov  4 09:13:56 2021


rc default logging started at Thu Nov  4 09:13:55 2021

syslog-ng         | * Checking your configfile (/etc/syslog-ng/syslog-ng.conf) ...
connmand          | * Starting connmand ...
 [ ok ]
netmount          | * Mounting network filesystems ...
 [ ok ]
avahi-daemon      | * Starting avahi-daemon ...
 [ ok ]
 [ ok ]
syslog-ng         | * Starting syslog-ng ...
 [ ok ]
cronie            | * Starting cronie ...
 [ ok ]
cupsd             | * Starting cupsd ...
acpid             | * Starting acpid ...
 [ ok ]
 [ ok ]
lightdm           | * Starting lightdm ...
 [ ok ]
sshd              | * Starting sshd ...
 [ ok ]
local             | * Starting local ...
 [ ok ]

rc default logging stopped at Thu Nov  4 09:13:56 2021

And here is with parallel = NO:
Code: [Select]
rc boot logging started at Thu Nov  4 09:16:04 2021

 * Loading module crypto_user ...
 [ ok ]
 * Setting system clock using the hardware clock [UTC] ...
 [ ok ]
 * Mounting misc binary format filesystem ...
 [ ok ]
 * Loading custom binary format handlers ...
 [ ok ]
 * Checking local filesystems  ...
fsck.fat 4.2 (2021-01-31)
/dev/nvme0n1p1: 348 files, 22938/65536 clusters
/dev/nvme0n1p8: clean, 282242/1966080 files, 2493814/7864320 blocks
/dev/nvme0n1p12: clean, 612/5898240 files, 2674770/23592960 blocks
/dev/nvme0n1p6: clean, 11/1966080 files, 167453/7864320 blocks
/dev/nvme0n1p9: clean, 12680/6553600 files, 731524/26214400 blocks
fsck.ext4: No such file or directory while trying to open /dev/mapper/home
Possibly non-existent device?
/dev/nvme0n1p11: clean, 951102/23789568 files, 17073022/95145728 blocks
 * Operational error
 [ !! ]
 * Remounting filesystems ...
 [ ok ]
 * Updating /etc/mtab ...
 * Creating mtab symbolic link
 [ ok ]
 * Activating swap devices ...
 [ ok ]
 * Mounting local filesystems ...
 [ ok ]
 * Configuring kernel parameters ...
 [ ok ]
 * Creating user login records ...
 [ ok ]
 * Wiping /tmp directory ...
 [ ok ]
 * Setting terminal encoding [UTF-8] ...
 [ ok ]
 * Setting console font [default8x16] ...
 [ ok ]
setfont: INFO setfont.c:627 save_font: Found nothing to save
 * Starting dbus ...
 [ ok ]
 * Starting elogind ...
 [ ok ]
 * Setting hostname to x360 from /etc/hostname ...
 [ ok ]
 * Setting keyboard mode [UTF-8] ...
 [ ok ]
 * Loading key mappings [us] ...
 [ ok ]
 * Bringing up network interface lo ...
 [ ok ]
 * Bringing up interface lo
 *   Caching network module dependencies
 *   127.0.0.1/8 ...
 [ ok ]
 *   Adding routes
 *     127.0.0.0/8 via 127.0.0.1 ...
 [ ok ]
 [ ok ]
 * Setting up sysusers.d entries ...
 [ ok ]
 * Setting up tmpfiles.d entries ...
 [ ok ]
 * Saving key mapping ...
 [ ok ]
 * Saving terminal encoding ...
 [ ok ]
 * Initializing random number generator ...
 [ ok ]

rc boot logging stopped at Thu Nov  4 09:16:07 2021


rc default logging started at Thu Nov  4 09:16:07 2021

 * Checking your configfile (/etc/syslog-ng/syslog-ng.conf) ...
 [ ok ]
 * Starting syslog-ng ...
 [ ok ]
 * Starting acpid ...
 [ ok ]
 * Starting connmand ...
 [ ok ]
 * Starting cronie ...
 [ ok ]
 * Starting avahi-daemon ...
 [ ok ]
 * Starting cupsd ...
 [ ok ]
 * Mounting network filesystems ...
 [ ok ]
 * Starting lightdm ...
 [ ok ]
 * Starting sshd ...
 [ ok ]
 * Starting local ...
 [ ok ]

rc default logging stopped at Thu Nov  4 09:16:08 2021

Although I am still disturbed by the warm-vs-cold boot differences, I am in agreement that there is some synchronization / race condition.  However, since I am not troubled by the extra 2 seconds (+/-) required by parallel = NO, I'm completely happy to go that route.

I don't tend to reboot often... the number of times I rebooted yesterday made me feel like I was using windows, which I avoid like the plague.  Hopefully it won't take me long to figure out how to mount an encrypted partition at boot time (but that's another story) and then I should be good to go.  Having said that, if the above rc.log information causes anyone to have a brilliant idea and they would like another test or more information, just let me know.

Cheers.

From the log, when "parallel" option was off, acpid was broguht up much earlier. We could arrange acpid to come up before connmand by changing connmand service file.

Code: [Select]
#!/usr/bin/openrc-run
# Copyright 1999-2013 Gentoo Foundation
# Distributed under the terms of the GNU General Purpose License v2

supervisor=supervise-daemon
command=/usr/bin/connmand
command_args="-n ${CONNMAN_OPTS}"

depend() {
   need dbus
   after acpid
   provide net
}

Just curious to try. For a reliable system, you may still need to turn the parallel mode OFF.

I noticed that you're using a HP laptop. Do you have any acpi options passed to kernel during boot?

Re: X won't start after cold reboot, but starts after rebooting out of Ubuntu

Reply #22
Thanks for the link.  But in my case, I have only encrypted /home, and the procedures (as you probably know) are different.

In any case, I managed to get my fstab in sync with my conf.d/dmcrypt and my UUIDs, and all is now good.

Re: X won't start after cold reboot, but starts after rebooting out of Ubuntu

Reply #23
From the log, when "parallel" option was off, acpid was broguht up much earlier. We could arrange acpid to come up before connmand by changing connmand service file.

Code: [Select]
#!/usr/bin/openrc-run
# Copyright 1999-2013 Gentoo Foundation
# Distributed under the terms of the GNU General Purpose License v2

supervisor=supervise-daemon
command=/usr/bin/connmand
command_args="-n ${CONNMAN_OPTS}"

depend() {
   need dbus
   after acpid
   provide net
}

Just curious to try. For a reliable system, you may still need to turn the parallel mode OFF.

I noticed that you're using a HP laptop. Do you have any acpi options passed to kernel during boot?

I tried parallel = ON with that addition to connmand and Xorg.0.log once again whined about acpid.
However, X did start, although now that I have mounting of encrypted /home working, there is a delay in booting while I type in my passphrase.

I pass no ACPI options to the kernel (neither in Ubuntu nor in Artix).

While I am happy to contribute to debugging this problem should anyone wish to carry on, since setting parallel to NO solves my problem, I am going to mark this as solved.  I hope that isn't against standard practice for Artix.

Re: X won't start after cold reboot, but starts after rebooting out of Ubuntu

Reply #24
It's certainly possible that this is just an openrc bug with parallel in which you could spend all day arranging around service dependencies to no avail.

Re: X won't start after cold reboot, but starts after rebooting out of Ubuntu

Reply #25
I would just leave parallel mode off. Not worth spending too much time to save a split of second during boot.

HP laptops are known having acpi issues in Linux. You can google around for a solution.

 

Re: X won't start after cold reboot, but starts after rebooting out of Ubuntu

Reply #26
I would just leave parallel mode off. Not worth spending too much time to save a split of second during boot.

HP laptops are known having acpi issues in Linux. You can google around for a solution.
I tried applying some of the ACPI patches I found on an Arch page to Ubuntu, but they had no effect, so in ubuntu I can't enter state S2 (and S0 hangs the graphics half the time on resume).  One of the perks of Artix is that even without patching, I can suspend (presumably S0idle) successfully.  I'm not sure how much of this is the newer kernel in Artix (compared to Ubuntu 20.04, which is getting old) and how much is other things.  For the immediate future I will be happy with S0idle. 

I haven't yet seen any other problems in Ubuntu related to the hardware, so maybe on that aspect I'm lucky.