Jump to content

DToX

Members
  • Content Count

    54
  • Joined

  • Last visited

Community Reputation

0 Neutral

About DToX

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed
  1. I did not find any option like you mentioned so i tried to flash it and was unsuccessful, I'm pretty sure I bricked it so i'll just order one of the recommend cards in the next few days. I doubt you bricked it. That card is not based on the same hardware as this thread, so none of the commands should work. I do not think it can be flashed to JBOD. Well I figure it was worth a shot but I cant get it to show its gui and is not detected when running sas2flash
  2. I did not find any option like you mentioned so i tried to flash it and was unsuccessful, I'm pretty sure I bricked it so i'll just order one of the recommend cards in the next few days.
  3. DToX, he wasn't actually responding to you, he was announcing an issue he had found, one that should be straight forward to fix. I'm actually happy that you have the same issue I have, needing the Fintek f71882fg driver. I suspect you haven't read my post above (found here). Now that I know someone else needs 'f71882fg', I'll ask Tom if he can add it to UnRAID (didn't want to before if I was the only one). Since yours is very similar except your board uses the k10temp chipset instead of the k8temp chipset, I think you can probably use the sensors.conf file I posted, except change "k8temp-*" to "k10temp-*". Make sure you use an editor that keeps the linux line endings. That should at least give you 2 CPU temps for now, until f71882fg support is added. Be aware though that many users have reported that the k8temp and k10temp chipsets are notoriously unreliable for true temps. Works fine for me though. Thank you that was helpful, anyway fingers crossed on a future update
  4. Well that is good to know but I can't even read my mobo temp, I think from what I have gathered is that the linux kernel doesn't support the driver needed for my mobo so I cannot get the temps
  5. I can't get my Mobo Temp to show and i'm assuming it's from this Driver `f71882fg': * ISA bus, address 0x480 Chip `Fintek F71889A Super IO Sensors' (confidence: 9) Is there anyway to get this working corrrectly? root@Tower:~# sensors k10temp-pci-00c3 Adapter: PCI adapter CPU Temp: +20.8°C (high = +70.0°C) (crit = +70.0°C, hyst = +67.0°C) fam15h_power-pci-00c4 Adapter: PCI adapter power1: 124.95 W (crit = 124.95 W) root@Tower:~# Sensor-detect output root@Tower:/tmp# perl sensors-detect # sensors-detect revision $Revision$ # System: MSI MS-7693 [2.0] # Board: MSI 970A-G46 (MS-7693) 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): yes 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... Success! (driver `k10temp') AMD Family 16h thermal sensors... No AMD Family 15h power sensors... Success! (driver `fam15h_power') AMD Family 16h power sensors... No Intel digital thermal sensor... No Intel AMB FB-DIMM 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): yes 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'... No Probing for Super-I/O at 0x4e/0x4f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... Yes Found `Fintek F71889A Super IO Sensors' Success! (address 0x480, driver `f71882fg') 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): yes 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): yes 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): yes Using driver `i2c-piix4' for device 0000:00:14.0: ATI Technologies Inc SB600/SB700/SB800 SMBus Module i2c-dev loaded successfully. Next adapter: SMBus PIIX4 adapter at 0b00 (i2c-0) Do you want to scan it? (yes/NO/selectively): yes Client found at address 0x50 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... Yes (confidence 8, not a hardware monitoring chip) Probing for `EDID EEPROM'... No Client found at address 0x51 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... Yes (confidence 8, not a hardware monitoring chip) Client found at address 0x52 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... Yes (confidence 8, not a hardware monitoring chip) Client found at address 0x53 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... Yes (confidence 8, not a hardware monitoring chip) Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `fam15h_power' (autoloaded): * Chip `AMD Family 15h power sensors' (confidence: 9) Driver `k10temp' (autoloaded): * Chip `AMD Family 15h thermal sensors' (confidence: 9) Driver `f71882fg': * ISA bus, address 0x480 Chip `Fintek F71889A Super IO Sensors' (confidence: 9) Warning: the required module f71882fg is not currently installed on your system. Check http://www.lm-sensors.org/wiki/Devices for driver availability. No modules to load, skipping modules configuration. Unloading i2c-dev... OK root@Tower:/tmp#
  6. I popped it into my unraid server but unraid doesn't see it and i'm not 100% sure what to do when it comes to these cards, that's why I was trying to see if it was supported etc. I can get into it's gui before unraid boots and it detects the one hard drive i connected to it but that's as far as ive gotten
  7. Yeah I know what you mean but I was given this card for free and was in need so I figured I would try it out guess i'll buy one of the recommended ones.
  8. Hey I was wondering if someone could give me an answer on if I can use a LSI 8708EM2 controller (https://store.lsi.com/index.cfm/Clearance/8708-Controllers/LSI00187/) I couldn't really find a perfect answer on this and thank you for any help.
  9. preferences won't load, cursor just keeps spinning I got around the problem thanks nacat78, up too late banging my head
  10. I keep getting the following error when I try to make a virtual machine 00:21:23.993448 Medium::Task ERROR [COM]: aRC=VBOX_E_FILE_ERROR (0x80bb0004) aIID={05f2bbb6-a3a6-4fb9-9b49-6d0dda7142ac} aComponent={Medium} aText={Could not create the medium storage unit '/root/VirtualBox VMs/ubuntu/ubuntu.vdi'. 00:21:23.993464 Medium::Task VDI: disk would overflow creating image '/root/VirtualBox VMs/ubuntu/ubuntu.vdi' (VERR_DISK_FULL)}, preserve=false I'm getting this in the log but it seems like it's trying to save it to my ram and not to the actual cache drive Dec 17 14:23:07 Tower rc.virtualbox[28156]: Symbolically linked /mnt/cache/vbox to /root/.VirtualBox
  11. I had to use this to fix my issue installpkg /boot/packages/openssl-solibs-1.0.1c-i486-3.txz