Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!
Not eligible to see or edit group visibility for this bug.
View Bug Activity | Format For Printing | XML | Clone This Bug
I am testing kernel 2.6.19-r2 (~amd64 now) and I want to tell some **minor** issue about lm_sensors. I did sensors-detect, updated config and after I tryed to run the init script /etc/init.d/lm_sensors unsuccesfully. The weird thing is that sensors command returns correct values despite the init script didn't started. So there is maybe a bug in that script in conditions checking whether is is started or not.
Doubt it has anything to do with kernel version. Some errors in the log/on console? Also post emerge --info output.
I though it was kernel version fault because it started correctly with 2.6.18-r5..
Created an attachment (id=104823) [details] emerge --info
Please, could you tell me how to debug this init.d script in order to get a reason why it returns fail status despite it starts correctly? (As I said, maybe is only an error in this init.d script that does not return the OK status correctly). After this, I'll commit more info.
Well please post some errors you get, also see /var/log/dmesg; we really can't guess
I can confirm it, since I'm seeing the exact same error when booting kernel 2.6.19.2 whereas it works normally with 2.6.18.5 (both vanilla-sources). Even so, the sensor modules load fine and seem to give correct readings; it's just the sensors script that barfs with the following error: # sensors General parse error and the actual init script just shows [!!] after the modules load. Note, even though I'm not ~amd64, I have many ~ packages in *.keywords... # emerge --info Portage 2.1.2-r7 (default-linux/amd64/2006.1/desktop, gcc-4.1.1, glibc-2.5-r0, 2.6.19.2 x86_64) ================================================================= System uname: 2.6.19.2 x86_64 AMD Athlon(tm) 64 Processor 3000+ Gentoo Base System release 1.12.9 Timestamp of tree: Fri, 09 Feb 2007 10:50:01 +0000 ccache version 2.3 [enabled] dev-java/java-config: 1.3.7, 2.0.31-r3 dev-lang/python: 2.4.3-r4 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: 2.3 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.61 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.17 sys-devel/gcc-config: 1.3.14 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.17-r2 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=k8 -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/java-config/vms/ /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c" CXXFLAGS="-march=k8 -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig buildpkg ccache cvs distlocks metadata-transfer multilib-strict sandbox sfperms strict userpriv usersandbox" GENTOO_MIRRORS="http://kuroshin.arnolds.bogus/gentoo/" LDFLAGS="-Wl,-O1" LINGUAS="en" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://kuroshin.arnolds.bogus/gentoo-portage" USE="X Xaw3d a52 aac aalib accessibility acl acpi alsa amd64 ansi artworkextra avahi avi bitmap-fonts bonobo browserplugin bzip2 cairo cddb cdparanoia cdr clamav cli cracklib crypt cups dbus dga directfb divx4linux dlloader dri dts dv dvd dvdr dvdread dynagraph eds emacs emboss encode esd evo fam fame fbcon ffmpeg fits flac fontconfig fortran freetype freetype2 gb gcj gd gdbm geos gif gimp gmp gnome gphoto2 gpm gps graphviz grass gs gstreamer gtk gtk2 gtkhtml guile hal howl iconv icq ieee1394 imagemagick imap imlib ipv6 isdnlog jabber jasper java jbig jikes jpeg jpg junit lame lapack lcms ldap lesstif libg++ lirc lm_sensors logrotate mad midi mikmod motif mp3 mpeg mplayer mysql nas nautilus ncurses netcdf nfs nls nolvmstatic nptl nptlonly nsplugin numeric ogdi ogg oggvorbis opengl oss pam pcre pda pdf perl plotutils png postgres ppds pppd python qt qt3 quicktime readline reflection rtc ruby samba sasl sdl seamonkey session slp snmp spamassassin spell spl ssl subtitles svg tcl tcpd tetex threads tiff timidity tk truetype truetype-fonts type1-fonts udev unicode usb v4l v4l2 vcd vorbis wifi xanim xattr xext xine xml xml2 xorg xpm xv xvid xvmc zeo zlib zvbi" ALSA_CARDS="emu10k1" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" ELIBC="glibc" INPUT_DEVICES="keyboard mouse joystick evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="en" USERLAND="GNU" VIDEO_CARDS="radeon vesa fglrx v4l" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, PORTAGE_RSYNC_EXTRA_OPTS
Sigh. Did you *re-emerge* lm_sensors after kernel upgrade? Which lm_sensors version is this about? Anything in /var/log/dmesg? I'm really tired of asking for pretty basic info over and over again.
Just tested the new sys-apps/lm_sensors-2.10.2 ebuild and it works fine. This can be closed when the updated ebuilds are stable, and at least had time to propagate out to users (at least that makes sense to me anyway; you can slap me if it violates policy). Man, you're quick on the trigger; I haven't even left for work yet ;)
*** This bug has been marked as a duplicate of bug 161851 ***