Jump to content

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


Recommended Posts

37 minutes ago, DeadPixel said:

Yes. I also tried removing the plugin, rebooting, unloading the drivers from the system temp gui, installing the plugin again and rebooting.

Is anything not working currently?

 

Usually this shouldn't affect anything.

Link to comment
3 minutes ago, ich777 said:

Is anything not working currently?

 

Usually this shouldn't affect anything.

Aside from the 2 sets of data being reported everything seems fine. Unraid had been up around 12 hours without any problems and sensors seem to be updating ok so I think it might just be something to ignore 🙂

Link to comment
Just now, DeadPixel said:

Unraid had been up around 12 hours without any problems and sensors seem to be updating ok so I think it might just be something to ignore 🙂

You could blacklist the default one but if everything is working I would leave it as is.

Link to comment
31 minutes ago, ich777 said:

You could blacklist the default one but if everything is working I would leave it as is.

I would not really know where to start there, plus generally when I start poking things start breaking!!

 

I see the following in the logs

 

it87: it87 driver version v1.0-154-gf40148e.20240401
[   77.262609] it87: Found IT8688E chip at 0xa40, revision 1
[   77.262857] it87: Beeping is supported
[   77.266773] it87: Found IT8792E/IT8795E chip at 0xa60, revision 3
[   77.266919] it87: Beeping is supported

 

unless there is a simple way to force it to only use the first one and ignore the second, I will forget about it!

Link to comment
1 minute ago, DeadPixel said:

unless there is a simple way to force it to only use the first one and ignore the second, I will forget about it!

It seems that you have two chips on your Motherboard.

I don't know nothing about your system but I would recommend if something is not working anymore you'll come back here and report it including your Diagnostics, for now I would just leave it as is.

  • Thanks 1
Link to comment
2 hours ago, nassauer said:

What could be the issue here: the driver does work, as it reports accurate RPM and temps, but the PWM percentage is 0. Can´t control the fans at all. The only time they react is when set to 100% in Bios and then running the script (attached). But with the script they just turn off and never back on.

May I ask where that you get that script? I have to be honest, I've not looked through the whole script but you don't have to set anything in the BIOS to get this to work.

I think the script does miss a step where it has to set the actual fan to manual mode (which this script utilizes), but that differs from Motherboard to motherboard a bit, at least the path.

 

It's called "pwm<FAN>_enable" where you usually have to set this to 1 instead of 2 (1=manual | 2=auto), after that you will be able to change the fan speeds based on the PWM values between 0 and 255

 

Please don't do double posts (here and German sub forums), it is enough to have one post not two. After further investigation I saw that you already three posts. BTW I already answered in the German subforums but you didn't answer there. :/

  • Like 1
Link to comment
18 minutes ago, ich777 said:

Please see this post:


You have to wait until a public Unraid beta drops.

 

The plugin shouldn‘t be visible on 6.12.10 or is it?

ahh, Im using the custom kernel from thor, which added the Ugreen LED driver, thought I could use the two together

Link to comment

On a different topic, when I try to install "ITE IT87 Driver", I get this error message:

plugin: installing: it87-driver.plg
Executing hook script: pre_plugin_checks
plugin: downloading: it87-driver.plg ... done

Executing hook script: pre_plugin_checks

-----------------------Downloading IT87 Drivers!-------------------------
---------This could take some time, please don't close this window!----------

-----------------------Can't download IT87 Drivers-----------------------
plugin: run failed: '/bin/bash' returned 1
Executing hook script: post_plugin_checks

 

Link to comment
19 hours ago, ranova said:

On a different topic, when I try to install "ITE IT87 Driver", I get this error message

If you are running a different Kernel none of the driver plugins will work.

  • Like 1
  • Thanks 1
Link to comment
  • 2 weeks later...

Hey with the upgrade to 7.0 beta the python plugin pip broke.

 

```

WARNING: pip is configured with locations that require TLS/SSL, however the ssl module in Python is not available.
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/ssl/
```

I hope this is the right place to report the error. Or is the plugin forum better? But this explicitly happens with the upgrade to 7.0.

I read in here that it happend for someone before but I could not fix it with reinstalling/rebooting.

Link to comment
4 minutes ago, nexiz said:

I do not have nerd tools only un-get

Oh please mention that next time since there is also a pure Python plugin available in the CA App.

 

However, you have to keep in mind that Unraid 7 is based on Slackware current and that this could be the issue, you have to switch from Slackware 15.0 to Slackware current in your un-get sources.list file to get the new packages.

 

5 minutes ago, nexiz said:

does nerd-tools offer a python package

I'm pretty certain they do.

Link to comment

I am using the pure python plugin from the CA store. It links to this support forum. But now i also tried un-get and the same error occurs. I will try to switch to current. 

 

edit:

it works with un-get when changing the source in /boot/config/plugins/un-get/sources.list to https://mirrors.slackware.com/slackware/slackware64-current/slackware64/ current 

 

But it installs Python 3.11.9

Edited by nexiz
Link to comment
10 minutes ago, Govnah said:

