| View previous topic :: View next topic |
| Author |
Message |
p3nguin
Apprentice
Joined: 01 Jul 2003
Posts: 188
Location: ~/
|
 Posted: Mon Sep 15, 2003 7:24 pm Post subject: problem with lm-sensors |
 |
|
I moduled most everything under i2c in my kernel like lm-sensors wanted and yet when i try and emerge it i keep getting this: | Code: | !!! ERROR: sys-apps/lm-sensors-2.7.0-r1 failed.
!!! Function src_compile, Line 45, Exitcode 2
!!! lm_sensors requires the source of a compatible kernel\nversion installed in /usr/src/linux and >=i2c-2.7.0 support built as a modules this support is included in gentoo-sources as of 2.4.20-r1
|
| Code: | root@nuronet linux # cd /usr/src
root@nuronet src # ls -l
total 2
lrwxrwxrwx 1 root root 22 Aug 5 23:36 linux -> linux-2.4.20-gentoo-r5
drwxr-xr-x 16 root root 960 Sep 15 13:57 linux-2.4.20-gentoo-r5
drwxr-xr-x 16 root root 656 Aug 30 23:09 linux-2.4.20-gentoo-r6
lrwxrwxrwx 1 root root 14 Aug 13 20:01 linux-2.4.20-r5 -> /usr/src/linux
lrwxrwxrwx 1 root root 14 Aug 13 19:59 proxy-2.4.20-gentoo-r5 -> /usr/src/linux
root@nuronet src # cd /usr/src/linux
root@nuronet linux # ls -l
total 3594
-rw-r--r-- 1 root root 18691 Aug 5 23:36 COPYING
-rw-r--r-- 1 root root 79549 Aug 5 23:36 CREDITS
-rw-r--r-- 1 root root 13176 Aug 5 23:36 Changelog.rmap
drwxr-xr-x 31 root root 3680 Aug 5 23:36 Documentation
-rw-r--r-- 1 root root 43694 Aug 5 23:36 MAINTAINERS
-rw-r--r-- 1 root root 43425 Aug 5 23:36 MAINTAINERS~
-rw-r--r-- 1 root root 19207 Aug 5 23:36 Makefile
-rw-r--r-- 1 root root 19149 Aug 5 23:36 Makefile~
-rw-r--r-- 1 root root 14239 Aug 5 23:36 README
-rw-r--r-- 1 root root 2815 Aug 5 23:36 REPORTING-BUGS
-rw-r--r-- 1 root root 9601 Aug 5 23:36 Rules.make
-rw-r--r-- 1 root root 529101 Sep 15 13:57 System.map
drwxr-xr-x 19 root root 456 Aug 5 23:36 arch
drwxr-xr-x 5 root root 320 Sep 15 13:57 crypto
drwxr-xr-x 43 root root 1104 Aug 5 23:49 drivers
drwxr-xr-x 48 root root 4968 Sep 15 13:56 fs
drwxr-xr-x 2 root root 2112 Sep 15 13:57 grsecurity
drwxr-xr-x 28 root root 768 Sep 15 13:52 include
drwxr-xr-x 2 root root 280 Sep 15 13:53 init
drwxr-xr-x 2 root root 496 Sep 15 13:57 ipc
drwxr-xr-x 2 root root 2832 Sep 15 13:53 kernel
-rw-r--r-- 1 root root 30879 Aug 5 23:36 kernel-config
drwxr-xr-x 4 root root 1344 Sep 15 13:57 lib
lrwxrwxrwx 1 root root 14 Aug 13 19:10 linux -> /usr/src/linux
drwxr-xr-x 2 root root 2200 Sep 15 13:55 mm
drwxr-xr-x 29 root root 1336 Sep 15 13:57 net
-rw-r--r-- 1 root root 29158 Aug 5 23:36 patches.txt
drwxr-xr-x 4 root root 1120 Aug 13 19:29 scripts
-rwxr-xr-x 1 root root 2951105 Sep 15 13:57 vmlinux
|
Last edited by p3nguin on Mon Sep 15, 2003 8:15 pm; edited 1 time in total |
|
| Back to top |
|
 |
BackSeat
Apprentice
Joined: 12 Apr 2002
Posts: 242
Location: Reading, UK
|
| Posted: Mon Sep 15, 2003 7:48 pm Post subject: |
|
|
Make sure /usr/src/linux points to the sources for the kernel you are actually running (check with 'uname -a'). Emerge i2c (even if it is already installed) before emerge-ing lm-sensors.
Any better?
BS |
|
| Back to top |
|
|
BackSeat
Apprentice
Joined: 12 Apr 2002
Posts: 242
Location: Reading, UK
|
| Posted: Mon Sep 15, 2003 7:50 pm Post subject: |
|
|
Make sure /usr/src/linux points to the sources for the kernel you are actually running (check with 'uname -a'). Emerge i2c (even if it is already installed) before emerge-ing lm-sensors.
Any better?
BS |
|
| Back to top |
|
|
BackSeat
Apprentice
Joined: 12 Apr 2002
Posts: 242
Location: Reading, UK
|
| Posted: Mon Sep 15, 2003 7:53 pm Post subject: |
|
|
Make sure /usr/src/linux points to the sources for the kernel you are actually running (check with 'uname -a'). Emerge i2c (even if it is already installed) before emerge-ing lm-sensors.
Any better?
BS |
|
| Back to top |
|
|
p3nguin
Apprentice
Joined: 01 Jul 2003
Posts: 188
Location: ~/
|
| Posted: Mon Sep 15, 2003 8:02 pm Post subject: |
|
|
| yea, its pointing to the wrong one,...damnit...thanks |
|
| Back to top |
|
|
p3nguin
Apprentice
Joined: 01 Jul 2003
Posts: 188
Location: ~/
|
| Posted: Mon Sep 15, 2003 8:06 pm Post subject: |
|
|
its pointing to | Code: | | linux -> /usr/src/linux |
where should it be pointing? I ran menuconfig from within /usr/src/linux and cp that bzImage to /boot...the correct kernel is in /boot. So where should that sym link be going to? | Code: | root@nuronet linux # cd /usr/src
root@nuronet src # ls -l
total 2
lrwxrwxrwx 1 root root 22 Aug 5 23:36 linux -> linux-2.4.20-gentoo-r5
drwxr-xr-x 16 root root 960 Sep 15 13:57 linux-2.4.20-gentoo-r5
drwxr-xr-x 16 root root 656 Aug 30 23:09 linux-2.4.20-gentoo-r6
lrwxrwxrwx 1 root root 14 Aug 13 20:01 linux-2.4.20-r5 -> /usr/src/linux
lrwxrwxrwx 1 root root 14 Aug 13 19:59 proxy-2.4.20-gentoo-r5 -> /usr/src/linux
root@nuronet src # cd /usr/src/linux
root@nuronet linux # ls -l
total 3594
-rw-r--r-- 1 root root 18691 Aug 5 23:36 COPYING
-rw-r--r-- 1 root root 79549 Aug 5 23:36 CREDITS
-rw-r--r-- 1 root root 13176 Aug 5 23:36 Changelog.rmap
drwxr-xr-x 31 root root 3680 Aug 5 23:36 Documentation
-rw-r--r-- 1 root root 43694 Aug 5 23:36 MAINTAINERS
-rw-r--r-- 1 root root 43425 Aug 5 23:36 MAINTAINERS~
-rw-r--r-- 1 root root 19207 Aug 5 23:36 Makefile
-rw-r--r-- 1 root root 19149 Aug 5 23:36 Makefile~
-rw-r--r-- 1 root root 14239 Aug 5 23:36 README
-rw-r--r-- 1 root root 2815 Aug 5 23:36 REPORTING-BUGS
-rw-r--r-- 1 root root 9601 Aug 5 23:36 Rules.make
-rw-r--r-- 1 root root 529101 Sep 15 13:57 System.map
drwxr-xr-x 19 root root 456 Aug 5 23:36 arch
drwxr-xr-x 5 root root 320 Sep 15 13:57 crypto
drwxr-xr-x 43 root root 1104 Aug 5 23:49 drivers
drwxr-xr-x 48 root root 4968 Sep 15 13:56 fs
drwxr-xr-x 2 root root 2112 Sep 15 13:57 grsecurity
drwxr-xr-x 28 root root 768 Sep 15 13:52 include
drwxr-xr-x 2 root root 280 Sep 15 13:53 init
drwxr-xr-x 2 root root 496 Sep 15 13:57 ipc
drwxr-xr-x 2 root root 2832 Sep 15 13:53 kernel
-rw-r--r-- 1 root root 30879 Aug 5 23:36 kernel-config
drwxr-xr-x 4 root root 1344 Sep 15 13:57 lib
lrwxrwxrwx 1 root root 14 Aug 13 19:10 linux -> /usr/src/linux
drwxr-xr-x 2 root root 2200 Sep 15 13:55 mm
drwxr-xr-x 29 root root 1336 Sep 15 13:57 net
-rw-r--r-- 1 root root 29158 Aug 5 23:36 patches.txt
drwxr-xr-x 4 root root 1120 Aug 13 19:29 scripts
-rwxr-xr-x 1 root root 2951105 Sep 15 13:57 vmlinux
|
though when i goto /usr/src/linux it goes to the kernel that has the "m" for i2c but when i do uname -a it shows a date of the kernel that is last month |
|
| Back to top |
|
|
BackSeat
Apprentice
Joined: 12 Apr 2002
Posts: 242
Location: Reading, UK
|
| Posted: Mon Sep 15, 2003 10:38 pm Post subject: |
|
|
"make menuconfig" does not make the kernel. You need to then run something like: | Code: | | make dep && make clean bzImage modules modules_install |
and then copy the kernel from /usr/src/linux/arch/i386/boot/bzImage to /boot (remembering to mount /boot first). It looks as if your /usr/src/linux does point to the kernel sources, although the "linux-2.4.20-r5" link is confusing and should probably be removed.
BS |
|
| Back to top |
|
|
p3nguin
Apprentice
Joined: 01 Jul 2003
Posts: 188
Location: ~/
|
| Posted: Mon Sep 15, 2003 11:00 pm Post subject: |
|
|
| Quote: | Code:
make dep && make clean bzImage modules modules_install |
this i know.....i did this. is there anything else you notice i should do? |
|
| Back to top |
|
|
p3nguin
Apprentice
Joined: 01 Jul 2003
Posts: 188
Location: ~/
|
| Posted: Mon Sep 15, 2003 11:04 pm Post subject: |
|
|
i just modprobed i2c-dev so it is infact using the new kernel.
just noticed this as well.... | Code: | kernel/busses/i2c-amd8111.c:25:2: #error Your i2c is too old - i2c-2.7.0 or grea
ter required!
kernel/busses/i2c-amd8111.c: In function `amd8111_access':
kernel/busses/i2c-amd8111.c:238: `I2C_CLIENT_PEC' undeclared (first use in this
function)
kernel/busses/i2c-amd8111.c:238: (Each undeclared identifier is reported only on
ce
kernel/busses/i2c-amd8111.c:238: for each function it appears in.)
kernel/busses/i2c-amd8111.c:298: `I2C_SMBUS_BLOCK_PROC_CALL' undeclared (first u
se in this function)
kernel/busses/i2c-amd8111.c:309: `I2C_SMBUS_WORD_DATA_PEC' undeclared (first use
in this function)
kernel/busses/i2c-amd8111.c:310: `I2C_SMBUS_BLOCK_DATA_PEC' undeclared (first us
e in this function)
kernel/busses/i2c-amd8111.c:311: `I2C_SMBUS_PROC_CALL_PEC' undeclared (first use
in this function)
kernel/busses/i2c-amd8111.c:312: `I2C_SMBUS_BLOCK_PROC_CALL_PEC' undeclared (fir
st use in this function)
kernel/busses/i2c-amd8111.c: In function `amd8111_func':
kernel/busses/i2c-amd8111.c:385: `I2C_FUNC_SMBUS_BLOCK_PROC_CALL' undeclared (fi
rst use in this function)
kernel/busses/i2c-amd8111.c:386: `I2C_FUNC_SMBUS_HWPEC_CALC' undeclared (first u
se in this function)
kernel/busses/i2c-amd8111.c: In function `amd8111_probe':
kernel/busses/i2c-amd8111.c:426: `I2C_HW_SMBUS_AMD8111' undeclared (first use in
this function)
make: *** [kernel/busses/i2c-amd8111.o] Error 1
make: *** Waiting for unfinished jobs....
!!! ERROR: sys-apps/lm-sensors-2.7.0-r1 failed.
!!! Function src_compile, Line 45, Exitcode 2
!!! lm_sensors requires the source of a compatible kernel\nversion installed in
/usr/src/linux and >=i2c-2.7.0 support built as a modules this support is includ
ed in gentoo-sources as of 2.4.20-r1
|
|
|
| Back to top |
|
|
p3nguin
Apprentice
Joined: 01 Jul 2003
Posts: 188
Location: ~/
|
| Posted: Wed Sep 17, 2003 2:51 am Post subject: |
|
|
| anyone have any idea? |
|
| Back to top |
|
|
dmarner
n00b
Joined: 25 Mar 2003
Posts: 5
Location: Morgantown, WV, US
|
| Posted: Wed Sep 17, 2003 4:30 am Post subject: |
|
|
| I was having the same problem. An "emerge i2c" before doing the "emerge lmsensors" fixed it. I think you need to re-run that every time you install a new kernel. |
|
| Back to top |
|
|
p3nguin
Apprentice
Joined: 01 Jul 2003
Posts: 188
Location: ~/
|
| Posted: Thu Sep 18, 2003 5:43 pm Post subject: |
|
|
k, i finally got it emerged. I modprobed i2c-proc then i ran sensors-detect.
| Code: | sensors-detect
BIOS vendor (ACPI): Nvidia
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 `i2c-riva' for device 03:00.0: GeForce2 GTS
Probe succesfully concluded.
We will now try to load each adapter module in turn.
Load `i2c-riva' (say NO if built into your kernel)? (YES/no): yes
modprobe: Can't locate module i2c-riva
Loading failed... skipping. |
this is what I have in my kernel...
| Code: | <M> I2C support x x
x x <M> I2C bit-banging interfaces x x
x x < > Philips style parallel port adapter x x
x x < > ELV adapter x x
x x < > Velleman K9000 adapter x x
x x < > Basic I2C on Parallel Port x x
x x <M> I2C PCF 8584 interfaces x x
x x < > Elektor ISA card x x
x x < > PCF on EPP port x x
x x <M> I2C device interface x x
x x <M> I2C /proc interface (required for hardware sensors) |
Im just not sure what else i need to do...I looked on their site and it said that the driver it needs is a i2c-nforce2 driver...what do i need to do? |
|
| Back to top |
|
|
p3nguin
Apprentice
Joined: 01 Jul 2003
Posts: 188
Location: ~/
|
| Posted: Fri Sep 19, 2003 2:52 pm Post subject: |
|
|
| can anyone help me out? |
|
| Back to top |
|
|
BackSeat
Apprentice
Joined: 12 Apr 2002
Posts: 242
Location: Reading, UK
|
| Posted: Fri Sep 19, 2003 2:55 pm Post subject: |
|
|
Did you continue 'sensors-detect' to completion? It will fail in certain places, but let it run to completion.
BS |
|
| Back to top |
|
|
p3nguin
Apprentice
Joined: 01 Jul 2003
Posts: 188
Location: ~/
|
| Posted: Fri Sep 19, 2003 4:03 pm Post subject: |
|
|
| yes i did...I just kept hitting yes to have it try and load different modules and it completed. Still said no chips found. |
|
| Back to top |
|
|
BackSeat
Apprentice
Joined: 12 Apr 2002
Posts: 242
Location: Reading, UK
|
| Posted: Fri Sep 19, 2003 4:11 pm Post subject: |
|
|
Does your motherboard have sensor chips? What motherboard is it?
BS |
|
| Back to top |
|
|
p3nguin
Apprentice
Joined: 01 Jul 2003
Posts: 188
Location: ~/
|
| Posted: Fri Sep 19, 2003 4:22 pm Post subject: |
|
|
| its the GIGABYTE 7N400 PRO2 400FSB MOTHERBOARD. |
|
| Back to top |
|
|
manywele
l33t
Joined: 12 Jul 2003
Posts: 739
Location: Inside
|
| Posted: Fri Sep 19, 2003 9:38 pm Post subject: |
|
|
The I2C modules in the kernel won't work with lm-sensors 2.7.0, they're too old. Emerging i2c should get the i2c-2.7.0 modules, compile them and put them in /lib/modules/your_kernel/misc so all you need in your kernel is to have i2c enabled as a module, the actual modules being loaded are from the i2c ebuild. When sensors-detect tried to load the i2c-riva modules it said it couldn't locate it, not that it couldn't load it. Is it in /lib/modules/? Is uname -r pointing to where in /lib/modules the drivers are being installed?
If it's the i2c-nforce2 you need that it says here (http://www2.lm-sensors.nu/~lm78/newdrivers.html) that support started in 2.8.0. Maybe try getting lm-sensors and i2c 2.8.0? It's in portage but masked. |
|
| Back to top |
|
|
p3nguin
Apprentice
Joined: 01 Jul 2003
Posts: 188
Location: ~/
|
| Posted: Sat Sep 20, 2003 6:33 pm Post subject: |
|
|
hmm im not seeing any masked 2.8 versions and I just emerged rsync...I also tried | Code: | | ACCEPT_KEYWORDS="~x86" emerge -s i2c |
|
|
| Back to top |
|
|
manywele
l33t
Joined: 12 Jul 2003
Posts: 739
Location: Inside
|
| Posted: Sat Sep 20, 2003 8:17 pm Post subject: |
|
|
| It's masked in /usr/portage/profiles/package.mask. If you look in /usr/portage/sys-apps/i2c there is an ebuild for it. |
|
| Back to top |
|
|
p3nguin
Apprentice
Joined: 01 Jul 2003
Posts: 188
Location: ~/
|
| Posted: Sun Sep 21, 2003 7:49 pm Post subject: |
|
|
ok, emerged it. then got this | Code: | I2C modules installed ...
*
* IMPORTANT ... if you are installing this package you need to
* IMPORTANT ... *disable* kernel I2C support OR *modularize it*
* IMPORTANT ... if your 2.4.x kernel is patched with such support |
So do i need to now rmmod everything with i2c and then modprobe i2c-riva? |
|
| Back to top |
|
|
manywele
l33t
Joined: 12 Jul 2003
Posts: 739
Location: Inside
|
| Posted: Sun Sep 21, 2003 8:28 pm Post subject: |
|
|
Have you run sensors-detect?
As long as i2c is enabled as a module in your kernel and not compiled directly in everything should be ok. The other i2c modules you enabled in the kernel shouldn't matter (I think). But what the hell, rmmod everything, run sensors-detect and do what it says.
Good luck. |
|
| Back to top |
|
|
p3nguin
Apprentice
Joined: 01 Jul 2003
Posts: 188
Location: ~/
|
| Posted: Sun Sep 21, 2003 9:38 pm Post subject: |
|
|
well i rmmod everything and ran sensors-detect
| Code: | BIOS vendor (ACPI): Nvidia
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 `i2c-riva' for device 03:00.0: GeForce2 GTS
Probe succesfully concluded.
We will now try to load each adapter module in turn.
Load `i2c-riva' (say NO if built into your kernel)? (YES/no): yes
modprobe: Can't locate module i2c-riva
Loading failed... skipping.
** Note: i2c-riva module is available at
** http://drama.obuda.kando.hu/~fero/cgi-bin/rivatv.shtml
Do you now want to be prompted for non-detectable adapters? (yes/NO): yes
Load `i2c-elektor' (say NO if built into your kernel)? (YES/no): yes
insmod: /lib/modules/2.4.20-gentoo-r5/misc/i2c-elektor.o: No such file or directory
insmod: insmod /lib/modules/2.4.20-gentoo-r5/misc/i2c-elektor.o failed
insmod: insmod i2c-elektor failed
Loading failed... skipping.
Load `i2c-elv' (say NO if built into your kernel)? (YES/no): yes
Module loaded succesfully.
Load `i2c-philips-par' (say NO if built into your kernel)? (YES/no): yes
Module loaded succesfully.
Load `i2c-velleman' (say NO if built into your kernel)? (YES/no): yes
/lib/modules/2.4.20-gentoo-r5/kernel/drivers/i2c/i2c-velleman.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-gentoo-r5/kernel/drivers/i2c/i2c-velleman.o: insmod /lib/modules/2.4.20-gentoo-r5/kernel/drivers/i2c/i2c-velleman.o failed
insmod: /lib/modules/2.4.20-gentoo-r5/misc/i2c-velleman.o: No such file or directory
insmod: insmod /lib/modules/2.4.20-gentoo-r5/misc/i2c-velleman.o failed
insmod: insmod i2c-velleman failed
Loading failed... skipping.
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: ELV Parallel port adaptor (Bit-shift algorithm)
Do you want to scan it? (YES/no/selectively): no
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
Sorry, no chips were detected.
Either your sensors are not supported, or they are
connected to an I2C bus adapter that we do not support.
See doc/FAQ, doc/lm_sensors-FAQ.html, or
http://www2.lm-sensors.nu/~lm78/cvs/lm_sensors2/doc/lm_sensors-FAQ.html
(FAQ #4.24.3) for further information.
If you find out what chips are on your board, see
http://secure.netroedge.com/~lm78/newdrivers.html for driver status. |
|
|
| Back to top |
|
|
p3nguin
Apprentice
Joined: 01 Jul 2003
Posts: 188
Location: ~/
|
| Posted: Sun Sep 21, 2003 9:39 pm Post subject: |
|
|
| dbl post |
|
| Back to top |
|
|
manywele
l33t
Joined: 12 Jul 2003
Posts: 739
Location: Inside
|
| Posted: Sun Sep 21, 2003 10:03 pm Post subject: |
|
|
| Well, try getting the i2c-riva module from the site listed. Compile it, put it in /lib/modules/2.4.20-gentoo-r5/misc, modprobe it and run sensors and see if you get an output. You might try scanning the ISA bus also and see what it says. Or it might be as the output says in the last paragraph. Try Googling for your mobo specs and see if you can find info about the sensors on it and try looking at http://www2.lm-sensors.nu/~lm78/support2.html for your mobo or the i2c-riva module. |
|
| Back to top |
|
|
|
Other Things Gentoo
