Linux hifi 5.15.76-v8+ #1597 SMP PREEMPT Fri Nov 4 12:16:41 GMT 2022 aarch64 GNU/Linux
RPi 4 Model B (aarch64)
Usually all the last updates went smooth this one for some reason doesn’t start Kodi.
Tried reinstalling kodi but that didn’t fix it.
Let me know what other info you might want to troubleshoot and i can reinstall update.
you could start sharing an error message.
Kodi is on autostart, pi boots up and when the screen darkens before Kodi pops up is where it remains with cursor blinking in top left corner.
I could ssh into it though to get info.
disable autostart first, reboot your system, login via SSH and run following from CLI
Reinstalled the update
on first reboot rpi screen was showing services started
ssh as root and startkodi fired up kodi
ssh as root switch to kodi user account
startkodi works again
enable autostart with my kodi user account, rpi boots but hangs with blinking cursor top left on black screen
same with root user account in autostart
could you disable autostart for kodi and try to run following from command line
Either directly or via ssh kodi starts up with,
I noticed that there is also a file called kodi - standalone next to kodi.
Tested that one too and works also.
I should mention that right after posting yesterday automatic login to cli also stopped working.
I had to open up another console and login there and manually start kodi.
you mean even just simple login to CLI is not working anymore? It’s given the same black screen? If you disable automatic login. Does it show the login screen on an attached monitor?
ssh always works and if i disable automatic login, it shows the services loaded and i have to press enter to see login: entry field.
The automatic login to cli does the same as automatic login to kodi.
Black screen with cursor blinking in top left.
Ok means it is not an issue with Kodi, more with the automatic login. Can you login locally without issue? (Not using SSH)
ok issue is with automatic login and not with Kodi
any idea what could make the automatic login process stuck?
Can you enable auto-login, then, when it hangs, login via SSH and check the following:
systemctl status getty@tty1
systemctl cat getty@tty1
And also check
htop which might show the
dietpi-login script, if it is the one which hangs.
There were 13
apt upgrade updates that i run first. The problem remained.
Enabled auto-login again, problem remained.
:~# systemctl status getty@tty1
● firstname.lastname@example.org - Getty on tty1
Loaded: loaded (/lib/systemd/system/getty@.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2022-12-18 08:53:25 EET; 5s ago
Main PID: 1279 (agetty)
Tasks: 1 (limit: 3723)
└─1279 /sbin/agetty -a qbthost -J - linux
Dec 18 08:53:25 hifi systemd: Started Getty on tty1.
Dec 18 08:53:25 hifi agetty: -: not open for read/write
:~# systemctl cat getty@tty1
# SPDX-License-Identifier: LGPL-2.1-or-later
# This file is part of systemd.
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
Description=Getty on %I
After=systemd-user-sessions.service plymouth-quit-wait.service getty-pre.target
# If additional gettys are spawned during boot then we should make
# sure that this is synchronized before getty.target, even though
# getty.target didn't actually pull it in.
# IgnoreOnIsolate causes issues with sulogin, if someone isolates
# rescue.target or starts rescue.service from multi-user.target or
# On systems without virtual consoles, don't start any getty. Note
# that serial gettys are covered by serial-getty@.service, not this
# the VT is cleared by TTYVTDisallocate
# The '-o' option value tells agetty to replace 'login' arguments with an
# option to preserve environment (-p), followed by '--' for safety, and then
# the entered username.
ExecStart=-/sbin/agetty -o '-p -- \\u' --noclear %I $TERM
# Unset locale for the console getty since the console has problems
# displaying some internationalized messages.
UnsetEnvironment=LANG LANGUAGE LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT LC_IDENTIFICATION
ExecStart=-/sbin/agetty -a qbthost -J - $TERM
dietpi-login is not hanging nor running
Are or were you on the v8.12 beta already? Does this help?
cat << '_EOF_' > /email@example.com/dietpi-autologin.conf
ExecStart=-/sbin/agetty -a qbthost -J %I $TERM
As i wrote earlier, i installed the v8.12.0 and went back to backup after facing that problem, now i am running v8.12.0 again (reinstalled the update) so i can give feedback.
-bash: /firstname.lastname@example.org/dietpi-autologin.conf: No such file or directory
root@hifi:~# ll /etc/systemd/system/getty
root@hifi:~# ll /etc/systemd/system/getty.target.wants/
drwxr-xr-x 2 root root 4.0K Dec 11 2021 .
drwxr-xr-x 17 root root 4.0K Dec 18 09:01 ..
lrwxrwxrwx 1 root root 34 Nov 13 2021 email@example.com -> /lib/systemd/system/getty@.service
I reverted some change. Please update to the just released (stable/master) v8.12.1 and reapply the
dietpi-autostart. That should work like with v8.11.
Made a mistake in above post, forgot to put kodi on autostart the
firstname.lastname@example.org does exist only then. Sorry.
Run update to v8.12.1 and kodi does now autostart.