Kernel Power
The enhanced kernel "kernel-power" is compatible with PR1.2 and PR1.3, contain lots of additional features (IPv6, NAT etc) and bugfixes. The kernel can be installed via Application manager from the System section. Installation of the customization package Kernel-Power-Settings is sufficient, as it depends on the kernel page.
The custom kernel contains additional modules for IPv6, packet filtering, QoS, NAT, tunneling, kernel configuration, Wifi mesh networking, builtin ext3 for booting from other media, ext4, XFS, reiserfs, NTFS read support, ISO9660, UDF, CIFS, automounter, squashfs, unionfs, device mapper and dm-loop, cryptography, cryptoloop, EFI partitions, UTF8 codepages, mouse+joystick input, PPP, PPTP, serial support, USB hostmode (h-e-n), USB/IP and generic USB device drivers, battery info, overclocking and kexec support.
Note: This page is under construction and based on the overclocking/undervolting instructions. Hence the heavy bias to overclocking. For overclocking it includes a large set of possible frequencies (125 MHz-1.15 GHz) which you manually set and try out without flashing a new kernel. The defaults are set to the standard 250-600 MHz range. You can also fine tune the voltages for your device for power-saving. Every device is different.
talk.maemo.org: Discussion of the enhanced kernel Discussion of the enhanced kernel beginning with version 47
Changes between versions are announced on the garage page.
Installation of the kernel
Note: all commands on this page must be run as root in X Terminal (install rootsh package and enter "sudo gainroot")
Warning: the power kernel is not compatible with older versions of the fcam drivers and will cause all camera functionality to be lost until those drivers are updated. You can update them either by removing all programs that use the fcam drivers (BlessN900, Fcamera, Panorama, etc.) and then installing them again or by running as root:
apt-get install fcam-drivers
Installation of the stable kernel from extras
With this kernel you can change the frequency limits, the voltages and DSP frequencies online. It requires firmware PR1.1 or newer.
- Install the package
kernel-power-settings(section system in Application manager). It will automatically also installkernel-power-flasher. - shutdown and boot again. There's no need for reflashing etc.
See below for configuration information
Installation of the testing kernel from extras-testing
This kernel version contains additional experimental features and patches.
Just enable the Extras-testing catalogue and install according to these instructions.
Please follow the QA checklist and vote for the package.
Verification of proper installation
First verify, that the kernel is actually running:
uname -r
should return "2.6.28.10power-omap1" or "2.6.28.10power<version>". If it does not, you should reboot or try to install again
apt-get install --reinstall -y kernel-power kernel-power-flasher
reboot, and test again.
Upgrade from older versions (< maemo24)
The kernel package was previously called kernel-flasher-maemo. Unfortunately, Application Manager does not support package transitions, i.e. installation of the new version leads to conflicts with kernel-maemo and kernel-modules-maemo.
If you have one of the older packages installed it you need to upgrade in X Terminal
sudo gainroot apt-get install -y kernel-power-flasher apt-get remove kernel-flasher-maemo
If the new kernel still doesn't boot up, try
apt-get install --reinstall -y kernel-power kernel-power-flasher
Also try other hints for deinstalling the old package.
Make sure you reset /etc/pmconfig to the defaults:
# Power management configuration file enable_off_mode 1 sleep_while_idle 1 sr_vdd1_autocomp 0 sr_vdd2_autocomp 0 clocks_off_while_idle 1 voltage_off_while_idle 1 scaling_governor ondemand scaling_max_freq 600000 scaling_min_freq 125000 sleep_ind 1
Deinstallation
Do not try to deinstall the package in Application Manager! It does not work.
You never want to DEINSTALL a kernel, your device can't work without kernel, so you rather replace the kernel. That's what the following instructions actually do.
For all kernels the safest method for deinstallation is the following:
- make sure you have a working Internet connection (and possibly wait a little bit until the updates are downloaded)
- make sure the package rootsh (Section system) is installed
- close Application manager
-
execute the following in X-Terminal
root apt-get install --reinstall -y kernel kernel-flasher
-
if it finishes successfully (with "SIGTERM received" and "Image flashed successfully" messages) then you can continue with
apt-get remove -y kernel-power kernel-power-modules
-
after successful deinstallation the command:
ls -l /lib/modules/current
should show:
... /lib/modules/current -> 2.6.28-omap1
- shutdown (without USB cable or charger connected) and boot again
- your device should now be running the stock kernel
If the device fails to boot or you have other problems, perform the deinstallation from PC with USB cable and flasher utility:
- make sure you have a version 28 or later installed (it fixes the broken /sbin/preinit)
- for older versions it is not guaranteed that this method will work without a complete reflash.
- make sure your battery is properly charged (if it fails, charge your battery)
- execute the following on your PC (see this for more details)
flasher-3.5 -f --flash-only=kernel -R -F <firmware-image>
The firmware image file could be, for example, RX-51_2009SE_3.2010.02-8_PR_COMBINED_MR0_ARM.bin. This is only way of deinstallation with leaked release 1.2 firmware.
If you have a recent kernel (>v27), there is a "Deinstall kernel" application in your menu. This applications is, however, still experimental (for >v27 it is more stable). Only use if have can fall back to reflashing the kernel using the flasher (see below) in case of problems. Read the instructions carefully when you start the deinstall application!
Upgrading to a new PR
Before upgrading, always make a backup. There are two ways of upgrading the firmware to a new Nokia public release (PR):
- reflashing the complete firmware via flasher or NSU. This is safest way (especially for PR1.2). In this case you simply reinstall the kernel after the upgrade. The settings should be restored by the backup application.
- Over The Air (OTA) upgrade: this upgrades only system components of your device so that you don't need to restore your settings or reinstall applications. see below
OTA upgrade: Disable extras-devel and extras-testing. DIsable autodisconnect if is installed. Perform the upgrade. If the PR does not deliver a new kernel (PR1.1.1) then you're done. If it provides a new kernel (PR1.1 and PR1.2) then you need to reinstall the enhanced kernel with the following commands:
sudo gainroot apt-get install --reinstall kernel-power kernel-power-modules kernel-power-flasher
Holding a specific kernel version
If your manually installed kernel should be not upgraded to the one in extras* try this:
echo kernel-power-flasher hold | dpkg --set-selections echo kernel-power hold | dpkg --set-selections echo kernel-power-modules hold | dpkg --set-selections
to unlock the version:
echo kernel-power-flasher install | dpkg --set-selections echo kernel-power install | dpkg --set-selections echo kernel-power-modules install | dpkg --set-selections
Issues after multiboot or Nitdroid installation
Multiboot changes the boot process and might not load kernel-power properly. This is not a kernel-power problem. Please read the multiboot threads or Nitdroid forums. For versions >=v39 typically
apt-get install kernel-power-bootimg apt-get install --reinstall multiboot-kernel-power
adds kernel-power to your boot menu.
Features
Configuring the kernel speed/voltage settings
The following instructions require the kernel-power-flasher >=v27 and kernel-power-settings >=0.8.
If you upgraded from the old stable version the old settings should still work and be loaded during boot.
Basic, Conservative Undervolting/overclocking
After installing the power kernel and verifying it is installed, make sure you have rootsh installed and have backed up your data to an external storage device and type
sudo kernel-config load ideal
This will load the ideal template, which has these undervolted settings. These are stable on most N900s, but be sure to test by playing back some videos and doing some web browsing. Make sure your device is stable at all the frequencies! Then, type
sudo kernel-config default ideal
and you will have the ideal undervoltage/overclock settings as standard that persist through reboots. Until you type that, your settings will default to standard after a reboot.
Use of kernel-config
In the following "kernel-config" must be replaced by either "sudo kernel-config" or "/usr/sbin/kernel-config". If you get an error message "command not found" then you have an old version of kernel-power-settings installed. Use:
dpkg -l kernel-power-settings
to show the installed version number.
To list the current configuration of the kernel use:
kernel-config show
If you have loaded an old config, or changed the current settings manually or using CPUfreqUI you can save the current settings with
kernel-config save myconfig
this will automatically save it in /home/user/.kernel/myconfig and create the directory if necessary (replace myconfig with any name you like). To save it somewhere else (why would you?) use the absolute path.
A configuration (here myconfig) is loaded with
kernel-config load myconfig
If the filename is not absolute (e.g. "./myconfig") it searches for the file in the current dir, /home/user/.kernel and /usr/share/kernel-power-settings/. Without a file name it loads /etc/default/kernel-power, or /usr/share/kernel-power-settings/default. Do NOT modify the files in /usr/share/kernel-power-settings. They are templates. The template names are: default, lv, ulv, xlv, ideal, starving.
kernel-config default myconfig
copies the configuration file to /etc/default/kernel-power (or symlinks if it is a template file from /usr/share/kernel-power-settings). If you do not specify a filename, the current settings are saved in /etc/default/kernel-power. These settings are then loaded during boot.
kernel-config limits 250 600
sets the limits to [min,max]. If you use "-" for a frequency, the current value is used. For example, "kernel-config limits - 850" only changes the upper limit to 850 Mhz.
kernel-config lock freq volt dsp
(e.g. 500 48 400) can be used to test voltage and dsp settings with a certain frequency. It overwrites the current settings for that frequency and locks the CPU to only that frequency until you run "kernel-config unlock" to unlock it.
Configuration files
You can edit /etc/default/kernel-power or the files in /home/user/.kernel/.
The content of the default template is:
# minimum frequency to use MINFREQ=250 # maximum frequency to use MAXFREQ=600 # list of frequency configurations: each "frequency:volt,dsprate" FREQS="0:30,90 125:30,90 250:38,180 500:48,360 550:54,400 600:60,430 700:60,430 750:60,430 805:60,430 850:60,500 900:60,500 950:60,500 1000:60,500 1100:72,520 1150:72,520" SMARTREFLEX_VDD1=0 SMARTREFLEX_VDD2=0 GOVERNOR=ondemand UP_THRESHOLD=95 SAMPLING_RATE=300000 IGNORE_NICE_LOAD=0 POWERSAVE_BIAS=0
available frequencies not listed in FREQS as well as frequencies below MINFREQ are avoided. This means when you save a profile, all frequencies below MINFREQ will not be saved in FREQS!
The boot sequence
The kernel settings are only loaded if you had a normal reboot or shutdown but not after a crash. In that case the file /etc/kernel-power/.notloaded is created
and a notification will be shown after booting. The settings will be loaded at the next boot again unless it crashes again.
Configuring the kernel speed/voltage settings (of the obsolete version 24)
These instructions refer to the obsolete kernel-power-flasher v24 and kernel-power-settings 0.3.
Some remarks for version v24:
- If you for some reason get errors like this during removal or installation "rm: cannot remove '/lib/modules/2.6.28.10maemo-lv-omap1/modules.*': No such file or directory".try this workaround. There was a bug in one of the early LV kernels but it should be fixed in more recent versions.
- The screen calibration in settings crashes immediately with v24. It is a known bug in the calibration app, not in the kernel. It's mentioned in the kernel package description and is due to additional evdev (joystick,mouse) support. Just calibrate once with the stock kernel before you install the fully featured kernel. Alternatively run the following commands and reboot
sudo gainroot echo blacklist mousedev > /etc/modprobe.d/blacklist
This kernel makes it possible to dynamically change the maximum frequency up to 1.15GHz (supported frequencies are 125,250,500,550,600,700,750,805,850,900,950,1000,1100,1150 MHz). WARNING: Overclocking may damage your device and is at your own risk! It may void your warranty and destroy your data. You have been warned.
For more details on voltages read Overclocking#Voltage_tables.
Make sure the packages kernel-power-settings and rootsh are installed. All commands need to be run as root user. If you are normal user in X Terminal enter "sudo gainroot".
-
to try a configuration (you can replace "ideal" with default, lv, ulv, xlv or specify a file you created based on the template
/usr/share/kernel-power-settings/default)/usr/sbin/kernel-load /usr/share/kernel-power-settings/ideal
'Note: do NOT modify the files in
/usr/share/kernel-power-settings/! see Creating your own configuration: below. -
to permanently install a default configuration
rm -f /etc/default/kernel-power ln -s /usr/share/kernel-power-settings/ideal /etc/default/kernel-power
-
or your own config
rm -f /etc/default/kernel-power cp <filename> /etc/default/kernel-power
-
and to immediately apply it
/usr/sbin/kernel-load
For beginners: first reboot. then try 1) and check whether the device is stable. then do 2).
Creating your own configuration
-
copy the template to your mydocs (when not in mass storage mode)
cp /usr/share/kernel-power-settings/ideal /home/user/MyDocs/kernel.txt
-
edit the file
/home/user/MyDocs/kernel.txt. The defaults are#UP_THRESHOLD=75 #SAMPLING_RATE=150000 VDD1_OPPS_VSEL="30 30 38 48 54 48 60 60 60 60 60 60 60 72 72" DSP_OPPS_RATE="90 90 180 360 400 430 430 430 430 500 500 500 500 520 520" MIN_FREQ=250000 MAX_FREQ=599000 SMARTREFLEX_VDD1=0 SMARTREFLEX_VDD2=0
For changing the frequency range change MIN_FREQ/MAX_FREQ (see "Temporary change of the frequency limits" below ). Either edit the file with an editor on your device (e.g., leafpad) or USB mount it to edit it on the PC. unmount and unplug USB. After editing load the configuration with:
/usr/sbin/kernel-load /home/user/MyDocs/kernel.txt
and repeat 6) until you're happy.
-
to permanently install this new configuration
rm -f /etc/default/kernel-power cp /home/user/MyDocs/kernel.txt /etc/default/kernel-power /usr/sbin/kernel-load
-
to reset the device to the defaults use:
rm -f /etc/default/kernel-power /usr/sbin/kernel-load /usr/share/kernel-power-settings/default
Note: the package automatically detects whether a certain misconfiguration has caused reboot loop. If your device reboots twice within 5 minutes, it will load the default settings (250-600 Mhz) so that you can fix or remove the invalid configuration file. This also means that, when for some reason you manually reboot too quickly (<5 min) your configuration will not be loaded. To load it nonetheless run after booting:
/usr/sbin/kernel-load
Temporary change of the frequency limits
sudo gainroot echo 250000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq echo 599000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
The last line shows which values were actually set. To set 125 MHz use 124999, for 600 MHz 599999, for everthing else x000 with x=MHz. This setting takes effect immediately and is cleared with the next reboot.
Permanent configuration of the frequency limits
WARNING: Permanent overclocking is very dangerous!
Install kernel-power-settings and follow the above instructions.
Battery
In kernels version >=maemo20 you can read out the current battery info:
modprobe bq27x00_battery cat /sys/class/power_supply/bq27200-0/capacity cat /sys/class/power_supply/bq27200-0/voltage_now cat /sys/class/power_supply/bq27200-0/current_now cat /sys/class/power_supply/bq27200-0/temp cat /sys/class/power_supply/bq27200-0/charge_full cat /sys/class/power_supply/bq27200-0/charge_full_design cat /sys/class/power_supply/bq27200-0/charge_now cat /sys/class/power_supply/bq27200-0/time_to_empty_avg cat /sys/class/power_supply/bq27200-0/time_to_empty_now cat /sys/class/power_supply/bq27200-0/time_to_full_now
- 'capacity' value in percentage of battery level.
- 'voltage_now' value in mV of battery voltage level.
- 'current_now' value in microA of battery current consumption.
- 'temp' value in degrees C of battery temperature. (>= v47: in tenths of degree Celsius)
In kernel version >= v47 is additional info:
- 'charge_full' value in µAh - last remembered value of charge when battery became full
- 'charge_full_design' value in µAh - design charge value, when battery considered full
- 'charge_now' value in µAh - actual charge value
- 'time_to_empty_avg' averaged value - seconds left for battery to be considered empty (i.e. while battery powers a load)
- 'time_to_empty_now' seconds left for battery to be considered empty (i.e. while battery powers a load)
- 'time_to_full_now' seconds left for battery to be considered full (i.e. while battery is charging)
To remove this kernel module use:
rmmod bq27x00_battery
or reboot.
With kernel-power-settings >=0.6 the module can be loaded on boot. Just execute this once:
sudo gainroot echo bq27x00_battery >> /etc/modules
With kernel version >= v47 the bq module is automatically loaded on boot. To disable, blacklist bq27x00_battery module:
sudo gainroot echo bq27x00_battery >> /etc/modprobe.d/blacklist
Mobile hotspot
all necessary modules are included. read this for more details.
JoikuSpot
seems to work. read this post.
Update: it doesn't work for me (recent version of Joikuspot and Maemo), ICMP and DNS resolving work OK, but TCP connections are completely freezed...If it works for you, let us know.
CIFS Support
You can now mount a network drive using Microsoft's CIFS protocol. To do so you need to do the following:
1) Share a folder on your Windows PC, with the latest versions of Windows you will have to create a user account with a password to share a specific folder that is not the Public Library.
2) Create a folder for the mount, pressumably on your /home/users/MyDocs folder, so that you could access your network drive through the file manager.
3) Mount the folder on your device by typing the following into xterm under root:
mount -t cifs //netbiosname/sharename /media/sharename -o user=winusername,pass=winpassword,ip=destip,direct
Working example:
mount -t cifs //KOPC/Users/Public /home/users/MyDocs/Share -o user=lilo,pass=1234,ip=192.168.2.2,direct
kexec (booting MeeGo and other kernels)
all necessary kexec patches are included. read [1] and this post for MeeGo support.
boot options
There is a separate file /etc/default/kernel-boot for extra boot options. It requires kernel-power-settings >= 0.11 and is disabled by default. These two options are experimental and may brick your device! Just install the template with the following commands and edit it (by default the options are disabled)
sudo gainroot cp /usr/share/kernel-power-settings/boot /etc/default/kernel-boot
The default template looks like this
# start USB networking and sshd early during boot EARLY_SSH=0 # fsck of /home partition before mounting? # 1=if necessary, force=always check FSCK_HOME=0
file system check and repair of /home, premount scripts
see boot options for enabling this feature. The following operations are performed before mounting /home:
- If you have a script (e.g. for repartitiong) called /etc/kernel-power/pre-mount.once it will be executed once and then moved away.
- if FSCK_HOME is enabled the /home partition (first ext3 on eMMC) will be fscked on boot.
Alternatively
sudo gainroot echo 1 > /etc/kernel-power/force_fsck
should check it only during next boot.
sudo gainroot echo 0 > /etc/kernel-power/force_fsck
disables it only for the next boot. If you reset or reboot the device during fsck, it will not fsck (only) during the next boot. All messages are logged to /etc/kernel-power/pre-mount.log
IPv6
IPv6 support is enabled and many users are successfully using it. Note, however, not all applications are IPv6 compatible.
So far, it has been successfully used with Chromium and Firefox out of the box. To run with the MicroB browser, you need to change one of the settings.
The setting is 'network.dns.disableIPv6' in about:config. When set to false, IPv6 just works when the phone has IPv6 connectivity.
IPv6 has also been used successfully with ssh and sshd.
Please share additional experiences here.
PPTP
Kismet
tutorial and TMO thread
other filesystems
the kernel includes support for many alternative filesystem (incl. ext4 bugfixes and large files). You might want to repartition your eMMC or SD card with Repartitioning_the_flash.
Remarks
- even if 125 Mhz is disabled, the telephone app will always try to set the minimum freq. to 125 Mhz after a phone call, but it is ignored unless you enable 125 Mhz.
- if you enable 125 MHz also set "
echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/ignore_nice_load" hint - the 125 MHz issue
- Installing another version of the enhanced kernel will just overwrite the older version. The stock kernel modules are preserved so that you can simply reflash the stock kernel via USB.
- The kernel supports 125 MHz but this frequency is disabled by default in avoid_frequencies. In version <25, it is enabled by specifying "124999", in later versions it is disabled in
/sys/devices/system/cpu/cpu0/cpufreq/ondemand/avoid_frequenciesand can be enabled with:echo > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/avoid_frequencies
similarily, individual frequencies can be disabled in >=v25:echo 125000 250000 750000 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/avoid_frequencies