OS6 now works on x86 Legacy WARNING: NO NTGR SUPPORT!

No, legacy add-ons are not supported. The new OS makes use of a new and different SDK.

However you can compile stuff manually or install stuff from the Debian Wheezy repo if you wish.

demetris wrote:

Hello for the Fan problem on Utra 6 you might find useful this: http://pkgs.org/debian-wheezy/debian-ma ... 4.deb.html And you may need these: http://pkgs.org/debian-wheezy/debian-ma ... 4.deb.html http://pkgs.org/debian-wheezy/debian-ma ... l.deb.html http://pkgs.org/debian-wheezy/debian-ma ... 4.deb.html http://pkgs.org/debian-wheezy/debian-ma ... 4.deb.html sudo apt-get purge lm-sensors dpkg -i *.deb etc then #yes "" | sensors-detect

I instaled the lm-sensor package and dependencies on Ultra 2. but after the command : yes "" | sensors-detect, I have the folowing message :

root@NAS:~# yes "" | sensors-detect
# sensors-detect revision 6031 (2012-03-07 17:14:01 +0100)
# System: NETGEAR ReadyNAS [09/08/2010 ReadyNAS-ProUltra2 V1.4]

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): 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
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): Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... Yes
Found `ITE IT8721F/IT8758E Super IO Sensors' Success!
(address 0xa10, driver `it87')
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): # DMI data unavailable, please consider installing dmidecode 2.7
# or later for better results.
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):
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): Using driver `i2c-i801' for device 0000:00:1f.3: Intel 82801G ICH7
Module i2c-i801 loaded successfully.

Next adapter: SMBus I801 adapter at 0400 (i2c-0)
Do you want to scan it? (yes/NO/selectively):
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `it87':
* ISA bus, address 0xa10
Chip `ITE IT8721F/IT8758E Super IO Sensors' (confidence: 9)

Driver `coretemp':
* Chip `Intel digital thermal sensor' (confidence: 9)

Warning: the required module it87 is not currently installed
on your system. If it is built into the kernel then it's OK.
Otherwise, check http://www.lm-sensors.org/wiki/Devices for
driver availability.

Warning: the required module coretemp is not currently installed
on your system. If it is built into the kernel then it's OK.
Otherwise, check http://www.lm-sensors.org/wiki/Devices for
driver availability.

No modules to load, skipping modules configuration.

Unloading i2c-i801... failed

modprobe it87

modprobe coretemp

You will get what modules needed and where to put them /lib/modules/etc/etc/it87.ko
then go get them
BTW Thats why the fan is full speed!
Fix this and you fix the fan speed too

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/

demetris wrote:
I have an answer from TheHijacker: Redoing the project for new NAS sounds great. But first I would need to get the device myself.Together with vpeter

I recognise these names from the XT early days, right?

(Sorry for the off topic.) :D

The kernel has the drivers. Excerpt from dmesg:

coretemp coretemp.0: Unable to read TjMax from CPU.
coretemp coretemp.0: Using relative temperature scale!
coretemp coretemp.0: Unable to read TjMax from CPU.
coretemp coretemp.0: Using relative temperature scale!

it87: Found IT8721F chip at 0xa10, revision 1
it87: in3 is VCC (+5V)
it87: in7 is VCCH (+5V Stand-By)
it87: Ultra 6: 92

Running sensors:

coretemp-isa-0000
Adapter: ISA adapter
Core 0:       +53.0°C  (high = +80.0°C, crit = +100.0°C)
Core 1:       +51.0°C  (high = +80.0°C, crit = +100.0°C)

it8721-isa-0a10
Adapter: ISA adapter
in0:         +12.05 V  (min =  +4.66 V, max =  +6.72 V)  ALARM
in1:          +4.98 V  (min =  +3.77 V, max =  +2.16 V)  ALARM
in2:          +3.27 V  (min =  +4.75 V, max =  +3.09 V)  ALARM
in3:          +0.00 V  (min =  +0.00 V, max =  +0.00 V)
in4:          +1.10 V  (min =  +2.04 V, max =  +2.35 V)  ALARM
in5:          +1.81 V  (min =  +2.58 V, max =  +2.66 V)  ALARM
in6:         -11.87 V  (min = -44.47 V, max = -34.90 V)  ALARM
in7:          +3.24 V  (min =  +4.06 V, max =  +0.77 V)  ALARM
in8:          +3.34 V
fan1:           0 RPM  (min =   54 RPM)  ALARM
fan2:           0 RPM  (min =   40 RPM)  ALARM
fan3:         910 RPM  (min =   18 RPM)
temp1:         +0.0°C  (low  = -31.0°C, high = +17.0°C)  ALARM  sensor = thermistor
temp2:         +0.1°C  (low  = +54.0°C, high = +94.0°C)  sensor = thermal diode
temp3:         +0.1°C  (low  = -40.0°C, high = -14.0°C)  ALARM  sensor = thermal diode
cpu0_vid:    +2.050 V

So for me things seems to be ok, even tough frontview is not reporting correctly. (Ultra 6)

bajorgensen wrote:
So for me things seems to be ok, even tough frontview is not reporting correctly. (Ultra 6)

He has ProUltra2 ;)
Maybe he don’t have them.
So bajorgensen Is your fan fixed now?

InTheShires wrote:
demetris wrote: I have an answer from TheHijacker: Redoing the project for new NAS sounds great. But first I would need to get the device myself.Together with vpeter I recognise these names from the XT early days, right? (Sorry for the off topic.) :D

Exactly on spot!
Xtreamer app installer.
He needs to have the device though so he can debug etc
any old ultra0 donation? ;p
Doesn’t have to be ultra pro etc just anything legacy that can help him work on the app installer.

He has ProUltra2 Maybe he don’t have them. So bajorgensen Is your fan fixed now?

I think it is working as it should 900 rpm is normal operation, 1200 is max.
What is his output from dmesg?

BTW: LCD is also working...

This OS6 thing is annoying me more and more as it looks like a good release... :(

Anyone tried compiling the source yet? I get a missing reference during make menuconfig:

scripts/kconfig/mconf Kconfig
arch/x86/Kconfig.debug:6: can't open file "lib/Kconfig.debug"
make[1]: *** [menuconfig] Error 1
make: *** [menuconfig] Error 2