| View previous topic :: View next topic |
| Author |
Message |
Guinpen
Guru
Joined: 08 Dec 2004
Posts: 393
|
 Posted: Fri Jun 24, 2005 9:45 am Post subject: lm_sensors not emerging - OK - don't drink AND login as root |
 |
|
lm_sensors-2.9.1 complains about I2C with the following message:
| Code: |
lm_sensors-2.9.1 requires CONFIG_I2C_SENSOR to be enabled for non-2.4.x kernels.
|
My kernel is 2.6.11. I have tried to get I2C enabled but I haven't been successful. In my kernel config I have "I2C support" and "I2C device interface" enabled, but no specific I2C device (I have no idea whether I have one or what it is - my laptop is a Dell Latitude D800). I'd unmerge lm_sensors altogether, but ksysguard requires it, and quite a few things require ksysguard, so I guess I have no choice.
By the way, "make oldconfig | grep I2C" gives the following:
| Code: |
* I2C support
I2C support (I2C) [Y/n/m/?] y
I2C device interface (I2C_CHARDEV) [Y/n/m/?] y
* I2C Algorithms
I2C bit-banging interfaces (I2C_ALGOBIT) [N/m/y/?] n
I2C PCF 8584 interfaces (I2C_ALGOPCF) [N/m/y/?] n
I2C PCA 9564 interfaces (I2C_ALGOPCA) [N/m/y/?] n
* I2C Hardware Bus support
ALI 1535 (I2C_ALI1535) [N/m/y/?] n
ALI 1563 (I2C_ALI1563) [N/m/y/?] n
ALI 15x3 (I2C_ALI15X3) [N/m/y/?] n
AMD 756/766/768/8111 and nVidia nForce (I2C_AMD756) [N/m/y/?] n
XBOX I2C (I2C_XBOX) [N/m/y] n
AMD 8111 (I2C_AMD8111) [N/m/y/?] n
Intel 801 (I2C_I801) [N/m/y/?] n
Intel 810/815 (I2C_I810) [N/m/y/?] n
ISA Bus support (I2C_ISA) [N/m/y/?] n
Nvidia Nforce2 (I2C_NFORCE2) [N/m/y/?] n
Parallel port adapter (I2C_PARPORT) [N/m/y/?] n
Parallel port adapter (light) (I2C_PARPORT_LIGHT) [N/m/y/?] n
Intel PIIX4 (I2C_PIIX4) [N/m/y/?] n
S3/VIA (Pro)Savage (I2C_PROSAVAGE) [N/m/y/?] n
S3 Savage 4 (I2C_SAVAGE4) [N/m/y/?] n
SiS 5595 (I2C_SIS5595) [N/m/y/?] n
SiS 630/730 (I2C_SIS630) [N/m/y/?] n
SiS 96x (I2C_SIS96X) [N/m/y/?] n
I2C/SMBus Test Stub (I2C_STUB) [N/m/?] n
VIA 82C586B (I2C_VIA) [N/m/y/?] n
VIA 82C596/82C686/823x (I2C_VIAPRO) [N/m/y/?] n
Voodoo 3 (I2C_VOODOO3) [N/m/y/?] n
PCA9564 on an ISA bus (I2C_PCA_ISA) [N/m/y/?] n
* Other I2C Chip support
I2C Core debugging messages (I2C_DEBUG_CORE) [N/y/?] n
I2C Algorithm debugging messages (I2C_DEBUG_ALGO) [N/y/?] n
I2C Bus debugging messages (I2C_DEBUG_BUS) [N/y/?] n
I2C Chip debugging messages (I2C_DEBUG_CHIP) [N/y/?] n
|
Last edited by Guinpen on Sat Jun 25, 2005 9:50 am; edited 1 time in total |
|
| Back to top |
|
 |
