Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
if you are using DNS-343 and having this problem, please help to test and comment on my fancontrol
***update 4*** improved version, <40°C stop fan, >43°C low fan, >47°C high fan
***update 3*** reduced the time which fan stays on high speed
***update 2*** removed sleep and wait for temperature change event instead
***update 1*** daemonized
-------
minimal fun_plug
http://www.megaupload.com/?d=YJ4MA2E8
fancontrol
http://www.megaupload.com/?d=BEQ8AC2Q
fancontrol.c (the sourcecode if you are interested)
http://www.megaupload.com/?d=8ME3F5CM
-------
http://forums.dlink.com/index.php?topic … 3#msg68223
DNS-343 will (100%) hang / freeze when the fan speed is changed from stop to high
No problem from stop to low, low to high, low to stop, high to low, high to stop
From stop to high is the only case that will hang / freeze the system
if you do the following:
/usr/sbin/fanspeed s; /usr/sbin/fanspeed h
system will hang / freeze and fan will stay on at high
if you do the following
/usr/sbin/fanspeed s; /usr/sbin/fanspeed l; /usr/sbin/fanspeed h
system will continue working
-------
option 1:
leave original fancontrol running and before doing any task send the following command
/usr/sbin/fanspeed l
when the system reaches high temperature, fancontrol will set fan to high and will not freeze the system
when the temperature is low, fancontrol will stop or set the fan to low accordingly
Note: when fan is stopped you must set to low before doing any task, or else when the temperature increases to high, fancontrol will try to set fan to high and system will hang / freeze
option 2:
killall fancontrol
use your own fancontrol script
fancontrol uses fanspeed anyway, so there is not much different if you use your own script
(you can try running fancontrol as a non root user and you will see what I mean)
just remember, if fan is stopped, set to low before setting to high!!!
Last edited by timezlicer (2010-03-15 06:23:17)
Offline
Another way exists.
If somebody not familiar with compilers, but fun_plug (or similiar) toolset installed, you can do:
(instruction for fun_plug)
1. put this script to /ffp/sbin, name it /ffp/sbin/fanspeed.sh
#!/bin/sh case $1 in l) /sys/crfs/sbin/fanspeed l ;; h) /sys/crfs/sbin/fanspeed l /sys/crfs/sbin/fanspeed h ;; s) /sys/crfs/sbin/fanspeed s ;; g) /sys/crfs/sbin/fanspeed g ;; *) /sys/crfs/sbin/fanspeed $1 esac
do command:
chmod a+x /ffp/sbin/fanspeed.sh
Place another script to /ffp/start, name it /ffp/start/systune.sh
#!/bin/sh cp -f /ffp/sbin/fanspeed.sh /tmp/ ln -s -f /tmp/fanspeed.sh /usr/sbin/fanspeed
do command:
chmod a+x /ffp/start/systune.sh
after it - reboot you DNS-343 or do command once:
/ffp/start/systune.sh
--------------------------------------------
Effect of this wrapper script, similiar as timezlicer's executable
--------------------------------------------
Warning!
This code not supported by D-Link, or anybody!
You can use (or not use) it, for you own risk.
Installation of fun_plug or this script can void D-Link warranty
Last edited by Tmorfus (2010-02-25 00:32:16)
Offline
does this fix the dns-343 constant freeze problem?
So the problem is due to the fan speed control component?
edit: ok seems like this is worth a try. I am so sad that dlink is not doing anything to solve this problem.
Is there any way to fix this issue without hacking the firmware?
Last edited by abubin (2010-04-22 10:17:40)
Offline
yes, this is the cause of the hang
if you are uncomfortable using this 'hack', you can email dlink for the beta firmware
the beta firmware does more or less the same thing
http://timezlicer.blogspot.com/2010/03/ … hanks.html
abubin wrote:
does this fix the dns-343 constant freeze problem?
So the problem is due to the fan speed control component?
edit: ok seems like this is worth a try. I am so sad that dlink is not doing anything to solve this problem.
Is there any way to fix this issue without hacking the firmware?
Offline
timezlicer wrote:
if you are using DNS-343 and having this problem, please help to test and comment on my fancontrol
***update 4*** improved version, <40°C stop fan, >43°C low fan, >47°C high fan
***update 3*** reduced the time which fan stays on high speed
***update 2*** removed sleep and wait for temperature change event instead
***update 1*** daemonized
I tried out your replacement for fancontrol, seems to work as advertised. I was able to see it switch between stop, low and high and it appeared to be right on with "temperature g 0" reading.
One question though, any idea how to update the LCD display temp? Mine has been stuck at 44c for a long time, never changes.
Offline
it's OLED not LCD and you can't directly update the temperature readings,
they are written to 3 files (/tmp/temper /tmp/temper_C /tmp/temper_F)
and OLED firmware will read them and display accordingly
try
/usr/sbin/temperature
it reads the current temperature from the sensor and writes to the 3 files
if you still see 44c, maybe it's really 44c inside or your sensor is faulty
my unit is stable at about 44-45c
during idle, fan low/stop every few minutes
caust1c wrote:
if you are using DNS-343 and having this problem, please help to test and comment on my fancontrol
One question though, any idea how to update the LCD display temp? Mine has been stuck at 44c for a long time, never changes.
Offline
Strange, my /tmp/temper etc are updated correctly, it does not seem to be reading on the OLED however. At rest it was at 38c/100f but still showing 44c/111f on the display... Might there be some sort of cron that is updating that stopped running on mine? I have all sorts of reboot issues so I can been up running for a few weeks on this device.
Offline
negative, when you run /usr/sbin/temperature the files in /tmp are updated and OLED should change,
hence i would suspect that you OLED firmware might be having problem
try flashing your firmware again (1.03 or 1.04 beta)
the oled part is flash after the main firmware (after reboot)
maybe your oled firmware didn't get flashed properly that last time
caust1c wrote:
Strange, my /tmp/temper etc are updated correctly, it does not seem to be reading on the OLED however. At rest it was at 38c/100f but still showing 44c/111f on the display... Might there be some sort of cron that is updating that stopped running on mine? I have all sorts of reboot issues so I can been up running for a few weeks on this device.
Offline
Thanks for the advice! Will give it a shot!
Offline
D-LINK has also apparently addressed the issue in a BETA firmware for the DNS-343 (Version 1.04 beta03) which can be downloaded directly from here: ftp://ftp.dlink.com/Multimedia/dns343/B … 3_beta.zip and has the following changes:
Version 1.04 beta03
1. Bugfix : fixed unable to connect to 343 by using Netbios name in ADS mode.
2. Updates UPnP AV Server to support Windows 7 Media Player 12.
3. Device Lockup bugfix : Fan Control : changes design to Off -> Low -> High Speed instead of going from Off -> High when temperature reached the high speed threshold.
4. OLED warning message "DISK IS FULL" can be enabled or disabled by user.
5. Email Alert : allow user to set temperature threshold from 1% to 100%.
6. UPnP AV server bugfix : %20 is used instead of a space on all files and directories.
7. UPnP AV server bugfix : work with mpeg4.
I haven't used the beta firmware yet myself, and am going to try out timezlicer's method first as I have too much data to backup and possibly have to re-initialize my drives after. If anyone does update the firmware, please post your results back -- and let me know if you did indeed need to re-initialize your drives after the upgrade, or if it retained the arrays as they were (doubtful).
I will also post back my experience with timezlicer's fancontrol script.
Last edited by ouija (2011-01-27 22:34:01)
Offline
fyi, d-link's fix is based on my script, the experience should be very similar
nevertheless it's still only a workaround, and after over a year, there is no root cause and permanent fix...
there are some tricks in other post which can overcome the need to reinitialize the drives
good luck and enjoy!
ouija wrote:
I haven't used the beta firmware yet myself, and am going to try out timezlicer's method first as I have too much data to backup and possibly have to re-initialize my drives after. If anyone does update the firmware, please post your results back -- and let me know if you did indeed need to re-initialize your drives after the upgrade, or if it retained the arrays as they were (doubtful).
I will also post back my experience with timezlicer's fancontrol script.
Offline