Ticket #2116 (closed defect: fixed)

Opened 7 years ago

Last modified 7 years ago

no sensors on ASUS A7VC

Reported by: corfiot_von_grek@… Owned by: ruik
Priority: major Milestone:
Component: hardware Version:
Keywords: Cc:

Description

Hi, I tried both via686a and w83781d and got no sensors. There is no newer BIOS available for my mboard.

detect found via686a

via686a complains about the need to force an address but i can't find one. If i force a random address i get sensor results but they are bogus.

I then tried w83781d after reading some posts online:

modprobe w83781d force_as99127f=0,0x2d <-- no sensors

modprobe w83781d force_as99127f=0,0x2d <-- duplicate subsensor 48, no sensors

Any ideas? Thanks in advance

--G

server:~ # i2cdetect -l
i2c-1   unknown         SMBus Via Pro adapter at e800           Algorithm unavailable
i2c-0   dummy           ISA main adapter                        ISA bus algorithm


server:~ # i2cdetect 1
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-1.
I will probe address range 0x03-0x77.
Continue? [Y/n] y
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          XX XX XX XX XX XX XX XX XX XX XX XX XX
10: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
20: XX XX XX XX XX XX XX XX XX XX XX XX XX 2d XX XX
30: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
40: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
50: UU UU XX XX XX XX XX XX XX XX XX XX XX XX XX XX
60: XX XX XX XX XX XX XX XX XX 69 XX XX XX XX XX XX
70: XX XX XX XX XX XX XX 77

server:~ # i2cdump 1 0x2d
No size specified (using byte-data access)
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-1, address 0x2d, mode byte
Continue? [Y/n] y
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 09 00 00 00 00 00 00 50 ad 05 00 00 00 00 00 00    ?......P??......
10: 00 00 00 80 00 00 00 80 00 00 00 00 00 00 04 00    ...?...?......?.
20: 9f 0f 00 00 04 00 00 00 81 20 00 a0 01 00 00 00    ??..?...? .??...
30: 00 00 00 10 00 00 80 00 00 00 40 00 00 00 00 a2    ...?..?...@....?
40: 09 00 00 00 00 00 00 50 ad 05 00 00 00 00 00 00    ?......P??......
50: 00 00 00 80 00 00 00 80 00 00 00 00 00 00 04 00    ...?...?......?.
60: 9f 0f 00 00 04 00 00 00 81 20 00 a0 01 00 00 00    ??..?...? .??...
70: 00 00 00 10 00 00 80 00 00 00 40 00 00 00 00 a2    ...?..?...@....?
80: 09 00 00 00 00 00 00 50 ad 05 00 00 00 00 00 00    ?......P??......
90: 00 00 00 80 00 00 00 80 00 00 00 00 00 00 04 00    ...?...?......?.
a0: 9f 0f 00 00 04 00 00 00 81 20 00 a0 01 00 00 00    ??..?...? .??...
b0: 00 00 00 10 00 00 80 00 00 00 40 00 00 00 00 a2    ...?..?...@....?
c0: 09 00 00 00 00 00 00 50 ad 05 00 00 00 00 00 00    ?......P??......
d0: 00 00 00 80 00 00 00 80 00 00 00 00 00 00 04 00    ...?...?......?.
e0: 9f 0f 00 00 04 00 00 00 81 20 00 a0 01 00 00 00    ??..?...? .??...
f0: 00 00 00 10 00 00 80 00 00 00 40 00 00 00 00 a2    ...?..?...@....?

Change History

  Changed 7 years ago by ticket

contact: corfiot_von_grek@…

  Changed 7 years ago by ruik

  • owner changed from somebody to ruik
  • status changed from new to assigned

Hi,

Sorry for the delay. Please can you attach the sensors-detect output?

Regards

Rudolf

follow-up: ↓ 4   Changed 7 years ago by ruik

  • reporter changed from ticket to corfiot_von_grek@…

in reply to: ↑ 3   Changed 7 years ago by ticket

server:~ # sensors-detect

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 `to-be-written' for device 01:00.0: S3 ProSavage? KM Use driver `i2c-viapro' for device 00:07.4: VIA Technologies VT82C686 Apollo ACPI Probe succesfully concluded.

