Re: [gentoo-user] kernel 2.6.12-r9 : sensors don't work : solved with comment
050901 Philip Webb wrote: 050902 Holly Bostick wrote: Philip Webb schreef: I've installed kernel 2.6.12-gentoo-r9 Gkrellm doesn't show sensors. There's no problem with 2.6.9-gentoo-r1 . I am also using GKrellm2, and while I didn't know it had its own sensors, they work fine : temperature, fan, thermal, hdd, and voltage. This is with 2.6.12-gentoo-r9 and gkrellm-2.2.7; I will investigate later tonight, after reading the day's news horrors, report whatever I manage to find. Others have had the problem (forum). The problem seems to be that the Gkrellm2 sensor display needs to be reactivated ( R-click top edge, config, built-in, sensors) after each boot of a different kernel, but continues ok if the same kernel is booted. This is with Lm_sensors, which I have emerged configured: I haven't tried what happens if I unmerge it again, but my suspicion is that it makes no difference using kernel Sysfs instead. In any case, 'sensors' (Lm command) shows the correct figures from CLI, which shows the problem is Gkrellm2, not the kernel itself. 2 oddities I've noticed going over to Udev along with changing kernels: (1) Udev make the floppy device root-only by default, so you have to add 'purslow' (whoever) to the 'floppy' group; (2) 2.6.12 + Udev defines a smaller set of devices than 2.6.9 + Udev , even tho' I've suppressed the cacheing which Gentoo adds (the extras are ptya0-zf ttya0-zf : perhaps due to kernel config ? ). -- ,, SUPPORT ___//___, Philip Webb : [EMAIL PROTECTED] ELECTRIC /] [] [] [] [] []| Centre for Urban Community Studies TRANSIT`-O--O---' University of Toronto -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] kernel 2.6.12-r9 : sensors don't work
Philip Webb schreef: I've installed kernel 2.6.12-gentoo-r9 find Gkrellm doesn't show sensors. There's no problem with 2.6.9-gentoo-r1 . The same modules are being installed removed at each (re)boot. There is a recent thread on the forum which reported that removing ACPI from the kernel config options solved the problem, but I've just done that it made no difference. Has anyone else encountered this problem or have any advice ? That seems odd... I just *started* using lm_sensors for the first time with 2.6.12-gentoo-r9 (no previous experience, thus), and once I got the hang of it, it worked fine. If lm_sensors the package compiles against the kernel, as I would imagine it must, it would need to be re-emerged when you upgraded the kernel. Perhaps that's the problem? Holly -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] kernel 2.6.12-r9 : sensors don't work
+++ Holly Bostick [gentoo-user] [Thu, Sep 01, 2005 at 07:03:47PM +0200]: If lm_sensors the package compiles against the kernel, as I would imagine it must, it would need to be re-emerged when you upgraded the kernel. I don't mean to thread-hijack, but... I was just thinking that it would be really nice if after I run genkernel I got a list of packages that need to be recompiled against the new kernel (i.e. nvidia-kernel, zaptel, lm_sensors, etc.). I inevitably forget which packages need to be re-emerged... -- // Andrew MacKenzie | http://www.edespot.com // GPG public key: http://www.edespot.com/~amackenz/public.key // Every why hath a wherefore. // -- William Shakespeare, A Comedy of Errors pgpuIb2DfdnmL.pgp Description: PGP signature
Re: [gentoo-user] kernel 2.6.12-r9 : sensors don't work
Andrew MacKenzie schreef: +++ Holly Bostick [gentoo-user] [Thu, Sep 01, 2005 at 07:03:47PM +0200]: If lm_sensors the package compiles against the kernel, as I would imagine it must, it would need to be re-emerged when you upgraded the kernel. I don't mean to thread-hijack, but... I was just thinking that it would be really nice if after I run genkernel I got a list of packages that need to be recompiled against the new kernel (i.e. nvidia-kernel, zaptel, lm_sensors, etc.). I inevitably forget which packages need to be re-emerged... Or... since you know (sometimes) which of such packages need to be re-emerged, and you also know when you have upgraded your kernel, you *could* just write a (one line) script to re-emerge the relevant packages, throw it in /usr/sbin or whatever (optional), and run it after you upgraded a kernel. I've been meaning to do that for some time now, since it's much easier to maintain (you only have to add any new packages the first time you emerge them, then you're free to forget what you want :) ). Holly -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] kernel 2.6.12-r9 : sensors don't work
On Thu, 01 Sep 2005 21:48:50 +0200, Holly Bostick wrote: Or... since you know (sometimes) which of such packages need to be re-emerged, and you also know when you have upgraded your kernel, you *could* just write a (one line) script to re-emerge the relevant packages, throw it in /usr/sbin or whatever (optional), and run it after you upgraded a kernel. I've been meaning to do that for some time now, since it's much easier to maintain (you only have to add any new packages the first time you emerge them, then you're free to forget what you want :) ). Some packages only compile against the running kernel, others use the /usr/src/linux symlink to decide. So I have a few lines in /etc/conf.d/local.start to take care of such re-emerges when I reboot with a new kernel. # Re-emerge NVidia drivers after a kernel compile lsmod | grep --quiet nvidia || grep --quiet softlevel /proc/cmdline || \ (FEATURES=-distcc -buildpkg -sandbox emerge --oneshot nvidia-kernel modprobe -v nvidia /etc/init.d/xdm stop zap start) # Rebuild VMware modules if needed lsmod | grep --quiet vmnet || grep --quiet softlevel /proc/cmdline || /opt/vmware/bin/vmware-config.pl default # Re-emerge fuse lsmod | grep --quiet fuse || FEATURES=-distcc -buildpkg emerge --oneshot sys-fs/fuse modprobe -v fuse #Re-emerge wlan-ng if [ ! -f /lib/modules/$(uname -r)/linux-wlan-ng/prism2_usb.ko ] ; then if rc-status -nc | grep -q net\.eth0.*started ethtool eth0 | grep -q 'Link detected: yes' ; then FEATURES=-distcc -buildpkg emerge --oneshot linux-wlan-ng fi fi -- Neil Bothwick Southern DOS: Y'all reckon? (Yep/Nope) pgpgx2zZ1HlRr.pgp Description: PGP signature
Re: [gentoo-user] kernel 2.6.12-r9 : sensors don't work
Peter Ruskin schreef: On Thursday 01 September 2005 20:37, Andrew MacKenzie wrote: I don't mean to thread-hijack, but... I was just thinking that it would be really nice if after I run genkernel I got a list of packages that need to be recompiled against the new kernel (i.e. nvidia-kernel, zaptel, lm_sensors, etc.). I inevitably forget which packages need to be re-emerged... emerge -v $(equery b /lib/modules | sed -e 's:^:=:' ) Peter, why does running this command give me the following output: emerge -v $(equery b /lib/modules | sed -e 's:^:=:' ) !!! No command or unknown command given cfg-update 1.7.1 : Building checksum index... (takes a few seconds) done! !!! Error: -, is an invalid short action or option. ?? I don't know enough about scripting to 'debug' it, but I do know I don't see any loose '-' that is meant to precede an option (but does not). So I really don't know what the error is trying to tell me. Am I missing some essential piece of the puzzle (I certainly have both equery and sed)? Holly -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] kernel 2.6.12-r9 : sensors don't work
Peter Ruskin schreef: On Friday 02 September 2005 00:21, Holly Bostick wrote: Peter, why does running this command give me the following output: emerge -v $(equery b /lib/modules | sed -e 's:^:=:' ) !!! No command or unknown command given _ ___ cfg-update 1.7.1 : Building checksum index... (takes a few seconds) done! _ ___ !!! Error: -, is an invalid short action or option. ?? I don't know enough about scripting to 'debug' it, but I do know I don't see any loose '-' that is meant to precede an option (but does not). So I really don't know what the error is trying to tell me. Am I missing some essential piece of the puzzle (I certainly have both equery and sed)? That beats me Holly. I always run that line at the end of my build-kernel script. Try running it with -p like this: $ emerge -vp $(equery b /lib/modules | sed -e 's:^:=:' ) These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild R ] media-video/nvidia-kernel-1.0.7676 0 kB [ebuild R ] net-fs/shfs-0.35-r1 -amd +doc 0 kB Total size of downloads: 0 kB Same error, but I figured it out (my mistake, of course). It's so dumb, I don't even want to tell you what I did (or didn't yet do, more precisely), but I will say that the key was your explanation of when you run this command. Sorry for the noise, at least I've learned something --or been reminded, yet again, that the kernel is very picky about when you access its source, and also very knowledgeable about the state of the source when you attempt to access it. Two DUH!s in two days. I'm definitely overextending myself :) . Holly -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] kernel 2.6.12-r9 : sensors don't work
050901 Holly Bostick wrote: Philip Webb schreef: I've installed kernel 2.6.12-gentoo-r9 find Gkrellm doesn't show sensors. There's no problem with 2.6.9-gentoo-r1 . The same modules are being installed removed at each (re)boot. There is a recent thread on the forum which reported that removing ACPI from the kernel config options solved the problem, but I've just done that it made no difference. Has anyone else encountered this problem or have any advice ? That seems odd ... (big smile) only because you didn't read my query carefully enough ... I just *started* using lm_sensors for the first time with 2.6.12-gentoo-r9 (no previous experience, thus) and once I got the hang of it, it worked fine. I'm not using Lm_sensors: I'm using Gkrellm2, which has its own internal sensors. Yes, Gkrellm1 used to rely on Lm_sensors, but that's obsolete. If lm_sensors the package compiles against the kernel, as I would imagine it must, it would need to be re-emerged when you upgraded the kernel. One of the tests I've thought of to probe what's going on is to emerge Lm_sensors see if I can get readings via CLI , which would show whether the problem is in Gkrellm2 or somewhere in the kernel/sensor interface. I suspect it's a bug in Gkrellm2 , so bug searches may also help. However, it could be the effect of some new kernel config option. But again -- and may thread-hijackers roast in hell -- , has anyone else had this problem using Kernel 2.6.10/11/12 + Gkrellm2 ? -- ,, SUPPORT ___//___, Philip Webb : [EMAIL PROTECTED] ELECTRIC /] [] [] [] [] []| Centre for Urban Community Studies TRANSIT`-O--O---' University of Toronto -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] kernel 2.6.12-r9 : sensors don't work
Philip Webb schreef: Philip Webb schreef: I've installed kernel 2.6.12-gentoo-r9 find Gkrellm doesn't show sensors. There's no problem with 2.6.9-gentoo-r1 . The same modules are being installed removed at each (re)boot. There is a recent thread on the forum which reported that removing ACPI from the kernel config options solved the problem, but I've just done that it made no difference. Has anyone else encountered this problem or have any advice ? One of the tests I've thought of to probe what's going on is to emerge Lm_sensors see if I can get readings via CLI , which would show whether the problem is in Gkrellm2 or somewhere in the kernel/sensor interface. I suspect it's a bug in Gkrellm2 , so bug searches may also help. However, it could be the effect of some new kernel config option. But again -- and may thread-hijackers roast in hell -- , has anyone else had this problem using Kernel 2.6.10/11/12 + Gkrellm2 ? My answer is still 'no problems here'; I am also using GKrellm2, and while I didn't know it had its own sensors, they work fine ( temperature, fan, thermal, hdd, and voltage. I had turned them off because I replaced them with conky, but turning them back on, there they are. This is with 2.6.12-gentoo-r9 and gkrellm-2.2.7; I've just compiled 2.6.12-gentoo-r10, if the situation changes, I'll let you know :). Holly -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] kernel 2.6.12-r9 : sensors don't work
050902 Holly Bostick wrote: Philip Webb schreef: I've installed kernel 2.6.12-gentoo-r9 Gkrellm doesn't show sensors. There's no problem with 2.6.9-gentoo-r1 . I am also using GKrellm2, and while I didn't know it had its own sensors, they work fine : temperature, fan, thermal, hdd, and voltage. This is with 2.6.12-gentoo-r9 and gkrellm-2.2.7; I've just compiled 2.6.12-gentoo-r10, if the situation changes, I'll let you know :). Thanx for your very prompt reply: your hours are as odd as mine (grin)! I will investigate later tonight, after reading the day's news horrors, report whatever I manage to find. Others have had the problem (forum). -- ,, SUPPORT ___//___, Philip Webb : [EMAIL PROTECTED] ELECTRIC /] [] [] [] [] []| Centre for Urban Community Studies TRANSIT`-O--O---' University of Toronto -- gentoo-user@gentoo.org mailing list
