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.

[Support] ich777 - AMD Vendor Reset, CoralTPU, hpsahba,...

Featured Replies

  • Author
1 hour ago, bmrowe said:

If both work independently, but not together, would that point to a driver or motherboard issue? I can't imagine the magic-blue-smoke pcie adapter is the problem.

In my opinion this then is a TPU issue since other people would have the same issue as you are having and no one else reported that a Dual Edge TPU is crashing the server.

  • Replies 2.4k
  • Views 479.8k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • can i be the first to say, wow!, i can see how this will be VERY useful for people wanting to pass through hardware to containers, and now being able to build out an image is impressive work indeed!,

  • Im still confused by him. He does not want to update to 8.6.3 from 8.6.2 due to personal reasons. Yet he keeps saying the only thing it fixed was a venerability. So I guess that he needs this venerabi

Posted Images

On 5/2/2025 at 8:36 PM, ich777 said:

It seems that you are correct and older cards are not supported any more on newer versions from mft-tools

 

I have to think about how to continue since this would possibly mean a complete overhaul from the plugin and how it works.

Thanks so much for confirming that — I really appreciate you taking the time to investigate this!

 

As a possible workaround (suggested by ChatGPT), maybe the plugin could offer an optional legacy mode for older cards like the ConnectX-3, which uses a precompiled mstflint 4.18.0 binary bundled with its own OpenSSL 1.1 libraries. These could be loaded using LD_LIBRARY_PATH to avoid conflicts with Unraid 7’s OpenSSL 3 environment.

 

This approach might allow legacy hardware to remain supported without affecting newer systems or requiring major changes to Unraid itself.

  • Author
11 minutes ago, Tardisyuan said:

As a possible workaround (suggested by ChatGPT), maybe the plugin could offer an optional legacy mode for older cards like the ConnectX-3, which uses a precompiled mstflint 4.18.0 binary bundled with its own OpenSSL 1.1 libraries. These could be loaded using LD_LIBRARY_PATH to avoid conflicts with Unraid 7’s OpenSSL 3 environment.

That would of course work but did ChatGPT also point out the risks in doing that, I assume not correct?

Just imagine what happens if for some reason that would cause corrupt flashed images, this would mean everyone who are using the plugin will break their cards. You can of course do that yourself by installing the library (which also means you don't even have to specify LD_LIBRARY_PATH) - ChatGPT is good and all but it leaves out most of the times the downsides and possible issues that may occur.

 

What you did by downgrading the plugin to an early version is just a workaround and won't even work for some plugins if maintainers for example delete the plugin packages entirely.

 

As said already, I have to think about that because I would rather have a good solution and not using libraries that are even not designed to run on this version and that means I have to build the plugin from the ground up <- please don't expect a release soon.

Intel GPU TOP

i am using dg1 gpu in unraid 7.1 with z490 MB,

but if i disabled xe drive, dg1 could not be used

if i use xe drive, intel gpu top could not show information about dg1

tower-diagnostics-20250508-1957.zip

  • Author
20 minutes ago, allenchou1994 said:

Intel GPU TOP

i am using dg1 gpu in unraid 7.1 with z490 MB,

but if i disabled xe drive, dg1 could not be used

if i use xe drive, intel gpu top could not show information about dg1

Can you please remove both files xe.conf and i915.conf from /boot/config/modprobe.d/ and reboot?

27 minutes ago, ich777 said:

Can you please remove both files xe.conf and i915.conf from /boot/config/modprobe.d/ and reboot?

deleted the 2 files and reboot

uhd630 works fine but dg1 can't work

iShot_2025-05-08_20_47_51.thumb.png.45f554cd3df7f528df8f5e8d4599c6d9.png

iShot_2025-05-08_20.49.57.png

tower-diagnostics-20250508-2050.zip

  • Author
6 minutes ago, allenchou1994 said:

uhd630 works fine but dg1 can't work

I would recommend that you create a post in the General Subforums, I'm not familiar with the DG1.

 

A few weeks ago I had another user with a DG1 which was not working and told him to do the same.

2 minutes ago, ich777 said:

I would recommend that you create a post in the General Subforums, I'm not familiar with the DG1.

 

A few weeks ago I had another user with a DG1 which was not working and told him to do the same.

alright

thanks for your help

On 5/6/2025 at 3:27 PM, ich777 said:

In my opinion this then is a TPU issue since other people would have the same issue as you are having and no one else reported that a Dual Edge TPU is crashing the server.

Ok, so I've now run stably on each of the TPUs (independently) on the dual edge card. Since this issue only seems to arise when using both TPUs, is there any further troubleshooting I can do, or should I assume the dual TPU card has some flaw causing this instability when both TPUs are used?

Any ideas how i can use the ugreen LED plugin INSIDE a virtual machine (which my docker instance is).

I tried to pass through the i2c LED controller, but i dont think its possible.

 

Running the controller on the proxmox host is also not possible because i have passed through the SATA controller and network controller to UNRAID, so the LED controller on the host never gets the infos regarding the LED status.

 

Only possible i see is that somehow the LED controller running in UNRAID send the commands to change the LED colors via e.g. ssh to a second LED controller on the proxmox host.

 

Help :D

7 hours ago, Jesuff_vom_Lazarett said:

Only possible i see is that somehow the LED controller running in UNRAID send the commands to change the LED colors via e.g. ssh to a second LED controller on the proxmox host.

 

Help :D

i rather would say you are in the wrong forum ;)

 

