Alpha 4 black screen on boot

I am running the Alpha 4 version of OSMC on a Raspberry Pi 2 model B. I am running OSMC from the micro sd slot on the Pi.

The problem is that on the boot of OSMC I only get a black screen, after it says ‘missing device mode for CPU x’ four times, with 0,1,2,3 in place of the x.

I have reinstalled OSMC several times, and it does not happen at the first reboot after the installation. I have traced my steps when configuring and rebooted every time:

  1. changing the skin to ‘confluence’ → reboots normally;
  2. ssh to pi and changing default password for user osmc → reboots normally;
  3. adding a new user and group; add osmc and new user to new group → black screen on reboot

I highly doubt that creating a new user or new group would create such behaviour. It does not seem like a trivial task.

I am still able to make a ssh connection to the Pi. When I read the Kodi log it does not seem to say anything related to the GUI not working, but i posted my log anyway.

    14:31:39 T:3024826368  NOTICE: special://profile/ is mapped to: special://maste$
14:31:39 T:3024826368  NOTICE: ------------------------------------------------$
14:31:39 T:3024826368  NOTICE: Starting Kodi (14.1 Git:Unknown). Platform: Linu$
14:31:39 T:3024826368  NOTICE: Using Release Kodi x32 build (version for Raspbe$
14:31:39 T:3024826368  NOTICE: Kodi compiled Jan 30 2015 by GCC 4.9.1 for Linux$
14:31:39 T:3024826368  NOTICE: Running on Open Source Media Center 0.0.4, kerne$
14:31:39 T:3024826368  NOTICE: FFmpeg statically linked, version: 77f79f0-xbmc-$
14:31:39 T:3024826368  NOTICE: Host CPU: ARMv7 Processor rev 5 (v7l), 4 cores a$
14:31:39 T:3024826368  NOTICE: ARM Features: Neon disabled
14:31:39 T:3024826368  NOTICE: special://xbmc/ is mapped to: /usr/share/kodi
14:31:39 T:3024826368  NOTICE: special://xbmcbin/ is mapped to: /usr/lib/kodi
14:31:39 T:3024826368  NOTICE: special://masterprofile/ is mapped to: /home/osm$
14:31:39 T:3024826368  NOTICE: special://home/ is mapped to: /home/osmc/.kodi
14:31:39 T:3024826368  NOTICE: special://temp/ is mapped to: /home/osmc/.kodi/t$
14:31:39 T:3024826368  NOTICE: The executable running is: /usr/lib/kodi/kodi.bin
14:31:39 T:3024826368  NOTICE: Local hostname: osmc
14:31:39 T:3024826368  NOTICE: Log File is located: /home/osmc/.kodi/temp/kodi.$
14:31:39 T:3024826368  NOTICE: ------------------------------------------------$
14:31:39 T:3024826368   ERROR: DBus: Error org.freedesktop.DBus.Error.ServiceUn$

My boot.log file in /var/log/ says the following (node the ‘FAILED’ line):

[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Reached target Paths.
[  OK  ] Started LSB: Tune IDE hard disks.
[  OK  ] Found device /dev/mmcblk0p1.
         Mounting /boot...
[  OK  ] Mounted /boot.
[  OK  ] Reached target Local File Systems.
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Reached target Remote File Systems.
         Starting Trigger Flushing of Journal to Persistent Storage...
         Starting Create Volatile Files and Directories...
         Starting LSB: RPC portmapper replacement...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Create Volatile Files and Directories.
[  OK  ] Started Trigger Flushing of Journal to Persistent Storage.
         Starting Update UTMP about System Boot/Shutdown...
[  OK  ] Started Update UTMP about System Boot/Shutdown.
[  OK  ] Started LSB: RPC portmapper replacement.
[  OK  ] Reached target RPC Port Mapper.
         Starting LSB: NFS support files common to client and server...
[  OK  ] Started LSB: NFS support files common to client and server.
[  OK  ] Reached target System Initialization.
[  OK  ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
[  OK  ] Listening on D-Bus System Message Bus Socket.
[  OK  ] Reached target Sockets.
[  OK  ] Reached target Timers.
[  OK  ] Reached target Basic System.
         Starting media center application...
[  OK  ] Started media center application.
         Starting mount disks automatically with standby...
         Starting Connection service...
         Starting Improves system performance tunables...
         Starting OpenBSD Secure Shell server...
[  OK  ] Started OpenBSD Secure Shell server.
         Starting eventlircd remote support...
         Starting /etc/rc.local Compatibility...
         Starting Login Service...
         Starting LSB: Starts LIRC daemon....
         Starting LSB: Start NTP daemon...
         Starting Avahi mDNS/DNS-SD Stack...
         Starting D-Bus System Message Bus...
[  OK  ] Started D-Bus System Message Bus.
[  OK  ] Started Connection service.
[  OK  ] Started Avahi mDNS/DNS-SD Stack.
         Starting Permit User Sessions...
[FAILED] Failed to start mount disks automatically with standby.
See 'systemctl status udisks-glue.service' for details.
[  OK  ] Started Improves system performance tunables.
[  OK  ] Started eventlircd remote support.
[  OK  ] Started /etc/rc.local Compatibility.
[  OK  ] Started LSB: Starts LIRC daemon..
[  OK  ] Started Permit User Sessions.
[  OK  ] Started LSB: Start NTP daemon.
         Starting Terminate Plymouth Boot Screen...
         Starting Wait for Plymouth Boot Screen to Quit...
[  OK  ] Started Login Service.

Here is a link to the system log: http://paste.osmc.io/qemixifevu

Does anyone have a clue about what I could try to solve this issue? Thanks in advance!

Creating a new user and group is probably not a problem, but I can assure you that the probable reason for this is moving osmc to another group. This is probably messing up some permissions and Kodi fails to start properly.
If this is a bug or not I cannot say, I am not very versed with systemd.

Why are you changing group for user omsc though?

1 Like

I changed the group for accessing files on my hard drive, but I can switch to a different user if I want to. Do you know what the default group of the osmc user is? Changing it back to ‘osmc’ does not seem to work. Otherwise I will reinstall the OS again.

Main UID/GID/Groups should be ‘osmc’ (1000), but I am quite certain that the user osmc are included in several groups:

osmc@osmc:~$ id osmc
uid=1000(osmc) gid=1000(osmc) grupper=1000(osmc),4(adm),6(disk),7(lp),20(dialout),24(cdrom),29(audio),44(video)
osmc@osmc:~$ id -G osmc
1000 4 6 7 20 24 29 44
osmc@osmc:~$ groups osmc
osmc : osmc adm disk lp dialout cdrom audio video

Thank you very much, I was able to resolve my issue.