Dear All,
it has been a very long time since my last visit here, it was everything fine till the last update.
I didn’t realize that last dist-upgrade would upgrade the base system from Wheezy to Buster, this has created issues with the services.
I kept the systemd conf and samba conf as my modified versions but it looks like that it wasn’t the best option to do. Now if I run my PI2 headless anything works properly but if I connect the monitor to the PI2 everything works (even in headless mode).
It is clear the culprit is systemd, it is waiting for some video/monitor event and if this doesn’t happen it gets stuck somewhere preventing all the following services (SSH and SAMBA specifically) to be initialized properly.
I need to fix this behavior because my equipment is supposed to be located in a place where it doesn’t need to be connected to a monitor. Maybe I can just reinstall o reconfigure the packages but I don’t know the name.
Fixing this issue is extremely important for me otherwise all my samba’s folders are inaccessible.
Thanks in advance,
D.
EDIT: Changed the title, it wasn’t a systemd issue.
We need to see logs to understand the issue you are experiencing.
OSMC’s earliest release was Jessie.
We never had a Wheezy release.
Sam
Yes sure… You see that my account was from 2015… 
I had a perfect and smooth experience till now.
Which logs do you think are most useful?
When I tool a look to xournactl I didn’t see anything relevant, however I hadn’t enough time to troubleshoot theOS, I just realized that something is preventing to boot properly when the monitor is disconnected, and those kind of issues are typicals of systemd.
To get a better understanding of the problem you are experiencing we need more information from you. The best way to get this information is for you to upload logs that demonstrate your problem. You can learn more about how to submit a useful support request here.
Depending on the used skin you have to set the settings-level to standard or higher, in summary:
-
enable debug logging at settings->system->logging
-
reboot the OSMC device twice(!)
-
reproduce the issue
-
upload the log set (all configs and logs!) either using the Log Uploader method within the My OSMC menu in the GUI or the ssh method invoking command grab-logs -A
-
publish the provided URL from the log set upload, here
Thanks for your understanding. We hope that we can help you get up and running again shortly.
OSMC skin screenshot:
@ActionA
Hi, thank you very much for your assistance.
Here is my log:
https://paste.osmc.tv/qodajujuba
To reproduce the bug is easy as keep the monitor just turned off.
If you turn on the monitor it goes immediately in stand-by mode as the signal was absent, any other service does not work, to reset the machine without unplug the AC I use the combination “alt + PrtSc + reisub”
It looks my issue is related with this:
[ 60.305762] vc4_hdmi 3f902000.hdmi: ASoC: error at snd_soc_dai_startup on 3f902000.hdmi: -19
[ 60.345503] vc4_hdmi 3f902000.hdmi: ASoC: error at snd_soc_dai_startup on 3f902000.hdmi: -19
[ 60.347424] vc4_hdmi 3f902000.hdmi: ASoC: error at snd_soc_dai_startup on 3f902000.hdmi: -19
[ 61.865227] vc4_hdmi 3f902000.hdmi: ASoC: error at snd_soc_dai_startup on 3f902000.hdmi: -19
[ 61.902876] vc4_hdmi 3f902000.hdmi: ASoC: error at snd_soc_dai_startup on 3f902000.hdmi: -19
[ 61.904541] vc4_hdmi 3f902000.hdmi: ASoC: error at snd_soc_dai_startup on 3f902000.hdmi: -19
[ 63.422076] vc4_hdmi 3f902000.hdmi: ASoC: error at snd_soc_dai_startup on 3f902000.hdmi: -19
[ 63.459772] vc4_hdmi 3f902000.hdmi: ASoC: error at snd_soc_dai_startup on 3f902000.hdmi: -19
[ 63.461450] vc4_hdmi 3f902000.hdmi: ASoC: error at snd_soc_dai_startup on 3f902000.hdmi: -19
[ 64.979139] vc4_hdmi 3f902000.hdmi: ASoC: error at snd_soc_dai_startup on 3f902000.hdmi: -19
[ 65.017155] vc4_hdmi 3f902000.hdmi: ASoC: error at snd_soc_dai_startup on 3f902000.hdmi: -19
[ 65.018899] vc4_hdmi 3f902000.hdmi: ASoC: error at snd_soc_dai_startup on 3f902000.hdmi: -19
[ 66.536279] vc4_hdmi 3f902000.hdmi: ASoC: error at snd_soc_dai_startup on 3f902000.hdmi: -19
[ 66.573867] vc4_hdmi 3f902000.hdmi: ASoC: error at snd_soc_dai_startup on 3f902000.hdmi: -19
[ 66.575547] vc4_hdmi 3f902000.hdmi: ASoC: error at snd_soc_dai_startup on 3f902000.hdmi: -19
Apparebtly it wasn’t systemd, altough I had similar weird situation with it, but this is something related with the PI, the Kernel and the same OSMC.
I found this thread where a dude was able to create a workaround to fix the problem, I don’t know if you were already aware of this workaround, I won’t try it until you guys have taken a look at it and left a comment about:
https://forum.kodi.tv/showthread.php?tid=363843&pid=3054288#pid3054288
EDIT, it looks like it is a well known bug:
Best regards,
D.
I tried to add these voices:
hdmi_force_hotplug=1
hdmi_ingore_cec_init=1
But the system does not want to boot.
I understood that I have to hardcode the EDID however I don’t have any folders called with this name:
ls -l /lib/firmware/
total 12
drwxr-xr-x 2 root root 4096 Nov 22 01:07 brcm
drwxr-xr-x 2 root root 4096 Nov 22 01:13 mediatek
-rw-r--r-- 1 root root 1271 May 1 2016 mt7610u_sta.dat
As for noiw my OSMC does not want to start in headless mode.
I hope to get better directions to fix this!
Thank in advance,
D.
You would indeed need to hardcode an EDID for now. This is currently a limitation of the new graphics stack that Raspberry Pi mandates.
Thank you very much, is there any OSMC guide/tutorial I can follow?
The one I found assumes that you have an EDID entry already available in your /lib/firmware which I don’t, or should I just create a fake entry?
EDIT: looks I found something: OSMC doesn't start with TV off after August 2021 update - #2 by sam_nazarko
Thanks in advance,
D.
