Hi Mathieu, On 11/1/2006, HALM Mathieu wrote: >I have a problem to launch the sensors command. > >I install the last ubuntu 6.10 >The kernel is 2.6.17-10 > >My system is a fujitsu-siemens laptop model : L7320G > >The version of lm-sensors I m using is 2.10.0 > > >Here is the result of the lspci command : > >00:00.0 Host bridge: VIA Technologies, Inc. P4M800CE Host Bridge >00:00.1 Host bridge: VIA Technologies, Inc. P4M800CE Host Bridge >00:00.2 Host bridge: VIA Technologies, Inc. P4M800CE Host Bridge >00:00.3 Host bridge: VIA Technologies, Inc. PT890 Host Bridge >00:00.4 Host bridge: VIA Technologies, Inc. P4M800CE Host Bridge >00:00.7 Host bridge: VIA Technologies, Inc. P4M800CE Host Bridge >00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge >00:06.0 Ethernet controller: Atheros Communications, Inc. AR5005G >802.11abgNIC (rev 01) >00:0f.0 IDE interface: VIA Technologies, Inc. VIA VT6420 SATA RAID >Controller (rev 80) >00:0f.1 IDE interface: VIA Technologies, Inc. >VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) >00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB >1.1Controller (rev 81) >00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB >1.1Controller (rev 81) >00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86) >00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge >[KT600/K8T800/K8T890 South] >00:11.5 Multimedia audio controller: VIA Technologies, Inc. >VT8233/A/8235/8237 AC97 Audio Controller (rev 60) >00:11.6 Communication controller: VIA Technologies, Inc. AC'97 Modem >Controller (rev 80) >00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev >78) >01:00.0 VGA compatible controller: VIA Technologies, Inc. UniChrome Pro IGP >(rev 01) > > > >Here is the result of the sensors-detect command : > > ># sensors-detect revision 1.413 (2006/01/19 20:28:00) > >This program will help you determine which I2C/SMBus modules you need to >load to use lm_sensors most effectively. You need to have i2c and >lm_sensors installed before running this program. >Also, you need to be `root', or at least have access to the /dev/i2c-* >files, for most things. >If you have patched your kernel and have some drivers built in, you can >safely answer NO if asked to load some modules. In this case, things may >seem a bit confusing, but they will still work. > >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. > You do not need any special privileges for this. > Do you want to probe now? (YES/no): YES >Probing for PCI bus adapters... >Use driver `i2c-viapro' for device 00:11.0: VIA Technologies VT8237 South >Bridge >Probe succesfully concluded. > >We will now try to load each adapter module in turn. >Module `i2c-viapro' already loaded. >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. > If it is built-in into your kernel, you can safely skip this. > i2c-dev is not loaded. Do you want to load it now? (YES/no): YES > Module loaded succesfully. > > We are now going to do the adapter probings. Some adapters may hang halfway > through; we can't really help that. Also, some chips will 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. That often > includes address 0x69 (clock chip). > >Next adapter: SMBus Via Pro adapter at 4100 >Do you want to scan it? (YES/no/selectively): YES >Client found at address 0x50 >Probing for `SPD EEPROM'... Success! > (confidence 8, driver `eeprom') >Probing for `DDC monitor'... Failed! >Probing for `Maxim MAX6900'... Failed! >Client found at address 0x69 >Client found at address 0x6e > >Some chips are also accessible through the ISA bus. ISA probes are >typically a bit more dangerous, as we have to write to I/O ports to do >this. This is usually safe though. > >Do you want to scan the ISA bus? (YES/no): YES >Probing for `National Semiconductor LM78' > Trying address 0x0290... Failed! >Probing for `National Semiconductor LM78-J' > Trying address 0x0290... Failed! >Probing for `National Semiconductor LM79' > Trying address 0x0290... Failed! >Probing for `Winbond W83781D' > Trying address 0x0290... Failed! >Probing for `Winbond W83782D' > Trying address 0x0290... Failed! >Probing for `Winbond W83627HF' > Trying address 0x0290... Failed! >Probing for `Winbond W83627EHF' > Trying address 0x0290... Failed! >Probing for `Silicon Integrated Systems SIS5595' > Trying general detect... Failed! >Probing for `VIA Technologies VT82C686 Integrated Sensors' > Trying general detect... Failed! >Probing for `VIA Technologies VT8231 Integrated Sensors' > Trying general detect... Failed! >Probing for `ITE IT8712F' > Trying address 0x0290... Failed! >Probing for `ITE IT8705F / SiS 950' > Trying address 0x0290... Failed! >Probing for `IPMI BMC KCS' > Trying address 0x0ca0... Failed! >Probing for `IPMI BMC SMIC' > Trying address 0x0ca8... Failed! > >Some Super I/O chips may also contain sensors. Super I/O probes are >typically a bit more dangerous, as we have to write to I/O ports to do >this. This is usually safe though. > >Do you want to scan for Super I/O sensors? (YES/no): YES >Probing for `ITE 8702F Super IO Sensors' > Failed! (skipping family) >Probing for `Nat. Semi. PC87351 Super IO Fan Sensors' > Failed! (skipping family) >Probing for `SMSC 47B27x Super IO Fan Sensors' > Failed! (skipping family) >Probing for `VT1211 Super IO Sensors' > Failed! (skipping family) >Probing for `Winbond W83627EHF/EHG Super IO Sensors' > Failed! (skipping family) > >Do you want to scan for secondary Super I/O sensors? (YES/no): YES >Probing for `ITE 8702F Super IO Sensors' > Failed! (skipping family) >Probing for `Nat. Semi. PC87351 Super IO Fan Sensors' > Failed! (skipping family) >Probing for `SMSC 47B27x Super IO Fan Sensors' > Failed! (skipping family) >Probing for `VT1211 Super IO Sensors' > Failed! (skipping family) >Probing for `Winbond W83627EHF/EHG Super IO Sensors' > Failed! (skipping family) > > Now follows a summary of the probes I have just done. > Just press ENTER to continue: > >Driver `eeprom' (should be inserted): > Detects correctly: > * Bus `SMBus Via Pro adapter at 4100' > Busdriver `i2c-viapro', I2C address 0x50 > Chip `SPD EEPROM' (confidence: 8) > > >I will now generate the commands needed to load the I2C modules. > >To make the sensors modules behave correctly, add these lines to >/etc/modules: > >#----cut here---- ># I2C adapter drivers >i2c-viapro ># I2C chip drivers >eeprom >#----cut here---- > > > >I put these lines in my /etc/module files >I loaded them and can see the 2 modules in lsmod > >But when I launched sensors, I got this error message : > >Can't access procfs/sysfs file >Unable to find i2c bus information; >For 2.6 kernels, make sure you have mounted sysfs and libsensors >was compiled with sysfs support! >For older kernels, make sure you have done 'modprobe i2c-proc'! > >/sys is well mounted > >I m not sure if I have the sysfs support in my kernel (I don't how to check >this) but I believed it should ok in the 2.6 kernel > >Thanks for your help, Looks like there are no sensors in this laptop. I guess there are no hardware monitoring information in the BIOS. lm_sensors won't work on your system, sorry. -- Jean Delvare
