Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

ich777

Community Developer
  • Joined

  1. Just a heads up for Unraid 7.2.8 and SR-IOV users. SRIOV currently doesn't compile against Kernel 6.12.98 which Unraid 7.2.8 is based on, so to speak, don't upgrade if you need SRIOV support. An issue was already opened in their GitHub but I think they are a bit exhausted supporting that many Kernel versions and it will take time to be updated so that it works again.
  2. No, that's actually not true, only the upload from the Kernel archive failed, the drivers where compiled just fine. GitHub is lately under heavy load (I assume because of heavy load because of AI pushing so much new code) and it doesn't always work as intended. You should try to remove the plugin from your server and then try to install it again, if that works then simply run this from an Unraid terminal, but usually you have to wait a few hours until everything works on GitHub as usual: wget -qO- https://raw.githubusercontent.com/ich777/unraid-plugin_update_helper/master/force_package_update | bash
  3. This is actually the worst idea, don't add privileged, you basically now allow the container to have access to your whole server and not much isolation going on.
  4. You can already enable Tailscale in the Unraid template.
  5. I didn't and I don't have a Blackwell card. No. The Open Source one. You've mentioned all things that you have to check, also make sure that you are on the latest BIOS version. GSP is closed firmware and just added to the driver package, the same as it is with the libraries, they are all closed source. Only the driver module is open source.
  6. ich777 changed their profile photo
  7. I don't see anything suspicious in your Diagnostics. How did you test if transcoding is working, did you force a transcode, if yes on which client (iOS, Android, Browser), did you made sure that this is a media file without burnt in subtitles (since these are nutritious to cause the CPU go wild in combination with Plex), also do note that audio transcoding is done on the CPU not GPU (just if audio needs to be transcoded). Please do also note that Plex transcodes in chunks so to speak, it will transcode, then pause the transcode, transcode, pause to transcode and so on. Do you also have the capabilities variable in your Docker template as pointed out in the second thread.
  8. I'm not familiar what Viseron is. However if everything is now working, glad that it's solved. :)
  9. Sorry but I'm not into modding, I assume the container would support that but I'm not too sure about that. You can copy whatever you like and add startup parameters to the template, maybe that will help you. I can only give support for the container if something isn't working and the container in general is working. :D
  10. These are Kernel Panics, not sure if the Module causes that or Frigate: ``` Jun 13 19:13:20 tower-one kernel: WARNING: CPU: 2 PID: 12957 at ./include/linux/rwsem.h:80 find_vma+0x28/0x60 ``` I would recommend that you ask in the Frigate support thread.
  11. Only Diagnostics would give me a full picture. However, is something not working?
  12. IIRC SotF needs a public IP so to speak a direct accessible connection from outside to work properly, I think there is no LAN only switch for that game.
  13. Okay, about what container are we talking about?
  14. Wrong support thread since the driver is meant to be not used if you are using the card in a VM: Please create a post in the General Subforums.
  15. This is really strange, however please do note that I deprecated TheLounge over a year ago, if possible, please switch over to the container from Linuxserver.io if possible. However if the container was running up until now I assume that something in appdata got corrupted or isn't there where it should be. Maybe look if everything is okay with your appdata directory since the deprecation won't affect the function from the container.
  16. No, this is just when you get the message in your logs. Nothing that I can do about that since this is related to steamcmd and not the container.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.