* [lm-sensors] no sensors were detected with Intel Corporation 82801H
@ 2007-11-09 0:06 Kessia Pinheiro
2007-11-14 17:45 ` [lm-sensors] no sensors were detected with Intel Corporation Juerg Haefliger
` (16 more replies)
0 siblings, 17 replies; 18+ messages in thread
From: Kessia Pinheiro @ 2007-11-09 0:06 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 7901 bytes --]
Hi folks,
I'm using ubuntu gutsy in dell vostro 1400 laptop. I try run sensors-detect,
but this dont recognize my sensors. Below is my configs. thanks:
--------------------------------------------------------------------------------------------------------------
lspci output:
00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory
Controller Hub (rev 0c)
00:01.0 PCI bridge: Intel Corporation Mobile PM965/GM965/GL960 PCI Express
Root Port (rev 0c)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI
Contoller #4 (rev 02)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI
Controller #5 (rev 02)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI
Controller #2 (rev 02)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio
Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port
1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port
2 (rev 02)
00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port
4 (rev 02)
00:1c.5 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port
6 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI
Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI
Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI
Controller #3 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI
Controller #1 (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f2)
00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M) LPC Interface
Controller (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE
Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA
AHCI Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev
02)
01:00.0 VGA compatible controller: nVidia Corporation GeForce 8400M GS (rev
a1)
03:01.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev
05)
03:01.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host
Adapter (rev 22)
03:01.2 System peripheral: Ricoh Co Ltd R5C843 MMC Host Controller (rev 12)
03:01.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter
(rev 12)
03:01.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 12)
09:00.0 Ethernet controller: Broadcom Corporation NetLink BCM5906M Fast
Ethernet PCI Express (rev 02)
0c:00.0 Network controller: Broadcom Corporation BCM4328 802.11a/b/g/n (rev
03)
--------------------------------------------------------------------------------------------------------------
uname -a:
Linux rainbows 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686
GNU/Linux
--------------------------------------------------------------------------------------------------------------
lm-sensors version:
Version: 1:2.10.4-1ubuntu1 (oficial package)
--------------------------------------------------------------------------------------------------------------
sensors-detect output:
# sensors-detect revision 4609 (2007-07-14 09:28:39 -0700)
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 82801H ICH8
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.
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: NVIDIA i2c adapter (i2c-0)
Do you want to scan it? (YES/no/selectively):
Can't open /dev/i2c-0
Next adapter: NVIDIA i2c adapter (i2c-1)
Do you want to scan it? (YES/no/selectively):
Can't open /dev/i2c-1
Next adapter: NVIDIA i2c adapter (i2c-2)
Do you want to scan it? (YES/no/selectively):
Can't open /dev/i2c-2
Next adapter: SMBus I801 adapter at 10c0 (i2c-3)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x44
Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
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 0x52
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'... No
Trying family `SMSC'... Yes
Found unknown chip with ID 0x3201
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
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.
--------------------------------------------------------------------------------------------------------------
--
Kessia Pinheiro
Bacharelanda em Ciência da Computação
Universidade Federal da Bahia
Linux Counter User #389695 [http://counter.li.org]
[-- Attachment #1.2: Type: text/html, Size: 11685 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [lm-sensors] no sensors were detected with Intel Corporation
2007-11-09 0:06 [lm-sensors] no sensors were detected with Intel Corporation 82801H Kessia Pinheiro
@ 2007-11-14 17:45 ` Juerg Haefliger
2007-11-15 17:04 ` Juerg Haefliger
` (15 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: Juerg Haefliger @ 2007-11-14 17:45 UTC (permalink / raw)
To: lm-sensors
Hi Kessia,
> Hi folks,
>
> I'm using ubuntu gutsy in dell vostro 1400 laptop. I try run sensors-detect,
> but this dont recognize my sensors. Below is my configs. thanks:
>
> --------------------------------------------------------------------------------------------------------------
> lspci output:
>
> 00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory
> Controller Hub (rev 0c)
> 00:01.0 PCI bridge: Intel Corporation Mobile PM965/GM965/GL960 PCI Express
> Root Port (rev 0c)
> 00: 1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI
> Contoller #4 (rev 02)
> 00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI
> Controller #5 (rev 02)
> 00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI
> Controller #2 (rev 02)
> 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio
> Controller (rev 02)
> 00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port
> 1 (rev 02)
> 00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port
> 2 (rev 02)
> 00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port
> 4 (rev 02)
> 00:1c.5 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port
> 6 (rev 02)
> 00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI
> Controller #1 (rev 02)
> 00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI
> Controller #2 (rev 02)
> 00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI
> Controller #3 (rev 02)
> 00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI
> Controller #1 (rev 02)
> 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f2)
> 00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M) LPC Interface
> Controller (rev 02)
> 00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE
> Controller (rev 02)
> 00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA
> AHCI Controller (rev 02)
> 00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev
> 02)
> 01:00.0 VGA compatible controller: nVidia Corporation GeForce 8400M GS (rev
> a1)
> 03:01.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev
> 05)
> 03:01.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host
> Adapter (rev 22)
> 03:01.2 System peripheral: Ricoh Co Ltd R5C843 MMC Host Controller (rev 12)
> 03:01.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter
> (rev 12)
> 03:01.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 12)
> 09:00.0 Ethernet controller: Broadcom Corporation NetLink BCM5906M Fast
> Ethernet PCI Express (rev 02)
> 0c:00.0 Network controller: Broadcom Corporation BCM4328 802.11a/b/g/n (rev
> 03)
>
>
> --------------------------------------------------------------------------------------------------------------
> uname -a:
> Linux rainbows 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686
> GNU/Linux
>
>
> --------------------------------------------------------------------------------------------------------------
> lm-sensors version:
> Version: 1:2.10.4-1ubuntu1 (oficial package)
>
> --------------------------------------------------------------------------------------------------------------
> sensors-detect output:
> # sensors-detect revision 4609 (2007-07-14 09:28:39 -0700)
>
> 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 82801H ICH8
>
> 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.
>
> 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: NVIDIA i2c adapter (i2c-0)
> Do you want to scan it? (YES/no/selectively):
> Can't open /dev/i2c-0
>
> Next adapter: NVIDIA i2c adapter (i2c-1)
> Do you want to scan it? (YES/no/selectively):
> Can't open /dev/i2c-1
>
> Next adapter: NVIDIA i2c adapter (i2c-2)
> Do you want to scan it? (YES/no/selectively):
> Can't open /dev/i2c-2
>
> Next adapter: SMBus I801 adapter at 10c0 (i2c-3)
> Do you want to scan it? (YES/no/selectively):
> Client found at address 0x44
> Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
> 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 0x52
> 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'... No
> Trying family `SMSC'... Yes
> Found unknown chip with ID 0x3201
> 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
As sensor-detect says, this chip is unknown. Can you run Speedfan
under windows on this machine? Speedfan might tell us what chip it is
and from that we can try to figure out if it's compatible with
anything that's currently supported.
...juerg
> Some CPUs or memory controllers may also contain embedded sensors.
> Do you want to scan for them? (YES/no):
> AMD K8 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.
>
>
>
> --------------------------------------------------------------------------------------------------------------
>
>
> --
> Kessia Pinheiro
> Bacharelanda em Ciência da Computação
> Universidade Federal da Bahia
> Linux Counter User #389695 [http://counter.li.org]
> _______________________________________________
> lm-sensors mailing list
> lm-sensors@lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
>
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [lm-sensors] no sensors were detected with Intel Corporation
2007-11-09 0:06 [lm-sensors] no sensors were detected with Intel Corporation 82801H Kessia Pinheiro
2007-11-14 17:45 ` [lm-sensors] no sensors were detected with Intel Corporation Juerg Haefliger
@ 2007-11-15 17:04 ` Juerg Haefliger
2007-11-16 16:34 ` Juerg Haefliger
` (14 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: Juerg Haefliger @ 2007-11-15 17:04 UTC (permalink / raw)
To: lm-sensors
Hi Kessia,
>
>
> The SpeedFan say me that... I think isnt good. I think was my laptop model
> very new for support.
>
>
>
> ERROR collecting CPU Usage : 1 (Unable to locate the "Processor" performance
> object)
> Win9x:NO 64Bit:NO GiveIO:YES SpeedFan:YES
> I/O properly initialized
> Linked ISA BUS at $0290
> Linked Intel 82801HB ICH8 SMBUS at $10C0
> Scanning ISA BUS at $0290...
> DELL Support Enabling has been disabled
> because SYSTEM CALLS were unsuccessful
> Please, report if you think this is an error
> Scanning Intel SMBus at $10C0...
> End of detection
> INFO : NO SUPPORTED CHIP DETECTED
>
Do you see any voltage/fan information in the BIOS? Can you run
'isadump -k 0x55 0x2e 0x2f' and post the output to the list?
...juerg
>
>
>
>
> On 11/14/07, Juerg Haefliger < juergh@gmail.com> wrote:
> > Hi Kessia,
> >
> >
> > > Hi folks,
> > >
> > > I'm using ubuntu gutsy in dell vostro 1400 laptop. I try run
> sensors-detect,
> > > but this dont recognize my sensors. Below is my configs. thanks:
> > >
> > >
> --------------------------------------------------------------------------------------------------------------
> > > lspci output:
> > >
> > > 00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory
> > > Controller Hub (rev 0c)
> > > 00:01.0 PCI bridge: Intel Corporation Mobile PM965/GM965/GL960 PCI
> Express
> > > Root Port (rev 0c)
> > > 00: 1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI
> > > Contoller #4 (rev 02)
> > > 00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI
> > > Controller #5 (rev 02)
> > > 00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI
> > > Controller #2 (rev 02)
> > > 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio
> > > Controller (rev 02)
> > > 00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express
> Port
> > > 1 (rev 02)
> > > 00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express
> Port
> > > 2 (rev 02)
> > > 00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express
> Port
> > > 4 (rev 02)
> > > 00:1c.5 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express
> Port
> > > 6 (rev 02)
> > > 00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI
> > > Controller #1 (rev 02)
> > > 00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI
> > > Controller #2 (rev 02)
> > > 00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI
> > > Controller #3 (rev 02)
> > > 00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI
> > > Controller #1 (rev 02)
> > > 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f2)
> > > 00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M) LPC Interface
> > > Controller (rev 02)
> > > 00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E)
> IDE
> > > Controller (rev 02)
> > > 00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E)
> SATA
> > > AHCI Controller (rev 02)
> > > 00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller
> (rev
> > > 02)
> > > 01:00.0 VGA compatible controller: nVidia Corporation GeForce 8400M GS
> (rev
> > > a1)
> > > 03:01.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller
> (rev
> > > 05)
> > > 03:01.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro
> Host
> > > Adapter (rev 22)
> > > 03:01.2 System peripheral: Ricoh Co Ltd R5C843 MMC Host Controller (rev
> 12)
> > > 03:01.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host
> Adapter
> > > (rev 12)
> > > 03:01.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev
> 12)
> > > 09:00.0 Ethernet controller: Broadcom Corporation NetLink BCM5906M Fast
> > > Ethernet PCI Express (rev 02)
> > > 0c:00.0 Network controller: Broadcom Corporation BCM4328 802.11a/b/g/n
> (rev
> > > 03)
> > >
> > >
> > >
> --------------------------------------------------------------------------------------------------------------
> > > uname -a:
> > > Linux rainbows 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007
> i686
> > > GNU/Linux
> > >
> > >
> > >
> --------------------------------------------------------------------------------------------------------------
> > > lm-sensors version:
> > > Version: 1:2.10.4-1ubuntu1 (oficial package)
> > >
> > >
> --------------------------------------------------------------------------------------------------------------
> > > sensors-detect output:
> > > # sensors-detect revision 4609 (2007-07-14 09:28:39 -0700)
> > >
> > > 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 82801H ICH8
> > >
> > > 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.
> > >
> > > 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: NVIDIA i2c adapter (i2c-0)
> > > Do you want to scan it? (YES/no/selectively):
> > > Can't open /dev/i2c-0
> > >
> > > Next adapter: NVIDIA i2c adapter (i2c-1)
> > > Do you want to scan it? (YES/no/selectively):
> > > Can't open /dev/i2c-1
> > >
> > > Next adapter: NVIDIA i2c adapter (i2c-2)
> > > Do you want to scan it? (YES/no/selectively):
> > > Can't open /dev/i2c-2
> > >
> > > Next adapter: SMBus I801 adapter at 10c0 (i2c-3)
> > > Do you want to scan it? (YES/no/selectively):
> > > Client found at address 0x44
> > > Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
> > > 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 0x52
> > > 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'... No
> > > Trying family `SMSC'... Yes
> > > Found unknown chip with ID 0x3201
> > > 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
> >
> > As sensor-detect says, this chip is unknown. Can you run Speedfan
> > under windows on this machine? Speedfan might tell us what chip it is
> > and from that we can try to figure out if it's compatible with
> > anything that's currently supported.
> >
> > ...juerg
> >
> >
> >
> > > Some CPUs or memory controllers may also contain embedded sensors.
> > > Do you want to scan for them? (YES/no):
> > > AMD K8 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.
> > >
> > >
> > >
> > >
> --------------------------------------------------------------------------------------------------------------
> > >
> > >
> > > --
> > > Kessia Pinheiro
> > > Bacharelanda em Ciência da Computação
> > > Universidade Federal da Bahia
> > > Linux Counter User #389695 [http://counter.li.org]
> > > _______________________________________________
> > > lm-sensors mailing list
> > > lm-sensors@lm-sensors.org
> > > http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
> > >
> >
>
>
>
> --
>
>
> Kessia Pinheiro
> Bacharelanda em Ciência da Computação
> Universidade Federal da Bahia
> Linux Counter User #389695 [http://counter.li.org ]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [lm-sensors] no sensors were detected with Intel Corporation
2007-11-09 0:06 [lm-sensors] no sensors were detected with Intel Corporation 82801H Kessia Pinheiro
2007-11-14 17:45 ` [lm-sensors] no sensors were detected with Intel Corporation Juerg Haefliger
2007-11-15 17:04 ` Juerg Haefliger
@ 2007-11-16 16:34 ` Juerg Haefliger
2007-11-20 22:30 ` Kessia Pinheiro
` (13 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: Juerg Haefliger @ 2007-11-16 16:34 UTC (permalink / raw)
To: lm-sensors
Hi Kessia,
Please keep the list in the loop for future replies.
> The isadump output is below, but the BIOS info i send later.
>
> 0 1 2 3 4 5 6 7 8 9 a b c d e f
> 00: 00 00 00 00 00 00 00 0e 00 00 00 00 00 00 00 00
> 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 20: 32 01 00 00 00 04 2e 00 00 00 00 00 00 00 00 00
> 30: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 60: 0c 90 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> a0: 00 00 00 00 00 00 00 00 00 00 ff ff ff ff ff ff
> b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>
OK, can you now run 'isadump -f 0x0c90'?
...juerg
>
> On Nov 15, 2007 3:04 PM, Juerg Haefliger <juergh@gmail.com> wrote:
> > Hi Kessia,
> >
> >
> > >
> > >
> > > The SpeedFan say me that... I think isnt good. I think was my laptop
> model
> > > very new for support.
> > >
> > >
> > >
> > > ERROR collecting CPU Usage : 1 (Unable to locate the "Processor"
> performance
> > > object)
> > > Win9x:NO 64Bit:NO GiveIO:YES SpeedFan:YES
> > > I/O properly initialized
> > > Linked ISA BUS at $0290
> > > Linked Intel 82801HB ICH8 SMBUS at $10C0
> > > Scanning ISA BUS at $0290...
> > > DELL Support Enabling has been disabled
> > > because SYSTEM CALLS were unsuccessful
> > > Please, report if you think this is an error
> > > Scanning Intel SMBus at $10C0...
> > > End of detection
> > > INFO : NO SUPPORTED CHIP DETECTED
> > >
> >
> > Do you see any voltage/fan information in the BIOS? Can you run
> > 'isadump -k 0x55 0x2e 0x2f' and post the output to the list?
> >
> > ...juerg
> >
> >
> >
> >
> >
> >
>
> --
> Kessia Pinheiro
> Bacharelanda em Ciência da Computação
> Universidade Federal da Bahia
> Linux Counter User #389695 [ http://counter.li.org]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [lm-sensors] no sensors were detected with Intel Corporation
2007-11-09 0:06 [lm-sensors] no sensors were detected with Intel Corporation 82801H Kessia Pinheiro
` (2 preceding siblings ...)
2007-11-16 16:34 ` Juerg Haefliger
@ 2007-11-20 22:30 ` Kessia Pinheiro
2007-11-22 20:18 ` Jean Delvare
` (12 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: Kessia Pinheiro @ 2007-11-20 22:30 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 2442 bytes --]
The output is below:
# isadump -f 0x0c90
WARNING! Running this program can cause system crashes, data loss and worse!
I will probe address range 0xc00 to 0xcff.
Continue? [Y/n]
0 1 2 3 4 5 6 7 8 9 a b c d e f
0c00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0c10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0c20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0c30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0c40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0c50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0c60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0c70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0c80: 0a ff ff ff 08 ff ff ff ff ff ff ff ff ff ff ff
0c90: 34 ff ff ff 00 ff ff ff ff ff ff ff ff ff ff ff
0ca0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0cb0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0cc0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0cd0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0ce0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0cf0: ff ff ff ff ff ff ff ff ff 00 ff ff ff ff ff ff
On 11/16/07, Juerg Haefliger <juergh@gmail.com> wrote:
>
> Hi Kessia,
>
> Please keep the list in the loop for future replies.
>
>
> > The isadump output is below, but the BIOS info i send later.
> >
> > 0 1 2 3 4 5 6 7 8 9 a b c d e f
> > 00: 00 00 00 00 00 00 00 0e 00 00 00 00 00 00 00 00
> > 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > 20: 32 01 00 00 00 04 2e 00 00 00 00 00 00 00 00 00
> > 30: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > 60: 0c 90 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > a0: 00 00 00 00 00 00 00 00 00 00 ff ff ff ff ff ff
> > b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> >
>
> OK, can you now run 'isadump -f 0x0c90'?
>
> ...juerg
>
>
--
Kessia Pinheiro
Bacharelanda em Ciência da Computação
Universidade Federal da Bahia
Linux Counter User #389695 [http://counter.li.org]
[-- Attachment #1.2: Type: text/html, Size: 3173 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [lm-sensors] no sensors were detected with Intel Corporation
2007-11-09 0:06 [lm-sensors] no sensors were detected with Intel Corporation 82801H Kessia Pinheiro
` (3 preceding siblings ...)
2007-11-20 22:30 ` Kessia Pinheiro
@ 2007-11-22 20:18 ` Jean Delvare
2007-11-25 20:22 ` Kessia Pinheiro
` (11 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: Jean Delvare @ 2007-11-22 20:18 UTC (permalink / raw)
To: lm-sensors
On Tue, 20 Nov 2007 20:30:40 -0200, Kessia Pinheiro wrote:
> The output is below:
>
> # isadump -f 0x0c90
> WARNING! Running this program can cause system crashes, data loss and worse!
> I will probe address range 0xc00 to 0xcff.
> Continue? [Y/n]
> 0 1 2 3 4 5 6 7 8 9 a b c d e f
> 0c00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0c10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0c20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0c30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0c40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0c50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0c60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0c70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0c80: 0a ff ff ff 08 ff ff ff ff ff ff ff ff ff ff ff
> 0c90: 34 ff ff ff 00 ff ff ff ff ff ff ff ff ff ff ff
> 0ca0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0cb0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0cc0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0cd0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0ce0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0cf0: ff ff ff ff ff ff ff ff ff 00 ff ff ff ff ff ff
This doesn't look like a hardware monitoring chip...
> On 11/16/07, Juerg Haefliger <juergh@gmail.com> wrote:
> >
> > Hi Kessia,
> >
> > Please keep the list in the loop for future replies.
> >
> >
> > > The isadump output is below, but the BIOS info i send later.
> > >
> > > 0 1 2 3 4 5 6 7 8 9 a b c d e f
> > > 00: 00 00 00 00 00 00 00 0e 00 00 00 00 00 00 00 00
> > > 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > 20: 32 01 00 00 00 04 2e 00 00 00 00 00 00 00 00 00
> > > 30: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > 60: 0c 90 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > a0: 00 00 00 00 00 00 00 00 00 00 ff ff ff ff ff ff
> > > b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > >
> >
> > OK, can you now run 'isadump -f 0x0c90'?
... which isn't all that surprising, as the LDN is 0x0e which is never
used for hardware monitoring features on SMSC Super-I/O chips. Most of
them use LDN 0x0a or 0x08. Only one model uses LDN 0x09.
So, Kessia, please provide the output of the following commands:
isadump -k 0x55 0x2e 0x2f 0xa
isadump -k 0x55 0x2e 0x2f 0x8
(Please keep posting your replie to the mailing list.)
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [lm-sensors] no sensors were detected with Intel Corporation
2007-11-09 0:06 [lm-sensors] no sensors were detected with Intel Corporation 82801H Kessia Pinheiro
` (4 preceding siblings ...)
2007-11-22 20:18 ` Jean Delvare
@ 2007-11-25 20:22 ` Kessia Pinheiro
2007-11-27 11:13 ` Jean Delvare
` (10 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: Kessia Pinheiro @ 2007-11-25 20:22 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 2421 bytes --]
Sorry for out post, but reply is for who send message. . . Here is a output
for isadump's:
# isadump -k 0x55 0x2e 0x2f 0xa
WARNING! Running this program can cause system crashes, data loss and worse!
I will probe address register 0x2e and data register 0x2f.
Probing bank 10 using bank register 0x07.
Continue? [Y/n]
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: 00 00 00 00 00 00 00 0a 00 00 00 00 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 32 01 00 00 00 04 2e 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 ff ff ff ff ff ff
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
# isadump -k 0x55 0x2e 0x2f 0x8
WARNING! Running this program can cause system crashes, data loss and worse!
I will probe address register 0x2e and data register 0x2f.
Probing bank 8 using bank register 0x07.
Continue? [Y/n]
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: 00 00 00 00 00 00 00 08 00 00 00 00 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 32 01 00 00 00 04 2e 00 00 00 00 00 00 00 00 00
30: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 62 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 ff ff ff ff ff ff
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
--
Kessia Pinheiro
Bacharelanda em Ciência da Computação
Universidade Federal da Bahia
Linux Counter User #389695 [http://counter.li.org]
[-- Attachment #1.2: Type: text/html, Size: 2717 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [lm-sensors] no sensors were detected with Intel Corporation
2007-11-09 0:06 [lm-sensors] no sensors were detected with Intel Corporation 82801H Kessia Pinheiro
` (5 preceding siblings ...)
2007-11-25 20:22 ` Kessia Pinheiro
@ 2007-11-27 11:13 ` Jean Delvare
2007-11-27 20:11 ` Kessia Pinheiro
` (9 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: Jean Delvare @ 2007-11-27 11:13 UTC (permalink / raw)
To: lm-sensors
On Sun, 25 Nov 2007 18:22:44 -0200, Kessia Pinheiro wrote:
> Sorry for out post, but reply is for who send message. . . Here is a output
> for isadump's:
>
> # isadump -k 0x55 0x2e 0x2f 0xa
> WARNING! Running this program can cause system crashes, data loss and worse!
> I will probe address register 0x2e and data register 0x2f.
> Probing bank 10 using bank register 0x07.
> Continue? [Y/n]
> 0 1 2 3 4 5 6 7 8 9 a b c d e f
> 00: 00 00 00 00 00 00 00 0a 00 00 00 00 00 00 00 00
> 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 20: 32 01 00 00 00 04 2e 00 00 00 00 00 00 00 00 00
> 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
No I/O area configured...
> 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> a0: 00 00 00 00 00 00 00 00 00 00 ff ff ff ff ff ff
> b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>
> # isadump -k 0x55 0x2e 0x2f 0x8
> WARNING! Running this program can cause system crashes, data loss and worse!
> I will probe address register 0x2e and data register 0x2f.
> Probing bank 8 using bank register 0x07.
> Continue? [Y/n]
> 0 1 2 3 4 5 6 7 8 9 a b c d e f
> 00: 00 00 00 00 00 00 00 08 00 00 00 00 00 00 00 00
> 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 20: 32 01 00 00 00 04 2e 00 00 00 00 00 00 00 00 00
> 30: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 60: 00 62 00 00 00 00 00 00 00 00 00 00 00 00 00 00
And this one is definitely not a hardware monitoring device, more
likely the keyboard controller.
> 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> a0: 00 00 00 00 00 00 00 00 00 00 ff ff ff ff ff ff
> b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
The last hope is LDN 9:
isadump -k 0x55 0x2e 0x2f 0x9
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [lm-sensors] no sensors were detected with Intel Corporation
2007-11-09 0:06 [lm-sensors] no sensors were detected with Intel Corporation 82801H Kessia Pinheiro
` (6 preceding siblings ...)
2007-11-27 11:13 ` Jean Delvare
@ 2007-11-27 20:11 ` Kessia Pinheiro
2007-11-27 20:45 ` Jean Delvare
` (8 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: Kessia Pinheiro @ 2007-11-27 20:11 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 1328 bytes --]
The output:
# isadump -k 0x55 0x2e 0x2f 0x9
WARNING! Running this program can cause system crashes, data loss and worse!
I will probe address register 0x2e and data register 0x2f.
Probing bank 9 using bank register 0x07.
Continue? [Y/n]
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: 00 00 00 00 00 00 00 09 00 00 00 00 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 32 01 00 00 00 04 2e 00 00 00 00 00 00 00 00 00
30: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 09 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 ff ff ff ff ff ff
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>The last hope is LDN 9:
>isadump -k 0x55 0x2e 0x2f 0x9
>
>--
>Jean Delvare
--
Kessia Pinheiro
Bacharelanda em Ciência da Computação
Universidade Federal da Bahia
Linux Counter User #389695 [http://counter.li.org]
[-- Attachment #1.2: Type: text/html, Size: 1543 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [lm-sensors] no sensors were detected with Intel Corporation
2007-11-09 0:06 [lm-sensors] no sensors were detected with Intel Corporation 82801H Kessia Pinheiro
` (7 preceding siblings ...)
2007-11-27 20:11 ` Kessia Pinheiro
@ 2007-11-27 20:45 ` Jean Delvare
2007-11-28 23:57 ` Juerg Haefliger
` (7 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: Jean Delvare @ 2007-11-27 20:45 UTC (permalink / raw)
To: lm-sensors
On Tue, 27 Nov 2007 18:11:07 -0200, Kessia Pinheiro wrote:
> The output:
>
> # isadump -k 0x55 0x2e 0x2f 0x9
> WARNING! Running this program can cause system crashes, data loss and worse!
> I will probe address register 0x2e and data register 0x2f.
> Probing bank 9 using bank register 0x07.
> Continue? [Y/n]
> 0 1 2 3 4 5 6 7 8 9 a b c d e f
> 00: 00 00 00 00 00 00 00 09 00 00 00 00 00 00 00 00
> 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 20: 32 01 00 00 00 04 2e 00 00 00 00 00 00 00 00 00
> 30: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 60: 09 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> a0: 00 00 00 00 00 00 00 00 00 00 ff ff ff ff ff ff
> b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
We already have a dump for 0x910 from one of your previous post, and no
hardware monitoring device there either.
My conclusion is that you do not have a hardware monitoring chip, which
is rather common for laptops anyway, so no real surprise. Just use
"acpi -t" to get your system temperature.
Either that, or the ICH8 integrated sensors are used. But we don't
support them at the moment.
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [lm-sensors] no sensors were detected with Intel Corporation
2007-11-09 0:06 [lm-sensors] no sensors were detected with Intel Corporation 82801H Kessia Pinheiro
` (8 preceding siblings ...)
2007-11-27 20:45 ` Jean Delvare
@ 2007-11-28 23:57 ` Juerg Haefliger
2007-11-29 8:48 ` Jean Delvare
` (6 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: Juerg Haefliger @ 2007-11-28 23:57 UTC (permalink / raw)
To: lm-sensors
Hi Jean,
On Nov 27, 2007 12:45 PM, Jean Delvare <khali@linux-fr.org> wrote:
> On Tue, 27 Nov 2007 18:11:07 -0200, Kessia Pinheiro wrote:
> > The output:
> >
> > # isadump -k 0x55 0x2e 0x2f 0x9
> > WARNING! Running this program can cause system crashes, data loss and worse!
> > I will probe address register 0x2e and data register 0x2f.
> > Probing bank 9 using bank register 0x07.
> > Continue? [Y/n]
> > 0 1 2 3 4 5 6 7 8 9 a b c d e f
> > 00: 00 00 00 00 00 00 00 09 00 00 00 00 00 00 00 00
> > 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > 20: 32 01 00 00 00 04 2e 00 00 00 00 00 00 00 00 00
> > 30: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > 60: 09 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > a0: 00 00 00 00 00 00 00 00 00 00 ff ff ff ff ff ff
> > b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>
> We already have a dump for 0x910 from one of your previous post, and no
> hardware monitoring device there either.
We do? He gave us a dump for 0xc90 but I haven't seen anything for 0x910.
Kessia, can you please run 'isadump -f 0x910'?
...juerg
> My conclusion is that you do not have a hardware monitoring chip, which
> is rather common for laptops anyway, so no real surprise. Just use
> "acpi -t" to get your system temperature.
>
> Either that, or the ICH8 integrated sensors are used. But we don't
> support them at the moment.
>
>
> --
> Jean Delvare
>
> _______________________________________________
> lm-sensors mailing list
> lm-sensors@lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
>
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [lm-sensors] no sensors were detected with Intel Corporation
2007-11-09 0:06 [lm-sensors] no sensors were detected with Intel Corporation 82801H Kessia Pinheiro
` (9 preceding siblings ...)
2007-11-28 23:57 ` Juerg Haefliger
@ 2007-11-29 8:48 ` Jean Delvare
2007-11-30 19:29 ` Kessia Pinheiro
` (5 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: Jean Delvare @ 2007-11-29 8:48 UTC (permalink / raw)
To: lm-sensors
On Wed, 28 Nov 2007 15:57:15 -0800, Juerg Haefliger wrote:
> Hi Jean,
>
>
> On Nov 27, 2007 12:45 PM, Jean Delvare <khali@linux-fr.org> wrote:
> > On Tue, 27 Nov 2007 18:11:07 -0200, Kessia Pinheiro wrote:
> > > The output:
> > >
> > > # isadump -k 0x55 0x2e 0x2f 0x9
> > > WARNING! Running this program can cause system crashes, data loss and worse!
> > > I will probe address register 0x2e and data register 0x2f.
> > > Probing bank 9 using bank register 0x07.
> > > Continue? [Y/n]
> > > 0 1 2 3 4 5 6 7 8 9 a b c d e f
> > > 00: 00 00 00 00 00 00 00 09 00 00 00 00 00 00 00 00
> > > 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > 20: 32 01 00 00 00 04 2e 00 00 00 00 00 00 00 00 00
> > > 30: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > 60: 09 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > a0: 00 00 00 00 00 00 00 00 00 00 ff ff ff ff ff ff
> > > b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> >
> > We already have a dump for 0x910 from one of your previous post, and no
> > hardware monitoring device there either.
>
> We do? He gave us a dump for 0xc90 but I haven't seen anything for 0x910.
> Kessia, can you please run 'isadump -f 0x910'?
Oops, my bad, I swapped digits in my head. You're right, thanks for
watching me!
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [lm-sensors] no sensors were detected with Intel Corporation
2007-11-09 0:06 [lm-sensors] no sensors were detected with Intel Corporation 82801H Kessia Pinheiro
` (10 preceding siblings ...)
2007-11-29 8:48 ` Jean Delvare
@ 2007-11-30 19:29 ` Kessia Pinheiro
2007-12-01 11:09 ` Jean Delvare
` (4 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: Kessia Pinheiro @ 2007-11-30 19:29 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 3148 bytes --]
isadump -f 0x910
WARNING! Running this program can cause system crashes, data loss and worse!
I will probe address range 0x900 to 0x9ff.
Continue? [Y/n]
0 1 2 3 4 5 6 7 8 9 a b c d e f
0900: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0910: af 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0920: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0930: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0940: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0950: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0960: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0970: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0980: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0990: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
09a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
09b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
09c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
09d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
09e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
09f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
On 11/29/07, Jean Delvare <khali@linux-fr.org> wrote:
>
> On Wed, 28 Nov 2007 15:57:15 -0800, Juerg Haefliger wrote:
> > Hi Jean,
> >
> >
> > On Nov 27, 2007 12:45 PM, Jean Delvare <khali@linux-fr.org> wrote:
> > > On Tue, 27 Nov 2007 18:11:07 -0200, Kessia Pinheiro wrote:
> > > > The output:
> > > >
> > > > # isadump -k 0x55 0x2e 0x2f 0x9
> > > > WARNING! Running this program can cause system crashes, data loss
> and worse!
> > > > I will probe address register 0x2e and data register 0x2f.
> > > > Probing bank 9 using bank register 0x07.
> > > > Continue? [Y/n]
> > > > 0 1 2 3 4 5 6 7 8 9 a b c d e f
> > > > 00: 00 00 00 00 00 00 00 09 00 00 00 00 00 00 00 00
> > > > 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > > 20: 32 01 00 00 00 04 2e 00 00 00 00 00 00 00 00 00
> > > > 30: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > > 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > > 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > > 60: 09 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > > 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > > 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > > 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > > a0: 00 00 00 00 00 00 00 00 00 00 ff ff ff ff ff ff
> > > > b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > > c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > > d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > > e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > > f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > >
> > > We already have a dump for 0x910 from one of your previous post, and
> no
> > > hardware monitoring device there either.
> >
> > We do? He gave us a dump for 0xc90 but I haven't seen anything for
> 0x910.
> > Kessia, can you please run 'isadump -f 0x910'?
>
> Oops, my bad, I swapped digits in my head. You're right, thanks for
> watching me!
>
> --
> Jean Delvare
>
--
Kessia Pinheiro
Bacharelanda em Ciência da Computação
Universidade Federal da Bahia
Linux Counter User #389695 [http://counter.li.org]
[-- Attachment #1.2: Type: text/html, Size: 3938 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [lm-sensors] no sensors were detected with Intel Corporation
2007-11-09 0:06 [lm-sensors] no sensors were detected with Intel Corporation 82801H Kessia Pinheiro
` (11 preceding siblings ...)
2007-11-30 19:29 ` Kessia Pinheiro
@ 2007-12-01 11:09 ` Jean Delvare
2007-12-01 17:16 ` Kessia Pinheiro
` (3 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: Jean Delvare @ 2007-12-01 11:09 UTC (permalink / raw)
To: lm-sensors
On Fri, 30 Nov 2007 17:29:40 -0200, Kessia Pinheiro wrote:
> isadump -f 0x910
> WARNING! Running this program can cause system crashes, data loss and worse!
> I will probe address range 0x900 to 0x9ff.
> Continue? [Y/n]
> 0 1 2 3 4 5 6 7 8 9 a b c d e f
> 0900: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0910: af 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0920: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0930: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0940: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0950: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0960: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0970: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0980: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0990: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 09a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 09b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 09c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 09d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 09e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 09f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Hmm, that could be an index/data pair as on the LPC47B397 and
LPC47N252. Then the next step would be:
isadump 0x910 0x911
That being said, without a datasheet, I'm not sure where we are going.
Especially as it is a laptop and most laptops don't have usable
sensors, there's probably nothing to find.
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [lm-sensors] no sensors were detected with Intel Corporation
2007-11-09 0:06 [lm-sensors] no sensors were detected with Intel Corporation 82801H Kessia Pinheiro
` (12 preceding siblings ...)
2007-12-01 11:09 ` Jean Delvare
@ 2007-12-01 17:16 ` Kessia Pinheiro
2007-12-01 18:21 ` Jean Delvare
` (2 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: Kessia Pinheiro @ 2007-12-01 17:16 UTC (permalink / raw)
To: lm-sensors
isadump 0x910 0x911
WARNING! Running this program can cause system crashes, data loss and worse!
I will probe address register 0x910 and data register 0x911.
Continue? [Y/n]
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 23 00 00 00 ff 1f 80 4c 00 00 00 07 37 39 37 39
90: 02 00 00 00 80 00 00 08 00 00 00 00 00 00 00 43
a0: 00 01 01 4f ec f5 07 2d a8 0f 20 0c 06 01 37 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
On 12/1/07, Jean Delvare <khali@linux-fr.org> wrote:
> On Fri, 30 Nov 2007 17:29:40 -0200, Kessia Pinheiro wrote:
> > isadump -f 0x910
> > WARNING! Running this program can cause system crashes, data loss and worse!
> > I will probe address range 0x900 to 0x9ff.
> > Continue? [Y/n]
> > 0 1 2 3 4 5 6 7 8 9 a b c d e f
> > 0900: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > 0910: af 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > 0920: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > 0930: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > 0940: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > 0950: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > 0960: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > 0970: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > 0980: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > 0990: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > 09a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > 09b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > 09c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > 09d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > 09e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > 09f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>
> Hmm, that could be an index/data pair as on the LPC47B397 and
> LPC47N252. Then the next step would be:
>
> isadump 0x910 0x911
>
> That being said, without a datasheet, I'm not sure where we are going.
> Especially as it is a laptop and most laptops don't have usable
> sensors, there's probably nothing to find.
>
> --
> Jean Delvare
>
--
Kessia Pinheiro
Bacharelanda em Ciência da Computação
Universidade Federal da Bahia
Linux Counter User #389695 [http://counter.li.org]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [lm-sensors] no sensors were detected with Intel Corporation
2007-11-09 0:06 [lm-sensors] no sensors were detected with Intel Corporation 82801H Kessia Pinheiro
` (13 preceding siblings ...)
2007-12-01 17:16 ` Kessia Pinheiro
@ 2007-12-01 18:21 ` Jean Delvare
2008-01-03 14:50 ` Kessia Pinheiro
2008-01-13 13:35 ` Jean Delvare
16 siblings, 0 replies; 18+ messages in thread
From: Jean Delvare @ 2007-12-01 18:21 UTC (permalink / raw)
To: lm-sensors
On Sat, 1 Dec 2007 15:16:07 -0200, Kessia Pinheiro wrote:
> isadump 0x910 0x911
> WARNING! Running this program can cause system crashes, data loss and worse!
> I will probe address register 0x910 and data register 0x911.
> Continue? [Y/n]
> 0 1 2 3 4 5 6 7 8 9 a b c d e f
> 00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 80: 23 00 00 00 ff 1f 80 4c 00 00 00 07 37 39 37 39
> 90: 02 00 00 00 80 00 00 08 00 00 00 00 00 00 00 43
> a0: 00 01 01 4f ec f5 07 2d a8 0f 20 0c 06 01 37 00
> b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
OK, so it was indeed an index/data pair. Now, if some of these register
values correspond to sensors, their values should change a little over
time. Try running the same isadump command a few seconds apart and see
if some values change. Do that while the fan is spinning, otherwise you
might miss it. Also try with and without CPU load to increase the
chances to spot a change.
Note that the register map above looks like what the LPC47N252
datasheet describes. The bad news is that the chip does only fan speed
monitoring and control. On top of that, the fan speeds cannot be read
directly from the I/O space, so I don't even know how we would write a
driver. Someone would need to take a deeper look at the datasheet, I
don't have the time myself.
I also think that it would be worth taking a look at the ACPI
implementation of your laptop to see what they are doing with
temperatures and fans. We don't want to interfere with that. Can you
read the temperature using acpi?
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [lm-sensors] no sensors were detected with Intel Corporation
2007-11-09 0:06 [lm-sensors] no sensors were detected with Intel Corporation 82801H Kessia Pinheiro
` (14 preceding siblings ...)
2007-12-01 18:21 ` Jean Delvare
@ 2008-01-03 14:50 ` Kessia Pinheiro
2008-01-13 13:35 ` Jean Delvare
16 siblings, 0 replies; 18+ messages in thread
From: Kessia Pinheiro @ 2008-01-03 14:50 UTC (permalink / raw)
To: lm-sensors
> OK, so it was indeed an index/data pair. Now, if some of these register
> values correspond to sensors, their values should change a little over
> time. Try running the same isadump command a few seconds apart and see
> if some values change. Do that while the fan is spinning, otherwise you
> might miss it. Also try with and without CPU load to increase the
> chances to spot a change.
I execute some times "isadump 0x910 0x911" and got differents values, like:
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 59 ff 00 00 01 27 80 4c 00 00 00 07 37 39 37 39
90: 02 00 00 00 00 00 00 08 00 00 00 00 00 00 00 1e
a0: 00 01 00 62 00 00 a9 30 50 14 b8 0b 0a 47 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
and
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 23 00 00 00 01 27 80 4c 00 00 00 07 37 39 37 39
90: 02 00 00 00 80 00 00 08 00 00 00 00 00 00 00 43
a0: 00 01 00 62 00 00 a9 30 50 14 b8 0b 0a 47 32 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> Note that the register map above looks like what the LPC47N252
> datasheet describes. The bad news is that the chip does only fan speed
> monitoring and control. On top of that, the fan speeds cannot be read
> directly from the I/O space, so I don't even know how we would write a
> driver. Someone would need to take a deeper look at the datasheet, I
> don't have the time myself.
>
> I also think that it would be worth taking a look at the ACPI
> implementation of your laptop to see what they are doing with
> temperatures and fans. We don't want to interfere with that. Can you
> read the temperature using acpi?
Can i read:
processor/CPU0:
info limit power throttling
# cat processor/CPU0/*
processor id: 0
acpi id: 0
bus mastering control: yes
power management: yes
throttling control: yes
limit interface: yes
active limit: P0:T0
user limit: P0:T0
thermal limit: P0:T0
active state: C3
max_cstate: C8
bus master activity: 00000000
maximum allowed latency: 6666 usec
states:
C1: type[C1] promotion[C2] demotion[--]
latency[001] usage[00000040] duration[00000000000000000000]
C2: type[C2] promotion[C3] demotion[C1]
latency[001] usage[00023260] duration[00000000000211173996]
*C3: type[C3] promotion[--] demotion[C2]
latency[017] usage[01032996] duration[00000000014670215004]
state count: 8
active state: T0
state available: T0 to T7
states:
*T0: 00%
T1: 12%
T2: 25%
T3: 37%
T4: 50%
T5: 62%
T6: 75%
T7: 87%
thermal_zone/THM:
cooling_mode polling_frequency state temperature trip_points
# cat thermal_zone/THM/*
<setting not supported>
<polling disabled>
state: ok
temperature: 40 C
critical (S5): 99 C
video/VID:
CRT DOS DVI LCD POST POST_info ROM TV info
video/VID1:
CRT DOS DVI LCD POST POST_info ROM TV info
video/VID2:
DOS POST POST_info ROM info
--
Kessia Pinheiro
Bacharelanda em Ciência da Computação
Universidade Federal da Bahia
Linux Counter User #389695 [http://counter.li.org]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [lm-sensors] no sensors were detected with Intel Corporation
2007-11-09 0:06 [lm-sensors] no sensors were detected with Intel Corporation 82801H Kessia Pinheiro
` (15 preceding siblings ...)
2008-01-03 14:50 ` Kessia Pinheiro
@ 2008-01-13 13:35 ` Jean Delvare
16 siblings, 0 replies; 18+ messages in thread
From: Jean Delvare @ 2008-01-13 13:35 UTC (permalink / raw)
To: lm-sensors
Hi Kessia,
On Thu, 3 Jan 2008 12:50:04 -0200, Kessia Pinheiro wrote:
> > OK, so it was indeed an index/data pair. Now, if some of these register
> > values correspond to sensors, their values should change a little over
> > time. Try running the same isadump command a few seconds apart and see
> > if some values change. Do that while the fan is spinning, otherwise you
> > might miss it. Also try with and without CPU load to increase the
> > chances to spot a change.
>
> I execute some times "isadump 0x910 0x911" and got differents values, like:
>
> 0 1 2 3 4 5 6 7 8 9 a b c d e f
> 00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 80: 59 ff 00 00 01 27 80 4c 00 00 00 07 37 39 37 39
> 90: 02 00 00 00 00 00 00 08 00 00 00 00 00 00 00 1e
> a0: 00 01 00 62 00 00 a9 30 50 14 b8 0b 0a 47 00 00
> b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>
>
> and
>
> 0 1 2 3 4 5 6 7 8 9 a b c d e f
> 00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 80: 23 00 00 00 01 27 80 4c 00 00 00 07 37 39 37 39
> 90: 02 00 00 00 80 00 00 08 00 00 00 00 00 00 00 43
> a0: 00 01 00 62 00 00 a9 30 50 14 b8 0b 0a 47 32 00
> b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
I see the following changes:
Register 0x80 from 0x59 to 0x23
Register 0x81 from 0xff to 0x00
Register 0x94 from 0x00 to 0x80
Register 0x9f from 0x1e to 0x43
Register 0xae from 0x00 to 0x32
Unfortunately these changes don't really look like sensor value changes.
Sensor values typically change to values nearby, that's not the case
here. Without documentation, it looks like a dead end, sorry.
> > I also think that it would be worth taking a look at the ACPI
> > implementation of your laptop to see what they are doing with
> > temperatures and fans. We don't want to interfere with that. Can you
> > read the temperature using acpi?
>
> Can i read:
> (...)
> # cat thermal_zone/THM/*
> <setting not supported>
> <polling disabled>
> state: ok
> temperature: 40 C
> critical (S5): 99 C
OK, so at least you can get your system temperature and it looks valid.
That's probably all you will get from your laptop, at least for the
time being. If you have the "acpi" client installed you can get the
temperature value with "acpi -t".
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 18+ messages in thread
end of thread, other threads:[~2008-01-13 13:35 UTC | newest]
Thread overview: 18+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-11-09 0:06 [lm-sensors] no sensors were detected with Intel Corporation 82801H Kessia Pinheiro
2007-11-14 17:45 ` [lm-sensors] no sensors were detected with Intel Corporation Juerg Haefliger
2007-11-15 17:04 ` Juerg Haefliger
2007-11-16 16:34 ` Juerg Haefliger
2007-11-20 22:30 ` Kessia Pinheiro
2007-11-22 20:18 ` Jean Delvare
2007-11-25 20:22 ` Kessia Pinheiro
2007-11-27 11:13 ` Jean Delvare
2007-11-27 20:11 ` Kessia Pinheiro
2007-11-27 20:45 ` Jean Delvare
2007-11-28 23:57 ` Juerg Haefliger
2007-11-29 8:48 ` Jean Delvare
2007-11-30 19:29 ` Kessia Pinheiro
2007-12-01 11:09 ` Jean Delvare
2007-12-01 17:16 ` Kessia Pinheiro
2007-12-01 18:21 ` Jean Delvare
2008-01-03 14:50 ` Kessia Pinheiro
2008-01-13 13:35 ` Jean Delvare
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.