I would like to point that from my experience, Titan's undervolting profiles were really BAD and maybe this is source of all reboot problems people are reporting here.
Although your comments seem to agree with what I said a few pages back, I hasten to disassociate myself with the general tone of what you say here, with words like "trash" and "really bad".
I have used Titan's undervolting profiles blindly and trustingly (and daily) for more than a year and they haven't caused me any mysterious problens at all -- my N900 has worked well the whole time. Oh, I have run into unknown problems, but they were solved with common sense solutions like flashing. Titan always made clear that undervolting was something experimental.
It sounds to me like you took his settings too seriously to begin with, and you blame him for that. I have always undervolted cautiously and didn't try hard for maximum undervolting.
I agree with you that many problems mentioned here may be caused by undervolting, but it seems to me that the reason for that is that many users ignore the excellent documentation and instead randomly apply settings thinking that they are magic, and assuming that all N900s are identical, when the whole theory of overclocking and undervolting is that N900s are not identical and the special kernels provide you with ways to customize your unique device.
I also think that your comments exaggerate the hazards of overclocking, which I think has been remarkably safe. Undervolting is trickier.
I have used Titan's undervolting profiles blindly and trustingly (and daily) for more than a year and they haven't caused me any mysterious problens at all -- my N900 has worked well the whole time. Oh, I have run into unknown problems, but they were solved with common sense solutions like flashing
Common Sense solution like flashing your device ???? If you are any expert you wouldnt have had to flash your n900, not even once since you bought it. Most of the people that run into issues that they have to flash their device are noobs mostly. It is not a common sense solution in anyway. I cant imagine trying to install all the little hacks from scratch
Suprisingly didn't find answer for this question in thread:
Can (will) lxp's patched wl1251 driver be included in next kernel-power release? I think it's proven stable. Patched osso-wlan libraries can be included in CSSU to provide smooth transition.
can anyone guide me to fixing my mutiboot menu now? kernel power 2 doesnt load anymore after installing this 47 update need myoverclock any ideas guys?
Mate im stuck at an airport no laptop dont want to go right try threads on my phone, an update just came through earlierfor the boot image which i update, any chance to let me know how to add and remove kernel 46 and ad 47?
hello all.. i read through the postings late last night so I may have missed it but could someone take a minute to tell me how to fix this as I was greeted with an update this morning and when I started I got the message..
!!! Linux kernel for power user(boot image) breaks the 3rd party package policy,, thanks (not using multi-boot)
Ok to make it clear. If you re using a power kernel and you want to update it to version 47 from pali you have to do the following steps (always as root):
1. Remove multiboot-kernel-power package(it's not needed anymore for overclock) by running in xterm
Code:
apt-get remove multiboot-kernel-power
2. Install the new kernel
Code:
apt-get install kernel-power-flasher
3. Create multiboot entry with
Code:
apt-get install kernel-power-bootimg
These steps are written on the first post. I can't understand why are you keep asking and having problems.
