Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[SOLVED] SDDM is not starting-up on boot
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
digreamon
n00b
n00b


Joined: 18 Oct 2018
Posts: 4

PostPosted: Mon Oct 22, 2018 11:36 am    Post subject: [SOLVED] SDDM is not starting-up on boot Reply with quote

Hello, please help me.

After updating "@world" I'm experiencing a very weird problem, which i totally don't understand: when system boots, network is not starting-up.
Actually, it says that it is started OK, but in fact - network is not working.

It causes GUI (SDDM+KDE) not to start-up either - I see black screen and cursor in the top left corner.
The only thing i can do - press "reset".

If, during boot, I enter interactive mode, and:
  • slowly go through each service:
    - networks starts-up normally and everything loads properly;
    - shutdowns properly;

  • quickly go through each service:
    - network fails to start, there is only TTY1, GUI fails to start;
    - shutdown: udev hangs for a while, hangs on "Remounting / readonly" and does not shutdown.


During update there was kernel update from 4.9.95 to 4.14.65. But the behavior is absolutely the same with the old version.

Logs:


UPD (22-OCT-2018 22:59 EET):
Code:

[I] sys-apps/dbus
     Available versions:  1.10.18^t 1.10.24 ~1.12.8 ~1.12.10 {X debug doc elogind selinux static-libs systemd test user-session ABI_MIPS="n32 n64 o32" ABI_PPC="32 64" ABI_S390="32 64" ABI_X86="32 64 x32" KERNEL="linux"}
     Installed versions:  1.10.24(00:04:28 16.10.18)(X -debug -doc -elogind -selinux -static-libs -systemd -test -user-session ABI_MIPS="-n32 -n64 -o32" ABI_PPC="-32 -64" ABI_S390="-32 -64" ABI_X86="32 64 -x32" KERNEL="linux")
     Homepage:            https://dbus.freedesktop.org/
     Description:         A message bus system, a simple way for applications to talk to each other

[I] sys-fs/udev
     Available versions:  236-r1^t 238^t ~239^t **9999^t {acl +kmod selinux ABI_MIPS="n32 n64 o32" ABI_PPC="32 64" ABI_S390="32 64" ABI_X86="32 64 x32" KERNEL="linux"}
     Installed versions:  238^t(03:39:40 16.10.18)(acl kmod -selinux ABI_MIPS="-n32 -n64 -o32" ABI_PPC="-32 -64" ABI_S390="-32 -64" ABI_X86="32 64 -x32" KERNEL="linux")
     Homepage:            https://www.freedesktop.org/wiki/Software/systemd
     Description:         Linux dynamic and persistent device naming support (aka userspace devfs)

[I] sys-auth/consolekit
     Available versions:  0.4.6 1.1.0-r1 1.1.2 1.2.0 1.2.1 **9999 {acl cgroups debug doc evdev pam pm-utils policykit selinux systemd-units test udev KERNEL="linux"}
     Installed versions:  1.2.1(00:33:36 16.10.18)(acl pam policykit udev -cgroups -debug -doc -evdev -pm-utils -selinux -test KERNEL="linux")
     Homepage:            https://github.com/ConsoleKit2/ConsoleKit2 https://www.freedesktop.org/wiki/Software/ConsoleKit
     Description:         Framework for defining and tracking users, login sessions and seats


UPD (23-OCT-2018 03:17 EET):
Downgraded kernel to
Code:
4.9.122-gentoo
, reinstalled drivers. Still the same.

There is a difference in /var/log/messages that i have noticed (under for both versions of kernel):
- when the network fails to start-up, causing UI to fail as well, i can see following message:

Code:
kernel: random: crng init done


Logs:


Last edited by digreamon on Wed Oct 24, 2018 9:39 am; edited 5 times in total
Back to top
View user's profile Send private message
Ralphred
Tux's lil' helper
Tux's lil' helper


Joined: 31 Dec 2013
Posts: 87

PostPosted: Mon Oct 22, 2018 12:45 pm    Post subject: Reply with quote

