risparmio energetico. tipo RMClock!

[TrunksSsj]

ciao raga sul mio nuovo muletto volevo mettere un processore decente come l'amd 4450e per avere power on demand quando mi serve, altrimenti quiete e consumo irrisorio. volevo però mettere linux come SO. qualcuno mi sa dire come eseguire i fantastici "magheggi" di RMClock x win anke su linux? ho sentito parlare di cpufreq ma non so molto... io vorrei cmq creare dei profili intermedi per i vari moltiplicatori del processore e, soprattutto, poter abbassare il VCore del processore. grazie davvero tantissimo a chi può aiutarmi!:rolleyes:

ps: credo monterò una debian

[Exeba]

Per quanto riguarda la gestione delle frequenze penso non ci siano problemi, tutti i processori che hanno queste funzionalità sono ben supportati in linux.

Il problema potrebbe sorgere con il Vcore; a meno che tu non sia in grado di regolare questo parametro dal bios non credo che per gli amd sia possibile agire via software su linux (almeno fino a qualche tempo fa era così)

[massi_it]

Il problema potrebbe sorgere con il Vcore; a meno che tu non sia in grado di regolare questo parametro dal bios non credo che per gli amd sia possibile agire via software su linux (almeno fino a qualche tempo fa era così)

io uso kpowersave per gestire le frequenze, ma in particolare per il vcore, su un centrino 1,60ghz, ho usato questa soluzione (http://ubuntuforums.org/showthread.php?t=726932) anche se, in quanto profondamente noob, non so se esattamente ho fatto la cosa giusta....

come posso monitorare il valore di vcore sul pinguino?

[Devil!]

come posso monitorare il valore di vcore sul pinguino?

lm-sensors

es:

server:~#sensors
w83627dhg-isa-0290
Adapter: ISA adapter
VCore: +1.20 V (min = +0.00 V, max = +1.74 V)
in1: +11.99 V (min = +3.64 V, max = +0.37 V) ALARM
AVCC: +3.44 V (min = +0.10 V, max = +3.20 V) ALARM
3VCC: +3.44 V (min = +3.84 V, max = +3.26 V) ALARM
in4: +1.80 V (min = +1.86 V, max = +0.04 V) ALARM
in5: +0.09 V (min = +0.20 V, max = +0.06 V) ALARM
in6: +5.12 V (min = +1.84 V, max = +0.15 V) ALARM
VSB: +3.26 V (min = +0.14 V, max = +1.47 V) ALARM
VBAT: +3.15 V (min = +0.03 V, max = +0.85 V) ALARM
Case Fan: 0 RPM (min = 2636 RPM, div = 128) ALARM
CPU Fan: 4821 RPM (min = 1670 RPM, div = 8)
Aux Fan: 0 RPM (min = 703 RPM, div = 128) ALARM
fan4: 0 RPM (min = 10546 RPM, div = 128) ALARM
Sys Temp: +41.0°C (high = +68.0°C, hyst = +48.0°C) sensor = thermistor
CPU Temp: +34.0°C (high = +127.0°C, hyst = +75.0°C) sensor = diode
AUX Temp: +16.0°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor
cpu0_vid: +0.000 V

coretemp-isa-0000
Adapter: ISA adapter
Core 0: +32.0°C (crit = +100.0°C)

[massi_it]

lm-sensors

es:

ho omesso di dire che sul mio centrino 1.60ghz (un portatile Acer Aspire 1682 WLmi) lm-sensors non funge :( :( :(

massi@massi-laptop:~$ sensors
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.



massi@massi-laptop:~$ sudo sensors-detect
[sudo] password for massi:
# sensors-detect revision 5016 (2007-11-11 22:20:16 +0100)

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.

We can start with probing for (PCI) I2C or SMBus adapters.
Do you want to probe now? (YES/no):
Probing for PCI bus adapters...
Use driver `i2c-i801' for device 0000:00:1f.3: Intel 82801DB ICH4

We will now try to load each adapter module in turn.
Load `i2c-i801' (say NO if built into your kernel)? (YES/no):
Module loaded successfully.
If you have undetectable or unsupported adapters, you can have them
scanned by manually loading the modules before running this script.

To continue, we need module `i2c-dev' to be loaded.
Do you want to load `i2c-dev' now? (YES/no):
Module loaded successfully.

We are now going to do the I2C/SMBus adapter probings. Some chips may
be double detected; we choose the one with the highest confidence
value in that case.
If you found that the adapter hung after probing a certain address,
you can specify that address to remain unprobed.

Next adapter: SMBus I801 adapter at 1880 (i2c-0)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x50
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'... No
Client found at address 0x51
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'... No

Some chips are also 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):
Probing for `National Semiconductor LM78' at 0x290... No
Probing for `National Semiconductor LM78-J' at 0x290... No
Probing for `National Semiconductor LM79' at 0x290... No
Probing for `Winbond W83781D' at 0x290... No
Probing for `Winbond W83782D' at 0x290... No
Probing for `Silicon Integrated Systems SIS5595'... No
Probing for `VIA VT82C686 Integrated Sensors'... No
Probing for `VIA VT8231 Integrated Sensors'... No
Probing for `IPMI BMC KCS' at 0xca0... No
Probing for `IPMI BMC SMIC' at 0xca8... No

Some Super I/O chips may also contain 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'... Yes
Found `Nat. Semi. PC87591 Super IO'
(but not activated)
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No
Trying family `ITE'... No

Some CPUs or memory controllers may also contain embedded sensors.
Do you want to scan for them? (YES/no):
AMD K8 thermal sensors... No
AMD K10 thermal sensors... No
Intel Core family thermal sensor... No
Intel AMB FB-DIMM thermal sensor... No

Sorry, no sensors were detected.
Either your sensors are not supported, or they are connected to an
I2C or SMBus adapter that is not supported. See doc/FAQ,
doc/lm_sensors-FAQ.html or http://www.lm-sensors.org/wiki/FAQ
(FAQ #4.24.3) for further information.
If you find out what chips are on your board, check
http://www.lm-sensors.org/wiki/Devices for driver status.



pare non sia supportato...
non c'è un workaround?

[TrunksSsj]

uhm forse dico una ca**ata immensa: ma far girare rmclock (nel mio caso) o HWMonitor (x massi_it) col wine???