wtf do u mean keep asking this is the first time ive asked?

You do not remove multiboot, you just remove the old multiboot v46 kernel image (so you can install new v47). Nitdroid will work, you do not have to do anything with it.

It means your question has been answered many times over, and they are present in the first post of the topic. Generally when you do not know something, you read the first post (as they usually describe what is it you are reading about, what does it do and how it does it).

Man, you re not the only one. If you look on the previous pages you ll get it.

Multiboot is still there, we re just removing a package which is not needed anymore. Also, nitdroid is intact with this procedure.

If you cannot install any packages now (airport internets have issues sometimes :P), but have installed kernel power 47 (you have file /boot/zImage-2.6.28.10-power47 and directory /lib/modules/2.6.28.10-power47 on your device), you can manually add multiboot entry. Just create file /etc/multiboot.d/02-temp.item with contents:
If your /boot/zImage-2.6.28.10-power47 file is named differently (e.g. you have old power46 kernel and /lib/modules/2.6.28.10-power46 directory) you can change the contents of file accordingly. Basically, you need to have kernel named /boot/zImage-$ITEM_KERNEL or /boot/vmlinuz-$ITEM_KERNEL and directory with modules named /lib/modules/$ITEM_KERNEL (if you know bash scripting, this shuld be enough information, if you don't know anything about bash scripting, please don't continue because you can end with device messed up and not booting anymore. Instead wait with fixing it for better internet connection, then type as suggested previously: as root.

Edit: And, one important thing. Package "multiboot-kernel-power" is just an entry in multiboot for kernel power (as stated bazillion times earlier). You are not uninstalling multiboot while uninstalling it. Multiboot's package is named just "multiboot". All other packages named "multiboot-blahblahblah" are just additional stuff to it (like kernel images and entries in multibootboot menu) and by removing them you are not removing multiboot.

ive been using kernel v47 for around a week now @ 1150 with CSSU.

zero problems.

People here are giving their experience and I will do so.

I've also noticed fast battery draining with v47 and ideal overclocking at 500 MHz MIN and 850 MHz MAX.
This is directed to all of us having fast battery draining to check if you have tested this case to see if you had the same experience as me.

I wanted to mantain battery charge at higher levels so I've been using the stock clocking. My surprise was that responsiveness is nearly the same in normal cases as with overclocking, and it seems to consume less battery power.
I also changed some settings in swappolube.

I havent't followed a scientific method, but I wanted to ask if we are such blinded about overclocking that we haven't noticed that the stock clocking works well on this v47 power kernel?

Maybe with a "Use it when you need it" overclocking use battery lifetime won't be an issue.

if anything my battery lasts longer with v47 @ 1150 with swappolube and some other mods

and no its not placebo. ive had this device since it was released, overclocked since that was released, CSSU since it was released.

cant even remember all the mods on my phone

the N900 is the best value 'phone' ive ever bought. it just keeps getting better and better!

thanks to everyone in this great community!

Hi
I have kernel-power v47 installed
Then tried installing Fcam .Causes camera not to operate when you open lense cover and when you open fcam you have to end proccess to shut it down.
Also notification and keyboard lights dont work.
So uninstalled Fcam, This returned camera function to normal,Switched off phone and removed battery and pluged in charger till notification light flashed then refit battery turn phone on, notification and keyboard lights functioning again.
Is there a way to install fcam on v47?

Got it to work finnaly
straight after you download and install Fcam switch phone off, Remove battery plug in charger to flash notification light reinstall battery turn phone on.
Fcam works great.

Hi guys, quick question...
I had been using kernel-power v46 with no issues at all, now I recently upgraded to kernel-power v47 and the last few times I have used my n900 with my BH-214 bluetooth headset it connects no problem to the headset however it continually has audio problems occasionally dropping the connection.

Could this be related to v47, is there any way to know what is happening here? The bluetooth icon shows that the headset is still connected however there is no audio after a while..

Thanks.

@ that one guy who said something to the effect of "could it be we're so obsessed with overclocking that ..."

Yes. Yes we are. I have never overclocked my N900, and I have almost never felt the need for it. Modern CPUs, even at 600MHz, are faster at that clock rate than the clock rates of other hardware, and depending on the quality of the code being executed, the processor could be spending hundreds of CPU cycles just waiting for the right data to make its way out of the harddrive to it. It has also been repeatedly demonstarted that the majority of N900 slowness is I/O bottlenecks and swap fragmentation as uptime continues (as fragmentation of flash media doesn't effect read speeds but DOES effect write speeds).

Overclocking isn't bad - but it only increases performance in only CPU-intensive tasks that aren't already I/O or RAM -bound. It certainly does not make the phone AS more responsive and smooth/snappy/fluid/whatever as most users exclaim/believe.

Just look at both this thread and CSSU threads - every update in the CSSU for example, there's people who comment how their phone feels snappier/more-responsive - there's no reasonable cause for that to be so though, as CSSU updates have never, if I recall correctly, included patches optimizing the code for performance speeds.

Overclocking has its uses, but it's specific uses and a computer (phones included) doesn't magically improve at everything just because its overclocked.