I had a very similar issue after upgrading dev-qt/*-5.11 and kde-plasma/*-5.13.
76 packages were upgraded, nothing gui worked (except twm xterm etc), I reverted them to the older versions (dev-qt*-9.6 and kde-plasma/*-5.12) so I could log in here and look for answers, but things still didn't work.
Before starting a thread here, I removed the masks and "re-upgraded".
Once qt-core had been upgraded for the 2nd time things started to work, at the end of the merge everything was back to normal.

I know this isn't a lot of info to go on, but on the initial merge, somewhere between qt-core installing and starting the build of qt-webkit, everything qt related sh*t the bed.

There is a little voice in the back of my head whispering dbus, and I don't know why...
Back to top
View user's profile Send private message
digreamon
n00b
n00b


Joined: 18 Oct 2018
Posts: 4

PostPosted: Mon Oct 22, 2018 7:32 pm    Post subject: Reply with quote

Ralphred wrote:
I had a very similar issue after upgrading dev-qt/*-5.11 and kde-plasma/*-5.13.
76 packages were upgraded, nothing gui worked (except twm xterm etc), I reverted them to the older versions (dev-qt*-9.6 and kde-plasma/*-5.12) so I could log in here and look for answers, but things still didn't work.
Before starting a thread here, I removed the masks and "re-upgraded".
Once qt-core had been upgraded for the 2nd time things started to work, at the end of the merge everything was back to normal.

I know this isn't a lot of info to go on, but on the initial merge, somewhere between qt-core installing and starting the build of qt-webkit, everything qt related sh*t the bed.

There is a little voice in the back of my head whispering dbus, and I don't know why...


Hello, Ralphred,
I already have
Code:
dev-qt/*-5.9.6
and
Code:
kde-plasma/*-5.15.5
, did not unmask them.
I'll listen to the whisper of the little voice, and see to dbus.
Back to top
View user's profile Send private message
baaann
Guru
Guru


Joined: 23 Jan 2006
Posts: 548
Location: uk

PostPosted: Mon Oct 22, 2018 9:04 pm    Post subject: Reply with quote

I recently experienced a similar situation with a machine booting to the terminal, but not sure about the network issue.

For me I found that dmesg was showing a problem with Nvidia-drivers, I can't recall the exact message, but googling suggested my old kernel may be the problem and sure enough updating the kernel followed by a reinstall of Nvidia-drivers solved it for me.

Hope that helps?
Back to top
View user's profile Send private message
digreamon
n00b
n00b


Joined: 18 Oct 2018
Posts: 4

PostPosted: Tue Oct 23, 2018 12:16 am    Post subject: Reply with quote

baaann wrote:
I recently experienced a similar situation with a machine booting to the terminal, but not sure about the network issue.

For me I found that dmesg was showing a problem with Nvidia-drivers, I can't recall the exact message, but googling suggested my old kernel may be the problem and sure enough updating the kernel followed by a reinstall of Nvidia-drivers solved it for me.

Hope that helps?


Hi, according to logs, it doesn't even get to loading Nvidia-drivers....
However, I have given it a try.
Downgraded kernel to
Code:
4.9.122-gentoo
, reinstalled drivers. Still the same.

There is a difference in /var/log/messages that i have noticed (under for both versions of kernel):
- when the network fails to start-up, causing UI to fail as well, i can see following message:

Code:
kernel: random: crng init done


There is no such record if I boot with RC interactive mode, going through each service with about 1 second interval.

Full log:
Code:

Oct 23 01:29:27 digreamon-pc syslog-ng[3052]: syslog-ng starting up; version='3.13.2'
Oct 23 01:29:28 digreamon-pc acpid[3083]: starting up with netlink and the input layer
Oct 23 01:29:28 digreamon-pc acpid[3083]: 1 rule loaded
Oct 23 01:29:28 digreamon-pc acpid[3083]: waiting for events: event logging is off
Oct 23 01:29:28 digreamon-pc kernel: random: dbus-daemon: uninitialized urandom read (12 bytes read)
Oct 23 01:29:28 digreamon-pc kernel: random: dbus-daemon: uninitialized urandom read (12 bytes read)
Oct 23 01:29:29 digreamon-pc dbus[3114]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper)
Oct 23 01:29:29 digreamon-pc polkitd[3150]: Started polkitd version 0.113
Oct 23 01:29:29 digreamon-pc polkitd[3150]: Loading rules from directory /etc/polkit-1/rules.d
Oct 23 01:29:29 digreamon-pc polkitd[3150]: Loading rules from directory /usr/share/polkit-1/rules.d
Oct 23 01:29:29 digreamon-pc polkitd[3150]: Finished loading, compiling and executing 3 rules
Oct 23 01:29:29 digreamon-pc dbus[3114]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Oct 23 01:29:29 digreamon-pc polkitd[3150]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
Oct 23 01:29:30 digreamon-pc /etc/init.d/dcron[3164]: /etc/init.d/dcron uses runscript, please convert to openrc-run.
Oct 23 01:29:30 digreamon-pc crond[3185]: /usr/sbin/crond 4.5 dillon's cron daemon, started with loglevel notice
Oct 23 01:29:30 digreamon-pc kernel: IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
Oct 23 01:29:30 digreamon-pc kernel: ip (3312) used greatest stack depth: 13056 bytes left
Oct 23 01:29:30 digreamon-pc dhcpcd[3419]: enp3s0: waiting for carrier
Oct 23 01:29:32 digreamon-pc kernel: random: crng init done
Oct 23 01:30:00 digreamon-pc dhcpcd[3419]: timed out
Oct 23 01:30:00 digreamon-pc dhcpcd[3419]: dhcpcd exited
Oct 23 01:30:00 digreamon-pc /etc/init.d/net.enp3s0[3219]: ERROR: net.enp3s0 failed to start
Oct 23 01:30:09 digreamon-pc /etc/init.d/ntpd[3444]: ERROR: cannot start ntpd as net.enp3s0 would not start
Oct 23 01:30:09 digreamon-pc /etc/init.d/samba[3445]: ERROR: cannot start samba as net.enp3s0 would not start
Oct 23 01:30:15 digreamon-pc start-stop-daemon[3467]: pam_unix(start-stop-daemon:session): session opened for user unifi by (uid=0)
Oct 23 01:30:44 digreamon-pc login[4418]: pam_unix(login:session): session opened for user root by LOGIN(uid=0)
Oct 23 01:30:45 digreamon-pc login[4434]: ROOT LOGIN  on '/dev/tty1'
Oct 23 01:33:16 digreamon-pc /etc/init.d/xdm-setup[4523]: WARNING: xdm-setup has already been started
Oct 23 01:33:31 digreamon-pc /etc/init.d/xdm[4550]: start-stop-daemon: 1 process refused to stop
Oct 23 01:33:31 digreamon-pc /etc/init.d/xdm[4526]: ERROR: xdm failed to stop
Oct 23 01:33:31 digreamon-pc /etc/init.d/xdm-setup[4525]: ERROR: cannot stop xdm-setup as xdm is still up
Oct 23 01:33:58 digreamon-pc /etc/init.d/xdm[4579]: start-stop-daemon: no matching processes found
Oct 23 01:34:29 digreamon-pc /etc/init.d/xdm[4693]: WARNING: xdm has already been started
Oct 23 01:39:29 digreamon-pc /usr/sbin/gpm[4735]: *** info [daemon/startup.c(136)]:
Oct 23 01:39:29 digreamon-pc /usr/sbin/gpm[4735]: Started gpm successfully. Entered daemon mode.
Back to top
View user's profile Send private message
Ralphred
Tux's lil' helper
Tux's lil' helper


Joined: 31 Dec 2013
Posts: 87

PostPosted: Tue Oct 23, 2018 1:44 am    Post subject: Reply with quote

Check this commit.

It causes systemd to hang and wait for the
Code:
kernel: random: crng init done
message on certain hardware.
You using interactive start-up on openrc would certainly explain how there was enough gathered entropy, that by the time you got to services that need it the kernel was ready.

There is some reported success with installing rng-tools and adding rngd to the boot runlevel, but check that urandom is in boot first.
Back to top
View user's profile Send private message
digreamon
n00b
n00b


Joined: 18 Oct 2018
Posts: 4

PostPosted: Wed Oct 24, 2018 12:10 am    Post subject: Reply with quote

Ralphred wrote:
Check this commit.

It causes systemd to hang and wait for the
Code:
kernel: random: crng init done
message on certain hardware.
You using interactive start-up on openrc would certainly explain how there was enough gathered entropy, that by the time you got to services that need it the kernel was ready.

There is some reported success with installing rng-tools and adding rngd to the boot runlevel, but check that urandom is in boot first.


Ralphred, thank you for the hint.

Unfortunately, I was not able too run rngd.
Looks like my board is missing device (even after activating all drivers for rng devices I get "/dev/hwrng: No such device" and rngd fails to start).
IMHO - it is weird, taking into account that I have rather modern full-format board, but nevertheless...
(OR maybe I just did something wrong)

Anyways, it made me take a closer look at urandom (in /etc/init.d/urandom):
Code:

depend()
{
        after clock
        need localmount
        keyword -docker -jail -lxc -openvz -prefix -systemd-nspawn
}


It made we wonder, whether everything is OK with the "clock".
Somehow I got to System Time page.
And it made me want to switch from OpenRCs hwclock to In-kernel method of setting clock.

After I did it - everything started booting without errors, as before.

So I can't be 100% sure, but it may be the actual solution.
Because the only thing I did more - delete and add urandom from/to boot. But I don't think it did the trick.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum