LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices



Reply
 
Search this Thread
Old 07-11-2007, 11:58 AM   #1
macroron
LQ Newbie
 
Registered: Jul 2005
Posts: 15

Rep: Reputation: 0
Conky - sensors-detect > modprobe i2c-nforce2 > WARNING: Error inserting i2c_core...


I have installed lm_sensors-2.10.3-i486-1.tgz successfully, but can not
read system temp and fan in Conky system monitor. I have had this
problem before. I think it had something to do with the "linking" of
kernel source info, but I can't find the solution again. Can anyone help
me?

Here are my sensors-detect, modprobe, sensors, lsmod, and grep dmesg
logs:

1. Sensors-Detect Log:

# sensors-detect

# sensors-detect revision 4348 (2007-03-18 02:45:21 -0700)

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):
Probing for PCI bus adapters...
Use driver `i2c-nforce2' for device 0000:00:01.1: nVidia Corporation
nForce4 SMB
us (MCP)

We will now try to load each adapter module in turn.
Module `i2c-nforce2' 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.
Do you want to load `i2c-dev' now? (YES/no):
WARNING: Error inserting i2c_core
(/lib/modules/2.6.21.5-smp/kernel/drivers/i2c/
i2c-core.ko): Invalid module format
Module loaded successfully.

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: NVIDIA i2c adapter 2 at 1:00.0 (i2c-4)
Do you want to scan it? (YES/no/selectively):

Next adapter: NVIDIA i2c adapter 1 at 1:00.0 (i2c-3)
Do you want to scan it? (YES/no/selectively):

Next adapter: NVIDIA i2c adapter 0 at 1:00.0 (i2c-2)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x50
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
Probing for `EDID EEPROM'... Success!
(confidence 8, driver `eeprom'), other addresses: 0x51 0x52 0x53
0x54 0x55 0
x56 0x57
Probing for `Maxim MAX6900'... No

Next adapter: SMBus nForce2 adapter at 4c40 (i2c-1)
Do you want to scan it? (YES/no/selectively):

Next adapter: SMBus nForce2 adapter at 4c00 (i2c-0)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x50
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'...
Success!
(confidence 8, driver `eeprom')
Probing for `EDID EEPROM'... No
Probing for `Maxim MAX6900'... No
Client found at address 0x51
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'...
Success!
(confidence 8, driver `eeprom')

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): 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... No
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

Some Super I/O chips may also contain sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): Probing for
Super-I/O at 0x
2e/0x2f
Trying family `ITE'... Yes
Found `ITE IT8712F Super IO Sensors' Success!
(address 0x290, driver `it87')
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No
Probing for Super-I/O at 0x4e/0x4f
Trying family `ITE'... No
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No

Some CPUs or memory controllers may also contain embedded sensors.
Do you want to scan for them? (YES/no):
AMD K8 thermal sensors... Success!
(driver `k8temp')
Intel Core family thermal sensor... No
Intel AMB FB-DIMM thermal sensor... 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 `NVIDIA i2c adapter 0 at 1:00.0'
Busdriver `UNKNOWN', I2C address 0x50 (and 0x51 0x52 0x53 0x54 0x55
0x56 0x5
7)
Chip `EDID EEPROM' (confidence: 8)
* Bus `SMBus nForce2 adapter at 4c00'
Busdriver `i2c-nforce2', I2C address 0x50
Chip `SPD EEPROM' (confidence: 8)
* Bus `SMBus nForce2 adapter at 4c00'
Busdriver `i2c-nforce2', I2C address 0x51
Chip `SPD EEPROM' (confidence: 8)

EEPROMs are *NOT* sensors! They are data storage chips commonly
found on memory modules (SPD), in monitors (EDID), or in some
laptops, for example.

Driver `it87' (should be inserted):
Detects correctly:
* ISA bus, address 0x290
Chip `ITE IT8712F Super IO Sensors' (confidence: 9)

Driver `k8temp' (should be inserted):
Detects correctly:
* Chip `AMD K8 thermal sensors' (confidence: 9)

I will now generate the commands needed to load the required modules.
Just press ENTER to continue:

To make the sensors modules behave correctly, add these lines to
/etc/modules.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 unknown adapter NVIDIA i2c adapter 0 at 1:00.0
# modprobe unknown adapter NVIDIA i2c adapter 1 at 1:00.0
# modprobe unknown adapter NVIDIA i2c adapter 2 at 1:00.0
modprobe i2c-nforce2
# Chip drivers
modprobe eeprom
modprobe it87
modprobe k8temp
# sleep 2 # optional
/usr/bin/sensors -s # recommended
#----cut here----

If you have some drivers 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 the needed
modules are loaded.

Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO):

---

2. Modprobe Log:

# modprobe i2c-nforce2

WARNING: Error inserting i2c_core
(/lib/modules/2.6.21.5-smp/kernel/drivers/i2c/i2c-core.ko): Invalid
module format

# modprobe eeprom

WARNING: Error inserting i2c_core
(/lib/modules/2.6.21.5-smp/kernel/drivers/i2c/i2c-core.ko): Invalid
module format

# modprobe it87

WARNING: Error inserting i2c_core
(/lib/modules/2.6.21.5-smp/kernel/drivers/i2c/i2c-core.ko): Invalid
module format

# modprobe k8temp
# /usr/bin/sensors -s

---

3. Sensors Log:

# sensors

k8temp-pci-00c3
Adapter: PCI adapter
Core0 Temp:
+29C

it8712-isa-0290
Adapter: ISA adapter
VCore 1: +1.09 V (min = +0.00 V, max = +4.08 V) ALARM
VCore 2: +0.00 V (min = +0.00 V, max = +4.08 V) ALARM
+3.3V: +3.28 V (min = +0.00 V, max = +4.08 V) ALARM
+5V: +4.89 V (min = +0.00 V, max = +6.85 V) ALARM
+12V: +11.78 V (min = +0.00 V, max = +16.32 V) ALARM
-12V: -4.90 V (min = -27.36 V, max = +3.93 V) ALARM
-5V: -13.64 V (min = -13.64 V, max = +4.03 V) ALARM
Stdby: +4.89 V (min = +0.00 V, max = +6.85 V) ALARM
VBat: +3.04 V
fan1: 1394 RPM (min = 811 RPM, div = 8) ALARM
fan2: 2136 RPM (min = 0 RPM, div = 8)
fan3: 0 RPM (min = 0 RPM, div = 8)
M/B Temp: +36C (low = -1C, high = +127C) sensor =
thermistor ALARM
CPU Temp: +38C (low = -1C, high = +127C) sensor =
thermistor ALARM
Temp3: +25C (low = -1C, high = +127C) sensor =
thermistor ALARM

---

4. lsmod log:

# lsmod
Module Size Used by
it87 20880 0
hwmon_vid 6784 1 it87
i2c_isa 7808 1 it87
eeprom 9616 0
i2c_dev 9732 0
snd_seq_dummy 6788 0
snd_seq_oss 32896 0
snd_seq_midi_event 10112 1 snd_seq_oss
snd_seq 50640 5
snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device 10508 3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_pcm_oss 42784 0
snd_mixer_oss 18048 1 snd_pcm_oss
ipv6 254496 14
ipt_LOG 10112 1
xt_tcpudp 7040 3
iptable_filter 6400 1
ip_tables 14276 1 iptable_filter
x_tables 15748 3 ipt_LOG,xt_tcpudp,ip_tables
cpufreq_ondemand 10508 1
powernow_k8 14112 0
freq_table 7936 2 cpufreq_ondemand,powernow_k8
processor 24552 1 powernow_k8
capability 7304 0
commoncap 9344 1 capability
lp 13736 0
parport_pc 27812 1
parport 34760 2 lp,parport_pc
pcspkr 6528 0
psmouse 39048 0
serio_raw 9220 0
nvidia 7241236 25
agpgart 31432 1 nvidia
sg 30364 0
snd_intel8x0 32412 0
snd_ac97_codec 98980 1 snd_intel8x0
ac97_bus 6016 1 snd_ac97_codec
snd_pcm 72068 3 snd_pcm_oss,snd_intel8x0,snd_ac97_codec
snd_timer 22532 2 snd_seq,snd_pcm
snd 47204 9
snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_intel8x0,snd_ac97_codec,snd_pcm,snd _timer
pata_amd 13964 0
ata_generic 9220 0
soundcore 9824 1 snd
snd_page_alloc 11528 2 snd_intel8x0,snd_pcm
i2c_nforce2 8704 0
k8temp 8320 0
hwmon 6404 2 it87,k8temp
forcedeth 46728 0
shpchp 33172 0
evdev 11904 1

---

5. grep dmesg log:

$ cat /var/log/dmesg | grep modprobe
$ cat /var/log/dmesg | grep modules
$ cat /var/log/dmesg | grep WARNING
$ cat /var/log/dmesg | grep kernel

Memory: 1029484k/1048512k available (6215k kernel code, 18360k reserved,
2017k data, 392k init, 131008k highmem)
virtual kernel memory layout:
OCFS2 User DLM kernel interface loaded
Freeing unused kernel memory: 392k freed
i2c_core: exports duplicate symbol i2c_smbus_write_i2c_block_data (owned
by kernel)
i2c_core: exports duplicate symbol i2c_smbus_write_i2c_block_data (owned
by kernel)
nvidia: module license 'NVIDIA' taints kernel.
usbhid: exports duplicate symbol hiddev_hid_event (owned by kernel)

$ cat /var/log/dmesg | grep i2c_core

i2c_core: exports duplicate symbol i2c_smbus_write_i2c_block_data (owned
by kernel)
i2c_core: exports duplicate symbol i2c_smbus_write_i2c_block_data (owned
by kernel)

$ cat /var/log/dmesg | grep sensors
$ cat /var/log/dmesg | grep lmsensors

---

$ uname -a

Linux slack 2.6.21.5-smp #2 SMP Tue Jun 19 14:58:11 CDT 2007 i686 AMD
Athlon(tm) 64 Processor 3000+ AuthenticAMD GNU/Linux

motherboard:

Asus A8NE

---
ron@slack:~$
 
Old 07-12-2007, 03:29 PM   #2
Road_map
Member
 
Registered: Jan 2007
Distribution: Slackware
Posts: 341

Rep: Reputation: 31
I have a K8N4-E motherboard. I got the same error with huge kernel. I switched to generic kernel and errors are gone. I also must to add append="acpi=off" in /etc/lilo.conf.
 
Old 07-12-2007, 04:10 PM   #3
macroron
LQ Newbie
 
Registered: Jul 2005
Posts: 15

Original Poster
Rep: Reputation: 0
Thank You,

I'll try the generic kernel.

--
macroron
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
WARNING: Error inserting freq_table Martin Pail Fedora 6 04-15-2007 03:28 PM
modprobe: FATAL: Error inserting hw_random logicalfuzz Linux - General 7 09-14-2005 11:37 PM
i2c and lm_sensors, sensors-detect johnnydangerous Fedora 2 03-15-2005 05:28 PM
modprobe: FATAL: Error inserting apm OneManArmy Linux - Software 2 08-21-2004 08:50 PM
modprobe: error inserting floppy borrrden Fedora 1 06-01-2004 01:33 PM


All times are GMT -5. The time now is 04:36 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration