In the ebuild for lm-sensors 2.8 (and 2.8.1), we read einfo "This ebuild assumes your /usr/src/linux kernel is the one you" einfo "used to build i2c-2.8.0. and is >=2.4.9 && < 2.5+" However, if I use it with kernel 2.4.20 (gentoo-sources-2.4.20-r10), I get a kernel crash when the eeprom module is loaded. Based on comments in bugs 36243 and 37277, it looks like something changed between kernels 2.4.20 and 2.4.22, and you must use lm-sensors 2.7 with kernel 2.4.20 and lm-sensor 2.8 with kernel 2.4.22. Reproducible: Always Steps to Reproduce: 1. Install a 2.4.20 kernel and lm-sensors 2.8-* 2. Reboot 3. Actual Results: System crashes during loading of lm-sensors modules (eeprom). Expected Results: The emerge file should note that it's incompatible with eralier kernels. Ideally, it should detect the earlier kernels and refuse to install. Portage 2.0.49-r20 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r3, 2.4.20-gentoo-r10) ================================================================= System uname: 2.4.20-gentoo-r10 i686 AMD Athlon(tm) XP 1900+ Gentoo Base System version 1.4.3.10p1 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-g -O2 -fstack-protector" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.1/share/config /usr/kde/3/share/config /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-g -O2 -fstack-protector" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs fixpackages nostrip sandbox userpriv" GENTOO_MIRRORS="http://mirror.tucdemonic.org/gentoo ftp://ftp.ussg.iu.edu/pub/linux/gentoo http://gentoo.noved.org ftp://mirrors.tds.net/gentoo http://cudlug.cudenver.edu/gentoo http://ftp.easynet.nl/mirror/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="3dnow X Xaw3d aalib apm arts avi berkdb canna cdr cjk crypt cups debug doc dvd encode esd foomaticdb freetype freewnn gdbm gif gnome gpm gtk gtk2 guile imlib java joystick jpeg kde libg++ libwww mad maildir matrox mbox mikmod mozilla mozsvg mpeg mule ncurses nls oggvorbis opengl oss pam pdflib perl png python qt quicktime readline ruby scanner sdl slang spell sse ssl svga tcltk tcpd tetex tiff truetype usb x86 xinerama xml2 xmms xv zlib video_cards_matrox"
Yep, that's because the I2C in the kernel API has to match the kernel API unless you are using the I2C modules and not using kernel I2C support - can also I please have the kernel OOPS? Also, can I please have ``emerge -p i2c''?
I did have i2c-2.8 installed at the time (though 2.7 might also have been installed). "emerge -p i2c" gives: These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild N ] sys-apps/i2c-2.8.1 From my notes, the oops started out something like this: Unable to handle kernel NULL pointer reference at virtual address 0000001 *pde = 00000000 OOPS : 0000 CPU : 0 EIP : 0010:[<00000001>] ... If you need more than that, let me know, but I'll have to emerge the relevant stuff again, and it may be awhile before I have time.
Have you fixed this? Have you upgraded the kernel? Did that help?
Three months. Moving on.
As it happens, kernel 2.4.25-gentoo and lm-sensors-2.8.1 seem to work okay. But, if you're going ask, it would have been nice to wait a *bit* longer for me to reply before closing the bug.
Sorry I didn't wait longer. I didn't realize the thread was that old when I asked.
