Ticket #1408 (closed task)
Opened 7 years ago
unable to load i2c-sis645 (asus p4s8x-x | sis 648/963) (Examined/Solved - sensors version 2.8.0 / Linux 2.4.20-19.9custom)
| Reported by: | contact | Owned by: | somebody |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | hardware | Version: | |
| Keywords: | Cc: |
Description
hi,
here is sensors-detect output: (version 2.8.0)
BIOS vendor (ACPI): ASUS
System vendor (DMI): System Manufacturer
BIOS version (DMI): ASUS P4S8X-X ACPI BIOS Revision 1003
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):
Probing for PCI bus adapters...
Use driver 'i2c-sis645' for device 00:00.0: Silicon Integrated Systems SIS648
Probe succesfully concluded.
We will now try to load each adapter module in turn.
Load 'i2c-sis645' (say NO if built into your kernel)? (YES/no):
/lib/modules/2.4.20-19.9custom/kernel/drivers/i2c/i2c-sis645.o: init_module: No
such device
Hint: insmod errors can be caused by incorrect module parameters, including
invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.20-19.9custom/kernel/drivers/i2c/i2c-sis645.o: insmod
/lib/modules/2.4.20-19.9custom/kernel/drivers/i2c/i2c-sis645.o failed
/lib/modules/2.4.20-19.9custom/kernel/drivers/i2c/i2c-sis645.o: insmod
i2c-sis645 failed
Loading failed... skipping.
dmesg output:
i2c-core.o: i2c core module
i2c-sis645.o: version 2.6.5 (20020915)
i2c-sis645.o: Error: Can't find SiS645 host bridge!
i2c-sis645.o: SiS645 not detected, module not inserted.
i2c-core.o: i2c core module
i2c-dev.o: i2c /dev entries driver module
i2c-core.o: driver i2c-dev dummy driver registered.
lspci & lspci -n:
00:00.0 Host bridge: Silicon Integrated Systems [SiS]: Unknown device 0648 (rev 03)
00:01.0 PCI bridge: Silicon Integrated Systems [SiS] SiS 530 Virtual PCI-to-PCI
bridge (AGP)
00:02.0 ISA bridge: Silicon Integrated Systems [SiS]: Unknown device 0963 (rev 25)
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE]
00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] SiS7012
PCI Audio Accelerator (rev a0)
00:03.0 USB Controller: Silicon Integrated Systems [SiS] SiS7001 USB Controller
(rev 0f)
00:03.1 USB Controller: Silicon Integrated Systems [SiS] SiS7001 USB Controller
(rev 0f)
00:03.2 USB Controller: Silicon Integrated Systems [SiS] SiS7002 USB 2.0
00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 10/100
Ethernet (rev 91)
00:0d.0 Communication controller: Rockwell International HCF 56k
Data/Fax/Voice/Spkp? (w/Handset) Modem (rev 01)
01:00.0 VGA compatible controller: nVidia Corporation: Unknown device 0322 (rev a1)
00:00.0 Class 0600: 1039:0648 (rev 03)
00:01.0 Class 0604: 1039:0001
00:02.0 Class 0601: 1039:0963 (rev 25)
00:02.5 Class 0101: 1039:5513
00:02.7 Class 0401: 1039:7012 (rev a0)
00:03.0 Class 0c03: 1039:7001 (rev 0f)
00:03.1 Class 0c03: 1039:7001 (rev 0f)
00:03.2 Class 0c03: 1039:7002
00:04.0 Class 0200: 1039:0900 (rev 91)
00:0d.0 Class 0780: 127a:1025 (rev 01)
01:00.0 Class 0300: 10de:0322 (rev a1)
i think i have all modules in my kernel:
i2c/
dmi_scan.o
i2c-algo-bit.o
i2c-algo-pcf.o
i2c-ali1535.o
i2c-ali15x3.o
i2c-amd756.o
i2c-core.o
i2c-dev.o
i2c-elektor.o
i2c-elv.o
i2c-hydra.o
i2c-i801.o
i2c-i810.o
i2c-isa.o
i2c-philips-par.o
i2c-piix4.o
i2c-proc.o
i2c-sis5595.o
i2c-sis630.o
i2c-sis645.o
i2c-velleman.o
i2c-via.o
i2c-viapro.o
i2c-voodoo3.o
sensors/
adm1021.o
adm1024.o
adm1025.o
adm9240.o
bt869.o
ddcmon.o
ds1621.o
eeprom.o
fscpos.o
fscscy.o
gl518sm.o
gl520sm.o
it87.o
lm75.o
lm78.o
lm80.o
lm87.o
lm92.o
maxilife.o
mtp008.o
sensors.o
sis5595.o
smsc47m1.o
thmc50.o
via686a.o
vt1211.o
w83781d.o
i don't understand because when i boot with kernel-2.4.20-19.23.rh9.at (), it works!
when loading i2c-sis645, output is:
PCI: No IRQ known for interrupt pin B of device 00:02.1. Please try using
pci=biosirq.
Module loaded succesfully.
modprobe w83781d
and it is ok...
any idea??
--- we have a fix in CVS that may fix this.
Please try and let us know.
Follow up by email, ref. your ticket number.
MDS 8/24/03
