[gentoo-user] kernel 2.6.12-r9 : sensors don't work

[gentoo-user] kernel 2.6.12-r9 : sensors don't work

[Philip Webb]

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 ?

-- 
========================,,============================================
SUPPORT     ___________//___,  Philip Webb : purslow@chass.utoronto.ca
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

[Holly Bostick]

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

[Andrew MacKenzie]

[-- Attachment #1: Type: text/plain, Size: 749 bytes --]

+++ 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"

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] kernel 2.6.12-r9 : sensors don't work

[Holly Bostick]

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

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 1684 bytes --]

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)

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] kernel 2.6.12-r9 : sensors don't work

[Peter Ruskin]

On Thursday 01 September 2005 20:37, Andrew MacKenzie wrote:
> +++ 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...

emerge -v $(equery b /lib/modules | sed -e 's:^:>=:' )

-- 
Peter
========================================================================
Gentoo Linux: Portage 2.0.51.22-r2.	kernel-2.6.12-gentoo-r6.
i686 AMD Athlon(tm) XP 3200+.		gcc(GCC): 3.3.5-20050130.
KDE: 3.4.2.				Qt: 3.3.4.
========================================================================
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] kernel 2.6.12-r9 : sensors don't work

[Holly Bostick]

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]

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

-- 
Peter
========================================================================
Gentoo Linux: Portage 2.0.51.22-r2.	kernel-2.6.12-gentoo-r6.
i686 AMD Athlon(tm) XP 3200+.		gcc(GCC): 3.3.5-20050130.
KDE: 3.4.2.				Qt: 3.3.4.
========================================================================
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] kernel 2.6.12-r9 : sensors don't work

[Holly Bostick]

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

[gentoo-user] emerging an old kernel (but not too old)

[Benjamin Grauer]

Hi there

i use an ati graphicscard with fglrx, and since this f* driver does not 
work with 2.6.12-kernels, i wondered if i could emerge old kernels...

so i wnet out there into portage to visit sys-kernel/gentoo-sources, and 
only found an old version of the kernel matching 2.6.9-r9

so i wondered, if someone has still an ebuild of an old 
2.6.11-r[newest], or if i could get one by cvs


QUESTION:
-------------------
Looking for ebuild gentoo-sources-2.6.11-r[newest]

greetings and thanks in advance
    Benjamin
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] emerging an old kernel (but not too old)

[Holly Bostick]

Benjamin Grauer schreef:
> Hi there
> 
> i use an ati graphicscard with fglrx, and since this f* driver does
> not work with 2.6.12-kernels, i wondered if i could emerge old
> kernels...

Yes it does work with 2.6.12 kernels..

8.14.13-r2 supports 2.6.12 with an (included) patch, and 8.16.20 (-*
masked under gentoo, but I'm testing it), supports 2.6.12 out of the box.
> 
> so i wondered, if someone has still an ebuild of an old 
> 2.6.11-r[newest], or if i could get one by cvs

Go to the main Gentoo page, use the "View our CVS" item in the sidebar
menu, once in CVS, go to sys-kernel, and download the ebuild of your
choice into your overlay, digest and emerge as normal for an overlay ebuild.

HTH,
Holly
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] emerging an old kernel (but not too old)

[Benjamin Grauer]

Holly Bostick wrote:

>Benjamin Grauer schreef:
>  
>
>>Hi there
>>
>>i use an ati graphicscard with fglrx, and since this f* driver does
>>not work with 2.6.12-kernels, i wondered if i could emerge old
>>kernels...
>>    
>>
>
>Yes it does work with 2.6.12 kernels..
>
>  
>
not for me... same config (as in 2.6.11) leads to black screen in 2.6.12 
and all i can do then is a reboot

>8.14.13-r2 supports 2.6.12 with an (included) patch, and 8.16.20 (-*
>masked under gentoo, but I'm testing it), supports 2.6.12 out of the box.
>  
>
>>so i wondered, if someone has still an ebuild of an old 
>>2.6.11-r[newest], or if i could get one by cvs
>>    
>>
>
>Go to the main Gentoo page, use the "View our CVS" item in the sidebar
>menu, once in CVS, go to sys-kernel, and download the ebuild of your
>choice into your overlay, digest and emerge as normal for an overlay ebuild.
>
>  
>
thanks

>HTH,
>Holly
>  
>

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] emerging an old kernel (but not too old)

[Holly Bostick]

Benjamin Grauer schreef:
> Holly Bostick wrote:
> 
>> Benjamin Grauer schreef:
>> 
>> 
>>> Hi there
>>> 
>>> i use an ati graphicscard with fglrx, and since this f* driver
>>> does not work with 2.6.12-kernels, i wondered if i could emerge
>>> old kernels...
>>> 
>> 
>> 
>> Yes it does work with 2.6.12 kernels..
>> 
>> 
>> 
> not for me... same config (as in 2.6.11) leads to black screen in
> 2.6.12 and all i can do then is a reboot

