Re: temps not being picked up by gkrellm

MillTek <[email protected]>
Newsgroups gmane.comp.gnome.apps.gkrellm
Message-ID <[email protected]>
Bill WIlson wrote:
> On Tue, 02 Jan 2007 14:24:39 -0600
> MillTek <[email protected]> wrote:
>
>   
>> Installing 2.2.10 worked.  IS there a way to pick up the fan speeds from 
>> the BIOS??
>>     
>
> Great!  Fan speeds come from the kernel driver and there's no
> interface to the BIOS.  Are you not getting fan speeds?  If not
> get -d 0x80 sensors debug output again.  If the debug output says
> gkrellm is using libsensors (the default), you can try reading
> directly from the kernel sysfs to see if it makes a difference
> by running:  gkrellm --without-libsensors
>
> Bill
>   
Hi Bill,

Still don't get an actual temp from the drive nor fan speeds.

Here's my hdparm;

 hdparm -I /dev/sda

/dev/sda:

ATA device, with non-removable media
        Model Number:       MAXTOR STM3320620AS                  
        Serial Number:      3QF0VX1F
        Firmware Revision:  3.AAE  
Standards:
        Supported: 7 6 5 4
        Likely used: 7
Configuration:
        Logical         max     current
        cylinders       16383   16383
        heads           16      16
        sectors/track   63      63
        --
        CHS current addressable sectors:   16514064
        LBA    user addressable sectors:  268435455
        LBA48  user addressable sectors:  625142448
        device size with M = 1024*1024:      305245 MBytes
        device size with M = 1000*1000:      320072 MBytes (320 GB)
Capabilities:
        LBA, IORDY(can be disabled)
        Queue depth: 32
        Standby timer values: spec'd by Standard, no device specific minimum
        R/W multiple sector transfer: Max = 16  Current = 16
        Recommended acoustic management value: 254, current value: 0
        DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
             Cycle time: min=120ns recommended=120ns
        PIO: pio0 pio1 pio2 pio3 pio4
             Cycle time: no flow control=120ns  IORDY flow control=120ns
Commands/features:
        Enabled Supported:
           *    SMART feature set
                Security Mode feature set
           *    Power Management feature set
           *    Write cache
           *    Look-ahead
           *    Host Protected Area feature set
           *    WRITE_BUFFER command
           *    READ_BUFFER command
           *    DOWNLOAD_MICROCODE
                SET_MAX security extension
           *    48-bit Address feature set
           *    Device Configuration Overlay feature set
           *    Mandatory FLUSH_CACHE
           *    FLUSH_CACHE_EXT
           *    SMART error logging
           *    SMART self-test
           *    General Purpose Logging feature set
           *    SATA-I signaling speed (1.5Gb/s)
           *    Native Command Queueing (NCQ)
           *    Phy event counters
                Device-initiated interface power management
           *    Software settings preservation
Security:
        Master password revision code = 65534
                supported
        not     enabled
        not     locked
                frozen
        not     expired: security count
        not     supported: enhanced erase
Checksum: correct



Here's the output from the debug;


 gkrellm -d 0x80
--- GKrellM 2.2.10 ---
hddtemp_daemon_read (once a minute):
        |/dev/sda|MAXTOR STM3320620AS|UNK|*|
libsensors: init OK
k8temp:/sys/devices/pci0000:00/0000:00:18.3 k8temp@c3/temp1 c3fffb
k8temp:/sys/devices/pci0000:00/0000:00:18.3 k8temp@c3/temp2 c3fffb
k8temp:/sys/devices/pci0000:00/0000:00:18.3 k8temp@c3/temp3 c3fffb
k8temp:/sys/devices/pci0000:00/0000:00:18.3 k8temp@c3/temp4 c3fffb
load_sensors_config: <sensor_config_version> <1>
load_sensors_config: <sensor_sysdep_private> <1>
load_sensors_config: <sensor_float_factor> <10000>
load_sensors_config: <gkrellm_float_factor> <1000>
load_sensors_config: <"GPU> <TEMP" "nVidia GPU Core" 10000 0 1 0>
load_sensors_config: <"CPU"> <"k8temp-hwmon0/temp1" 10000 0 1 0>
migrate name hwmon->libsensors: k8temp-hwmon0/temp1 -> k8temp@c3/temp1
load_sensors_config: <"Via> <Chip" "k8temp-hwmon0/temp3" 10000 0 1 0>
migrate name hwmon->libsensors: k8temp-hwmon0/temp3 -> k8temp@c3/temp3
load_sensors_config: <"sda"> <"hddtemp/sda" 10000 0 1 0>
load_sensors_config: <units_fahrenheit> <0>
load_sensors_config: <volt_display_mode> <0>
sensor_temp: GPU TEMP GPUCoreTemp t=44.00
sensor_temp: CPU k8temp:/sys/devices/pci0000:00/0000:00:18.3 t=25.00
sensor_temp: Via Chip k8temp:/sys/devices/pci0000:00/0000:00:18.3 t=26.00
sensor_temp: sda /dev/sda t=0.00
sensor_temp: GPU TEMP GPUCoreTemp t=44.00
sensor_temp: CPU k8temp:/sys/devices/pci0000:00/0000:00:18.3 t=25.00
sensor_temp: Via Chip k8temp:/sys/devices/pci0000:00/0000:00:18.3 t=26.00
sensor_temp: sda /dev/sda t=0.00
hddtemp_daemon_read (once a minute):
        |/dev/sda|MAXTOR STM3320620AS|UNK|*|
sensor_temp: GPU TEMP GPUCoreTemp t=44.00
sensor_temp: CPU k8temp:/sys/devices/pci0000:00/0000:00:18.3 t=25.00
sensor_temp: Via Chip k8temp:/sys/devices/pci0000:00/0000:00:18.3 t=26.00
sensor_temp: sda /dev/sda t=0.00
sensor_temp: GPU TEMP GPUCoreTemp t=44.00
sensor_temp: CPU k8temp:/sys/devices/pci0000:00/0000:00:18.3 t=26.00
sensor_temp: Via Chip k8temp:/sys/devices/pci0000:00/0000:00:18.3 t=25.00
sensor_temp: sda /dev/sda t=0.00
sensor_temp: GPU TEMP GPUCoreTemp t=44.00
sensor_temp: CPU k8temp:/sys/devices/pci0000:00/0000:00:18.3 t=25.00
sensor_temp: Via Chip k8temp:/sys/devices/pci0000:00/0000:00:18.3 t=25.00
sensor_temp: sda /dev/sda t=0.00
sensor_temp: GPU TEMP GPUCoreTemp t=44.00
sensor_temp: CPU k8temp:/sys/devices/pci0000:00/0000:00:18.3 t=25.00
sensor_temp: Via Chip k8temp:/sys/devices/pci0000:00/0000:00:18.3 t=25.00
sensor_temp: sda /dev/sda t=0.00

When I run gkrellm --without-libsensors I still don't get the fan speeds.



Thanks

Jim

_______________________________________________
Gkrellm mailing list
[email protected]
http://lists.jutley.org/cgi-bin/mailman/listinfo/gkrellm
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.