NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
AMRivlin
Mar 21, 2013Apprentice
OS6 now works on x86 Legacy WARNING: NO NTGR SUPPORT!
Update: It is now unofficially possible using NTGR images to update legacy hardware to os6.X
See Post #3, for directions to install 6.2.1 on x86 Ultra and Pro Models. (ARM NOT SUPPORTED by this OS)
Be forewarned, this requires a SYSTEM WIPE and likely voids any warranty support from NTGR
Supported so far: pro 2/4/6, ultra 2/4/6, old pro / Pioneer Pro, 2100v2
Not Supported: NVX and 2100v1
Thanks go out to "HomeBrew Anonymous" for making this possible.
Update 2: A firmware image to downgrade back to 4.2.26 is now available. See this thread. While this downgrade should get you a working system again on the supported firmware, be forewarned this requires a SYSTEM WIPE and NetGear also does not provide support for this downgrade. If you have issues seek help on these forums.
Original Post/Gripes
I have been reading these forums since Monday's announcement and there has been a resounding "ooof" regarding the fact the Ultras and Pros are unsupported for future OS improvements.
To clear the air: it would appear Netgear will never support os6 on past hardware. I have almost come to grips with this, and at least they have been open and honest with their forward direction and aren't stringing us along. viewtopic.php?f=138&t=70131
The upside is our devices still work and are mostly stable and eventually we can upgrade to a new shell that has os6 support, but in the meantime our $500-1000 investment is unable to take advantage of modern features we all desire.
I don't think I can add a poll here at RN forums, but I would like to garner support for a 100% unsupported home brew of the os6 on Pro6 units.
If we get enough support perhaps a talented member(s) here would help release a homebrew of sorts.
The 3 main caveats are:
1. Netgear will never be held responsible/your warranty is void
2. A format is required (new FS and OS)
3. Data loss is highly possible
If you are still interested please post a reply to this thread.
mdgm and I have decided that its time to lock this thread. So please do post any new OS6 on Legacy issues on their own threads.
1,274 Replies
Replies have been turned off for this discussion
- glemAspirant
pywong wrote :
I install fancontrol and did a reboot but it does not work right.
You must not define a very low temperature, otherwise fan run already loud to decrease temperature, and it cannot do this. For example, I think 20°C is too low for system temperature. MINTEMP parameter would be the optimal temp read by the sensor, id normal running temp.
This is the same thing for fan rpm : define MINSTART, MINSTOP, MINPWM as the same value, the optimal value correspond to the lowest realistic rpm value you want to have in normal running.
For example on Ultra6, minimal system temperature would be around 37°C, minimal CPU temp around 51°C, minimal system fan 900 rpm (may be higher on pro6).
Do you remember temp and rpm values with 4.2.xx ? they are the best ones. - pywongAspirantI got fancontrol working, Thanks for the tip.
Here's what I used:
INTERVAL=10
DEVPATH=hwmon0=devices/platform/coretemp.0 hwmon1=devices/platform/w83627ehf.2576
DEVNAME=hwmon0=coretemp hwmon1=w83627dhg
FCTEMPS= hwmon1/device/pwm2=hwmon1/device/temp2_input hwmon1/device/pwm1=hwmon1/device/temp1_input
FCFANS= hwmon1/device/pwm2=hwmon1/device/fan2_input hwmon1/device/pwm1=hwmon1/device/fan1_input
MINTEMP= hwmon1/device/pwm2=30 hwmon1/device/pwm1=55
MAXTEMP= hwmon1/device/pwm2=60 hwmon1/device/pwm1=60
MINSTART= hwmon1/device/pwm2=70 hwmon1/device/pwm1=16
MINSTOP= hwmon1/device/pwm2=70 hwmon1/device/pwm1=16
MINPWM= hwmon1/device/pwm2=70 hwmon1/device/pwm1=16
MAXPWM= hwmon1/device/pwm2=200 hwmon1/device/pwm1=80
I'm still having problems with the LCD screen, how can I use lcdproc to make the LCD screen work?
Thanks - chirpaLuminary
demetris wrote: I would install weezy somewhere and get them from that if you cant find them online.
Also put them here for others to use ;).
it87.ko (The fan sensor driver) ;)
coretemp.ko (the cpu sensor driver)
Or you can try these :D
http://www.multiupload.nl/YE7X1LRF8M
Place them in example given:
/lib/modules/3.0.0-generic/kernel/drivers/hwmon/
Owned by root
example with scp utility
scp -r *.ko root@192.168.1.209:/lib/modules/3.0.70.RNx86_64.2.1/kernel/drivers/hwmon/
Link doesn't work anymore. - BadButtonAspirant
chirpa wrote: demetris wrote: I would install weezy somewhere and get them from that if you cant find them online.
Also put them here for others to use ;).
it87.ko (The fan sensor driver) ;)
coretemp.ko (the cpu sensor driver)
Or you can try these :D
http://www.multiupload.nl/YE7X1LRF8M
Place them in example given:
/lib/modules/3.0.0-generic/kernel/drivers/hwmon/
Owned by root
example with scp utility
scp -r *.ko root@192.168.1.209:/lib/modules/3.0.70.RNx86_64.2.1/kernel/drivers/hwmon/
Link doesn't work anymore.
Linux noob here. Since the links for the Fancontrol drivers are dead. Ive been trying to find another copy of thoes drivers all over the internet, but sadly unable to find them. I however think i found their source code.
Coretemp--Here http://lxr.free-electrons.com/source/drivers/hwmon/coretemp.c?v=2.6.32
IT8721F/IT8758E --- Here http://khali.linux-fr.org/devel/misc/it87/
Question is how in the world do i get these files to compile/install? Ive tried make but i get an error stating "nothing to do here". Can this source code be compiled? Does anyone have a copy the readynas fan control drivers?
Untill thoes drivers are found im afraid this project is a dead end for me. :( - BadButtonAspirantThanks Spiderman!
Only issue is when i try to install the modules i get an error:
insmod: can't insert 'it87.ko': invalid module format same with coretemp - demetrisAspirantThey were from an ubuntu 12.04 OS. You guys have to find a matchable pair for Debian Wheezy.
- sventunusAspirant
demetris wrote: They were from an ubuntu 12.04 OS. You guys have to find a matchable pair for Debian Wheezy.
Nope.
"Us guys" [ReadyNAS Ultra 6] don't need to install any modules, they're available in the kernel (I'm on an Ultra 6).
Check dmesg | grep coretemp it87, the modules are there.
What you need to do first is the following:
apt-get update && apt-get -y upgrade
apt-get install lm-sensors fancontrol
Then edit /etc/fancontrol via vi or nano or whatever to be as such:INTERVAL=5
DEVPATH=hwmon0=devices/platform/coretemp.0 hwmon1=devices/platform/it87.2576
DEVNAME=hwmon0=coretemp hwmon1=it8721
FCTEMPS= hwmon1/device/pwm3=hwmon1/device/temp3_input
FCFANS= hwmon1/device/pwm3=hwmon1/device/fan3_input
MINTEMP= hwmon1/device/pwm3=51
MAXTEMP= hwmon1/device/pwm3=58
MINSTART= hwmon1/device/pwm3=40
MINSTOP= hwmon1/device/pwm3=40
MINPWM= hwmon1/device/pwm3=40
MAXPWM= hwmon1/device/pwm3=150
Then:reboot
Then, create & chmod 755 a file called /bin/fan-monitor with the following contents:#!/bin/bash
# log and send mail
function sendmail {
( echo "To:$email_address"
echo "From:$email_address"
echo "Subject:$host: temp-monitor: $1"
echo
echo "$2" ) | /usr/sbin/sendmail -t --read-envelope-from
echo $message >> $log
}
# files
lock="/tmp/.fan-monitor.lock" # lock file (needed?)
log="/var/log/fan-monitor.log" # log file
pwm_file="/sys/devices/platform/it87.2576/pwm3" # pwm file
# misc
dt=$(date +"%F %R") # get timestamp for logging
email_address="<your_email>"
host=`hostname`
# superuser check
if [[ $EUID -ne 0 ]]; then # check if process is running as superuser
echo $dt "This script must be run as root" >> $log # need su to write pwm file
exit 10
fi
# check for lock
[ -f "$lock" ] && exit # exit if another instance of this script
>$lock # is writing to pwm file (not nessesary?)
# get output from sensors into an array
OLDIFS="$IFS" # store current IFS
IFS=$'\n' # set IFS to newline
list=(`sensors`) # populate array from sensors output
IFS="$OLDIFS" # restore original IFS
# get values from array
cpu0=$(echo ${list[2]} | cut -f3 -d' ' | grep -P -o "[0-9.]+" | cut -f1 -d'.') # sensors cpu0 temperature
cpu1=$(echo ${list[3]} | cut -f3 -d' ' | grep -P -o "[0-9.]+" | cut -f1 -d'.') # sensors cpu1 temperature
fan=$(echo ${list[18]} | cut -f3 -d' ') # sensors fan speed
fan_min=$(echo ${list[18]} | cut -f7 -d' ') # sensors minimum fan speed
# read pwm values
pwm=$(cat $pwm_file) # pwm value from pwm file
pwm_min=40 # known minimum value
pwm_max=255 # known maximum value
# determine cpu with highest temperature
cpu=0
cpu_name=""
if ((cpu0 >= cpu1))
then
cpu=$cpu0
cpu_name="CPU0"
else
cpu=$cpu1
cpu_name="CPU1"
fi
# verify cpu test has returned a value
if ((cpu == 0)); then
message="$dt: CPU test failed, cpu0: $cpu0, cpu1: $cpu1"
sendmail "ERROR" "$message"
rm -f $lock # cleanup lock
exit 11 # exit error code
fi
# set the new pwm value for the fan speed.
if ((cpu < 40)); then
new_pwm=$pwm_min
elif ((cpu > 70)); then
new_pwm=$pwm_max
else
let new_pwm=($cpu-40)*10+40
fi
# check new pwm value
if ((new_pwm == 0)); then # no new pwm value = no need to do anything
echo "$dt: OK: $cpu_name: $cpu, pwm: $pwm" >> $log # log ok status if you want to keep track of what's
happening
rm -f $lock # cleanup locks
exit 0 # exit with ok status
fi
# don't resend emails if there is no change from previous run
if ((new_pwm != pwm)); then
# ok, now we have a new pwm value and need to set it
command_out=$( `echo $new_pwm > $pwm_file` 2>&1 ) # write new pwm value to pwm file, and catch any
output
command_rc=$? # get error codes
uptime=$(echo `uptime`) # get extra data for email
if (( command_rc == 0)); then
# no errors setting pwm.
message="$dt: pwm changed: $pwm -> $new_pwm, $cpu_name temp: $cpu, fan: $fan uptime: $uptime"
sendmail "Fan speed changed" "$message"
else
# oops, we got an error setting new pwm.
message="$dt: ERROR setting pwm: $pwm -> $new_pwm, $cpu_name temp: $cpu, fan: $fan uptime: $uptime -
ERRROR rc: $command_rc, stdout and stderr: $command_out"
sendmail "ERROR" "$message"
fi
fi
#cleanup locks
rm -f $lock
Change <your_email> to your own email address.
And then edit crontab by typingcrontab -e
and adding the following line:* * * * * /bin/fan-monitor > /dev/null
This will monitor the CPU temps for both Atom cores & adjust the fan speeds accordingly (for an Ultra 6) & send email when things get out of hand.
It doesn't make frontview display the correct fan speed though, need to figure out how to do that still.
I've finally come around to updating my RN Ultra 6's FW with 3 weeks delay. It's syncing the array right now, will play with it some more this weekend.
A BIG, ++MEGA++ thank you goes out to all the people who made it possible to run NG's latest FW on our legacy devices!!
You know... those devices that are perfectly capable from a HW POV, but were supposedly not eligible for running this firmware according to Netgear...
Too bad we don't get to post metal-smileys here, but you guys rock! \m/
If anyone might have some tips on how to make frontview report correct fan speeds for an Ultra 6, I'm all ears, thanks! :-) - chirpaLuminary
sventunus wrote: Too bad we don't get to post metal-smileys here, but you guys rock! \m/ 
- sventunusAspirant
chirpa wrote: sventunus wrote: Too bad we don't get to post metal-smileys here, but you guys rock! \m/ 
F this! :D
/** CHECKING SMILEYS NOW...
NOT FINDING THEM **/
// realizing it's too late to realize that chirpa ref'd an external url & feeling dumbass :-/
// 1AM here to excuse myself ;-)
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!