dgaffuri
Advocate
Joined: 05 Jun 2005
Posts: 2078
Location: Italy
|
| Posted: Fri Jun 24, 2005 11:13 pm Post subject: |
|
|
| Select all busses, chips and algorithms under I2C support in kernel to be built as modules, then emerge lm_sensors and run sensors-detect. That will tell you wich busses and chips are detected on ypur hardware platform. |
|
| Back to top |
|
|
Guinpen
Guru
Joined: 08 Dec 2004
Posts: 393
|
| Posted: Sat Jun 25, 2005 9:22 am Post subject: |
|
|
Hi,
I tried what you suggested but sensors-detect detected nothing. I'm currently builiding the srivers into the kernel (no modules) to see if there will be any difference.
As far I can see, lm_sensors is something that manages mainboard sensors for CPU temperature and the like. Do I really have/need this? I've always been able to read my CPU temperature by entering
| Code: |
cat /proc/acpi/thermal_zone/THM/temperature
|
|
|
| Back to top |
|
|
Guinpen
Guru
Joined: 08 Dec 2004
Posts: 393
|
| Posted: Sat Jun 25, 2005 9:30 am Post subject: |
|
|
It didn't detect anything with built-in drivers either. The only difference is that it deteced some PCI bus adapter; with modules, it coudn't detect that even.
Anyway, I'd gladly do away with lm_sensors and I2C altogether, since obivously I don't have the hardware, but every emerge --update world wants to emerge it back again. What should I do?
EDIT: Four seconds after I posted it I noticed that for some reason, I had the lm_sensors USE flag enabled... damn. I'm stupid 
Last edited by Guinpen on Sat Jun 25, 2005 9:32 am; edited 1 time in total |
|
| Back to top |
|
|
dgaffuri
Advocate
Joined: 05 Jun 2005
Posts: 2078
Location: Italy
|
| Posted: Sat Jun 25, 2005 9:32 am Post subject: |
|
|
| Godji wrote: | | I tried what you suggested but sensors-detect detected nothing. I'm currently builiding the srivers into the kernel (no modules) to see if there will be any difference. |
My notebook (a Toshiba Tecra M2) hides the SMBus chip, and it needs to be re-enabled by the kernel. Post an lspci output to check if this is the case.
| Godji wrote: | As far I can see, lm_sensors is something that manages mainboard sensors for CPU temperature and the like. Do I really have/need this? I've always been able to read my CPU temperature by entering
| Code: |
cat /proc/acpi/thermal_zone/THM/temperature
|
|
That's true, although I find differences between the two reported temps (but I don't know which one is the real one  ). lm_sensors may give you additional info, depending on your I2C hardware (if any). |
|
| Back to top |
|
|
Guinpen
Guru
Joined: 08 Dec 2004
Posts: 393
|
| Posted: Sat Jun 25, 2005 9:34 am Post subject: |
|
|
Here it comes:
| Code: |
0000:00:00.0 Host bridge: Intel Corp. 82855PM Processor to I/O Controller (rev 03)
0000:00:01.0 PCI bridge: Intel Corp. 82855PM Processor to AGP Controller (rev 03)
0000:00:1d.0 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01)
0000:00:1d.1 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 01)
0000:00:1d.2 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 01)
0000:00:1d.7 USB Controller: Intel Corp. 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 01)
0000:00:1e.0 PCI bridge: Intel Corp. 82801 Mobile PCI Bridge (rev 81)
0000:00:1f.0 ISA bridge: Intel Corp. 82801DBM (ICH4-M) LPC Interface Bridge (rev 01)
0000:00:1f.1 IDE interface: Intel Corp. 82801DBM (ICH4-M) IDE Controller (rev 01)
0000:00:1f.5 Multimedia audio controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01)
0000:01:00.0 VGA compatible controller: nVidia Corporation NV28 [GeForce4 Ti 4200 Go AGP 8x] (rev a1)
0000:02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5705M Gigabit Ethernet (rev 01)
0000:02:01.0 CardBus bridge: Texas Instruments: Unknown device ac47 (rev 01)
0000:02:01.2 FireWire (IEEE 1394): Texas Instruments: Unknown device 802b
0000:02:01.3 System peripheral: Texas Instruments: Unknown device 8204
0000:02:03.0 CardBus bridge: Texas Instruments PCI1410 PC card Cardbus Controller (rev 01)
|
No I2C as far as I can tell. |
|
| Back to top |
|
|
dgaffuri
Advocate
Joined: 05 Jun 2005
Posts: 2078
Location: Italy
|
| Posted: Sat Jun 25, 2005 9:55 am Post subject: |
|
|
The 82801DBM (ICH4-M) have an SMBus function that should show as 0000:00:1f.3, but is hidden by BIOS on most Centrino laptops. You should check if this is your case (that's a matter of lspci commands, but I don't remember exactly which. If you're really interested I can try to repeat Google searches that led me there) and then patch the kernel to enable it on boot.
This kernel patch against vanilla 2.6.12 re-enables it for my notebook:
| Code: |
--- linux-2.6.12//drivers/pci/quirks.c.orig 2005-06-17 21:48:29.000000000 +0200
+++ linux-2.6.12//drivers/pci/quirks.c 2005-06-18 15:03:49.000000000 +0200
@@ -819,6 +819,11 @@ static void __init asus_hides_smbus_host
case 0x0001: /* Toshiba Satellite A40 */
asus_hides_smbus = 1;
}
+ if (dev->device == PCI_DEVICE_ID_INTEL_82855PM_HB)
+ switch(dev->subsystem_device) {
+ case 0x0001: /* Toshiba Tecra M2 */
+ asus_hides_smbus = 1;
+ }
} else if (unlikely(dev->subsystem_vendor == PCI_VENDOR_ID_SAMSUNG)) {
if (dev->device == PCI_DEVICE_ID_INTEL_82855PM_HB)
switch(dev->subsystem_device) {
|
The asus refernces are there because the problem first arose with ASUS mainboards. |
|
| Back to top |
|
|
Guinpen
Guru
Joined: 08 Dec 2004
Posts: 393
|
| Posted: Sat Jun 25, 2005 10:30 am Post subject: |
|
|
Thanks a lot
But I'd say that's a little more tinkering than I feel confident with. For now, I'll go without lm_sensors. |
|
| Back to top |
|
|
|
Kernel & Hardware
