NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
More on CPU specs of the ReadyNAS Pro
Hi all, Does anyone know what FSB speeds the ReadyNAS Pro motherboard supports. I have three "servers" that I'm trying to consolidate. I figured that the file server (which is actually the slowe...
Hi everybody,
I couldn't resist and went and bought the Q6700 for my readynas Pro Pioneer. However, installing it wasn't as straightforward as I thought. Once installed, the system started sending out scary alarms like:
DDB18 power is out of normal range [expected: 1.80 current: -0.00].
AVCC power is out of normal range [expected: 3.30 current: -0.00].
VCC3 power is out of normal range [expected: 3.30 current: -0.00].
VCC1_25 power is out of normal range [expected: 1.25 current: -0.00].
VCC1_5 power is out of normal range [expected: 1.50 current: -0.00].
VCC1_05 power is out of normal range [expected: 1.04 current: -0.00].
3VDUAL power is out of normal range [expected: 3.30 current: -0.00].
VBAT power is out of normal range [expected: 3.30 current: -0.00].
However, the CPU seemed to be running fine. After some research I traced the cause to the /frontview/conf/enclosure.db file. Fortunately this file is a sqlite DB, which I could modify. To make a long story short, you have to change the paths where the system looks for voltage and temp data from /sys/class/hwmon/hwmon2 (which assumes a dual core CPU) to /sys/class/hwmon/hwmon4 (which assumes a quad core CPU).
I wonder if the people that tried quad core CPUs before ran into this too? Maybe this format was introduced recently? I'm running Radiator 4.2.21
I know it's too much to ask but maybe netgear can make this conf more CPU independent in later releases?
I couldn't resist and went and bought the Q6700 for my readynas Pro Pioneer. However, installing it wasn't as straightforward as I thought. Once installed, the system started sending out scary alarms like:
DDB18 power is out of normal range [expected: 1.80 current: -0.00].
AVCC power is out of normal range [expected: 3.30 current: -0.00].
VCC3 power is out of normal range [expected: 3.30 current: -0.00].
VCC1_25 power is out of normal range [expected: 1.25 current: -0.00].
VCC1_5 power is out of normal range [expected: 1.50 current: -0.00].
VCC1_05 power is out of normal range [expected: 1.04 current: -0.00].
3VDUAL power is out of normal range [expected: 3.30 current: -0.00].
VBAT power is out of normal range [expected: 3.30 current: -0.00].
However, the CPU seemed to be running fine. After some research I traced the cause to the /frontview/conf/enclosure.db file. Fortunately this file is a sqlite DB, which I could modify. To make a long story short, you have to change the paths where the system looks for voltage and temp data from /sys/class/hwmon/hwmon2 (which assumes a dual core CPU) to /sys/class/hwmon/hwmon4 (which assumes a quad core CPU).
I wonder if the people that tried quad core CPUs before ran into this too? Maybe this format was introduced recently? I'm running Radiator 4.2.21
I know it's too much to ask but maybe netgear can make this conf more CPU independent in later releases?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
