June 8, 20251 yr I'm trying to install intel.gpu.top but face this error:plugin: installing: intel-gpu-top.plg Executing hook script: pre_plugin_checks plugin: downloading: intel-gpu-top.plg ... done plugin: downloading: intel.gpu.top-2025.03.15.txz ... done +============================================================================== | Skipping package intel.gpu.top-2025.03.15 (already installed) +============================================================================== ---------Enabling Intel Kernel Module---------- ------Something went wrong! Can't enable------- ----Intel Kernel Module, removing package!----- No such package: intel-gpu-top-2025.03.15. Can't remove. plugin: run failed: '/bin/bash' returned 1 Executing hook script: post_plugin_checksHow can I further investigate the failure cause? I do not see the package in /boot/config/plugins.It's very possible that it's an issue with my BIOS. I have tried several things in configuring the IGP. I boot with a monitor connected.I basically just want to setup QSV. So far I'm able to confirm the PCI device existsroot@Tower:~# lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-S GT1 [UHD Graphics 770] (rev 04)However, I don't have a /dev/dri and i915 module fails to loadroot@Tower:~# modprobe i915 modprobe: ERROR: could not insert 'i915': No such deviceI hope some of this makes sense and someone could send me on the good path to hw accel tower-diagnostics-20250608-1047.zip
June 8, 20251 yr Author 3 hours ago, yan said:I hope some of this makes sense and someone could send me on the good path to hw accelPlease create a post in the General subforums.
June 8, 20251 yr Author 15 hours ago, sausuke said:Anyone know how to fix this?This is a common issue, please create a bug report if possible, there is no fix for this AFAIK.
June 21, 20251 yr On 5/8/2025 at 8:01 PM, allenchou1994 said:Intel GPU TOPi am using dg1 gpu in unraid 7.1 with z490 MB,but if i disabled xe drive, dg1 could not be usedif i use xe drive, intel gpu top could not show information about dg1tower-diagnostics-20250508-1957.zipI think the intel_gpu_top is i915-only and may not support xe driver (at least the dg1 ones).For alternative, you can use nvtop tool (yes it support intel gpus): differ from the unraid's package description, it actually not depends on Intel-GPU-TOP, it implemented xe support by it's own and works nearly well for dg1
June 21, 20251 yr duat-diagnostics-20250621-1627.zipNot finding anything regarding a seg fault. Anyone have any ideas? Any help would be appreciated! Edited June 21, 20251 yr by Ryndi
June 23, 20251 yr @ich777 do you still maintain and share your docker to build custom kernels and driver modules? If you do, where can I find it and is there any kind of documentation on how to use it?My GPU (RX9070) is currently forcing me to run a custom kernel until Unraid comes with at least 6.13.5 (at least that is my current understanding).The kernel from @thor2002ro is working great and I have no issues with it. However it's missing the Nuvoton NTC6687 driver. Therefore for the time being I'm at the mercy of my BIOS when it comes to fan control and with that my HDDs get too hot for my taste especially during parity or file integrity checks since the BIOS does not ramp up the fans..Therefore I'd like to build the Nuvoton driver for thor's kernel.Any hints and advice for someone that has never attempted this?Thank you both very much for the great work you have done and are doing. This is amazing!
June 23, 20251 yr Author 42 minutes ago, Tom082 said:@ich777 do you still maintain and share your docker to build custom kernels and driver modules? If you do, where can I find it and is there any kind of documentation on how to use it?Please take a look here:https://github.com/ich777/unraid_kernelHowever I don't think you can build modules for custom Kernels but this would definitely give you some clues and possibly the maintainer from your Kernel could implement your driver that you need.
June 23, 20251 yr Thank you very much!12 minutes ago, ich777 said:However I don't think you can build modules for custom Kernels but this would definitely give you some clues.Probably I'm too naive in thinking that I can replace the sources in your container with the ones from thor's repository?
July 8, 20251 yr Regarding the ITE IT87 plugin.Hey. I'm running Unraid on a Gigabyte Z790 UD motherboard with an Intel i7-14700 CPU.Earlier this month, I installed the ITE IT87 plugin because I was not able to see any fans on my new system. I had been using Dynamix Auto Fan Control previously on my old setup, but it did not detect any fans on this new HW - your plugin made them visible.My plan was originally to control my fans in Unraid, but I later changed my mind and decided to just let the BIOS handle all fan control. Since then (beginning of this month) I have really only used the plugin to monitor fan RPMs in the dashboard (collecting the data in Home Assistant).Everything was actually running nice for some days but after a power outage yesterday, my system started acting strange. My front fans now ramp up to full speed even though the system is idle and CPU/motherboard temps are totally normal. What is strange is that this does not happen immediately after boot. The system can run normally for several hours before the fans suddenly spike. When I check the sensor output at that point, I seeacpitz-acpi-0 Adapter: ACPI interface temp1: +16.8°C temp2: +27.8°C nvme-pci-0100 Adapter: PCI adapter Composite: +31.9°C (low = -273.1°C, high = +81.8°C) (crit = +84.8°C) Sensor 1: +31.9°C (low = -273.1°C, high = +65261.8°C) Sensor 2: +31.9°C (low = -273.1°C, high = +65261.8°C) gigabyte_wmi-virtual-0 Adapter: Virtual device temp1: +86.0°C temp2: +35.0°C temp3: +35.0°C temp4: +31.0°C temp5: +32.0°C temp6: +30.0°C it8689-isa-0a40 Adapter: ISA adapter in0: 708.00 mV (min = +0.00 V, max = +3.06 V) in1: 2.03 V (min = +0.00 V, max = +3.06 V) in2: 2.02 V (min = +0.00 V, max = +3.06 V) in3: 1.99 V (min = +0.00 V, max = +3.06 V) in4: 1.52 V (min = +0.00 V, max = +3.06 V) in5: 768.00 mV (min = +0.00 V, max = +3.06 V) in6: 1.99 V (min = +0.00 V, max = +3.06 V) 3VSB: 3.36 V (min = +0.00 V, max = +6.12 V) Vbat: 3.10 V fan1: 936 RPM (min = 0 RPM) fan2: 2089 RPM (min = 0 RPM) fan3: 1991 RPM (min = 0 RPM) fan4: 1182 RPM (min = 0 RPM) temp1: +86.0°C (low = +127.0°C, high = +127.0°C) sensor = disabled temp2: +35.0°C (low = +127.0°C, high = +127.0°C) sensor = disabled temp3: +35.0°C (low = +127.0°C, high = +127.0°C) sensor = Intel PECI temp4: +31.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor temp5: +32.0°C (low = +0.0°C, high = -119.0°C) sensor = thermistor MB Temp: +30.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor intrusion0: OK coretemp-isa-0000 Adapter: ISA adapter CPU Temp: +36.0°C (high = +80.0°C, crit = +100.0°C) Core 0: +35.0°C (high = +80.0°C, crit = +100.0°C) Core 4: +33.0°C (high = +80.0°C, crit = +100.0°C) Core 8: +34.0°C (high = +80.0°C, crit = +100.0°C) Core 12: +30.0°C (high = +80.0°C, crit = +100.0°C) Core 16: +35.0°C (high = +80.0°C, crit = +100.0°C) Core 20: +34.0°C (high = +80.0°C, crit = +100.0°C) Core 24: +34.0°C (high = +80.0°C, crit = +100.0°C) Core 28: +33.0°C (high = +80.0°C, crit = +100.0°C) Core 32: +35.0°C (high = +80.0°C, crit = +100.0°C) Core 33: +35.0°C (high = +80.0°C, crit = +100.0°C) Core 34: +35.0°C (high = +80.0°C, crit = +100.0°C) Core 35: +35.0°C (high = +80.0°C, crit = +100.0°C) Core 36: +31.0°C (high = +80.0°C, crit = +100.0°C) Core 37: +31.0°C (high = +80.0°C, crit = +100.0°C) Core 38: +31.0°C (high = +80.0°C, crit = +100.0°C) Core 39: +31.0°C (high = +80.0°C, crit = +100.0°C) Core 40: +33.0°C (high = +80.0°C, crit = +100.0°C) Core 41: +33.0°C (high = +80.0°C, crit = +100.0°C) Core 42: +33.0°C (high = +80.0°C, crit = +100.0°C) Core 43: +33.0°C (high = +80.0°C, crit = +100.0°C) nvme-pci-0200 Adapter: PCI adapter Composite: +33.9°C (low = -273.1°C, high = +84.8°C) (crit = +84.8°C) Sensor 1: +33.9°C (low = -273.1°C, high = +65261.8°C) Sensor 2: +30.9°C (low = -273.1°C, high = +65261.8°C)The high 86 degree readings seem to be what is triggering the BIOS fan response (I guess?) - even though actual temps are in the 30–35°C range. If I reboot, there is nothing in BIOS (normal temps), and after reboot the system is then back to normal. But after a while it spikes again. So far I have seen it twice.So of course I asked ChatGPT for thoughts 🙂 (Yes, I know I can not rely on it on it's own, which is why I am asking here 😉 - but it's here for context), and it's theory is that after a full power loss, the hardware may boot into a slightly different state. When the plugin (or the driver) initializes the sensors, it may be exposing or activating something that the BIOS then responds to - even if Unraid is not actively controlling the fans.Have you seen this behaviour before, and do you know the fix for it? I would like to just have the fans visible in my dashboard really.I have added my diag file.Thanks in advance! galaxy-diagnostics-20250708-1043.zip
July 8, 20251 yr Author 10 hours ago, TreksterDK said:Have you seen this behaviour before, and do you know the fix for it? I would like to just have the fans visible in my dashboard really.Not really, however someone reported a similar issue about a year ago I think.Issue with that is I don't have such a board, however you can report that here in the issue tracker from the creator from the module:https://github.com/frankcrawford/it87
July 30, 2025Jul 30 Tried installing a Coral M.2 with the Dual Edge TPU PCIe x1 Adapter, and have been finding that it crashes my entire system in under a minute or so after installing the Coral plugin.Looking at the plugin page shows that it's overheating pretty fiercely, despite nothing being configured to utilise it. Immediately after the machine is shutdown, the Coral TPU feels barely warm. Does this look like it could be a faulty Coral unit?Plugin page after installing plugin:Plugin page after around 30 seconds and immediately before system crashes:Jul 30 00:51:58 Tower plugin-manager: running: 'anonymous' Jul 30 00:51:58 Tower plugin-manager: creating: /boot/config/plugins/coral-driver/coral-driver-2025.03.25.txz - downloading from URL https://github.com/unraid/unraid-coral-driver/raw/master/packages/coral-driver-2025.03.25.txz Jul 30 00:51:58 Tower plugin-manager: checking: /boot/config/plugins/coral-driver/coral-driver-2025.03.25.txz - MD5 Jul 30 00:51:58 Tower plugin-manager: running: upgradepkg --install-new /boot/config/plugins/coral-driver/coral-driver-2025.03.25.txz Jul 30 00:51:59 Tower plugin-manager: creating: /usr/local/emhttp/plugins/coral-driver/README.md - from INLINE content Jul 30 00:51:59 Tower plugin-manager: running: 'anonymous' Jul 30 00:52:02 Tower kernel: apex 0000:08:00.0: enabling device (0000 -> 0002) Jul 30 00:52:03 Tower kernel: apex 0000:09:00.0: enabling device (0000 -> 0002) Jul 30 00:52:04 Tower plugin-manager: coral-driver.plg installed Jul 30 00:52:09 Tower kernel: apex 0000:09:00.0: Apex performance not throttled due to temperature Jul 30 00:52:09 Tower kernel: apex 0000:08:00.0: Apex performance not throttled due to temperature Jul 30 00:52:14 Tower kernel: apex 0000:08:00.0: Apex performance not throttled due to temperature Jul 30 00:52:19 Tower kernel: apex 0000:08:00.0: Apex performance not throttled due to temperature Jul 30 00:52:24 Tower kernel: apex 0000:08:00.0: Apex performance not throttled due to temperature Jul 30 00:52:29 Tower kernel: apex 0000:08:00.0: Apex performance not throttled due to temperature Jul 30 00:52:34 Tower kernel: apex 0000:08:00.0: Apex performance not throttled due to temperature Jul 30 00:52:40 Tower kernel: apex 0000:08:00.0: Apex performance not throttled due to temperature Jul 30 00:52:45 Tower kernel: apex 0000:08:00.0: Apex performance not throttled due to temperature Jul 30 00:52:45 Tower kernel: apex 0000:09:00.0: Apex performance not throttled due to temperature
July 30, 2025Jul 30 Author 1 hour ago, nmur said:Looking at the plugin page shows that it's overheating pretty fiercely, despite nothing being configured to utilise it.Do you have a heatsink on your Dual Edge TPU? It is recommended to use a heatsink otherwiese it is most likely that it will overheat.Please also do keep in mind that the failure rate from the PCI modules is pretty high from my experience, maybe you got a faulty module, just saying.On my Dual Edge TPU everything just works fine and with a heatsink attached it is about 36C while in idle and can reach up to 72C in my case depending on the workload.
July 30, 2025Jul 30 1 hour ago, ich777 said:Do you have a heatsink on your Dual Edge TPU? It is recommended to use a heatsink otherwiese it is most likely that it will overheat.Please also do keep in mind that the failure rate from the PCI modules is pretty high from my experience, maybe you got a faulty module, just saying.On my Dual Edge TPU everything just works fine and with a heatsink attached it is about 36C while in idle and can reach up to 72C in my case depending on the workload.Thanks for the quick reply. I do not have a heatsink (yet). I didn't think that even while idle it would overheat, but seems like I should take a look into it.I have seen that a few of the PCI modules have had replacement issues, so I may reach out to the maker to see what they think
July 30, 2025Jul 30 Author 8 minutes ago, nmur said:I do not have a heatsink (yet). I didn't think that even while idle it would overheat, but seems like I should take a look into it.Back in the days the documentation for the Dual Edge TPU even mentioned that this card is a Fire Hazard without a heatsink and the the main heat source is the power delivery.10 minutes ago, nmur said:I have seen that a few of the PCI modules have had replacement issues, so I may reach out to the maker to see what they thinkPobably also try to get a heatsink too if your distributor has some.
August 4, 2025Aug 4 I'm trying to figure out if my GPU or CPU is being used to do video encoding. When I start process, I see this in intel_gpu_top.My ARC A380 card is card1. The Video is 0.00%, but below that, the process is showing video to be about 75%. Confused...The command is run in the console of tdarr container.ffmpeg -hwaccel qsv -hwaccel_output_format qsv -qsv_device /dev/dri/card1 -i "/temp/test/test_in.mkv" -c:v av1_qsv -global_quality 30 -preset 4 -c:a copy -c:s copy -y "/temp/test/test_out.mkv"Is this CPU or GPU encoding?
August 4, 2025Aug 4 Author 4 hours ago, jj_uk said:Is this CPU or GPU encoding?I assume this is the GPU, however what is PID 1122864 from the screenshot from above? If this is the process that you've issued the command then yes, it's transcoding on the GPU.Did you pass over /dev/dri/card1 to your container too?How much load is on your CPU (please don't forget that you possibly have to transcode audio and this is done on the CPU).Please note that this would be a question for the General subforums.
August 8, 2025Aug 8 Author 4 minutes ago, pras1011 said:Can the Qnap plugin be updated?What should be updated?The plugin barely need updates since the plugin downloads the driver packages which are important and make the plugin work.
August 11, 2025Aug 11 I apologize if this was asked and answered, but is the QNAP EC plugin supported in Unraid 7? I'm currently running Unraid 6.12.15, and plugin version 2023.10.06 without any issues, but I would like to update to the current version of Unraid 7. However, my QNAP NAS was constantly overheating until I was able to control the fans with this plugin, so I don't want to risk breaking it. Can I expect the plugin will continue to work if I upgrade to the current version of 7.x (looks like that's 7.2 at the moment)? Thanks!
August 12, 2025Aug 12 Author 9 hours ago, mr.answer said:Can I expect the plugin will continue to work if I upgrade to the current version of 7.x (looks like that's 7.2 at the moment)? Thanks!Yes.
August 17, 2025Aug 17 The uinput plugin is not allowed to be installed if the system is on unraid 7. maybe you could take a look @ich777 ?
August 17, 2025Aug 17 Author 18 minutes ago, Little709 said:The uinput plugin is not allowed to be installed if the system is on unraid 7. maybe you could take a look @ich777 ?Exactly, uinput is integrated a long time now into Unraid itself, so to speak, no need for a install anymore.
August 22, 2025Aug 22 @ich777 我的电脑主板的I/O芯片是 fintek F81966AB，使用Dynamix System Temperature插件无法显示主板温度及风扇转速。应该是没有驱动的原因，请问如何解决呢，如何正确的添加这个芯片的驱动？root@Tower:~# sensors-detect --auto# sensors-detect version 3.6.0# Board: ASRock Industrial IMB-X1314# Kernel: 6.12.24-Unraid x86_64# Processor: 12th Gen Intel(R) Core(TM) i5-12500 (6/151/5)Running in automatic mode, default answers to all questionsare assumed.Some south bridges, CPUs or memory controllers contain embedded sensors.Do you want to scan for them? This is totally safe. (YES/no):Silicon Integrated Systems SIS5595... NoVIA VT82C686 Integrated Sensors... NoVIA VT8231 Integrated Sensors... NoAMD K8 thermal sensors... NoAMD Family 10h thermal sensors... NoAMD Family 11h thermal sensors... NoAMD Family 12h and 14h thermal sensors... NoAMD Family 15h thermal sensors... NoAMD Family 16h thermal sensors... NoAMD Family 17h thermal sensors... NoAMD Family 15h power sensors... NoAMD Family 16h power sensors... NoHygon Family 18h thermal sensors... NoIntel digital thermal sensor... Success!(driver `coretemp')Intel AMB FB-DIMM thermal sensor... NoIntel 5500/5520/X58 thermal sensor... NoVIA C7 thermal sensor... NoVIA Nano thermal sensor... NoSome Super I/O chips contain embedded sensors. We have to write tostandard I/O ports to probe them. This is usually safe.Do you want to scan for Super I/O sensors? (YES/no):Probing for Super-I/O at 0x2e/0x2fTrying family `National Semiconductor/ITE'... NoTrying family `SMSC'... NoTrying family `VIA/Winbond/Nuvoton/Fintek'... YesFound unknown chip with ID 0x1502(logical device 4 has address 0x290, could be sensors)Probing for Super-I/O at 0x4e/0x4fTrying family `National Semiconductor/ITE'... NoTrying family `SMSC'... NoTrying family `VIA/Winbond/Nuvoton/Fintek'... NoTrying family `ITE'... NoSome systems (mainly servers) implement IPMI, a set of common interfacesthrough which system health data may be retrieved, amongst other things.We first try to get the information from SMBIOS. If we don't find itthere, we have to read from arbitrary I/O ports to probe for suchinterfaces. This is normally safe. Do you want to scan for IPMIinterfaces? (YES/no):Probing for `IPMI BMC KCS' at 0xca0... NoProbing for `IPMI BMC SMIC' at 0xca8... NoSome hardware monitoring chips are accessible through the ISA I/O ports.We have to write to arbitrary I/O ports to probe them. This is usuallysafe though. Yes, you do have ISA I/O ports even if you do not have anyISA slots! Do you want to scan the ISA I/O ports? (YES/no):Probing for `National Semiconductor LM78' at 0x290... Success!(confidence 6, driver `lm78')Probing for `National Semiconductor LM79' at 0x290... NoProbing for `Winbond W83781D' at 0x290... NoProbing for `Winbond W83782D' at 0x290... NoLastly, we can probe the I2C/SMBus adapters for connected hardwaremonitoring devices. This is the most risky part, and while it worksreasonably well on most systems, it has been reported to cause troubleon some systems.Do you want to probe the I2C/SMBus adapters now? (YES/no):Found unknown SMBus adapter 8086:7aa3 at 0000:00:1f.4.Sorry, no supported PCI bus adapters found.Module i2c-dev loaded successfully.Next adapter: SMBus I801 adapter at efa0 (i2c-0)Do you want to scan it? (YES/no/selectively):Client found at address 0x51Probing for `Analog Devices ADM1033'... NoProbing for `Analog Devices ADM1034'... NoProbing for `SPD EEPROM'... Yes(confidence 8, not a hardware monitoring chip)Client found at address 0x53Probing for `Analog Devices ADM1033'... NoProbing for `Analog Devices ADM1034'... NoProbing for `SPD EEPROM'... Yes(confidence 8, not a hardware monitoring chip)Next adapter: i915 gmbus dpa (i2c-1)Do you want to scan it? (yes/NO/selectively):Next adapter: i915 gmbus dpb (i2c-2)Do you want to scan it? (yes/NO/selectively):Next adapter: i915 gmbus dpc (i2c-3)Do you want to scan it? (yes/NO/selectively):Next adapter: i915 gmbus tc1 (i2c-4)Do you want to scan it? (yes/NO/selectively):Next adapter: i915 gmbus tc2 (i2c-5)Do you want to scan it? (yes/NO/selectively):Next adapter: i915 gmbus tc3 (i2c-6)Do you want to scan it? (yes/NO/selectively):Next adapter: i915 gmbus tc4 (i2c-7)Do you want to scan it? (yes/NO/selectively):Next adapter: i915 gmbus tc5 (i2c-8)Do you want to scan it? (yes/NO/selectively):Next adapter: i915 gmbus tc6 (i2c-9)Do you want to scan it? (yes/NO/selectively):Next adapter: AUX USBC2/DDI TC2/PHY C (i2c-10)Do you want to scan it? (yes/NO/selectively):Next adapter: AUX USBC4/DDI TC4/PHY E (i2c-11)Do you want to scan it? (yes/NO/selectively):Now follows a summary of the probes I have just done.Driver `lm78':* ISA bus, address 0x290Chip `National Semiconductor LM78' (confidence: 6)Driver `coretemp':* Chip `Intel digital thermal sensor' (confidence: 9)Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO):To load everything that is needed, add this to one of the systeminitialization scripts (e.g. /etc/rc.d/rc.local):#----cut here----# Chip driversmodprobe coretempmodprobe lm78/usr/bin/sensors -s#----cut here----You really should try these commands right now to make sure everythingis working properly. Monitoring programs won't work until the neededmodules are loaded.Unloading i2c-dev... OK Edited August 22, 2025Aug 22 by chen7210517
August 22, 2025Aug 22 Author 34 minutes ago, chen7210517 said:我的电脑主板的I/O芯片是 fintek F81966AB，使用Dynamix System Temperature插件无法显示主板温度及风扇转速。应该是没有驱动的原因，请问如何解决呢，如何正确的添加这个芯片的驱动？Is there a open source driver that can be installed from this manufacturer?If yes, where can I find it?
August 26, 2025Aug 26 On 2025/8/22 at PM8点44分, ich777 said:是否有可从该制造商安装的开源驱动程序？如果是的话，我在哪里可以找到它？https://github.com/torvalds/linux/commit/df293076a903530d7d12966ca19aa9570a6c70b3#diff-1659c1c1bf0e068ae1cde518e58ba13ce4159dcf9e1fdc3a3772c28ceeb5325f
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.