That suggests that you have misconfigured something in your new kernel....

Do you possibly have DRI enabled in the kernel? It is on by default in a
new kernel config, but it must be turned off for the ATI drivers to work.

Second, did you re-emerge ati-drivers after compiling the new kernel?

Third, is your xorg.conf set to use internal agpgart (from the fglrx
driver) or not (external agpgart from the kernel)?

If it is set to "no", because you need to use the kernel module, did you
also enable support for your motherboard, if a kernel module is
available for that?

What, btw, is your motherboard/chipset? And what is your ATI card, while
we're at it? Is your system 32-bit or 64-bit?

This driver does in fact work under 2.6.12; I've been using two
different versions of the driver (8.14.13-r2 and 8.16.20) under several
2.6.12 series kernels (-r6, r9, and now -r10 as soon as I reboot), and I
know it works without 'extra' modification from what is normally
necessary to get these drivers to install properly. I haven't seen the
'black screen on boot' issue since before we went to the new numbering
system (or shortly after we went to the new numbering system; in any
case, it's been so long that I don't even remember exactly when it
stopped in terms of it being a driver problem, rather than an error on
my part).

Holly
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] emerging an old kernel (but not too old)

[Benjamin Grauer]

Holly Bostick wrote:

>Benjamin Grauer schreef:
>  
>
>>Holly Bostick wrote:
>>
>>    
>>
>>>Benjamin Grauer schreef:
>>>
>>>
>>>      
>>>
>>>>Hi there
>>>>
>>>>i use an ati graphicscard with fglrx, and since this f* driver
>>>>does not work with 2.6.12-kernels, i wondered if i could emerge
>>>>old kernels...
>>>>
>>>>        
>>>>
>>>Yes it does work with 2.6.12 kernels..
>>>
>>>
>>>
>>>      
>>>
>>not for me... same config (as in 2.6.11) leads to black screen in
>>2.6.12 and all i can do then is a reboot
>>    
>>
>
>That suggests that you have misconfigured something in your new kernel....
>
>Do you possibly have DRI enabled in the kernel? It is on by default in a
>new kernel config, but it must be turned off for the ATI drivers to work.
>
>  
>
no..

>Second, did you re-emerge ati-drivers after compiling the new kernel?
>
>  
>
yes

>Third, is your xorg.conf set to use internal agpgart (from the fglrx
>driver) or not (external agpgart from the kernel)?
>
>  
>
internal/external both tested

>If it is set to "no", because you need to use the kernel module, did you
>also enable support for your motherboard, if a kernel module is
>available for that?
>
>  
>
yes enabled intel-module

>What, btw, is your motherboard/chipset? And what is your ATI card, while
>we're at it? Is your system 32-bit or 64-bit?
>
>  
>
intel 875P (32bit)

>This driver does in fact work under 2.6.12; I've been using two
>different versions of the driver (8.14.13-r2 and 8.16.20) under several
>2.6.12 series kernels (-r6, r9, and now -r10 as soon as I reboot), and I
>know it works without 'extra' modification from what is normally
>necessary to get these drivers to install properly. I haven't seen the
>'black screen on boot' issue since before we went to the new numbering
>system (or shortly after we went to the new numbering system; in any
>case, it's been so long that I don't even remember exactly when it
>stopped in terms of it being a driver problem, rather than an error on
>my part).
>
>  
>
so i think it is my fault, but do not know exactly

>Holly
>  
>

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] kernel 2.6.12-r9 : sensors don't work

[Philip Webb]

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 : purslow@chass.utoronto.ca
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

[Holly Bostick]

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

[Philip Webb]

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 : purslow@chass.utoronto.ca
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 : solved with comment

[Philip Webb]

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 : purslow@chass.utoronto.ca
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

[Holly Bostick]

Philip Webb schreef:

> I'm using Gkrellm2, which has its own internal sensors. Yes, Gkrellm1
>  used to rely on Lm_sensors, but that's obsolete.

This does not seem to be completely the case, based on my (currently
ongoing) experience.

Prior to rebooting to my new kernel, I was able to use all of the
inbuilt sensors, from THRM to Voltages.

After rebooting, I only had THRM and hddtemp available.

This seems to be because I misconfigured my kernel (totally left all the
I2C modules blank, like a yutz).

Conky won't run (unsurprising), /usr/sbin/sensors-detect can't find
anything (because the modules don't exist to be found, either statically
or loadable)-- and GKrellM2 only allows me to enable THRM and hddtemp
(which work properly), but all the other sections are unavailable (not
even uncheckable, there are simply no other options under the
Temperatures, Fans, or Voltages headers).

So it would seem that GKrellm2 does, to some extent, still rely on
lm_sensors.

More as I fix this set of stupid mistakes... but at least maybe it gives
you some useful info about the environment.

Holly
-- 
gentoo-user@gentoo.org mailing list