No, downloaded driver just fine, just no drivers detected, see attached.

Have you tried to click detect?

 

What does sensors-detect output if you execute it from a terminal.

 

This seems more like a misconfiguration to me.

Link to comment

Yes I have clicked on detect and here is the output:

 

root@unRAID-Spare:~# sensors-detect
bash: sensors-detect: command not found

 

sensors:

root@unRAID-Spare:~# sensors
coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +70.0°C  (high = +100.0°C, crit = +100.0°C)
Core 0:        +60.0°C  (high = +100.0°C, crit = +100.0°C)
Core 4:        +64.0°C  (high = +100.0°C, crit = +100.0°C)
Core 8:        +70.0°C  (high = +100.0°C, crit = +100.0°C)
Core 9:        +70.0°C  (high = +100.0°C, crit = +100.0°C)
Core 10:       +70.0°C  (high = +100.0°C, crit = +100.0°C)
Core 11:       +70.0°C  (high = +100.0°C, crit = +100.0°C)
Core 12:       +69.0°C  (high = +100.0°C, crit = +100.0°C)
Core 13:       +69.0°C  (high = +100.0°C, crit = +100.0°C)
Core 14:       +69.0°C  (high = +100.0°C, crit = +100.0°C)
Core 15:       +69.0°C  (high = +100.0°C, crit = +100.0°C)

eth1-pci-5800
Adapter: PCI adapter
PHY Temperature:  +44.0°C  
MAC Temperature:  +44.0°C  

nvme-pci-0100
Adapter: PCI adapter
Composite:    +45.9°C  (low  =  -5.2°C, high = +79.8°C)
                       (crit = +84.8°C)

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +27.8°C  

it8613-isa-0a30
Adapter: ISA adapter
in0:           1.18 V  (min =  +0.92 V, max =  +1.49 V)
in1:           1.12 V  (min =  +2.73 V, max =  +0.34 V)  ALARM
in2:           2.04 V  (min =  +2.77 V, max =  +2.09 V)  ALARM
in4:           2.01 V  (min =  +2.64 V, max =  +2.08 V)  ALARM
in5:           2.06 V  (min =  +2.04 V, max =  +2.50 V)
3VSB:          3.30 V  (min =  +5.57 V, max =  +3.59 V)  ALARM
Vbat:          2.75 V  
+3.3V:         3.34 V  
Array Fan:   1814 RPM  (min =    0 RPM)
Array Fan:    720 RPM  (min =    0 RPM)
Array Fan:    694 RPM  (min =    0 RPM)
temp1:        +74.0°C  (low  = +62.0°C, high = -77.0°C)  ALARM  sensor = Intel PECI
temp2:        +32.0°C  (low  =  -8.0°C, high = -70.0°C)  ALARM  sensor = thermal diode
temp3:       -128.0°C  (low  = -102.0°C, high = +33.0°C)
intrusion0:  ALARM

eth0-pci-5900
Adapter: PCI adapter
PHY Temperature:  +57.0°C  
MAC Temperature:  +57.0°C  

nvme-pci-5700
Adapter: PCI adapter
Composite:    +40.9°C  (low  = -273.1°C, high = +81.8°C)
                       (crit = +84.8°C)
Sensor 1:     +40.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +44.9°C  (low  = -273.1°C, high = +65261.8°C)

nvme-pci-5600
Adapter: PCI adapter
Composite:    +45.9°C  (low  =  -5.2°C, high = +83.8°C)
                       (crit = +87.8°C)

 

 

Thanks

Link to comment
Posted (edited)

Update: I rolled back, installed, and then upgraded.

 

I installed 6.12.10 on another USB and works. On my current version, do you suggest I downgrade to load the driver and then upgrade again to beta/unRAID 7? I rather not unless that's what is recommended.

 

Thanks

Edited by Govnah
Link to comment
6 hours ago, Govnah said:

I installed 6.12.10 on another USB and works. On my current version, do you suggest I downgrade to load the driver and then upgrade again to beta/unRAID 7? I rather not unless that's what is recommended.

All the values are there so I suspect a configuration error within System Temp.

Please uninstall the plugin, reboot, reinstall the plugin and click detect and see if anything changes (the reboot after uninstalling the plugin is important.

 

If that also doesn't help I would recommend that you create a post in the System Temp support thread since as said above all values are listed.

Link to comment
Posted (edited)
On 6/30/2024 at 2:00 AM, nexiz said:

Hey with the upgrade to 7.0 beta the python plugin pip broke.

 

```

WARNING: pip is configured with locations that require TLS/SSL, however the ssl module in Python is not available.
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/ssl/
```

I hope this is the right place to report the error. Or is the plugin forum better? But this explicitly happens with the upgrade to 7.0.

I read in here that it happend for someone before but I could not fix it with reinstalling/rebooting.

anyone having python, pip issues after installing Unraid 7 grab this install:

https://slackware.uk/slackware/slackware64-current/slackware64/n/openssl11-1.1.1w-x86_64-1.txz

 

and drop it in /boot/extra and reboot.

Edited by meunraid
  • Like 1
Link to comment

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...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...