Fails to install on OSMC Build for RPi4

[Hainswof]

Build link: http://download.osmc.tv/installers/diskimages/v19testing/OSMC_TGT_vero3_20210414.img.gz

Process I followed:

1. Install above OSMC image onto fresh MicroSD card (Samsung 64GB)
2. Insert MicroSD card into RPi4 (Model 8GB)
3. Updated OSMC from it's internal updater
4. Attempted to install steamlink-launcher v0.0.9 - error installing

Error message: "Failed to install due to an invalid structure"

[swetoast]

Readded a ckean ziip but again im not supporting rpi4 since its not supported by steam unless @slouken gives the thumbs up

[Hainswof]

also im not sure if rpi4 will work well since it doesnt have hardware acceleration so if there is performance issues i have no way to fix that

@swetoast - steamlink works very well on RPi4 running the latest Raspberry Pi OS.

I was simply hoping for a method that would avoid me having to manually swap SD cards each time one would like to go from using OSMC and then like to play SteamLink.

Regardless, I appreciate what you have done creating this plugin for others that are using the correctly supported hardware. :)

[slouken]

again im not supporting rpi4 since its not supported by steam unless @slouken gives the thumbs up

thumbs up :)

[swetoast]

@Hainswof retry the zip it should work

[swetoast]

@slouken ill update the readme to include rpi4

[Hainswof]

@swetoast @slouken - Thank you kindly to you both!

I can confirm it now installs :)

A New Challenge Emerges:
When launching the app we get the following screen (attached)

Pressing Enter at this stage exits back to OSMC.

[Hainswof]

UPDATE:
I managed to solve the above challenge by connecting via SSH and entering the following command:

sudo apt-get install gnupg

Now, when launching the SteamLink Launcher app we get the following:

Pressing Enter at this stage, once again, exits back to OSMC.

[Hainswof]

UPDATE:
I have tried commenting out the line mentioned in the above output (#dtoverlay=vc4-kms-v3d)

However when rebooting OSMC gives us a sad face:

I have also tried changing the line of code from:
dtoverlay=vc4-kms-v3d,cma-512
to
dtoverlay=vc4-fkms-v3d,cma-512

This gets us booting correctly into OSMC again and also past the "dtoverlay=vc4-kms-v3d" challenge.

However, with this configuration, SteamLink Launcher while it looks like it's about to launch correctly (going through it's TXT output like before), it simply exits itself now, back to OSMC before it gets any further.

[swetoast]

Will look at it this weekend

[swetoast]

keep the reports coming with your findings cause i dont have an rpi4

[swetoast]

@Hainswof looks like the rpi4 itselt has some issue with blank screens etc releated to the kernel gonna investigate see if i can borrow or pick up a rpi4 to experiment with.

• added gnupg to the launcher for next release

[Hainswof]

@Hainswof looks like the rpi4 itselt has some issue with blank screens etc releated to the kernel gonna investigate see if i can borrow or pick up a rpi4 to experiment with.

• added gnupg to the launcher for next release

Brilliant! Thank you kindly for your willingness to solve this challenge for all those in the same boat as us 🙏

Let me know if you would like me to test anything for you and give feedback, I will gladly help

[swetoast]

Keep hacking away at it and if you find anything post it to this thread meanwhile ill hunt for a rpi4 either pick up or borrow one you can ask @samnazarko for pointers in OSMC

[swetoast]

@Hainswof

grab-logs -A

mind posting those after it crashes that would be of great help

[Hainswof]

@swetoast gladly.

Here is the log after the crash when using "dtoverlay=vc4-fkms-v3d,cma-512" in config.txt:
https://paste.osmc.tv/kemedebiqo

Here is the log when using the original "dtoverlay=vc4-kms-v3d,cma-512" in config.txt:
https://paste.osmc.tv/zumaziradi

[swetoast]

common theme when it crashes is

[   25.687618] vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19
[   25.688259] vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19
[  131.647063] vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19
[  131.647631] vc4_hdmi fef05700.hdmi: ASoC: error at snd_soc_dai_startup on fef05700.hdmi: -19

need to investigate what that error is

[swetoast]

Seems like a bug in the kernel, this might be good to ping @samnazarko so he can merge a patch and make a test kernel

https://www.mail-archive.com/dri-devel@lists.freedesktop.org/msg337479.html

[swetoast]

added a thread at osmc forums

https://discourse.osmc.tv/t/race-condition-in-the-rpi4-kernel/89371

[swetoast]

Closing this bug since its limited to OSMC itself and not the launcher, all you can do @Hainswof is wait for @samnazarko to update the kernel

[Hainswof]

Closing this bug since its limited to OSMC itself and not the launcher, all you can do @Hainswof is wait for @samnazarko to update the kernel

I understand.

Thank you kindly for your help so far in this @swetoast - really appreciated 🙏

[samnazarko]

Our kernel is very recent -- so it's not an OSMC issue.

[swetoast]

Techically its kernel issue so like sam said on the forums just wait for the patch to be merged upstreams then trickle down to OSMC then you will be gaming in no time :)

[Hainswof]

Brilliant - thank you both for your help @swetoast and @samnazarko 😁

Looking forward to it 🎮

[cwilhelmsen]

Yup, thanks to all of you for your hard work on this!

[flos06]

Is there any way to see if/when it gets merged? Or should I just try every time there is an OSMC update?

[xsellier]

Any news on that, still having, but the kernel has been patched ever since.

[swetoast]

Provide logs on the OSMC forum board is better then asking around it here, waiting for a patch myself

[xsellier]

Posted on the osmc forum:
https://discourse.osmc.tv/t/rpi-4-steamlink-doesnt-work/91134