huntastikus

Members
  • Posts

    59
  • Joined

  • Last visited

Everything posted by huntastikus

  1. So further digging: I booted into the Unraid GUI. The X server in Unraid is storing the configs in /etc/X11/xorg.conf, and it creates the file /tmp/X0-lock and NOTHING in the .X11-unix folder that is mapped to the container. I think this is why some people in the thread are not able to get this container to run. I tried changing the display variable, I tried changing primary/secondary variable but the container would not run. The steam process keeps restarting over and over: so I think there needs to be some sort of config to handle this? Next I will try to copy the xorg.conf file from /etc/X11 somewhere persistent and then map it to the container is hopes of getting this to work.
  2. So I went into the BIOS settings of the server, I set prefer "VGA offboard". I was watching Unraid boot on the TV, and then the screen just turned off. I don't know much about this x11 settings, but could it be that this is not working for me because I am using Unraid OS (Without GUI) and Unraid is not loading X server? in /tmp/.X11-unix I have a files called "X1=" and a folder called "run" I am not sure what should be in here. When I restart the container the X1= file disappears. I think this is because my server is not running Xorg normally.
  3. Hi Josh, I think it works differently with server boards, the display defaults to the on board graphics card even though there is nothing connected to it. The output of the On board graphics is VGA only, I don't even have a VGA compatible screen anymore lol. I have a TV connected to the Titan though, but so far every time I booted the server the TV was off. I will try to boot unraid with the TV ON. Sure would be nice to be able to use the NVidia X server settings to detect the displays. I see the button but it doesn't seem to do anything If you have a hint on how to properly trigger the detection, just push me in the right direction, I would much appreciate it!
  4. Hi Josh, Thanks for your hard work on this container. I have been reading through these posts and something caught my eye, am I supposed to be able to connect my GPU to my TV and be able to get an Image that mirros what I see in the browser? At the moment this is not working for me, but it would solve my workaround of having to shut this container and emby down to be able to run a VM that can use the GPU. Here is my setup: I have a Supermicro motherboard with built in graphics and I also have an Nvidia Titan X GPU. I run Unraid without the gui, so no displays are connected except a TV to the Nvidia GPU. Emby encoding/decoding is working fine, I am also able to play games at pretty high resolutions in the browser through VNC. Audio works through the browser too. But I am not getting any output on my TV connected via HDMI to the GPU. With the card passed through to a Linux or Windows VM, the card is working as expected. Please see my settings below: Extra Parameters: --runtime=nvidia --dns='10.10.1.2' --hostname='SteamHeadless' --add-host='SteamHeadless:127.0.0.1' --restart=unless-stopped --shm-size=8G --ipc="host" -v '/tmp/.X11-unix':'/tmp/.X11-unix':'rw' -v '/dev/input':'/dev/input':'ro' --log-opt max-size=50m --log-opt max-file=1 Here are the logs of the container: [ /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 video, audio, input and pulse groups Adding default user to any additional required device groups Adding user 'default' to group: 'user-gid-71' for device: /dev/input/event0 Adding user 'default' to group: 'user-gid-18' for device: /dev/dri/card0 Setting umask to 000 Create the user XDG_RUNTIME_DIR path '/tmp/.X11-unix/run' Adding default home directory template Setting ownership of all log files in '/home/default/.cache/log' Setting root password Setting user password DONE [ /etc/cont-init.d/20-configre_sshd.sh: executing... ] **** Configure SSH server **** Disable SSH server 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 container to run udev management **** **** Ensure the default user has permission to r/w on input devices **** DONE [ /etc/cont-init.d/40-setup_locale.sh: executing... ] **** Locales already set correctly to en_US.UTF-8 UTF-8 **** DONE [ /etc/cont-init.d/50-configure_pulseaudio.sh: executing... ] **** Configure pulseaudio **** Configure pulseaudio to pipe audio to a socket DONE [ /etc/cont-init.d/60-configure_gpu_driver.sh: executing... ] **** Found NVIDIA device 'NVIDIA TITAN X (Pascal)' **** **** Found Intel device 'Intel(R) Xeon(R) CPU E5-2690 v2 @ 3.00GHz' **** Install Intel vulkan driver **** No AMD device found **** DONE [ /etc/cont-init.d/70-configure_xorg.sh: executing... ] **** Generate NVIDIA xorg.conf **** Configure container as primary the X server Leaving evdev inputs disabled Configuring X11 with GPU ID: 'GPU-ee2de819-579b-23a9-4a68-23d9ea167887' Configuring X11 with PCI bus ID: 'PCI:4:0:0' Writing X11 config with Modeline "1920x1200R" 154.00 1920 1968 2000 2080 1200 1203 1209 1235 +hsync -vsync WARNING: Unable to locate/open X configuration file. Package xorg-server was not found in the pkg-config search path. Perhaps you should add the directory containing `xorg-server.pc' to the PKG_CONFIG_PATH environment variable No package 'xorg-server' found Option "ProbeAllGpus" "False" added to Screen "Screen0". Option "AllowEmptyInitialConfiguration" "True" added to Screen "Screen0". New X configuration file written to '/etc/X11/xorg.conf' DONE [ /etc/cont-init.d/80-configure-dind.sh: executing... ] **** Configure Dockerd **** Enable Dockerd daemon DONE [ /etc/cont-init.d/90-configure_neko.sh: executing... ] **** Configure Neko **** Disable Neko server DONE [ /etc/cont-init.d/90-configure_sunshine.sh: executing... ] **** Configure Sunshine **** Disable Sunshine server DONE [ /etc/cont-init.d/90-configure_vnc.sh: executing... ] **** Configure VNC **** Configure VNC service port '32036' Configure noVNC service port '32037' Configure audio websocket port '32038' Configure pulseaudio encoded stream port '32039' Enable VNC server DONE [ /etc/cont-init.d/95-configure_secondary.sh: executing... ] DONE [ USER:/home/default/init.d/install_heroic.sh: executing... ] Hit:1 http://deb.debian.org/debian bullseye InRelease Hit:2 http://deb.debian.org/debian-security bullseye-security InRelease Get:3 http://download.opensuse.org/repositories/home:/strycore/Debian_10 ./ InRelease [1,497 B] Get:4 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB] Hit:5 https://nvidia.github.io/libnvidia-container/stable/debian10/amd64 InRelease Hit:6 https://nvidia.github.io/nvidia-container-runtime/stable/debian10/amd64 InRelease Hit:7 https://nvidia.github.io/nvidia-docker/debian10/amd64 InRelease Fetched 45.6 kB in 2s (19.8 kB/s) Reading package lists... Reading package lists... Building dependency tree... Reading state information... heroic is already the newest version (2.5.0-beta.1). 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. Reading package lists... Building dependency tree... Reading state information... zenity is already the newest version (3.32.0-6). 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. Archive: /home/default/Downloads/HeroicBashLauncher-v3.0.1.zip creating: HeroicBashLauncher-3.0.1/ creating: HeroicBashLauncher-3.0.1/HeroicBashLauncher/ inflating: HeroicBashLauncher-3.0.1/HeroicBashLauncher/how-to-guide.txt inflating: HeroicBashLauncher-3.0.1/HeroicBashLauncher/settings.config inflating: HeroicBashLauncher-3.0.1/HeroicBashLauncher/HeroicBashLauncher creating: HeroicBashLauncher-3.0.1/HeroicBashLauncher/GameFiles/ inflating: HeroicBashLauncher-3.0.1/HeroicBashLauncher/GameFiles/readme.txt creating: HeroicBashLauncher-3.0.1/HeroicBashLauncher/GameFiles/logs/ '/tmp/hbl/HeroicBashLauncher-3.0.1/HeroicBashLauncher/GameFiles/readme.txt' -> '/home/default/HeroicBashLauncher/GameFiles/readme.txt' '/tmp/hbl/HeroicBashLauncher-3.0.1/HeroicBashLauncher/HeroicBashLauncher' -> '/home/default/HeroicBashLauncher/HeroicBashLauncher' '/tmp/hbl/HeroicBashLauncher-3.0.1/HeroicBashLauncher/how-to-guide.txt' -> '/home/default/HeroicBashLauncher/how-to-guide.txt' '/tmp/hbl/HeroicBashLauncher-3.0.1/HeroicBashLauncher/settings.config' -> '/home/default/HeroicBashLauncher/settings.config' [ USER:/home/default/init.d/install_lutris.sh: executing... ] [ USER:/home/default/init.d/install_protonup.sh: executing... ] **** Starting supervisord **** Logging all root services to '/var/log/supervisor/' Logging all user services to '/home/default/.cache/log/' 2022-10-31 16:32:21,214 INFO Included extra file "/etc/supervisor.d/dbus.ini" during parsing 2022-10-31 16:32:21,214 INFO Included extra file "/etc/supervisor.d/desktop.ini" during parsing 2022-10-31 16:32:21,215 INFO Included extra file "/etc/supervisor.d/dind.ini" during parsing 2022-10-31 16:32:21,215 INFO Included extra file "/etc/supervisor.d/neko.ini" during parsing 2022-10-31 16:32:21,215 INFO Included extra file "/etc/supervisor.d/pulseaudio.ini" during parsing 2022-10-31 16:32:21,215 INFO Included extra file "/etc/supervisor.d/sshd.ini" during parsing 2022-10-31 16:32:21,215 INFO Included extra file "/etc/supervisor.d/steam.ini" during parsing 2022-10-31 16:32:21,215 INFO Included extra file "/etc/supervisor.d/sunshine.ini" during parsing 2022-10-31 16:32:21,216 INFO Included extra file "/etc/supervisor.d/udev.ini" during parsing 2022-10-31 16:32:21,216 INFO Included extra file "/etc/supervisor.d/vnc-audio.ini" during parsing 2022-10-31 16:32:21,216 INFO Included extra file "/etc/supervisor.d/vnc.ini" during parsing 2022-10-31 16:32:21,216 INFO Included extra file "/etc/supervisor.d/xorg.ini" during parsing 2022-10-31 16:32:21,216 INFO Included extra file "/etc/supervisor.d/xvfb.ini" during parsing 2022-10-31 16:32:21,216 INFO Set uid to user 0 succeeded 2022-10-31 16:32:21,233 INFO RPC interface 'supervisor' initialized 2022-10-31 16:32:21,233 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2022-10-31 16:32:21,234 INFO supervisord started with pid 1 2022-10-31 16:32:22,238 INFO spawned: 'dbus' with pid 915 2022-10-31 16:32:22,244 INFO spawned: 'udev' with pid 916 2022-10-31 16:32:22,253 INFO spawned: 'dind' with pid 917 2022-10-31 16:32:22,263 INFO spawned: 'xorg' with pid 918 2022-10-31 16:32:22,275 INFO spawned: 'audiostream' with pid 921 2022-10-31 16:32:22,287 INFO spawned: 'novnc' with pid 924 2022-10-31 16:32:22,297 INFO spawned: 'pulseaudio' with pid 925 2022-10-31 16:32:22,311 INFO spawned: 'vncproxy' with pid 926 2022-10-31 16:32:22,329 INFO spawned: 'x11vnc' with pid 928 2022-10-31 16:32:22,337 INFO spawned: 'audiowebsock' with pid 932 2022-10-31 16:32:22,353 INFO spawned: 'desktop' with pid 933 PULSEAUDIO: Starting pulseaudio service 2022-10-31 16:32:22,357 INFO success: vncproxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2022-10-31 16:32:22,687 INFO reaped unknown pid 968 (exit status 0) 2022-10-31 16:32:23,243 INFO success: dbus entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-10-31 16:32:23,245 INFO success: udev entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-10-31 16:32:23,246 INFO success: dind entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-10-31 16:32:23,328 INFO success: xorg entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-10-31 16:32:23,329 INFO success: audiostream entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-10-31 16:32:23,330 INFO success: novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-10-31 16:32:23,330 INFO success: pulseaudio entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-10-31 16:32:23,331 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-10-31 16:32:23,331 INFO success: audiowebsock entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-10-31 16:32:23,369 INFO success: desktop entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-10-31 16:32:27,720 INFO reaped unknown pid 1183 (exit status 1) 2022-10-31 16:37:30,855 INFO reaped unknown pid 1209 (exit status 0) 2022-10-31 16:40:55,727 INFO reaped unknown pid 1622 (exit status 0) 2022-10-31 16:40:55,728 INFO reaped unknown pid 1757 (exit status 1) 2022-10-31 16:40:55,728 INFO reaped unknown pid 1690 (exit status 0) 2022-10-31 16:40:55,728 INFO reaped unknown pid 1691 (exit status 0) Am I missing some configuration? or is it not possible to use the GPU to output to the TV?
  5. I will watch out for it during the next RC upgrade.
  6. THat explains Wireguard, howabout NVIDIA?
  7. But does anybody have any suggestions why my containers are losing their permissions to their own filesystems?!?!?!
  8. I didn't catch the thing about wireguard, However I don't see any mention of the nvidia driver being deprecated... My server was done rebooting about 1 minute before I posted the issue. I think the RC release post said 1h so I am guessing about an hour after release.
  9. I just upgraded, and once again some of my containers were not starting (I reported a bug related to this container permission issue) and now also the NVIDIA driver plugin and the Dynamix wireguard plugin are showing errors:
  10. After the reboot that upgraded to RC8, not only were containers not working, but also the NVIDIA and the Wireguard plugins were showing errors: Things seems to be getting worse with every release.
  11. The upgrade to RC7 was much smoother then 5, all the containers started as they should. So far so good.
  12. I would just like to add that if I delete the container and the image and recreate it, the container works perfectly.
  13. Hi, I don't restart my server very often, but this has caught my attention during the latest upgrade to 6.10.0-rc5. It seems that when I reboot my server, some containers lose their functionality and the logs are showing that the container was not able to access files. These files are not the files/folders mapped in the appdata share, but they are internal to the container itself. An example of this is my Authelia container (from Ibracorp's repository) which has errors showing that it cannot write to /var/log/*some file*. This folder/file is not mapped to anything outside of the container. The same behavior happens with the following containers as well: binhex-krusader, emby, MongoDB, Nextcloud. I am able to replicate this behavior by simply rebooting Unraid. This was never an issue with the previous builds, but as I understand there have been some changes to permissions with this new release of Unraid. Is this behavior a bug or am I doing something wrong? Is there anyone else having these issues? athena-diagnostics-20220429-2116.zip
  14. Has your server crashed with RC1? if so, try to delete the container and image and reinstall it.
  15. On closer observation, I get different errors then the original poster. I will create a new thread
  16. I am running Emby. I looked into the ACPI settings, but they are quite minimal. Also in the logs, I don't see absolutely anything. for example, nothing in the logs for hours and then all of a sudden the system is booting. I am using a Supermicro Motherboard with 2 Xeon E5 processors.
  17. I am experiencing the same behavior, I will collect syslogs as well on the next crash.
  18. This is a very good point, I myself am an example of this scenario! But I have my fingers and toes crossed this will be possible soon!!
  19. Great Job Sir!!!! Thank you for your continued efforts!!!!
  20. I use the same resolution. Unfortunately, the unraid UI doesn't seem to handle the stretching really well. When I maximize the window, this looks like garbage But frankly so does every other banner I have seen... Maybe there's a plugin to better handle the banner on ultrawide displays but I haven't found it yet. If someone know how to do this, PLEASE PLEASE PLEASE let me know. So far I tried CA Dynamix Unlimited Width which does OK for the bottom part of the interface, but just stretches the banner. With this image, I would say you can stretch the window to about 2/3 of your monitor and it still looks decent (personal opinion). If you want to try to make your own, I just cropped this image (My wallpaper): http://wallpaperswide.com/sound_2-wallpapers.html If you get it working nicely, please share your ways!!!
  21. nVidia DRIVERS PLEASE!!!!!! Or a mechanism of installing drivers!!!