I had the same ghost message after i removed kernel-power last year. It persisted until i reflashed for other reasons, but i never did look into how to get rid of it.

Damn.. is there a command which can search for that text or sentence? I guess its stored in some file what opens in startup.. perhaps removing that file would then remove the message? Just need to know which file or files kernel-power installs.

program grep

Usage: grep "string" "file"
Example:
$ grep "string*xyz" /etc/subdir/*file*a
This will output all files with mask /etc/subdir/*file*a which contains mask "string*xyz"

hey pali need abit help.
can you tell me how to get back to power kernel v46 , as upgrading to v47 has raised my cpu temp from 33 to 39 in sleeping mode ( while doing nothing)
i am not sure if it is kernel but need to test if it works or if you can help me without uninstalling or changing anything in my cell then please please please help.

I still not get responce from council... but I see that now I'm maintainer of package kernel-power in maemo repository.

I tried promote v47 to extras-testing, but maemo.org site does not see version v47 of kernel-power... BUG?? So I cannot move kernel-power to extras-testing/extras...

So I tried promote v46 to extras-testing. maemo.org site show that packages was moved to extras-testing but maemo.org site does not generated web page for package in testing... BUG?? So it is not possible to VOTE for kerne-power to move it to extras.

Sorry but I cannot do anythink... I tried maemo.org web request to be maintainer of all subpackage from kernel-power... So again I can only wait. But I think this is bug in maemo.org package view...

Replace <version> with which you want to use and run this comand as root:
$ apt-get install kernel-power=<version> kernel-power-modules=<version> kernel-power-flasher=<version>

in v47 there was change about version strings:
v47: 1:2.6.28-10power47
v46: 2.6.28-maemo46
v45: 2.6.28-maemo45
...

Yeah, that did it!

I went to /etc and searched:

grep "kernel-power" * -r 'and deleted the found "kernel-power, kernel-power-shutdown, kernel-modules" by hand manually in several subdirs. There still are kernel-power-deinstall, kernel-power-flasher.sudoers:user and kernel-power.conf: files left..

Many thanks.

edit. so yes the startup message is gone now.

Pali: While I have no idea about power47 appearing/not-appearing in the -devel repo, my experiences with the aircrack-ng package indicate to me that sometimes you have to wait a pretty long while before a promoted package gets imported into -testing from -devel.

So it might still show up if you wait long enough.

@Demolition, @pali and @Mentalist Traceur

Ok, now i understand what is it about - still, no idea why kernel-power v47 doesn't exist for site, while repositories are 100% aware of it presence. As Mentalist mentioned in aircrack-ng 1.1 topic, asking for debmaster help is pointless cause no one maintain this function now... Having in mind that pali isn't getting any responses from council using official "contact us" form (but!!! He GOT response in this thread from Tigerite and was given package maintainer rights - I must write this in bold, cause i don't want anyone to take my post as "rage again council" thing), maybe it's time to summarize Mentalist and pali repo bugs/faults experience, then report them in "ask the council" thread, as Demolition suggested?

I know, this may be little strange choose to ask about such things, but I think that only this way we can get more summarized response/help, instead of scattered posts from various Council members in this bloated topic, or somewhere around other threads.

Last, possibly dumb (but who knows?) idea that I have, is that pali can try to upload kp47 into repos again, now as maintainer. I know that this shouldn't be solution, cause Mentalist isn't (formally) maintainer of aircrack-ng, ho ever he succeed in putting new version into testing... Still, we're probably talking about unknown bugs, and "voodoo programing" tend to work in such cases

I'm not the maintainer of bonnie++ and yet was able to upload a newer version - the autobuilder doesn't seem to mind.