ich777 Posted January 16, 2022 Share Posted January 16, 2022 1 hour ago, Bot_Legolas said: Steam Play or noVNC doesn't seem to make any difference Are you really sure about that? Do you also have a VM running on that server where you can test the card? Are you sure that you are not bottlenecked by your CPU? I've never experienced anything like that. Quote Link to comment
Bot_Legolas Posted January 16, 2022 Share Posted January 16, 2022 8 hours ago, ich777 said: Are you really sure about that? Do you also have a VM running on that server where you can test the card? Are you sure that you are not bottlenecked by your CPU? I've never experienced anything like that. Yes I'm sure I will take a look later at this again. I got an VM but only for homeassistant right now. CPU could be but shouldn't in an GPU only benchmark. I played this games last year before I started studying with an gtx 970 with no problems. I'm remembering now that my CPU is not capable of IOMMU guess this might be the problem. I will try to force the power state later on to get this thing out of idle state. Never seen something like that too. Quote Link to comment
Bot_Legolas Posted January 16, 2022 Share Posted January 16, 2022 @ich777 I quickly set up folding@home to test if the GPU is working in docker. It is running now around 90% load, core clocks seems fine, power usage looks good. So this is working. Quote Link to comment
ich777 Posted January 16, 2022 Share Posted January 16, 2022 1 hour ago, Bot_Legolas said: I quickly set up folding@home to test if the GPU is working in docker. It is running now around 90% load, core clocks seems fine, power usage looks good. So this is working. The card should also work fine in this container. Can you try to setup a VM with the card passed through and do there various tests if it's the same in the VM. It's very unlikely that the card will be slower in a container since the driver should do it's job anyways. Have you yet tried to switch the driver to something else than you are currently on? Quote Link to comment
Bot_Legolas Posted January 16, 2022 Share Posted January 16, 2022 1 hour ago, ich777 said: The card should also work fine in this container. Can you try to setup a VM with the card passed through and do there various tests if it's the same in the VM. It's very unlikely that the card will be slower in a container since the driver should do it's job anyways. Have you yet tried to switch the driver to something else than you are currently on? The card works in every other container fine. Will switch the driver to test it. Would like to set up an VM but can't pass it through, CPU not capable of VT-d only VT-x. That's why I chose this container in the first place. Quote Link to comment
ich777 Posted January 16, 2022 Share Posted January 16, 2022 10 minutes ago, Bot_Legolas said: The card works in every other container fine. Will switch the driver to test it. Would like to set up an VM but can't pass it through, CPU not capable of VT-d only VT-x. That's why I chose this container in the first place. Okay. Have you tried yet to connect a monitor to the card, maybe the card thinks you are using it for mining because it's a LHR card. @Josh.5 is the display mirrored if a display is connected to the card from the container like it was in my container? Quote Link to comment
Josh.5 Posted January 16, 2022 Author Share Posted January 16, 2022 Okay. Have you tried yet to connect a monitor to the card, maybe the card thinks you are using it for mining because it's a LHR card. @Josh.5 is the display mirrored if a display is connected to the card from the container like it was in my container?I have not tested yet, but it should be yes. Quote Link to comment
ich777 Posted January 16, 2022 Share Posted January 16, 2022 Just now, Josh.5 said: I have not tested yet, but it should be yes. @Bot_Legolas I can think of an issue that the card thinks that it is used to mine crypto without a monitor connected, can you please try to connect a monitor to it and report back? If it works you can buy a dummy HDMI plug with a valid EDID on it for lets say 1920x1080. Quote Link to comment
Josh.5 Posted January 16, 2022 Author Share Posted January 16, 2022 Dummy hdmi plugs are essential for this. Makes life some much simpler.The one I have reports a 4k resolution and cost about $4 Quote Link to comment
Bot_Legolas Posted January 16, 2022 Share Posted January 16, 2022 11 minutes ago, ich777 said: @Bot_Legolas I can think of an issue that the card thinks that it is used to mine crypto without a monitor connected, can you please try to connect a monitor to it and report back? If it works you can buy a dummy HDMI plug with a valid EDID on it for lets say 1920x1080. HDMI dummy is connected but I will connect real display maybe that helps. Will report back if the output is mirrored when connected to a display @Josh.5 Quote Link to comment
Bot_Legolas Posted January 16, 2022 Share Posted January 16, 2022 33 minutes ago, Bot_Legolas said: HDMI dummy is connected but I will connect real display maybe that helps. Will report back if the output is mirrored when connected to a display @Josh.5 So driver downgraded changed nothing for me. Display connected gets regognized by the card itself reports fine but won't output. Is there maybe a parameter for that? Quote Link to comment
[RIVINS] Posted January 16, 2022 Share Posted January 16, 2022 (edited) On 1/14/2022 at 2:00 AM, Josh.5 said: Have you got something modifying the permissions of the files in that directory? Hey, No its a brand new install. this is a test on a test machine. i have one ssd set in the array not in the cache. what permission does the share need ?. installling the game works fine. i can see the files. Looks like the file filesystem_steam.so it's not even there. Edited January 16, 2022 by [RIVINS] Quote Link to comment
Mobious Posted January 17, 2022 Share Posted January 17, 2022 (edited) I'm trying to test this out with HL2 Deathmatch and I get this error. Also, my shared game directory didn't come over. I can see it in the file system but it wont let me add it in Steam. I tried running HL2 from the icon and got this. Edited January 17, 2022 by Mobious Quote Link to comment
Josh.5 Posted January 17, 2022 Author Share Posted January 17, 2022 @[RIVINS] @Mobious Try google the error "Unable to load filesystem_steam.so". Looks like there are some issues with steam and XFS file systems for some games. I have not looked into this, but let me know if you find a fix that can be applied to the container or Unraid configuration. Quote Link to comment
L4stIdi0t Posted January 17, 2022 Share Posted January 17, 2022 Maybe add this URL for steam to the post? https://help.steampowered.com/en/faqs/view/2EA8-4D75-DA21-31EB My controller still wont work in games ran through steam play network type: Host ports: 27031-27036 UDP; 27036, 8083, 32123 and 2222 are TCP I also have the plugin installed from Ich777 and rebooted my machine just in case but it didnt help How would we host multiple instances with controller support from the same machine? I am also getting this in my logs but the audio works fine 2022-01-17 10:37:51,293 INFO reaped unknown pid 418 (exit status 1) 2022-01-17 10:37:51,299 INFO spawned: 'audiostream' with pid 423 2022-01-17 10:37:51,302 INFO exited: audiostream (exit status 111; not expected) 2022-01-17 10:37:53,795 INFO spawned: 'audiostream' with pid 703 2022-01-17 10:37:53,800 INFO exited: audiostream (exit status 111; not expected) 2022-01-17 10:37:56,830 INFO spawned: 'audiostream' with pid 784 2022-01-17 10:37:56,834 INFO exited: audiostream (exit status 111; not expected) 2022-01-17 10:37:56,834 INFO gave up: audiostream entered FATAL state, too many start retries too quickly Quote Link to comment
ich777 Posted January 17, 2022 Share Posted January 17, 2022 1 minute ago, L4stIdi0t said: Maybe add this URL for steam to the post? I don't think that would be the best idea since it also lists other ports that are not necessary and not all these ports are needed for all games. If you for example have some game servers installed on your server you maybe run into various port conflicts if everything is added to the template. Steam Client selects only ports that are available for multiplayer games. 8 minutes ago, L4stIdi0t said: How would we host multiple instances with controller support from the same machine? Have you yet got a second container to run? Quote Link to comment
Josh.5 Posted January 17, 2022 Author Share Posted January 17, 2022 30 minutes ago, L4stIdi0t said: Maybe add this URL for steam to the post? https://help.steampowered.com/en/faqs/view/2EA8-4D75-DA21-31EB My controller still wont work in games ran through steam play network type: Host ports: 27031-27036 UDP; 27036, 8083, 32123 and 2222 are TCP I would like to just quietly add that, while I have added the ports to the template, I only did so so that Unraid was aware of them and they would show for people wanting to check for port conflicts. Just so we are clear, running a container with net=host means the port mapping is pointless in the `docker run` command. The processes inside the container are on the same network interface as the host already. Quote How would we host multiple instances with controller support from the same machine? This is still something I am investigating, but for now I am setting that aside and I'm going to work on improving the overall experience of the container. I suspect with the new SteamOS coming up in just over a month we may see some nice changes and I want to be in a place where I can rebase this container (or create a second one) with these things. Quote Link to comment
Josh.5 Posted January 17, 2022 Author Share Posted January 17, 2022 44 minutes ago, L4stIdi0t said: I am also getting this in my logs but the audio works fine 2022-01-17 10:37:51,293 INFO reaped unknown pid 418 (exit status 1) 2022-01-17 10:37:51,299 INFO spawned: 'audiostream' with pid 423 2022-01-17 10:37:51,302 INFO exited: audiostream (exit status 111; not expected) 2022-01-17 10:37:53,795 INFO spawned: 'audiostream' with pid 703 2022-01-17 10:37:53,800 INFO exited: audiostream (exit status 111; not expected) 2022-01-17 10:37:56,830 INFO spawned: 'audiostream' with pid 784 2022-01-17 10:37:56,834 INFO exited: audiostream (exit status 111; not expected) 2022-01-17 10:37:56,834 INFO gave up: audiostream entered FATAL state, too many start retries too quickly Can you check the path :/.cache/log/audiostream*" for errors. Are you running the latest version of the container AND did you remove and re-install the template from CA? Quote Link to comment
L4stIdi0t Posted January 17, 2022 Share Posted January 17, 2022 19 minutes ago, Josh.5 said: Can you check the path :/.cache/log/audiostream*" for errors. Are you running the latest version of the container AND did you remove and re-install the template from CA? audiostream.err.log tcpserver: fatal: no IP address for localhost audiostream.err libva info: VA-API version 1.10.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_10 libva info: va_openDriver() returns 0 ERROR: from element /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0: Disconnected: Connection terminated Additional debug info: ../ext/pulse/pulsesrc.c(368): gst_pulsesrc_is_dead (): /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0 ERROR: from element /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0: Disconnected: Connection terminated Additional debug info: ../ext/pulse/pulsesrc.c(368): gst_pulsesrc_is_dead (): /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0 ERROR: from element /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0: Internal data stream error. Additional debug info: ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0: streaming stopped, reason error (-5) ERROR: from element /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0: pa_stream_cork() failed: Connection terminated Additional debug info: ../ext/pulse/pulsesrc.c(1736): gst_pulsesrc_set_corked (): /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0 ERROR: from element /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0: Disconnected: Connection terminated Additional debug info: ../ext/pulse/pulsesrc.c(368): gst_pulsesrc_is_dead (): /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0 ERROR: from element /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0: Disconnected: Connection terminated Additional debug info: ../ext/pulse/pulsesrc.c(368): gst_pulsesrc_is_dead (): /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0 ERROR: from element /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0: Disconnected: Connection terminated Additional debug info: ../ext/pulse/pulsesrc.c(368): gst_pulsesrc_is_dead (): /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0 ERROR: from element /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0: Internal data stream error. Additional debug info: ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0: streaming stopped, reason error (-5) ERROR: from element /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0: pa_stream_cork() failed: Connection terminated Additional debug info: ../ext/pulse/pulsesrc.c(1736): gst_pulsesrc_set_corked (): /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0 ERROR: from element /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0: Disconnected: Connection terminated Additional debug info: ../ext/pulse/pulsesrc.c(368): gst_pulsesrc_is_dead (): /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0 audioswebsock.err 192.168.188.54 - - [10/Jan/2022 18:24:50] 192.168.188.54: Plain non-SSL (ws://) WebSocket connection 192.168.188.54 - - [10/Jan/2022 18:24:50] connecting to: localhost:5901 WebSocket server settings: - Listen on :32123 - No SSL/TLS support (no cert file) - proxying from :32123 to localhost:5901 audiowebsock.err.log WebSocket server settings: - Listen on :32123 - No SSL/TLS support (no cert file) - proxying from :32123 to localhost:5901 10.253.0.3 - - [17/Jan/2022 10:46:02] 10.253.0.3: Plain non-SSL (ws://) WebSocket connection 10.253.0.3 - - [17/Jan/2022 10:46:02] connecting to: localhost:5901 10.253.0.3 - - [17/Jan/2022 10:46:02] Failed to connect to localhost:5901: [Errno 111] Connection refused WebSocket server settings: - Listen on :32123 - No SSL/TLS support (no cert file) - proxying from :32123 to localhost:5901 WebSocket server settings: - Listen on :32123 - No SSL/TLS support (no cert file) - proxying from :32123 to localhost:5901 Quote Link to comment
L4stIdi0t Posted January 17, 2022 Share Posted January 17, 2022 1 hour ago, ich777 said: Have you yet got a second container to run? I ran a second container for friends with worse pcs or lan servers inside games(most are keyboard and mouse) Quote Link to comment
Josh.5 Posted January 17, 2022 Author Share Posted January 17, 2022 20 minutes ago, L4stIdi0t said: audiostream.err.log tcpserver: fatal: no IP address for localhost audiostream.err libva info: VA-API version 1.10.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_10 libva info: va_openDriver() returns 0 ERROR: from element /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0: Disconnected: Connection terminated Additional debug info: ../ext/pulse/pulsesrc.c(368): gst_pulsesrc_is_dead (): /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0 ERROR: from element /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0: Disconnected: Connection terminated Additional debug info: ../ext/pulse/pulsesrc.c(368): gst_pulsesrc_is_dead (): /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0 ERROR: from element /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0: Internal data stream error. Additional debug info: ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0: streaming stopped, reason error (-5) ERROR: from element /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0: pa_stream_cork() failed: Connection terminated Additional debug info: ../ext/pulse/pulsesrc.c(1736): gst_pulsesrc_set_corked (): /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0 ERROR: from element /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0: Disconnected: Connection terminated Additional debug info: ../ext/pulse/pulsesrc.c(368): gst_pulsesrc_is_dead (): /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0 ERROR: from element /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0: Disconnected: Connection terminated Additional debug info: ../ext/pulse/pulsesrc.c(368): gst_pulsesrc_is_dead (): /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0 ERROR: from element /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0: Disconnected: Connection terminated Additional debug info: ../ext/pulse/pulsesrc.c(368): gst_pulsesrc_is_dead (): /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0 ERROR: from element /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0: Internal data stream error. Additional debug info: ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0: streaming stopped, reason error (-5) ERROR: from element /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0: pa_stream_cork() failed: Connection terminated Additional debug info: ../ext/pulse/pulsesrc.c(1736): gst_pulsesrc_set_corked (): /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0 ERROR: from element /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0: Disconnected: Connection terminated Additional debug info: ../ext/pulse/pulsesrc.c(368): gst_pulsesrc_is_dead (): /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0 audioswebsock.err 192.168.188.54 - - [10/Jan/2022 18:24:50] 192.168.188.54: Plain non-SSL (ws://) WebSocket connection 192.168.188.54 - - [10/Jan/2022 18:24:50] connecting to: localhost:5901 WebSocket server settings: - Listen on :32123 - No SSL/TLS support (no cert file) - proxying from :32123 to localhost:5901 audiowebsock.err.log WebSocket server settings: - Listen on :32123 - No SSL/TLS support (no cert file) - proxying from :32123 to localhost:5901 10.253.0.3 - - [17/Jan/2022 10:46:02] 10.253.0.3: Plain non-SSL (ws://) WebSocket connection 10.253.0.3 - - [17/Jan/2022 10:46:02] connecting to: localhost:5901 10.253.0.3 - - [17/Jan/2022 10:46:02] Failed to connect to localhost:5901: [Errno 111] Connection refused WebSocket server settings: - Listen on :32123 - No SSL/TLS support (no cert file) - proxying from :32123 to localhost:5901 WebSocket server settings: - Listen on :32123 - No SSL/TLS support (no cert file) - proxying from :32123 to localhost:5901 Are there any other services running on port 5901 I need to change that, but I suspect that could be the issue... Quote Link to comment
L4stIdi0t Posted January 17, 2022 Share Posted January 17, 2022 Thanks for the responses and tips guys Reinstalling the container template from CA fixed my controller issue and it supports connecting all my controllers at the same time now so that is awesome Quote Link to comment
L4stIdi0t Posted January 17, 2022 Share Posted January 17, 2022 2 minutes ago, Josh.5 said: Are there any other services running on port 5901 I need to change that, but I suspect that could be the issue... I dont think so, if i runt the following root@Tower:~# sudo lsof -i:5901 root@Tower:~# Quote Link to comment
L4stIdi0t Posted January 17, 2022 Share Posted January 17, 2022 I was just browsing my steam games which i would install and the stream just crashed. This is what is in the docker log: 2022-01-17 12:39:29,279 INFO reaped unknown pid 704 (exit status 0) 2022-01-17 12:39:29,279 INFO reaped unknown pid 764 (exit status 0) 2022-01-17 12:39:29,279 INFO reaped unknown pid 765 (exit status 0) 2022-01-17 12:39:29,279 INFO reaped unknown pid 937 (exit status 0) 2022-01-17 12:39:29,279 INFO reaped unknown pid 966 (exit status 0) 2022-01-17 12:39:29,279 INFO reaped unknown pid 978 (exit status 0) 2022-01-17 12:39:29,279 INFO reaped unknown pid 2260 (exit status 0) 2022-01-17 12:39:29,279 INFO reaped unknown pid 2436 (exit status 0) 2022-01-17 12:39:29,279 INFO reaped unknown pid 2510 (exit status 0) 2022-01-17 12:39:29,279 INFO reaped unknown pid 2737 (exit status 0) 2022-01-17 12:39:29,279 INFO reaped unknown pid 2900 (exit status 0) 2022-01-17 12:39:29,487 INFO reaped unknown pid 3059 (exit status 0) 2022-01-17 12:39:30,165 INFO reaped unknown pid 1078 (exit status 0) 2022-01-17 12:39:30,165 INFO reaped unknown pid 3076 (exit status 0) Quote Link to comment
Bot_Legolas Posted January 18, 2022 Share Posted January 18, 2022 On 1/16/2022 at 12:41 PM, Josh.5 said: On 1/16/2022 at 12:40 PM, ich777 said: Okay. Have you tried yet to connect a monitor to the card, maybe the card thinks you are using it for mining because it's a LHR card. @Josh.5 is the display mirrored if a display is connected to the card from the container like it was in my container? I have not tested yet, but it should be yes. @ich777 card is mirroring the output if connected to a real display so this works Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.