Ticket #2306 (closed defect: fixed)
W83781D on ISA detected but not in /sys
| Reported by: | ticket | Owned by: | khali |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | kernel | Version: | kernel |
| Keywords: | i2c-isa, w83781d | Cc: | mc-sensors@… |
Description (last modified by khali) (diff)
Hi all,
after the restructuring and removal of the i2c-isa module in Kernel 2.6.22, my w83781d does not detect the chip on ISA any more. (Hint: The help page still says: What to do if it inserts, but nothing happens? For an ISA sensor chip, did you also modprobe i2c-isa? It must be inserted. )
Are there any special kind of steps to do when switching from <2.6.22 to 2.6.22++? At least I did not find any ...
File outputs follow:
##################
Output sensors-detect (same for 2.6.21.5 and 2.6.24.2):
skynet10:/home/mc# sensors-detect
# sensors-detect revision 5108 (2008-01-22 13:22:47 +0100)
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): YES
Probing for PCI bus adapters...
Use driver `i2c-piix4' for device 0000:00:07.3: Intel 82371AB PIIX4 ACPI
We will now try to load each adapter module in turn.
Module `i2c-piix4' already loaded.
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: SMBus PIIX4 adapter at 5000 (i2c-0)
Do you want to scan it? (YES/no/selectively): YES
Client found at address 0x50
Handled by driver `eeprom' (already loaded), chip type `eeprom'
(note: this is probably NOT a sensor chip!)
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): YES
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... Success!
(confidence 8, driver `w83781d')
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
###########
sensors: (2.6.21.5): skynet10:/home/mc# sensors w83781d-isa-0290 Adapter: ISA adapter [...usual sensor data...] (2.6.24.2): No sensors detected
############
(2.6.21.5) skynet10:/home/mc# ll /sys/bus/i2c/devices/ total 0 drwxr-xr-x 2 root root 0 Mar 7 13:22 . drwxr-xr-x 4 root root 0 Mar 7 01:23 .. lrwxrwxrwx 1 root root 0 Mar 7 13:22 0-0050 -> ../../../devices/pci0000:00/0000:00:07.3/i2c-0/0-0050 lrwxrwxrwx 1 root root 0 Mar 7 13:22 9191-0290 -> ../../../devices/platform/i2c-9191/9191-0290 9191-0290 (from w83871d) is missing in Kernel 2.6.24.2.
Kernel config is identical (except for i2c-isa o.c., which does not exist any more) #################
skynet10:/home/mc# sensors -v sensors version 3.0.1 with libsensors version 3.0.0
dmesg gives no hints....
#################
Kind regards, Martin
Attachments
-
hwmon-w83781d-fix-pnp-io-conflict.patch
(2.5 KB) - added by khali
2 years ago.
- Fix resource conflict between w83781d and pnp
Change History
Note: See
TracTickets for help on using
tickets.
