No display after entering the container

[mpskex]

Thank you very much for this plugin. It's really a great idea to put steam link to LibreELEC

I am using OrangePi 3 LTS with Allwinner H6. I am installing the raspberry os container from this plugin.

I can pair the device with steam link. but when I click on connect, I cannot see anything but only the sound, which suggests some display issue as the app is already responsive to my control (only playing sound when I select certain options)

Then I connect the remote gaming pc with hdmi and found the control from the pi is actually working.

May I ask for your advice on where I can debug from? For example enable certain logs inside the container.

Many thanks in advance.

[Maladril]

Hey ! I have pretty much the same problem but I'm on a Raspberry Pi 5. I have ruled it as a particularity of my gaming PC which is the most unorthodox thing in the galaxy: AMD GPU on Ubuntu (yes, that's what I game on). Still haven't figured it out. Would appreciate some help to troubleshoot.

[meekys]

@mpskex This plugin uses the official steamlink binaries from Valve, which (to my understanding) only support the raspberry pi.

@Maladril If you have another PC that's capable of running Steam, that would be the best way to rule out the host (gaming PC)

For both of you, the best option is to grab the output of the run.sh command.
launch.sh should already be doing this, and putting the output in $ADDON_PROFILE_PATH/steamlink.log

There are ways to increase the verbosity of the logging that QT outputs, which is how the SteamLink binaries render to the screen, but off the top of my head I don't recall what they are.

AI suggests trying QT_LOGGING_RULES="*.debug=false;qt.text.*=true" as an environment variable

Putting this into a file within ~/.kodi/userdata/addon_data/plugin.program.steamlink/data/.env should (hopefully?) enable more verbose logging