Jump to content

ich777

Community Developer
  • Posts

    15,752
  • Joined

  • Days Won

    202

Everything posted by ich777

  1. Have you read the red text on the LXC Settings page: I think that for printers/scanners a device in /dev is also created but I'm not too sure which one because I even don't own a printer/scanner and haven't done much with printers/scanners...
  2. What path did you try before? Doesn't your printer get entry in /dev itself? I don't think it is recognized as a ttyd in /dev? What about the devices in /dev/usb when the printer is connected? You should be also able to create a custom udev rule for your specific device ID. I haven't looked much into it but something like "Hotplugging USB Devices LXC" should point you in the right direction on google.
  3. Unfortunately no... I think someone forked my driver and made it available through some kind of proxy if I'm not mistaken? But I'm not entirely sure about that, please search on the Chinese subforums about that. What would be the preferred way to download the drivers from China? This would be the download URL for the latest Nvidia driver for Unraid 6.10.3 which the plugin tries to download: https://github.com/ich777/unraid-nvidia-driver/releases/download/5.15.46-Unraid/nvidia-515.48.07-5.15.46-Unraid-1.txz There are maybe some ways around this, by installing the driver and when it actually downloads the driver close the window with the red X and download the driver manually and place it in the correct folder (I don't explained this here because this is really not the recommended way to do it).
  4. But the error is resolved in the next line. I will trynit on my server if I can connect or not later that day and report back.
  5. You‘ve answered your question yourself…. The driver enables all functionality from the card itself, if CUDA isn‘t available in the container it won‘t work. Please keep in mind that Plex (and all other media servers) have most of the times issues with HDR content and Tone Mapping.
  6. You don‘t need the plugin for the USB TPU. The plugin is only needed if you own a PCI(e) based TPU.
  7. You can create a script with User Scripts plugin from the CA App. Simply Add a new script with a good name like "Restart Gameservers" then hover over the Gear icon and click on "Edit Script" and add the following contents: docker restart DOCKERNAME (of course replace "DOCKERNAME" with the corresponding Docker name, please note that it has to be the exact name - case sensitive) After that press "Save Changes", at Schedule Disabled enable "Schedule Daily" and press "Apply" at the bottom. This will restart your container once a day, you can also set your custom cron schedule if you want too... Hope that helps.
  8. Please never do that... This can cause other various issues, for example when you update the plugin the share could go missing inside the container...
  9. The default.ini. I have to look into this because I haven't played the game in a long time, but @Marcel40625 reported that it is working again.
  10. I only can imagine that it got completely overloaded and actually run into the temperature limit, but I can't tell for sure if this was the case here.
  11. So Unassigned Devices caused this? What temperature are you currently on?
  12. All the ports which are in the template need to be forwarded and of course with the corresponding protocol from the template. Leave it in default „bridge“ mode and it should work just fine.
  13. Why not? These are the redings from the TPU itself and nothing more but if it says -89.7C then ther must be something wrong… What does the Pligin page say? I really can‘t imagine thats related, but it may be if the application itself crashes.
  14. These are only shader and graphic errors, nothing to worry about on a dedicated server. Have you forwarded the ports properly in your router? Have you just yet tried to do a direct connection with your internal server IP?
  15. Sieh dir mal mein Setup an das ich oben verlinkt hab, das reicht alle mal und du hast haufenweise PCIe erweiterungsmöglichkeiten...
  16. Yes, it is most likely that the shutdown temperature of 104.80 °C was triggered and that the module shut itself off. What module do you own? Are you sure that you have enough airflow over the module? I've also posted a tutorial how you can write the temperature readings to a file to see what it actually does:
  17. Nur bei der iGPU und 12th gen. Verkauf sie doch wieder... ^^ Naja, ich hab auf meinem System keine Cores assigned oder irgendwas zugewiesen und der default Linux Scheduler macht das schon ganz gut. Ich würde dir eher dazu raten noch ein bis zwei generationen ab zu warten, sie es so wie mit AMD und Ryzen, die ersten zwei Generationen hatten auch so ihre "schwierigkeiten" und sind immer besser geworden. Big Little ist am Desktop gerade erst mal angekommen und die Software muss auch daran angepasst werden, in den meisten fällen... Puh, also da bist du dann schon hart an der Grenze und die Platten müssen auf jeden Fall im Idle sein meiner Meinung nach... Ich würd dir auf jeden Fall von Bleeding Edge Hardware auf Linux abraten...
  18. It says that this chip is on your Motherboard: Please also note the chips is most of the times in the lower part from the motherboard located.
  19. You should search for the exact Nuvoton chip, you should be able to see it on your Motherboard, if it is a Nuvoton chip. But from what I see you have a ITE chip on your Motherboard and this is another manufacturer. Also this is completely OT and not the right thread for this, please post in the SystemTemp plugin support thread.
  20. Aufpassen bei den Karten, bei den günstigen Angeboten ist meisten nur eine Low Profile Blende dabei und keine miniDisplayPort -> DisplayPort Kabeln. Aber bei dem siehts so aus als ob eine normale SlotBlende dabei ist aber ohne Kabel.
  21. Make also sure that you've stop the container before invoking the Mover.
  22. The main issue with that was that the developers from Valheim first messed up pretty bad since the worlds got deleted in the worlds folder and a new world within the worlds_local was created. After they found out about that they released an updated that actually don't delete the old worlds but instead created a new folder within the worlds_local folder. So if someone, like me, who haven't had the container running and update the containers everything will work since they Docker will move the world and the game will pick up the new location without creating a new worlds_local folder, hope that explains that a little bit more. In your case you are a user where the worlds folder doesn't get deleted because you've pulled the newer update from Valheim and instead a new world is created. I have to say I won't change that again since this is only a one time thing and users could move the files manually...
  23. Just for testing reasons, can you download this file on your local machine? https://archive.mozilla.org/pub/thunderbird/releases/91.10.0/linux-x86_64/en-US/thunderbird-91.10.0.tar.bz2 If you are using a Unassigned device path for a data path make sure that you've set the path to "Read/Write -Slave":
  24. Um was gehts hier genau? Crasht dein server?
  25. Please post a screenshot from your Docker template.
×
×
  • Create New...