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
- MACDaHacAspirantThere goes 20GB of pictures ... but it is worth it, OS6 runs on my Ultra 2 :D
Fan is still a bit noisy, because RPM tripled from 4.2.x
it8721-isa-0a10
Adapter: ISA adapter
in0: +0.00 V (min = +0.00 V, max = +0.00 V) ALARM
in1: +4.95 V (min = +4.31 V, max = +0.19 V) ALARM
in2: +0.00 V (min = +0.00 V, max = +0.00 V) ALARM
in3: +0.00 V (min = +0.00 V, max = +0.00 V) ALARM
in4: +3.27 V (min = +2.53 V, max = +1.51 V) ALARM
in5: +1.16 V (min = +0.89 V, max = +1.18 V)
in6: +11.92 V (min = +7.27 V, max = +2.04 V) ALARM
in7: +3.26 V (min = +0.05 V, max = +0.19 V) ALARM
in8: +3.26 V
fan1: 1934 RPM (min = 14 RPM)
fan2: 0 RPM (min = 28 RPM) ALARM
temp1: +0.0°C (low = +66.0°C, high = +2.0°C) ALARM sensor = thermal diode
temp2: +0.0°C (low = -99.0°C, high = -32.0°C) ALARM sensor = thermal diode
temp3: -0.1°C (low = +47.0°C, high = +26.0°C) sensor = disabled
cpu0_vid: +2.050 V
Thx to all that have made this possible.
Greets,
MACDaHac - mwlodarcAspirantHi
I installed 6.0.4 firmware on my ultra4. All work good exept fan. I use manual command to decrease fan speed.
I succeed to install crashplan on my ultra 4 with 6.0.4 firmware.
Now i ll try Royan script to automatically manage fan speed.
brgds
Mathieu - martroyAspirantI've also installed it on my brand new Ultra 4 that I got at a clearance price... At first, I had some problems adding a second drive to create a mirror (2x 2TB WD Red). It was trying to use it as a second volume with no name. I couldn't delete it because of that. I've resolved this by doing a factory reset and copying my stuff back. Now, everything is working fine. I'd really like to have the temp and the fan speed in the GUI but I can live with that for now.
In the meantime, I've adapted Royan's script to run on the Ultra 4 (single CPU, some optimizations, etc.). All credits go to him.
As usual, here is the disclaimer :
I'm not responsible of any damages caused by this script...
So, here it is :
#!/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/pwm1" # pwm file
# misc
dt=$(date +"%F %R") # get timestamp for logging
email_address="<your_email_address>"
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
fan=$(echo ${list[14]} | cut -f2 -d' ') # sensors fan speed
fan_min=$(echo ${list[14]} | cut -f7 -d' ') # sensors minimum fan speed
# read pwm values
pwm=$(cat $pwm_file) # pwm value from pwm file
pwm_min=50 # known minimum value
pwm_max=255 # known maximum value
# determine cpu with highest temperature
cpu=0
cpu_name=""
cpu=$cpu0
cpu_name="CPU0"
# 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 < 50)); then
new_pwm=$pwm_min
elif ((cpu > 70)); then
new_pwm=$pwm_max
else
let new_pwm=($cpu-50)*10+50
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 - FireWalkerXAspirantAnyone got any ideas regarding lm-sensors and Ultra 6?
i get the correct rpm for the fans, but i get N/A for the temp of the cpu (atom d510)
anyone knows how to fix the temp reading ?
(Ran 4.2.22 on it, but it was unstable because of bad termal paste, since i dont have any handy, i opted to install 6.0.4 on it with the fans at full speed and that is working flawlessly) - demetrisAspirantI always replace thermal paste with MX4 and note the day/month/year after 8 years i will be back if the machine still functions :D
- FireWalkerXAspirantHeh, exactly the same stuff from arctic cooling that ive used :-p (just dont let any fish near it) ;-)
- but anyway, it didnt fix the "suddenly the box doesnt respond" problem it keeps freezing, it did so on 4.2.22 as well, so its not a termal problem, maybe its a memory problem... ill have to run a mem test on the unit and see if that helps... or if anyone else has some ideas, im all ears :-) - glemAspirantHi to all,
Here is how to fix fan and temperature issues with OS 6.0 on legacy systems :
Fan and temperature controls are operational, but reports to GUI are false as well
NO WARRANTY / NO SUPPORT !!!
..with root access, execute the following commands:
apt-get update && apt-get upgrade
apt-get install lm-sensors fancontrol
yes "" | sensors-detect
sensors .......(to see your sensors values)
..give values to fan control
echo "#fancontrol" > /etc/fancontrol
pwmconfig
....... give answers to following tests / questions and give values to fan control
....... set interval to 5 seconds
....... save config file
..and now start fancontrol daemon (it will start automaticaly after reboot)
/etc/init.d/fancontrol stop
/etc/init.d/fancontrol start
...... enjoy your new silence !!!!
..use >> sensors << command to validate your values and fan RPM
..if you want to change pwmconfig values, you have to stop fancontrol daemon
pwmconfig ............or update values directly in file /etc/fancontrol
....... and so on
/etc/init.d/fancontrol stop
/etc/init.d/fancontrol start
Tested on Ultra6 model.
For example, values for Ultra6 model are ( /etc/fancontrol file ):
# Configuration file generated by pwmconfig, changes will be lost
INTERVAL=5
DEVPATH=hwmon0=devices/platform/coretemp.0 hwmon1=devices/platform/it87.2576
DEVNAME=hwmon0=coretemp hwmon1=it8721
FCTEMPS= hwmon1/device/pwm3=hwmon0/device/temp2_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=255 - pywongAspirant
glem wrote: Hi to all,
Here is how to fix the fan issue with OS 6.0 on legacy systems :
Fan control is operational, but reports to GUI are false as well
WITH NO WARANTY !!!
with root access, execute the following commands:
echo "#fancontrol" > /etc/fancontrol
apt-get install lm-sensors fancontrol
yes "" | sensors-detect
sensors (to see your sensors values)
pwmconfig
....... ask to following answers & tests & give values to fan control
....... set interval to 5 seconds
....... save config file
and now start fancontrol daemon (it will start automaticaly after reboot)
/etc/init.d/fancontrol start
...... enjoy your new silence !!!!
use sensors command to validate your values and fan RPM
if you want to change pwmconfig values, you have to stop fancontrol daemon
/etc/init.d/fancontrol stop
pwmconfig
....... and so on
Tested on Ultra6 model.
For example, values for Ultra6 model are (fancontrol file):
# Configuration file generated by pwmconfig, changes will be lost
INTERVAL=5
DEVPATH=hwmon0=devices/platform/coretemp.0 hwmon1=devices/platform/it87.2576
DEVNAME=hwmon0=coretemp hwmon1=it8721
FCTEMPS= hwmon1/device/pwm3=hwmon0/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
Does this control both the CPU and System fan?
Does the LCD screen turn off once raid initialization is complete?
Also has anyone figured out how to do dual redundancy with X-RAID2?
Thanks, - glemAspirantAll fans controled by pwmconfig are monitored by fancontrol.
For me, on Ultra6 model, LCD works fine, it turns off/on and displays infos as on 4.2.xx version
if it's wrong for you, you can try >> apt-get install lcdproc
I've just tested with two disks in XRAID2, I have no experience about dual redondancy on OS 6.0 - pywongAspirantI tried OS 6.0 last month but I couldn't find the dual redundancy option, I only could find RAID6.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!