RonUSMC Posted August 12, 2017 Share Posted August 12, 2017 Searching this forum has been very helpful so I'm going to start two threads for the issues I'm having today. New build on the 6.4.0-rc7a build to fix the random crashes.. Running AMD Ryzen 5 1600 on a Gigabyte GA-AB350M-D3H running the most recent F3 Bios. Repro steps: 1. Install Dynamix System Temp 2. Install NerdPack GUI 3. Go into NerdPack and enable perl-5.24.0-x86_64-1.txz 4. Go to http://tower/Settings/TempSettings 5. Click DETECT Nothing happens. Sometimes page refreshes, but nothing populates. 6. Reboot. 7. Retry, nothing changes. tower-diagnostics-20170812-0813.zip Quote Link to comment
RonUSMC Posted August 12, 2017 Author Share Posted August 12, 2017 Doing a sensors-detect I get two hits. root@Tower:~# sensors-detect # sensors-detect revision 6284 (2015-05-31 14:00:33 +0200) # System: Gigabyte Technology Co., Ltd. AB350M-D3H [Default string] # Board: Gigabyte Technology Co., Ltd. AB350M-D3H-CF # Kernel: 4.12.3-unRAID x86_64 # Processor: AMD Ryzen 5 1600 Six-Core Processor (23/1/1) This program will help you determine which kernel modules you need to load to use lm_sensors most effectively. It is generally safe and recommended to accept the default answers to all questions, unless you know what you're doing. Some south bridges, CPUs or memory controllers contain embedded sensors. Do you want to scan for them? This is totally safe. (YES/no): y Silicon Integrated Systems SIS5595... No VIA VT82C686 Integrated Sensors... No VIA VT8231 Integrated Sensors... No AMD K8 thermal sensors... No AMD Family 10h thermal sensors... No AMD Family 11h thermal sensors... No AMD Family 12h and 14h thermal sensors... No AMD Family 15h thermal sensors... No AMD Family 16h thermal sensors... No AMD Family 15h power sensors... No AMD Family 16h power sensors... No Intel digital thermal sensor... No Intel AMB FB-DIMM thermal sensor... No Intel 5500/5520/X58 thermal sensor... No VIA C7 thermal sensor... No VIA Nano thermal sensor... No Some Super I/O chips contain embedded sensors. We have to write to standard I/O ports to probe them. This is usually safe. Do you want to scan for Super I/O sensors? (YES/no): y Probing for Super-I/O at 0x2e/0x2f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... Yes Found unknown chip with ID 0x8686 Probing for Super-I/O at 0x4e/0x4f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... Yes Found unknown chip with ID 0x8733 Some systems (mainly servers) implement IPMI, a set of common interfaces through which system health data may be retrieved, amongst other things. We first try to get the information from SMBIOS. If we don't find it there, we have to read from arbitrary I/O ports to probe for such interfaces. This is normally safe. Do you want to scan for IPMI interfaces? (YES/no): y Probing for `IPMI BMC KCS' at 0xca0... No Probing for `IPMI BMC SMIC' at 0xca8... No Some 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 usually safe though. Yes, you do have ISA I/O ports even if you do not have any ISA slots! Do you want to scan the ISA I/O ports? (YES/no): y Probing for `National Semiconductor LM78' at 0x290... No Probing for `National Semiconductor LM79' at 0x290... No Probing for `Winbond W83781D' at 0x290... No Probing for `Winbond W83782D' at 0x290... No Lastly, we can probe the I2C/SMBus adapters for connected hardware monitoring devices. This is the most risky part, and while it works reasonably well on most systems, it has been reported to cause trouble on some systems. Do you want to probe the I2C/SMBus adapters now? (YES/no): y Found unknown SMBus adapter 1022:790b at 0000:00:14.0. Sorry, no supported PCI bus adapters found. Module i2c-dev loaded successfully. Next adapter: SMBus PIIX4 adapter port 0 at 0b00 (i2c-0) Do you want to scan it? (YES/no/selectively): y Client found at address 0x4f Probing for `National Semiconductor LM75'... No Probing for `National Semiconductor LM75A'... No Probing for `Dallas Semiconductor DS75'... No Probing for `Maxim MAX6642'... No Probing for `Texas Instruments TMP421'... No Probing for `Texas Instruments TMP422'... No Probing for `Texas Instruments TMP435'... No Probing for `Texas Instruments TMP441'... No Probing for `Maxim MAX6633/MAX6634/MAX6635'... No Probing for `NXP/Philips SA56004'... No Client found at address 0x52 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... No Client found at address 0x53 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... No Next adapter: SMBus PIIX4 adapter port 2 at 0b00 (i2c-1) Do you want to scan it? (YES/no/selectively): y Client found at address 0x4f Probing for `National Semiconductor LM75'... No Probing for `National Semiconductor LM75A'... No Probing for `Dallas Semiconductor DS75'... No Probing for `Maxim MAX6642'... No Probing for `Texas Instruments TMP421'... No Probing for `Texas Instruments TMP422'... No Probing for `Texas Instruments TMP435'... No Probing for `Texas Instruments TMP441'... No Probing for `Maxim MAX6633/MAX6634/MAX6635'... No Probing for `NXP/Philips SA56004'... No Client found at address 0x52 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... No Client found at address 0x53 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... No Next adapter: SMBus PIIX4 adapter port 3 at 0b00 (i2c-2) Do you want to scan it? (YES/no/selectively): y Client found at address 0x4f Probing for `National Semiconductor LM75'... No Probing for `National Semiconductor LM75A'... No Probing for `Dallas Semiconductor DS75'... No Probing for `Maxim MAX6642'... No Probing for `Texas Instruments TMP421'... No Probing for `Texas Instruments TMP422'... No Probing for `Texas Instruments TMP435'... No Probing for `Texas Instruments TMP441'... No Probing for `Maxim MAX6633/MAX6634/MAX6635'... No Probing for `NXP/Philips SA56004'... No Client found at address 0x52 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... No Client found at address 0x53 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... No Next adapter: SMBus PIIX4 adapter port 4 at 0b00 (i2c-3) Do you want to scan it? (YES/no/selectively): y Client found at address 0x4f Probing for `National Semiconductor LM75'... No Probing for `National Semiconductor LM75A'... No Probing for `Dallas Semiconductor DS75'... No Probing for `Maxim MAX6642'... No Probing for `Texas Instruments TMP421'... No Probing for `Texas Instruments TMP422'... No Probing for `Texas Instruments TMP435'... No Probing for `Texas Instruments TMP441'... No Probing for `Maxim MAX6633/MAX6634/MAX6635'... No Probing for `NXP/Philips SA56004'... No Client found at address 0x52 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... No Client found at address 0x53 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... No Sorry, no sensors were detected. Either your system has no sensors, or they are not supported, or they are connected to an I2C or SMBus adapter that is not supported. If you find out what chips are on your board, check http://www.lm-sensors.org/wiki/Devices for driver status. I can't seem to find how to load those sensors. I think the wiki is dead. Quote Link to comment
Frank1940 Posted August 12, 2017 Share Posted August 12, 2017 Did you go through this thread? The Ryzen introduction is/was a bit of a rocky one from what I have gleaned from watching this forum. You might to also ask this question there if someone doesn't back with a useful response here. Quote Link to comment
RonUSMC Posted August 12, 2017 Author Share Posted August 12, 2017 I'm getting closer. It seems that these chips aren't fully supported yet, but I could force it. Still not fixed though.. but closer.\ root@Tower:~# sudo modprobe --verbose it87 force_id=0x8733 insmod /lib/modules/4.12.3-unRAID/kernel/drivers/hwmon/it87.ko.xz force_id=0x873 3 root@Tower:~# sensors it8792-isa-0a40 Adapter: ISA adapter in0: +0.88 V (min = +0.00 V, max = +2.78 V) in1: +1.83 V (min = +0.00 V, max = +2.78 V) in2: +1.84 V (min = +0.00 V, max = +2.78 V) in3: +1.84 V (min = +0.00 V, max = +2.78 V) in4: +0.82 V (min = +0.00 V, max = +2.78 V) in5: +0.84 V (min = +0.00 V, max = +2.78 V) in6: +1.10 V (min = +0.00 V, max = +2.78 V) 3VSB: +1.48 V (min = +0.00 V, max = +2.78 V) Vbat: +1.41 V fan1: 1128 RPM (min = 10 RPM) fan2: 0 RPM (min = 0 RPM) fan3: 0 RPM (min = 0 RPM) temp1: +37.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor temp2: +39.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor temp3: +23.0°C (low = +0.0°C, high = +60.0°C) sensor = disabled intrusion0: ALARM it8792-isa-0a60 Adapter: ISA adapter in0: +0.92 V (min = +0.00 V, max = +2.78 V) in1: +1.08 V (min = +0.00 V, max = +2.78 V) in2: +1.11 V (min = +0.00 V, max = +2.78 V) +3.3V: +1.68 V (min = +0.00 V, max = +2.78 V) in4: +1.33 V (min = +0.00 V, max = +2.78 V) in5: +1.21 V (min = +0.00 V, max = +2.78 V) in6: +2.78 V (min = +0.00 V, max = +2.78 V) ALARM 3VSB: +1.67 V (min = +0.00 V, max = +2.78 V) Vbat: +1.58 V fan1: 0 RPM (min = 0 RPM) fan2: 0 RPM (min = 0 RPM) fan3: 0 RPM (min = 0 RPM) temp1: +27.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor temp2: +32.0°C (low = +127.0°C, high = +127.0°C) sensor = Intel PECI temp3: +34.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor intrusion0: ALARM Quote Link to comment
RonUSMC Posted August 12, 2017 Author Share Posted August 12, 2017 @Frank1940 Yes, thank you for that link. I read through and there is someone else that is stuck. I posted a link and results so far over there as well. Quote Link to comment
RonUSMC Posted August 12, 2017 Author Share Posted August 12, 2017 Well, I got really close. I did a dmesg and got [ 9142.757674] it87: Found IT8733E chip at 0xa40, revision 2 [ 9142.757699] it87: Beeping is supported [ 9142.758124] it87: Found IT8733E chip at 0xa60, revision 3 and the owner of the IT87 package said that it is supported in the update, but updating it is beyond my skills. I did a sudo sensors-detect and it froze my system. I think I will leave it where it is for now until someone that knows more than I can chime in. Quote Link to comment
RonUSMC Posted August 22, 2017 Author Share Posted August 22, 2017 Doing the same command I get different results. Then I can go into 'System Temp' and at least get something there, which is pretty cool. root@Tower:~# sudo modprobe --verbose it87 force_id=0x8733 insmod /lib/modules/4.12.3-unRAID/kernel/drivers/hwmon/hwmon-vid.ko.xz insmod /lib/modules/4.12.3-unRAID/kernel/drivers/hwmon/it87.ko.xz force_id=0x8733 1 Quote Link to comment
RonUSMC Posted August 22, 2017 Author Share Posted August 22, 2017 It's such a backwards way of doing it. If I knew how to update it87, then I might try to update that package and see if the results were better or atleast readable. 1 Quote Link to comment
TianJesper Posted May 17, 2018 Share Posted May 17, 2018 Finally a solution for my temp issue, ohh happy day ? But does anybody have a clue, as to why my temp settings disappear, each time i reboot. i've simply cant getting it to keep the settings...?? Quote Link to comment
Narvath Posted January 13, 2019 Share Posted January 13, 2019 Finaly, just writing it87 worked since my auto detect didn't work either... But i end up with 6 temp readings that starts with it8792 and ends with either temp1, temp2 or temp3 (2 of each) and they all have different readings !_! is that a problem since i din't use auto detect? or is there simply 6 temp readings from different places of the mobo? Quote Link to comment
Recommended Posts
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.