I just upgraded my 8.0 system with an ECS K7S5A motherboard and an Athlon XP 2400+ with no significant problems. After running sensors-detect and accepting the default/offered options for tests, got the following apparently successful scan: Driver `sis5595' (should be inserted): Detects correctly: * ISA bus, undetermined address (Busdriver `i2c-isa') Chip `Silicon Integrated Systems SIS5595' (confidence: 9) I inserted the recommended changes into /etc/modules.conf and /etc/init.d/boot.local. After booting the modules are loaded, but 'sensors' displays bogus output. Is there a known problem with sensors (code or configuration) with the ECS K7S5A motherboard? # sensors sis5595-isa-8088 Adapter: ISA adapter Algorithm: ISA algorithm VCore 1: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM VCore 2: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM +3.3V: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM +5V: +6.85 V (min = +6.85 V, max = +6.85 V) ALARM fan1: 0 RPM (min = 0 RPM, div = 8) ALARM fan2: 0 RPM (min = 0 RPM, div = 8) ALARM temp: +51.2�C (limit = +51�C, hysteresis = +51�C) ALARM alarms: Board temperature input (usually LM75 chips) ALARM Thanks, Jim Cunning
On Mon, 30 Jun 2003, Jim Cunning wrote:
I just upgraded my 8.0 system with an ECS K7S5A motherboard and an Athlon XP 2400+ with no significant problems. After running sensors-detect and accepting the default/offered options for tests, got the following apparently successful scan:
Driver `sis5595' (should be inserted): Detects correctly: * ISA bus, undetermined address (Busdriver `i2c-isa') Chip `Silicon Integrated Systems SIS5595' (confidence: 9)
I inserted the recommended changes into /etc/modules.conf and /etc/init.d/boot.local. After booting the modules are loaded, but 'sensors' displays bogus output. Is there a known problem with sensors (code or configuration) with the ECS K7S5A motherboard?
# sensors sis5595-isa-8088 Adapter: ISA adapter Algorithm: ISA algorithm VCore 1: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM VCore 2: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM +3.3V: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM +5V: +6.85 V (min = +6.85 V, max = +6.85 V) ALARM fan1: 0 RPM (min = 0 RPM, div = 8) ALARM fan2: 0 RPM (min = 0 RPM, div = 8) ALARM temp: +51.2°C (limit = +51°C, hysteresis = +51°C) ALARM alarms: Board temperature input (usually LM75 chips) ALARM
Jim, I have a similar motherboard - but I have SuSE 8.2 using the k_deflt 2.4.20-4GB kernel. I could not load the i2c-sis5595 module at all, and sensors-detect also recommends i2c-sis645 to me. No sensors work (but of course they are fine on the BIOS boot). Attached is the output of sensors-detect if it is interesting to you. I will try again when I upgrade to 2.4.21 k_athlon. My guess is that the SuSE kernel isn't quite ready for this mobo and we need to find the mailing list of the hackers of those modules to go much further. Best regards, David # sensors-detect This program will help you to determine which I2C/SMBus modules you need to load to use lm_sensors most effectively. You need to have done a `make install', issued a `depmod -a' and made sure `/etc/modules.conf' (or `/etc/conf.modules') contains the appropriate module path before you can use some functions of this utility. Read doc/modules for more information. Also, you need to be `root', or at least have access to the /dev/i2c[-/]* files for some things if you do not have them already. 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. BIOS vendor (ACPI): AMI Could not find dmidecode, which should have been installed with lm_sensors. Runing dmidecode would help us determining your system vendor, which allows safer operations. Please provide one of the following: /usr/local/sbin/dmidecode /usr/sbin/dmidecode You can still go on, but you are encouraged to fix the problem first. 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 SIS735 Use driver `i2c-sis5595' for device 00:02.0: Silicon Integrated Systems SIS5595 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): Module loaded succesfully. Load `i2c-sis5595' (say NO if built into your kernel)? (YES/no): /lib/modules/2.4.20-4GB/kernel/drivers/i2c/busses/i2c-sis5595.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-4GB/kernel/drivers/i2c/busses/i2c-sis5595.o: insmod /lib/modules/2.4.20-4GB/kernel/drivers/i2c/busses/i2c-sis5595.o failed /lib/modules/2.4.20-4GB/kernel/drivers/i2c/busses/i2c-sis5595.o: insmod i2c-sis5595 failed Loading failed... skipping. Do you now want to be prompted for non-detectable adapters? (yes/NO): 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): 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 SiS645 adapter at 0x0c00 (Non-I2C SMBus adapter) Do you want to scan it? (YES/no/selectively): Client found at address 0x50 Probing for `Serial EEPROM'... Success! (confidence 8, driver `eeprom') Probing for `DDC monitor'... Failed! Client found at address 0x69 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. Do you want to scan the ISA bus? (YES/no): no 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 SiS645 adapter at 0x0c00' (Non-I2C SMBus adapter) Busdriver `i2c-sis645', I2C address 0x50 Chip `Serial EEPROM' (confidence: 8) 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 WARNING! If you have some things built into your kernel, the below list will contain too many modules. Skip the appropriate ones! To load everything that is needed, add this to some /etc/rc* file: #----cut here---- # I2C adapter drivers modprobe i2c-sis645 # I2C chip drivers modprobe eeprom #----cut here---- To make the sensors modules behave correctly, add these lines to either /etc/modules.conf or /etc/conf.modules: #----cut here---- # I2C module options alias char-major-89 i2c-dev #----cut here---- Do you want to generate /etc/sysconfig/lm_sensors? (YES/no): Copy /usr/share/doc/packages/sensors/prog/init/lm_sensors.init to /etc/init.d/lm_sensors for initialization at boot time.
On Wednesday 09 July 2003 20:48 pm, David wrote:
On Mon, 30 Jun 2003, Jim Cunning wrote:
I just upgraded my 8.0 system with an ECS K7S5A motherboard and an Athlon XP 2400+ with no significant problems. After running sensors-detect and accepting the default/offered options for tests, got the following apparently successful scan:
<snip>
Jim, I have a similar motherboard - but I have SuSE 8.2 using the k_deflt 2.4.20-4GB kernel. I could not load the i2c-sis5595 module at all, and sensors-detect also recommends i2c-sis645 to me. No sensors work (but of course they are fine on the BIOS boot). Attached is the output of sensors-detect if it is interesting to you.
<snip> I have the K7S5A m/b, an Athlon1400 with k_athlon-2.4.20-86 and SuSE8,2 Sensors works (sort of) - I need to tinker to sort out some of the readings. Anyway, in /etc/modules.conf I have alias char-major-89 i2c-dev /etc/init.d/boot.local has modprobe i2c-proc modprobe i2c-sis645 modprobe i2c-isa modprobe eeprom modprobe it87 And here's the output from sensors eeprom-i2c-0-50 Adapter: SMBus SiS645 adapter at 0x0c00 Algorithm: Non-I2C SMBus adapter Memory type: DDR SDRAM DIMM SPD Memory size (MB): 256 it87-isa-0290 Adapter: ISA adapter Algorithm: ISA algorithm VCore 1: +1.77 V (min = +1.53 V, max = +1.87 V) VCore 2: +2.48 V (min = +2.25 V, max = +2.75 V) +3.3V: +6.48 V (min = +2.96 V, max = +3.60 V) ALARM +5V: +4.72 V (min = +4.50 V, max = +5.48 V) +12V: +12.72 V (min = +11.36 V, max = +13.80 V) -12V: -1.51 V (min = -15.86 V, max = -13.40 V) ALARM -5V: +2.29 V (min = -10.13 V, max = -9.44 V) ALARM Stdby: +4.94 V (min = +4.50 V, max = +5.48 V) VBat: +3.37 V fan1: 4753 RPM (min = 3000 RPM, div = 2) fan2: 0 RPM (min = 3000 RPM, div = 2) ALARM fan3: 0 RPM (min = 3000 RPM, div = 2) ALARM Temp1/MB: +38°C (min = +20°C, max = +60°C) Temp2/CPU: -10°C (min = +20°C, max = +60°C) Temp3: +53°C (min = +20°C, max = +60°C) -- Vic Ayres http://www.buckiechoral.org.uk
participants (3)
-
David
-
Jim Cunning
-
Vic Ayres