bonienl 689 Posted December 1, 2014 dynamix.cfg now looks like this. sleep="1" [sleep] sleep="1" [display] sleep="1" date="%c" sleep="1" number=",." sleep="1" scale="-1" sleep="1" align="right" sleep="1" tabs="0" sleep="1" text="0" sleep="1" view="" sleep="1" total="1" sleep="1" spin="1" sleep="1" usage="1" sleep="1" icons="1" sleep="1" banner="" sleep="1" theme="white" sleep="1" unit="C" sleep="1" hot="45" sleep="1" max="55" sleep="1" poll="0" sleep="1" refresh="60000" Kevin. Okay, I see what went wrong. Need to make a modification to the installation file (.plg). You better delete the file, it is completely mixed-up (don't worry settings will return to default once you delete). Quote Share this post Link to post
digitalfixer 7 Posted December 1, 2014 I just disabled page refresh and now the file looks normal again. Kevin. Quote Share this post Link to post
GHunter 9 Posted December 1, 2014 Bonienl, Thanks for all your hard work on these plugins and the Dynamix integration into unRAID! This really looks great! Gary Quote Share this post Link to post
jjslegacy 1 Posted December 1, 2014 Thanks for all the hardwork - very excited about all of this. One question on email notifications. The old simplefeatures email notify would email me when the server was booted and give me some basic info. Does this still exist? I have the email notify setup but don't get anything on boot. Is the new system only for major issues etc? Thanks! Quote Share this post Link to post
bonienl 689 Posted December 1, 2014 Notifications in the new system are event driven, this is a different approach from the past in which the email script in the background would poll every so many minutes to check status and report. In this situation email notifications and browser notifications was strictly separated. The event approach allows the usage of event handlers which determine what and how to process a notification, e.g. send a mail, show a popup or do both, this however is still work in progress and event handlers are being added for upcoming updates. Quote Share this post Link to post
itimpi 283 Posted December 1, 2014 The default for the dynamix GUI in beta12 appears to be the 'white' theme. Would it not be better to default to the 'black' one as it looks much slicker (at least in my opinion). Quote Share this post Link to post
archedraft 12 Posted December 1, 2014 I agree that black looks much better but changing that to default would start a riot. Quote Share this post Link to post
itimpi 283 Posted December 1, 2014 I agree that black looks much better but changing that to default would start a riot. Why? It would make it much clerer that there has been a major GUI overhaul. It can always be changed back to white for those who prefer it. Maybe changing between these themes is something that should be made particularly easy and obvious (e.g. an option on the dashboard). Quote Share this post Link to post
archedraft 12 Posted December 1, 2014 People dislike change. I am willing to bet that a few people are going to complain that the new GUI is dynamix and they are not used to the way it looks. Moral of the story is people be nuts! That said I vote black is default too. Quote Share this post Link to post
itimpi 283 Posted December 1, 2014 People dislike change. I am willing to bet that a few people are going to complain that the new GUI is dynamix and they are not used to the way it looks. Moral of the story is people be nuts! That said I vote black is default too. At one level I guess you are corrett. However there is a vocal set o fusers who have been complaining that the current GUI is outdated and needs upting to a more modern look. I was thinking that changing the default for v6 to black what make it more obvious to people that this release is something new. It might encourage them to go looking for the new features rather than assuming that it is just 'more of the same'. On a side inote are other colored themes easy to implement for those who like things to be really flamboyant? Quote Share this post Link to post
mostlydave 1 Posted December 1, 2014 ah, sorry for the confusion. If you are using a sensors.conf file, you need to move it into the folder /boot/config. Otherwise you need to create one to set the correct names for the sensors of your M/B and CPU. Where can we find more info on how to create the sensors.conf and what it should contain? Quote Share this post Link to post
GHunter 9 Posted December 1, 2014 Where can we find more info on how to create the sensors.conf and what it should contain? Check out the Wiki for information on setting up CPU and board temperature sensing here: http://lime-technology.com/wiki/index.php/Setting_up_CPU_and_board_temperature_sensing You'll want to save your sensors.conf file to your flash drive here: /boot/config/sensors.conf Gary Quote Share this post Link to post
Ashe 4 Posted December 1, 2014 Skip to step 7, and see which driver comes up at the end. Mine only showed the virtual-0 until I ran sensors-detect which came up with chip it87, ran 'modprobe it87' at cli then 'sensors' which then displayed the it87 core information for me to create the sensors.conf file Quote Share this post Link to post
dstroot 1 Posted December 1, 2014 Anyone having difficulty getting cache-dirs to start? I can't seem to get it rolling. I took the script version out of my go file already. Quote Share this post Link to post
eroz 0 Posted December 2, 2014 trying to setup my sensors.cfg, This is what I have in it, #modprobe for each sensor modprobe nct6775 modprobe <sensor2> modprobe <sensor3> Not sure what <Sensor2> and <sensor3> should actually be? Quote Share this post Link to post
MyKroFt 5 Posted December 2, 2014 The modprobe lines need to go into your go file my sensors.conf is as follows for a example # lines starting with "#" are comments and ignored # sensor configuration chip "nct6776-isa-*" label temp1 "MB Temp" label temp2 "CPU Temp" The wiki entry listed tells you step by step what to do Myk trying to setup my sensors.cfg, This is what I have in it, #modprobe for each sensor modprobe nct6775 modprobe <sensor2> modprobe <sensor3> Not sure what <Sensor2> and <sensor3> should actually be? Quote Share this post Link to post
eroz 0 Posted December 2, 2014 The modprobe lines need to go into your go file my sensors.conf is as follows for a example # lines starting with "#" are comments and ignored # sensor configuration chip "nct6776-isa-*" label temp1 "MB Temp" label temp2 "CPU Temp" The wiki entry listed tells you step by step what to do Myk trying to setup my sensors.cfg, This is what I have in it, #modprobe for each sensor modprobe nct6775 modprobe <sensor2> modprobe <sensor3> Not sure what <Sensor2> and <sensor3> should actually be? Missed all that since I had no output the first time. I get this root@Tower:~# sensors coretemp-isa-0000 Adapter: ISA adapter Physical id 0: +31.0 C (high = +80.0 C, crit = +100.0 C) Core 0: +29.0 C (high = +80.0 C, crit = +100.0 C) Core 1: +29.0 C (high = +80.0 C, crit = +100.0 C) Core 2: +31.0 C (high = +80.0 C, crit = +100.0 C) Core 3: +28.0 C (high = +80.0 C, crit = +100.0 C) nct6776-isa-0290 Adapter: ISA adapter Vcore: +0.88 V (min = +0.00 V, max = +1.74 V) in1: +1.85 V (min = +0.00 V, max = +0.00 V) ALARM AVCC: +3.34 V (min = +2.98 V, max = +3.63 V) +3.3V: +3.34 V (min = +2.98 V, max = +3.63 V) in4: +0.90 V (min = +0.00 V, max = +0.00 V) ALARM in5: +1.69 V (min = +0.00 V, max = +0.00 V) ALARM in6: +0.80 V (min = +0.00 V, max = +0.00 V) ALARM 3VSB: +3.47 V (min = +2.98 V, max = +3.63 V) Vbat: +3.30 V (min = +2.70 V, max = +3.63 V) fan1: 0 RPM (min = 0 RPM) fan2: 1580 RPM (min = 0 RPM) fan3: 0 RPM (min = 0 RPM) fan4: 0 RPM (min = 0 RPM) fan5: 0 RPM (min = 0 RPM) SYSTIN: +31.0 C (high = +0.0 C, hyst = +0.0 C) ALARM sensor = thermistor CPUTIN: +40.5 C (high = +80.0 C, hyst = +75.0 C) sensor = thermistor AUXTIN: +36.0 C (high = +80.0 C, hyst = +75.0 C) sensor = thermistor PECI Agent 0: +31.0 C (high = +80.0 C, hyst = +75.0 C) (crit = +100.0 C) PCH_CHIP_TEMP: +0.0 C PCH_CPU_TEMP: +0.0 C PCH_MCH_TEMP: +0.0 C intrusion0: ALARM intrusion1: ALARM beep_enable: disabled I'm still not sure what my sensors are? This is what I get for labels root@Tower:~# sensors -u coretemp-isa-0000 coretemp-isa-0000 Adapter: ISA adapter Physical id 0: temp1_input: 31.000 temp1_max: 80.000 temp1_crit: 100.000 temp1_crit_alarm: 0.000 Core 0: temp2_input: 28.000 temp2_max: 80.000 temp2_crit: 100.000 temp2_crit_alarm: 0.000 Core 1: temp3_input: 27.000 temp3_max: 80.000 temp3_crit: 100.000 temp3_crit_alarm: 0.000 Core 2: temp4_input: 31.000 temp4_max: 80.000 temp4_crit: 100.000 temp4_crit_alarm: 0.000 Core 3: temp5_input: 30.000 temp5_max: 80.000 temp5_crit: 100.000 temp5_crit_alarm: 0.000 so can I use this for my sensors.cfg # lines starting with "#" are comments and ignored # sensor configuration chip "nct6775-isa-0290" label temp1 "MB Temp" label temp2 "CPU 1 Temp" label temp3 "CPU 2 Temp" label temp4 "CPU 3 Temp" label temp5 "CPU 4 Temp" Quote Share this post Link to post
JustinChase 3 Posted December 2, 2014 Where can we find more info on how to create the sensors.conf and what it should contain? Check out the Wiki for information on setting up CPU and board temperature sensing here: http://lime-technology.com/wiki/index.php/Setting_up_CPU_and_board_temperature_sensing You'll want to save your sensors.conf file to your flash drive here: /boot/config/sensors.conf Gary Hmmm... root@media:~# sensors No sensors found! Make sure you loaded all the kernel drivers you need. Try sensors-detect to find out which these are. so I did... root@media:~# sensors-detect # sensors-detect revision 6170 (2013-05-20 21:25:22 +0200) # System: # SMBIOS implementations newer than version 2.7 are not # SMBIOS implementations newer than version 2.7 are not [# SMBIOS implementations newer than version 2.7 are not] 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... No AMD Family 15h power sensors... No AMD Family 16h power sensors... No Intel digital thermal sensor... Success! (driver `coretemp') 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'... Yes Found unknown chip with ID 0xc803 (logical device B 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): 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 Found unknown SMBus adapter 8086:8ca2 at 0000:00:1f.3. Sorry, no supported PCI bus adapters found. Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `coretemp': * Chip `Intel digital thermal sensor' (confidence: 9) Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): yes 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. then, I still get... root@media:~# sensors No sensors found! Make sure you loaded all the kernel drivers you need. Try sensors-detect to find out which these are. This is on an ASRock Z97 Extreme6 motherboard. I see temps and fans speeds in BIOS, just not in putty/console. Quote Share this post Link to post
GHunter 9 Posted December 2, 2014 I'm still not sure what my sensors are? eroz, try this for your sensors.conf file and save on your flash drive. Since you are returning results from sensors -u coretemp-isa-0000, I am pretty sure it will work. /boot/config/sensors.conf # sensor configuration chip "coretemp-isa-0000" label temp1 "MB Temp" label temp2 "CPU Temp" Don't forget to add modprobe coretemp in your go file. Hope that helps, Gary Quote Share this post Link to post
GHunter 9 Posted December 2, 2014 JustinChase, I pretty much have the same board as you and get the same results from sensors-detect so you can use my sensors.conf file above below too. Here is my /boot/config/sensors.conf file: # sensor configuration chip "coretemp-isa-0000" label temp1 "MB Temp" label temp2 "CPU Temp" Don't forget to add modprobe coretemp in your go file. Gary Quote Share this post Link to post
JustinChase 3 Posted December 2, 2014 JustinChase, I pretty much have the same board as you and get the same results from sensors-detect so you can use my sensors.conf file above below too. Here is my /boot/config/sensors.conf file: # sensor configuration chip "coretemp-isa-0000" label temp1 "MB Temp" label temp2 "CPU Temp" Don't forget to add modprobe coretemp in your go file. Gary Thanks for the help. I created a /boot/config/sensors.conf file and added only the lines quoted above. I then added "modprobe coretemp" (without quotes) to my go file. I have not rebooted, but I did run modprobe coretemp in putty, but still no temps. I'll reboot soon, just wanted to confirm I did it right before rebooting. #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & echo 192.168.20.150 media >>/etc/hosts /usr/local/sbin/vfio-bind 0000:01:00.0 0000:01:00.1 0000:07:00.0 /boot/config/plugins/snap/snap.sh -m snapdisk modprobe coretemp Quote Share this post Link to post
trurl 662 Posted December 2, 2014 JustinChase, I pretty much have the same board as you and get the same results from sensors-detect so you can use my sensors.conf file above below too. Here is my /boot/config/sensors.conf file: # sensor configuration chip "coretemp-isa-0000" label temp1 "MB Temp" label temp2 "CPU Temp" Don't forget to add modprobe coretemp in your go file. Gary Thanks for the help. I created a /boot/config/sensors.conf file and added only the lines quoted above. I then added "modprobe coretemp" (without quotes) to my go file. I have not rebooted, but I did run modprobe coretemp in putty, but still no temps. I'll reboot soon, just wanted to confirm I did it right before rebooting. #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & echo 192.168.20.150 media >>/etc/hosts /usr/local/sbin/vfio-bind 0000:01:00.0 0000:01:00.1 0000:07:00.0 /boot/config/plugins/snap/snap.sh -m snapdisk modprobe coretemp I think if you remove and then re-install the plugin it should work for you now. Did for me anyway. Quote Share this post Link to post
JustinChase 3 Posted December 2, 2014 I think if you remove and then re-install the plugin it should work for you now. Did for me anyway. That seems to have worked, thanks! Both temps show 117; not sure if that's right. I'd expect them to be at least a little different. ** I refreshed a few times, and now they are different. Any way to know which is which? There are no labels. Quote Share this post Link to post
sacretagent 0 Posted December 2, 2014 bonienl, is the powerdown package installed with dynamix? i thought it was before.. just want to make sure.... Quote Share this post Link to post
