December 5, 20232 yr On 11/29/2023 at 9:14 AM, SavellM said: So few things... I've just spun up this container and so far nice! Got Steam up and running. For games that say 'Runs on Windows' do you just go into force compatibility? Secondly, I was looking at installing some bits, but it needs to do a apt install, I noticed there are a ton of updates to do right out of the box. Is it safe to do this? I tried to apt update, but it just hung at 22% *edit*: I saw in unRAID logs: Nov 29 16:31:08 Namek login: pam_unix(login:auth): check pass; user unknown Nov 29 16:31:08 Namek login: pam_unix(login:auth): authentication failure; logname=LOGIN uid=0 euid=0 tty=/dev/tty1 ruser= rhost= Nov 29 16:31:10 Namek login: FAILED LOGIN 3 FROM tty1 FOR full-upgrade, Authentication failure Not sure if it helps diagnose the upgrading? I was running the command as sudo apt-get full-upgrade Thirdly, I was trying to get steam to install games onto my NVME but it took forever to 'Reserve Space' - is this normal? Fourth, I launch a game, seems to be fine, but it never actually loads or plays, it says Launching and then Changes to STOP, but nothing displays, there is no game. Then eventually it just goes back to 'Play' like the game gets stopped automatically. I have noticed: Nov 30 14:46:55 Namek kernel: nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DP-0 In unRAID logs. I do have a DP dummy plug installed. Even trying Steam-Link play nothing happens, games dont load. For reference I have passed through a Quadro P2000 to test. I know it's not a gaming card, but I wanted to check before I purchased a GPU just for this. But so far no luck... Games dont load and I just get kicked back to desktop @Josh.5 any help would be massively appreciated. I would join Discord but the link for whatever reason doesn't work I am by no way an expert but you may find my answers useful To help you with your first question, if you haven't figured it out, your question 1is just like your question 4. Once you open steam you have to go to steam, then settings, then capability and click to turn on the two options to force steam to work with your library. And choose a default proton layer. And to update the apps you have installed within the container your going to go to the start menu ( Applications) then system, then software, and there should be an option to update all your installed apps through this option. Also If you install apps using this software manager its easier to install what your looking for like kodi, and other applications. Hope this help.
December 5, 20232 yr 10 hours ago, Mrtj18 said: I am by no way an expert but you may find my answers useful To help you with your first question, if you haven't figured it out, your question 1is just like your question 4. Once you open steam you have to go to steam, then settings, then capability and click to turn on the two options to force steam to work with your library. And choose a default proton layer. And to update the apps you have installed within the container your going to go to the start menu ( Applications) then system, then software, and there should be an option to update all your installed apps through this option. Also If you install apps using this software manager its easier to install what your looking for like kodi, and other applications. Hope this help. Thanks it does a bit. I did manage to figure out the compatibility tab and got that sorted. Clicking Apps then System then Software never yields any updates available. Its always you're updated. Even tho I know there is like 650 updates pending if you do apt update... I *Think* I figured out no4 - I believe its to do with my P2000 not really being compatible for gaming, so will get a proper GPU and test again.
December 5, 20232 yr Yeah im running 2 Gaming gpu's in my system. One is a rtx 3080 which runs this docker app, and the other is a gtx 1080 which drives my VMs. My setup runs very well. I did have a few issues running some of my games at the correct frame rates and such. But it took some trail and error to tweak my game settings right, and it didnt happen over night. lol
December 10, 20232 yr Hi Team, If anyone running an AMD GPU is having the issue where X Serve is crashing add --device='/dev/dri' to your docker extra paramaters section and do an apt-get upgrade for the AMD driver this seems to have sorted it for me.
December 11, 20232 yr Hi ! Thanks for this great project! I just tested it on a fresh unraid install (uptodate) For the moment with an Intel iGPU for proof of concept. If it works, he'll get an nvidia. Anyway, the install works, the docker launches: but it's impossible to log into the webUI. What a miss ?! Neko : I have access to the webUI, but I can't login. "Invalid password". What should I do? VNC : I get a page not found error. docker run -d --name='steam-headless' --net='host' --privileged=true -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Serveur" -e HOST_CONTAINERNAME="steam-headless" -e 'USER_PASSWORD'='*******************' -e 'TZ'='Europe/Paris' -e 'USER_LOCALES'='fr_FR.UTF-8 UTF-8' -e 'NVIDIA_PATCH_VERSION'='' -e 'WEB_UI_MODE'='neko' -e 'NVIDIA_VISIBLE_DEVICES'='all' -e 'NVIDIA_DRIVER_CAPABILITIES'='all' -e 'DISPLAY'=':0' -e 'MODE'='primary' -e 'PORT_NOVNC_WEB'='8083' -e 'ENABLE_VNC_AUDIO'='false' -e 'ENABLE_EVDEV_INPUTS'='true' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8083]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/Josh5/docker-steam-headless/master/images/steam-icon.png' -v '/mnt/user/appdata/steam-headless':'/home/default':'rw' -v '/mnt/user/Gaming/':'/mnt/games':'rw' --hostname='SteamHeadless' --add-host='SteamHeadless:127.0.0.1' --restart='unless-stopped' --shm-size='2G' --ipc='host' -v '/tmp/.X11-unix/':'/tmp/.X11-unix/':'rw' -v '/tmp/tmp/pulse/':'/tmp/tmp/pulse/':'rw' --ulimit='nofile=1024:524288' --device='/dev/fuse' --device='/dev/uinput' --device-cgroup-rule='c 13:* rmw' --cap-add='NET_ADMIN' --cap-add='SYS_ADMIN' --cap-add='SYS_NICE' --security-opt='seccomp=unconfined' 'josh5/steam-headless:latest' 1dad834005135f44abad486b3212bd052736d7cfcc191c85bf9caa294bb52de7 And the log : cat: '/sys/class/drm/card*/status': No such file or directory [ /etc/cont-init.d/70-configure_desktop.sh: executing... ] **** Configure Desktop **** - Enable Desktop service. - Ensure home directory template is owned by the default user. - Installing default home directory template DONE [ /etc/cont-init.d/70-configure_xorg.sh: executing... ] **** Generate default xorg.conf **** /etc/cont-init.d/90-configure_neko.sh: line 17: ip: command not found - Configure Xwrapper.config - Configure container as primary the X server - Enabling evdev input class on pointers, keyboards, touchpads, touch screens, etc. - No monitors connected. Installing dummy xorg.conf DONE [ /etc/cont-init.d/80-configure_flatpak.sh: executing... ] **** Configure Flatpak **** - Flatpak configured for running inside a Docker container DONE [ /etc/cont-init.d/90-configure_neko.sh: executing... ] **** Configure Neko **** - Enable Neko server - Setting NEKO_NAT1TO1= DONE [ /etc/cont-init.d/90-configure_steam.sh: executing... ] **** Configure Steam **** - Enable Steam auto-start script DONE [ /etc/cont-init.d/90-configure_sunshine.sh: executing... ] **** Configure Sunshine **** - Enable Sunshine server DONE [ /etc/cont-init.d/90-configure_vnc.sh: executing... ] **** Configure VNC **** - Configure VNC service port '32036' - Configure pulseaudio encoded stream port '32037' - Disable VNC server DONE [ /etc/cont-init.d/95-setup_wol.sh: executing... ] **** Configure WoL Manager **** - Disable WoL Manager service. **** Starting supervisord **** - Logging all root services to '/var/log/supervisor/' - Logging all user services to '/home/default/.cache/log/' Edited December 11, 20232 yr by Viking
December 17, 20232 yr I have installed this on a server and, once a game is running, see exceptional performance. But getting a game to launch can take significant time. I've tried installing the game library both to my main array and to my SSD cache disk (SATA though, not NvME)... I've tried various flavors of Proton... I've tried Moonlight, Remote Play, and NoVNC... All take forever for a game to launch. Pinning CPU cores to the container also did not seem to have any affect. The computer is an ex-server, primarily used for media storage, so it's not exactly gaming hardware, but it should be solid enough. The container also has sole access to a RTX 3080, besides the hardware in the attached image. Any help is appreciated! Edited December 17, 20232 yr by MOEman365 Removed the obvious "installed on Unraid"
December 18, 20232 yr On 12/17/2023 at 1:48 AM, MOEman365 said: I have installed this on a server and, once a game is running, see exceptional performance. But getting a game to launch can take significant time. I've tried installing the game library both to my main array and to my SSD cache disk (SATA though, not NvME)... I've tried various flavors of Proton... I've tried Moonlight, Remote Play, and NoVNC... All take forever for a game to launch. Pinning CPU cores to the container also did not seem to have any affect. The computer is an ex-server, primarily used for media storage, so it's not exactly gaming hardware, but it should be solid enough. The container also has sole access to a RTX 3080, besides the hardware in the attached image. Any help is appreciated! I noticed greatly improved loading times, if I used pool/cache mount points for games share, instead of user or user0. Fx /mnt/data_ssd/Games/ instead of /mnt/user/Games. Also for appdata: /mnt/cache/appdata/steam-headless.
December 24, 20232 yr The docker has been working very well for the last few months. Yesterday I spun it up and when accessing the GUI, it "fails to connect to server." The logs are: 2023-12-25 09:22:30,699 INFO spawned: 'xorg' with pid 274 2023-12-25 09:22:30,727 WARN exited: xorg (exit status 1; not expected) 2023-12-25 09:22:33,645 INFO spawned: 'xorg' with pid 318 2023-12-25 09:22:33,674 WARN exited: xorg (exit status 1; not expected) 2023-12-25 09:22:37,652 INFO spawned: 'xorg' with pid 368 2023-12-25 09:22:37,681 WARN exited: xorg (exit status 1; not expected) 2023-12-25 09:22:38,682 INFO gave up: xorg entered FATAL state, too many start retries too quickly 2023-12-25 09:22:59,742 WARN exited: x11vnc (exit status 11; not expected) 2023-12-25 09:22:59,742 WARN exited: sunshine (exit status 11; not expected) 2023-12-25 09:22:59,743 INFO spawned: 'x11vnc' with pid 638 2023-12-25 09:22:59,745 INFO spawned: 'sunshine' with pid 639 2023-12-25 09:22:59,759 WARN exited: desktop (exit status 11; not expected) 2023-12-25 09:22:59,760 INFO spawned: 'desktop' with pid 646 2023-12-25 09:23:00,765 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-12-25 09:23:00,765 INFO success: desktop entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-12-25 09:23:00,765 INFO success: sunshine entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-12-25 09:23:00,765 INFO reaped unknown pid 652 (exit status 0) 2023-12-25 09:23:29,870 WARN exited: x11vnc (exit status 11; not expected) 2023-12-25 09:23:29,870 WARN exited: sunshine (exit status 11; not expected) 2023-12-25 09:23:29,870 WARN exited: desktop (exit status 11; not expected) 2023-12-25 09:23:29,872 INFO spawned: 'x11vnc' with pid 1011 2023-12-25 09:23:29,873 INFO spawned: 'desktop' with pid 1012 2023-12-25 09:23:29,874 INFO spawned: 'sunshine' with pid 1013 Not sure what's changed. I recently updated to 6.12.6, but nothing else is having an issue.
December 30, 20232 yr Hi Team, for those having the X Server crashing issue please add --device='/dev/dri' to your extra paramaters, i am using an AMD GPU and this solved the crashing for me. Happy new year.
January 5, 20242 yr I am having the same issue as well. I upgraded from 6.12.4 to 6.12.6, and how this container no longer works, which is a shame. I really like it. 2024-01-06 01:39:28,109 INFO Included extra file "/etc/supervisor.d/dbus.ini" during parsing 2024-01-06 01:39:28,109 INFO Included extra file "/etc/supervisor.d/desktop.ini" during parsing 2024-01-06 01:39:28,110 INFO Included extra file "/etc/supervisor.d/neko.ini" during parsing 2024-01-06 01:39:28,110 INFO Included extra file "/etc/supervisor.d/pulseaudio.ini" during parsing 2024-01-06 01:39:28,110 INFO Included extra file "/etc/supervisor.d/steam.ini" during parsing 2024-01-06 01:39:28,110 INFO Included extra file "/etc/supervisor.d/sunshine.ini" during parsing 2024-01-06 01:39:28,110 INFO Included extra file "/etc/supervisor.d/udev.ini" during parsing 2024-01-06 01:39:28,110 INFO Included extra file "/etc/supervisor.d/vnc-audio.ini" during parsing 2024-01-06 01:39:28,110 INFO Included extra file "/etc/supervisor.d/vnc.ini" during parsing 2024-01-06 01:39:28,110 INFO Included extra file "/etc/supervisor.d/wol-power-manager.ini" during parsing 2024-01-06 01:39:28,110 INFO Included extra file "/etc/supervisor.d/xorg.ini" during parsing 2024-01-06 01:39:28,110 INFO Included extra file "/etc/supervisor.d/xvfb.ini" during parsing 2024-01-06 01:39:28,110 INFO Set uid to user 0 succeeded 2024-01-06 01:39:28,112 INFO RPC interface 'supervisor' initialized 2024-01-06 01:39:28,112 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2024-01-06 01:39:28,112 INFO supervisord started with pid 1 2024-01-06 01:39:29,114 INFO spawned: 'dbus' with pid 1026 2024-01-06 01:39:29,115 INFO spawned: 'udev' with pid 1027 2024-01-06 01:39:29,116 INFO spawned: 'xorg' with pid 1028 2024-01-06 01:39:29,116 INFO spawned: 'frontend' with pid 1029 2024-01-06 01:39:29,117 INFO spawned: 'pulseaudio' with pid 1030 2024-01-06 01:39:29,118 INFO spawned: 'x11vnc' with pid 1032 2024-01-06 01:39:29,119 INFO spawned: 'desktop' with pid 1035 2024-01-06 01:39:29,120 INFO spawned: 'sunshine' with pid 1039 PULSEAUDIO: Starting pulseaudio service 2024-01-06 01:39:29,128 INFO reaped unknown pid 1058 (exit status 0) 2024-01-06 01:39:30,124 INFO success: dbus entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-01-06 01:39:30,124 INFO success: udev entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-01-06 01:39:30,124 INFO success: xorg entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-01-06 01:39:30,124 INFO success: frontend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-01-06 01:39:30,124 INFO success: pulseaudio entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-01-06 01:39:30,124 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-01-06 01:39:30,124 INFO success: desktop entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-01-06 01:39:30,124 INFO success: sunshine entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-01-06 01:39:30,168 WARN exited: xorg (exit status 134; not expected) 2024-01-06 01:39:30,203 INFO spawned: 'xorg' with pid 1096 2024-01-06 01:39:30,231 WARN exited: xorg (exit status 134; not expected) 2024-01-06 01:39:32,144 INFO spawned: 'xorg' with pid 1124 2024-01-06 01:39:32,172 WARN exited: xorg (exit status 134; not expected) 2024-01-06 01:39:35,144 INFO spawned: 'xorg' with pid 1166 2024-01-06 01:39:35,171 WARN exited: xorg (exit status 134; not expected) 2024-01-06 01:39:38,174 INFO spawned: 'xorg' with pid 1208 2024-01-06 01:39:38,202 WARN exited: xorg (exit status 134; not expected) 2024-01-06 01:39:39,203 INFO gave up: xorg entered FATAL state, too many start retries too quickly It seems like the issue is related to PULSEAUDIO? Or perhaps xorg? I do not have an NVidia card installed, and use my iGPU, but I passthrough --device==/dev/dri and the container confirms it can see it. I only connect over VNC, and use this container purely as a lancache for steam.
January 6, 20242 yr Actually, changing the container to neko and then back to vnc seems to have fixed it. It is now working for me.
January 7, 20242 yr On 12/18/2023 at 8:38 PM, daemon9th said: I noticed greatly improved loading times, if I used pool/cache mount points for games share, instead of user or user0. Fx /mnt/data_ssd/Games/ instead of /mnt/user/Games. Also for appdata: /mnt/cache/appdata/steam-headless. You just fix all the issues I had! Changing both mount points and now it just performs as it should!
January 9, 20242 yr I'm encountering a problem where it seems stalled trying to download drivers and Firefox. It gets stuck on one specific download. The ones before it went fine, but it'll never progress to the ones after. It always gets stuck at 8%.
January 18, 20242 yr I was able to resolve this by renaming a manual driver download and placing it in the proper directory. Instead of trying to download the file, it ran what was already there.
January 26, 20242 yr Hello, I encountered this error while trying to run Steam headless. What should I do? Thank you very much. [ /etc/cont-init.d/10-setup_user.sh: executing... ] **** Configure default user **** - Setting default user uid=99(default) gid=100(default) usermod: no changes - Adding default user to any additional required device groups - Adding user 'default' to group: 'video' - Adding user 'default' to group: 'audio' - Adding user 'default' to group: 'input' - Adding user 'default' to group: 'pulse' - Setting umask to 000 - Create the user XDG_RUNTIME_DIR path '/tmp/.X11-unix/run' - Setting ownership of all log files in '/home/default/.cache/log' - Setting root password - Setting user password DONE [ /etc/cont-init.d/11-setup_sysctl_values.sh: executing... ] **** Configure some system kernel parameters **** - The vm.max_map_count is already greater than '524288' DONE [ /etc/cont-init.d/30-configure_dbus.sh: executing... ] **** Configure container dbus **** - Container configured to run its own dbus DONE [ /etc/cont-init.d/30-configure_udev.sh: executing... ] **** Configure udevd **** - Disable udevd - /sys is mounted RO - Enable dumb-udev service - Ensure the default user has permission to r/w on input devices DONE [ /etc/cont-init.d/40-setup_locale.sh: executing... ] **** Configure local **** - Locales already set correctly to en_US.UTF-8 UTF-8 DONE [ /etc/cont-init.d/50-configure_pulseaudio.sh: executing... ] **** Configure pulseaudio **** - Enable pulseaudio service. - Configure pulseaudio to pipe audio to a socket DONE [ /etc/cont-init.d/60-configure_gpu_driver.sh: executing... ] **** Found Intel device 'Intel(R) Xeon(R) CPU E5-2690 v4 @ 2.60GHz' **** - Mesa has already been installed into this container **** No AMD device found **** **** Found NVIDIA device 'Tesla P4' **** - Leaving NVIDIA driver stock without patching DONE [ /etc/cont-init.d/70-configure_desktop.sh: executing... ] **** Configure Desktop **** - Enable Desktop service. DONE [ /etc/cont-init.d/70-configure_xorg.sh: executing... ] **** Generate NVIDIA xorg.conf **** - Configure container as primary the X server - Enabling evdev input class on pointers, keyboards, touchpads, touch screens, etc. - Configuring X11 with GPU ID: 'GPU-d223a8f5-9dfb-c8d0-bf28-5d9830ce433b' - Configuring X11 with PCI bus ID: 'PCI:131:0:0' - Writing X11 config with Modeline "1600x900R" 201.00 1600 1648 1680 1760 900 903 908 953 +hsync -vsync nvidia-xconfig: unrecognized option: "--no-multigpu" Invalid commandline, please run `nvidia-xconfig --help` for usage information. Some important configurations are shown in the figure Edited January 26, 20242 yr by medivh
January 27, 20242 yr On 1/26/2024 at 11:10 AM, medivh said: Hello, I encountered this error while trying to run Steam headless. What should I do? Thank you very much. [ /etc/cont-init.d/10-setup_user.sh: executing... ] **** Configure default user **** - Setting default user uid=99(default) gid=100(default) usermod: no changes - Adding default user to any additional required device groups - Adding user 'default' to group: 'video' - Adding user 'default' to group: 'audio' - Adding user 'default' to group: 'input' - Adding user 'default' to group: 'pulse' - Setting umask to 000 - Create the user XDG_RUNTIME_DIR path '/tmp/.X11-unix/run' - Setting ownership of all log files in '/home/default/.cache/log' - Setting root password - Setting user password DONE [ /etc/cont-init.d/11-setup_sysctl_values.sh: executing... ] **** Configure some system kernel parameters **** - The vm.max_map_count is already greater than '524288' DONE [ /etc/cont-init.d/30-configure_dbus.sh: executing... ] **** Configure container dbus **** - Container configured to run its own dbus DONE [ /etc/cont-init.d/30-configure_udev.sh: executing... ] **** Configure udevd **** - Disable udevd - /sys is mounted RO - Enable dumb-udev service - Ensure the default user has permission to r/w on input devices DONE [ /etc/cont-init.d/40-setup_locale.sh: executing... ] **** Configure local **** - Locales already set correctly to en_US.UTF-8 UTF-8 DONE [ /etc/cont-init.d/50-configure_pulseaudio.sh: executing... ] **** Configure pulseaudio **** - Enable pulseaudio service. - Configure pulseaudio to pipe audio to a socket DONE [ /etc/cont-init.d/60-configure_gpu_driver.sh: executing... ] **** Found Intel device 'Intel(R) Xeon(R) CPU E5-2690 v4 @ 2.60GHz' **** - Mesa has already been installed into this container **** No AMD device found **** **** Found NVIDIA device 'Tesla P4' **** - Leaving NVIDIA driver stock without patching DONE [ /etc/cont-init.d/70-configure_desktop.sh: executing... ] **** Configure Desktop **** - Enable Desktop service. DONE [ /etc/cont-init.d/70-configure_xorg.sh: executing... ] **** Generate NVIDIA xorg.conf **** - Configure container as primary the X server - Enabling evdev input class on pointers, keyboards, touchpads, touch screens, etc. - Configuring X11 with GPU ID: 'GPU-d223a8f5-9dfb-c8d0-bf28-5d9830ce433b' - Configuring X11 with PCI bus ID: 'PCI:131:0:0' - Writing X11 config with Modeline "1600x900R" 201.00 1600 1648 1680 1760 900 903 908 953 +hsync -vsync nvidia-xconfig: unrecognized option: "--no-multigpu" Invalid commandline, please run `nvidia-xconfig --help` for usage information. Some important configurations are shown in the figure I changed the nvidia driver to production and solved the problem
January 28, 20242 yr On 1/27/2024 at 5:17 AM, medivh said: I changed the nvidia driver to production and solved the problem I had the same issue on unraid, steam-headless went into a bootloop trying to match the server's nvidia driver Changed the driver to the production driver as you pointed out, rebooted and steam-headless worked again.
January 31, 20242 yr Hi Guys ! I have two problems which seems to be only one problem... Everthing is install without any prob, but as soon as i loggin to my steam account the window "Loading User Data" is staying for ever.. Second problem, i'll try to launch the Big Picture, i ear the loading, and when clicking i ear windows of steam opening without any image.. I have a AMD Graphic Car ( RX390 ) and Amd CPU (FX8320) Thx
February 1, 20242 yr Those who are having issues with this container crashing repeatedly, and never getting going, should consult this thread, it solved the problem for me: https://github.com/Steam-Headless/docker-steam-headless/issues/111 More specifically, xorg was crashing, and the container was not accessible. It was working fine for a while, and suddenly wouldn't run anymore a few months back. Scroll down to apclapp's comment. A real hero.
February 2, 20242 yr On 1/28/2024 at 2:55 PM, verci said: I had the same issue on unraid, steam-headless went into a bootloop trying to match the server's nvidia driver Changed the driver to the production driver as you pointed out, rebooted and steam-headless worked again. I don't have this luck. Unraid 6.12.4 I swear I had production branch before but it's gone since I moved the card in my case (found out it was in x1 instead of x16). Quadro RTX A4000. Cannot run any games in steam, it just either start and stop or just show nothing.
February 2, 20242 yr 19 minutes ago, Nodiaque said: I don't have this luck. Unraid 6.12.4 I swear I had production branch before but it's gone since I moved the card in my case (found out it was in x1 instead of x16). Quadro RTX A4000. Cannot run any games in steam, it just either start and stop or just show nothing. Weird. This is actually what fixed it for me, was just stepping down to Production Branch. But I'm on 6.12.6... don't know why you're not updated, but I don't think theres any harm in updating your Unraid. It'll probably show up then.
February 2, 20242 yr 1 hour ago, stry8993 said: Weird. This is actually what fixed it for me, was just stepping down to Production Branch. But I'm on 6.12.6... don't know why you're not updated, but I don't think theres any harm in updating your Unraid. It'll probably show up then. I also had to go to production branch for my nvidia drivers to get it to work. Another issue I'm having is I can't get my resolution above 1600x900. Edited February 2, 20242 yr by bobdole199534
February 3, 20242 yr I see there's some pull request to fix some >500 driver issue. Unsure if it will be merged, don't see any new built since september 2023. Owner must be busy.
February 4, 20242 yr Ok I manage to update to latest version of unraid and install production. Now I do have it starting and steam running. But when I start a game, it's says running and I never see the game, it just sit in running. After sometime, steam return as if the game nicely closed. I tried using the vnc and steam remote play and all yield same result. I tried installing protonge and samething. Any clues? Is there something I'm missing? Edited February 4, 20242 yr by Nodiaque
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.