Hi,
for some time now I'm experiencing some troubles with the battery and
cpu modules in e17. Everything is with a fresh svn-everything install
and with a new ~/.e directory on a debian testing and a debian unstable box.
battery module:
The batget binary uses up 100 % cpu time. Running the bin
This is known... Kernel 2.6.30 changed the info reported by
poll/select on /sys uevents. As we don't know of a way to block for
updates or be informed of such we're waiting before adding ugly timmed
polling hacks
On 6/14/09, Florian Schaefer wrote:
> Hi,
>
> for some time now I'm experiencing som
You are talking about batget here, right? So batget and tempget use
different ways of obtaining their information? Anyway, I can confirm
this behavior, batget works in conjunction with 2.6.29 but fails with
2.6.30 -- so this is what you get for running bleeding edge stuff. ;)
So you're waiting fo
At 5:13pm, Florian Schaefer wrote:
> You are talking about batget here, right? So batget and tempget use
> different ways of obtaining their information? Anyway, I can confirm
> this behavior, batget works in conjunction with 2.6.29 but fails with
> 2.6.30 -- so this is what you get for runni
On Sun, Jun 14, 2009 at 12:13 PM, Florian Schaefer wrote:
> You are talking about batget here, right? So batget and tempget use
> different ways of obtaining their information? Anyway, I can confirm
> this behavior, batget works in conjunction with 2.6.29 but fails with
> 2.6.30 -- so this is wha
Hi,
thank you so much for this. That really did the trick. :-) It is
interesting how uninformed you feel not knowing what your CPU is doing.
Cheers,
Florian
P Purkayastha wrote:
[...]
> About the cpu module,- the "Shelf contents" will actually list cpu module
> as added to the shelf, but it w