your LED controller is on the host (prox), so i would ask in a prox forum ... while you are running Unraid in a VM (whyever, you will have your reasons ...), so in the end you need a software on the host, then you can consider running a command from your VM to your host to do something ...

  • 2 weeks later...

I'm considering getting one of those AMD Ryzen AI Max+ 395 mini-pcs with 128GB of shared (V)RAM. It's based on Ryzen 8000 APU series / gfx1151 / RDNA 3.5. Any idea of this is already or will be supported? Not sure if I should pull the trigger on the purchase right now for a unraid system...

Edited by iLaurens

The OpenRGB patch plugin does not seem to be supported for UnRAID v7.1.2 - can it be updated to support this version?

  • Author
40 minutes ago, rpetrina14 said:

The OpenRGB patch plugin does not seem to be supported for UnRAID v7.1.2 - can it be updated to support this version?

Shouldn‘t be needed anymore since this was implemented upstrem into the Kernel.

  • Author
1 hour ago, iLaurens said:

Any idea of this is already or will be supported?

Please create a post in the General subforums, this is not related to a plugin this is directly related to the base OS.

Hi,

first of all: thanks @ich777 for doing all the great stuff you do. :)

Second, maybe someone can help me here. I recently rebuilt my server and plopped in an Arc750. Specs attached.

Now I see the following: if I install the intel-gpu-top plugin, the system freezes 2-5 minutes later. No error, nothing more in the log. The GUI is frozen, direct access on the server doesnt work too, no input possible anymore.

I tried changing a few settings in Bios, disabling C States, enabling/disabling resbar, no avail. I cant even get anything to check in the logs as it freezes and stops writing.

Diagnostics attached, I hope someone can check this and provide some tips.

Thanks!

PCI Devices and IOMMU Groups.txt ransomshare-diagnostics-20250528-1143.zip

  • Author
20 minutes ago, zeus3 said:

Second, maybe someone can help me here. I recently rebuilt my server and plopped in an Arc750. Specs attached.

Your ARC Card is bound to VFIO so to speak your Host can't see it.

03:00.0 VGA compatible controller [0300]: Intel Corporation DG2 [Arc A750] [8086:56a1] (rev 08)
    Subsystem: Intel Corporation Device [8086:1021]
	Kernel driver in use: vfio-pci
	Kernel modules: i915, xe