We will now try to load each adapter module in turn. Load `to-be-written' (say NO if built into your kernel)? (YES/no): yes FATAL: Module to_be_written not found. Loading failed... skipping. Load `i2c-viapro' (say NO if built into your kernel)? (YES/no): yes Module loaded succesfully. 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 e800 Do you want to scan it? (YES/no/selectively): yes Client found at address 0x2d Probing for `Myson MTP008'... Failed! Probing for `National Semiconductor LM78'... Failed! Probing for `National Semiconductor LM78-J'... Failed! Probing for `National Semiconductor LM79'... Failed! Probing for `National Semiconductor LM80'... Failed! Probing for `National Semiconductor LM85 or LM96000'... Failed! Probing for `Analog Devices ADM1027, ADT7460 or ADT7463'... Failed! Probing for `SMSC EMC6D100 or EMC6D101'... Failed! Probing for `National Semiconductor LM87'... Failed! Probing for `National Semiconductor LM93'... Failed! Probing for `Winbond W83781D'... Failed! Probing for `Winbond W83782D'... Failed! Probing for `Winbond W83783S'... Failed! Probing for `Winbond W83791D'... Failed! Probing for `Winbond W83792D'... Failed! Probing for `Winbond W83791SD'... Failed! Probing for `Winbond W83627HF'... Failed! Probing for `Asus AS99127F (rev.1)'... Failed! Probing for `Asus AS99127F (rev.2)'... Failed! Probing for `Asus ASB100 Bach'... Failed! Probing for `Winbond W83L784R/AR'... Failed! Probing for `Winbond W83L785R'... Failed! Probing for `Genesys Logic GL518SM Revision 0x00'... Failed! Probing for `Genesys Logic GL518SM Revision 0x80'... Failed! Probing for `Genesys Logic GL520SM'... Failed! Probing for `Genesys Logic GL525SM'... Failed! Probing for `Analog Devices ADM9240'... Failed! Probing for `Dallas Semiconductor DS1780'... Failed! Probing for `National Semiconductor LM81'... Failed! Probing for `Analog Devices ADM1026'... Failed! Probing for `Analog Devices ADM1025'... Failed! Probing for `Philips NE1619'... Failed! Probing for `Analog Devices ADM1024'... Failed! Probing for `Analog Devices ADM1029'... Failed! Probing for `Analog Devices ADM1030'... Failed! Probing for `Analog Devices ADM1031'... Failed! Probing for `Analog Devices ADM1022'... Failed! Probing for `Texas Instruments THMC50'... Failed! Probing for `ITE IT8705F / IT8712F / SiS 950'... Failed! Probing for `ALi M5879'... Failed! 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 0x51 Probing for `SPD EEPROM'... Success!

(confidence 8, driver `eeprom')

Client found at address 0x69 Client found at address 0x77 Probing for `Asus ASM58 Mozart-2'... Failed! Probing for `Asus AS2K129R Mozart-2'... Success!

(confidence 5, driver `to-be-written')

Probing for `Asus Mozart-2'... Failed!

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 W83697HF'

Trying address 0x0290... Failed!

Probing for `Silicon Integrated Systems SIS5595'

Trying general detect... Failed!

Probing for `VIA Technologies VT82C686 Integrated Sensors'

Trying general detect... Success!

(confidence 9, driver `via686a')

Probing for `VIA Technologies VT8231 Integrated Sensors'

Trying general detect... Failed!

Probing for `ITE IT8705F / IT8712F / 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)

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)

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 e800' (Algorithm unavailable) Busdriver `i2c-viapro', I2C address 0x50 Chip `SPD EEPROM' (confidence: 8)
  • Bus `SMBus Via Pro adapter at e800' (Algorithm unavailable) Busdriver `i2c-viapro', I2C address 0x51 Chip `SPD EEPROM' (confidence: 8)

Driver `to-be-written' (should be inserted):

Detects correctly:

  • Bus `SMBus Via Pro adapter at e800' (Algorithm unavailable) Busdriver `i2c-viapro', I2C address 0x77 Chip `Asus AS2K129R Mozart-2' (confidence: 5)

Driver `via686a' (should be inserted):

Detects correctly:

  • ISA bus, undetermined address (Busdriver `i2c-isa')

Hint: Try forcing the chip address. Consult the documentation of particular chip for details and address value.

Chip `VIA Technologies VT82C686 Integrated Sensors' (confidence: 9)

I will now generate the commands needed to load the I2C modules. Sometimes, a chip is available both through the ISA bus and an I2C bus. ISA bus access is faster, but you need to load an additional driver module for it. If you have the choice, do you want to use the ISA bus or the I2C/SMBus (ISA/smbus)? smbus

To make the sensors modules behave correctly, add these lines to /etc/modprobe.conf:

#----cut here---- # I2C module options alias char-major-89 i2c-dev #----cut here----

To load everything that is needed, add this to some /etc/rc* file:

#----cut here---- # I2C adapter drivers modprobe i2c-viapro modprobe i2c-isa # I2C chip drivers modprobe eeprom # no driver for Asus AS2K129R Mozart-2 yet modprobe via686a # sleep 2 # optional /usr/bin/sensors -s # recommended #----cut here----

WARNING! If you have some things built into your kernel, the list above will contain too many modules. Skip the appropriate ones! You really should try these commands right now to make sure everything is working properly. Monitoring programs won't work until it's done.

Do you want to generate /etc/sysconfig/lm_sensors? (YES/no): yes Copy /usr/share/doc/packages/sensors/prog/init/lm_sensors.init.suse to /etc/init.d/lm_sensors for initialization at boot time. server:~ #

  Changed 7 years ago by ruik

  • status changed from assigned to closed
  • resolution set to fixed

Hello, you need the asm58 driver. We have one for 2.6.15. It never made it into mainline. You just need this patch  http://lists.lm-sensors.org/pipermail/lm-sensors/2006-March/015735.html

Hope it helps,

Regards

Rudolf

Note: See TracTickets for help on using tickets.