Jack Skellington

Members
  • Posts

    10
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Jack Skellington's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Is it safe to run the isaset command?
  2. Xxx@xxx:~# modprobe it87 force_id=0x8620 Xxx@xxx:~# sensors No sensors found! Make sure you loaded all the kernel drivers you need. Try sensors-detect to find out which these are. Xxx@xxx:~#
  3. # sensors-detect revision 6284 (2015-05-31 14:00:33 +0200) # Board: ASUSTeK COMPUTER INC. PRIME B350-PLUS # Kernel: 4.14.26-unRAID x86_64 # Processor: AMD Ryzen 7 1700X Eight-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): 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): 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 0x8655 (logical device 4 has address 0x290, could be sensors) 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'... No 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): 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): Probing for `National Semiconductor LM78' at 0x290... Success! (confidence 6, driver `lm78') 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): 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): 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): Next adapter: SMBus PIIX4 adapter port 3 at 0b00 (i2c-2) Do you want to scan it? (YES/no/selectively): Next adapter: SMBus PIIX4 adapter port 4 at 0b00 (i2c-3) Do you want to scan it? (YES/no/selectively): Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `lm78': * ISA bus, address 0x290 Chip `National Semiconductor LM78' (confidence: 6) Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): y Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors for initialization at boot time. You should now start the lm_sensors service to load the required kernel modules. Unloading i2c-dev... OK Do I need to copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors ?
  4. Hi, I can't get any info with my config. Anyone has a way to fix it? Thx! Unraid version 6.4.0_rc15e CPU = AMD Ryzen 1700X MB = ASUS Prime B350-Plus AMD Ryzen AM4 Detected sensor = lm78
  5. Once I deleted ZM, an Orphan image was left. I cleared it with the Cleanup Appdata App. EDIT: It reappeared after rebooting: (orphan image) Image ID: f7d4c6a69478 Error: Execution error Server error
  6. I deleted ZoneMinder Docker and now I can't use Docker! Great! Hope to get it running again fast. Thanks in advance! asgard-diagnostics-20170726-2218.zip
  7. Hi everyone! It's been a while since I wanted to really build an unRAID server! I'm very pleased with it, but something is wrong with it. Can someone check the diagnostics please? Best regards, asgard-diagnostics-20170722-1449.zip