04:00.0 Audio device [0403]: Intel Corporation DG2 Audio Controller [8086:4f90]
	Subsystem: Intel Corporation Device [8086:1021]

Please unbind the card from VFIO, reboot and it should show up.

For the crashing I can't help since this is probably related to your system in general, try to set up a syslog server and create a post in the General Subforums.

Just updated to 7.1.2 and now my openrgb i2c is broken. I am getting the following error message:

<h2>WARNING:</h2><p>One or more I2C/SMBus interfaces failed to initialize.</p><p>RGB DRAM modules and some motherboards' onboard RGB lighting will not be available without I2C/SMBus.</p><p>On Linux, this is usually because the i2c-dev module is not loaded. You must load the i2c-dev module along with the correct i2c driver for your motherboard. This is usually i2c-piix4 for AMD systems and i2c-i801 for Intel systems.</p><p>See <a href='https://help.openrgb.org/'>help.openrgb.org</a> for additional troubleshooting steps if you keep seeing this message.<br></p>

Prior to updating, I installed the ich777 openrgb patch and this solved the issue. I now see the patch is pulled from the community applications and above I see a post claiming this patch is depreciated and should be functional with the new kernel.

As well, USER_ID and GROUP_ID look like they've been corrected in the most recent version of the openrgb docker. This shouldn't be it.

image.png

Anyone have a solution?

  • Author
2 hours ago, unclenino69 said:

As well, USER_ID and GROUP_ID look like they've been corrected in the most recent version of the openrgb docker. This shouldn't be it.

Sorry I don't maintain the OpenRGB container, maybe try to post on their Discord or directly in the OpenRGB Gitlab.

However the other user responded with Thanks so I was assuming it is working.

1 hour ago, ich777 said:

Sorry I don't maintain the OpenRGB container, maybe try to post on their Discord or directly in the OpenRGB Gitlab.

However the other user responded with Thanks so I was assuming it is working.

Sounds good I will keep reaching out until I find a solution and report back here in case somebody has the same issue as me.

One thing I noticed was your patch is still available on github.

GitHub
No image preview

GitHub - ich777/unraid-openrgb-patch

Contribute to ich777/unraid-openrgb-patch development by creating an account on GitHub.

I tried installing this from the UNRAID plugins menu, but the file formats don’t match up. It’s looking for a .plg file, but the release is .txz. I couldn’t find any guides on how to install a plugin, if this is worth doing could you point me in the right direction?

Or would installing this mess up something with the newest kernel version?

Thanks!

Edited by unclenino69

  • Author
1 hour ago, unclenino69 said:

Or would installing this mess up something with the newest kernel version?

Doesn‘t compile against the latest Kernel.

  • Author
4 hours ago, unclenino69 said:

Not sure which worked, tried them all, but I am seeing my missing i2c devices now.

Probably the i2c modules since the first one even does nothing.

17 hours ago, ich777 said:

Probably the i2c modules since the first one even does nothing.

I have the exact guide for anyone facing this issue with missing i2c devices on UNRAID 7.1.2.

  1. Run sensors-detect. Press y to probe i2c and then y to probe i2c-0. All of my sensors were detected here. Then press y or n to the remainder of the i2c-x devices, I didn't have any on these only i2c-0. Then y at the end to write.

image.png

image.png

  1. "cd /boot/config"

  2. "sudo nano go" (edit the boot go file)

  3. Add line "modprobe i2c-dev"

  4. Press ctrl+x, then y to write

  5. Reboot UNRAID to load command, i2c devices should now appear in openrgb after every reboot

    image.png

Good day, anyone know why when I'm rebooting, sometimes intel IGPU goes to /dev/dri/card1 and the nvidia (5070ti) is on /dev/dri/card0 and vice versa when rebooting.
Anyone know how to fix this? thanks28603.png

Edited by sausuke

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.

Guest
Reply to this topic...

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.