On a Fujitsu Siemens Amilo D7830 laptop, I have sensors working just fine with gentoo-dev-sources 2.6.9r6. With r8 and r9 there are none found. dmesg output is identical between r6,r8,r9. I2C is Intel (82)801 on ICH4. (P4 2.66) Reproducible: Always Steps to Reproduce: 1. Boot from 269r6 and sensors work 2. Boot from 269r8 or r9 and sensors dont work 3. Try i2c & lm-sensors 2.8.8, same result Actual Results: Sensors was able to report cpu and board temp with r6, r8 and r9 dont find sensors. "i2c /dev entries driver" is reported from dmesg on boot in the 3 kernels. amilo craig # emerge info Portage 2.0.51-r3 (default-linux/x86/2004.2, gcc-3.3.4, glibc-2.3.4.20040808-r1, 2.6.9-gentoo-r9 i686) ================================================================= System uname: 2.6.9-gentoo-r9 i686 Intel(R) Pentium(R) 4 CPU 2.66GHz Gentoo Base System version 1.6.6 distcc 2.16 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.3 [enabled] Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.15.90.0.1.1-r3 Headers: sys-kernel/linux-headers-2.4.21-r1 Libtools: sys-devel/libtool-1.5.2-r7 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=pentium4 -O2 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=pentium4 -O2 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms" GENTOO_MIRRORS="http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/ http://trumpetti.atm.tut.fi/gentoo/ http://gentoo.mirror.sdv.fr http://linux.rz.ruhr-uni-bochum.de/download/gentoo-mirror/ http://ftp.uni-erlangen.de/pub/mirrors/gentoo http://mirrors.sec.informatik.tu-darmstadt.de/gentoo/ http://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ http://ftp.easynet.nl/mirror/gentoo/ http://ftp.snt.utwente.nl/pub/os/linux/gentoo http://gentoo.tiscali.nl/gentoo/ http://www.mirrorservice.org/sites/www.ibiblio.org/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://luxbg/portage" USE="X acpi alsa apache2 apm arts avi berkdb bitmap-fonts cdr crypt cups divx4linux dvd dvdr dvdread encode esd f77 fam foomaticdb fortran gcj gd gdbm gif gnutls gphoto2 gpm gtk gtk2 imagemagick imap imlib innodb java jpeg jpeg2k junit kde lcms libg++ libwww mad mikmod mmx motifmozilla mpeg mysql ncurses nls odbc oggvorbis opengl oss pam pdflib perl png ppds python qt quicktime radeon readline samba sdl slang slp spell sse sse2 ssl svg svga tcltk tcpd tiff truetype truetype-fonts type1-fonts usb vhosts wifi x86 xml xml2 xmms xv zlib linguas_en_GB"
Strange, there is only one patch difference between -r6 and -r8 Please try reverting this patch : http://bugs.gentoo.org/attachment.cgi?id=44854&action=view
Reverting to the old af_unix.c.orig doesnt help, but I have checked and double checked. r6 gives me this: # sensors max1617-i2c-0-4c Adapter: SMBus I801 adapter at 0540 Board: +43
Reverting to the old af_unix.c.orig doesnt help, but I have checked and double checked. r6 gives me this: # sensors max1617-i2c-0-4c Adapter: SMBus I801 adapter at 0540 Board: +43°C (low = +0°C, high = +85°C) CPU: +52°C (low = +0°C, high = +85°C) and r8 and r9 say No sensors found. A diff of the .configs shows 0 differences apart from the time (I had run make oldconfig after copying the file over).
Oh, I should say, there are no modules, all built in, so its not that I forgot to do something with the modules in later kernels. hmm.. rebooting to see if running sensors-detect finds anything, tho I never did before.
I have added another chip into the sensors config of 2.6.9r9 and they now work. However, they certainly worked in r6 and in r8 and r9 they didnt work with the same kernel config. Please resolve with your chosen resolution. I wouldnt say its fixed in terms of knowing why r6 works and r9 doesnt but at least it is working.
Knowing the exact (very small) differences between each kernel revision, i'm suspicious that it something you are doing wrong, or some software (non-kernel) inconsitency. THe patches we applied between revisions would not affect this.