Hi.
Im using a Intel NUC with SSD.
I have just installed Ubuntu 16, and installed kodi.
I have a problem that Kodi boots faster than the network is ready, or at least i think that is the problem.
I can add network sources after kodi has started, but at next reboot i can't access them. It's SMB shares.
I can't see the shared mysql database either, i have en empty library.
I start kodi with lightdm.conf as i have read here:
http://kodi.wiki/view/HOW-TO:Autostart_Kodi_for_Linux
Solution 1+6
How do i delay the boot, or get it to wait for the network to be ready before starting kodi?
This NUC is the "updater" for our system here at home, so i would like to get it working ASAP
How should the lightdm.conf look if i need to add the code wsnipex wrote?
Like this?
Code:
start on ((filesystem
and runlevel [!06]
and started dbus
- and plymouth-ready)
+ and plymouth-ready
+ and (starting network-interface
+ or starting network-manager
+ or starting networking)
+ )
or runlevel PREVLEVEL=S)
stop on runlevel [016]
[Seat:*]
#autologin-guest=false
#autologin-user=kodi
#autologin-user-timeout=0
autologin-user=kodi
autologin-session=kodi
You obviously don't add the "+" and "-" signs.
Post your lightdm.conf when you are ready.
Depending on the OS you are using - there is a better method with systemd ...
edit /lib/systemd/system/lightdm.service
and in the second line where it states:
Quote:After=systemd-user-sessions.service [email protected] plymouth-quit.service
Change it to:
Quote:After=sound.target network-online.target systemd-user-sessions.service [email protected] plymouth-quit.service
Now do:
sudo systemctl disable lightdm
sudo systemctl enable lightdm
sudo reboot
Done.
Now when it boots it has stopped before gui, and there is this on the screen:
Code:
/dev/sda1: clean, 240432/7299072 files, 1684462/29190656 blocks
If i push the power button, it shuts down correctly, but it's the same when i turn it on again
I can also connect to it via putty.
rather sounds like you did not enable lightdm anymore.
Undo the changes and try again ..
By undo, you mean change
After=sound.target network-online.target systemd-user-sessions.service
[email protected] plymouth-quit.service
to
After=systemd-user-sessions.service
[email protected] plymouth-quit.service
again right?
Did that, and
sudo systemctl disable lightdm
sudo systemctl enable lightdm
sudo reboot
afterwards, same result as before -
/dev/sda1: clean, 240432/7299072 files, 1684462/29190656 blocks
(2017-02-25, 18:37)fritsch Wrote: [ -> ]Remember: v16 is outdated and not suitable for a nuc.
What OS should i be using on my NUC if not Ubuntu 16.04?
Then you broke something totally and absolutely NOT related to the above changes ...
post:
systemd-analyze critical-chain
and:
systemctl status lightdm
All in a pastebin
(2017-02-25, 22:09)Dennisreneholm Wrote: [ -> ] (2017-02-25, 18:37)fritsch Wrote: [ -> ]Remember: v16 is outdated and not suitable for a nuc.
What OS should i be using on my NUC if not Ubuntu 16.04?
Kodi version 16 is outdated.
sudo systemctl restart lightdm ...
lightdm seems dead :-) - sure that you did not edit something in a wrong way?
