Editing Kernel Power

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|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.

[http://talk.maemo.org/showthread.php?t=43420 talk.maemo.org: Discussion of the enhanced kernel]

[http://talk.maemo.org/showthread.php?t=71879: Discussion of the enhanced kernel beginning with version 47]

==Installing kernel-power==

'''Note:''' All commands on this page must be [[root access|run as root]] in [[terminal|X Terminal]] (install rootsh package and enter "root")

 

 

===Installing the [http://maemo.org/downloads/product/Maemo5/kernel-power-flasher/ Stable Kernel]===

# Shutdown the device, and boot it up again.

# The kernel is now installed.

===Installing the Unstable Kernels===

Just enable the [[Extras-testing]] or [[Extras-devel]] catalogue and install according to [[#Installing the Stable Kernel|these instructions]].

 

=== Verifying Proper Installation ===  

First verify, that the kernel is actually running:<pre>uname -r</pre>

should return "2.6.28.10power<version>".

If it does not, you should reboot or try to [[#Installing kernel-power|install the kernel again]].

The kernel package was previously called <code>kernel-flasher-maemo</code>. Unfortunately, Application Manager does not support package transitions, i.e. installation of the new version leads to conflicts with <code>kernel-maemo</code> and <code>kernel-modules-maemo</code>.

If you have one of the older packages installed it you need to upgrade in X Terminal.

apt-get install -y kernel-power-flasher

apt-get remove kernel-flasher-maemo

<pre>apt-get install --reinstall -y kernel-power kernel-power-flasher</pre>

Also try [http://talk.maemo.org/showpost.php?p=608343&postcount=2603 other hints] for uninstalling the old package.

Make sure you reset <code>/etc/pmconfig</code> 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

===Uninstalling kernel-power===

Do not try to uninstall the "kernel-power" package in Application Manager!

This does not remove the kernel, as it is installed in the device's NAND.

'''You never want to uninstall a kernel''', as your device can't work without a kernel.

====Installing the Nokia Kernel with X Terminal====

The standard process for replacing the kernel is as follows:

# Ensure that you have a working Internet connection.

# Install the package '''rootsh'''. (available in the System section of the Application Manager)

# Close the Application Manager.

# Gain root permissions<pre>sudo gainroot</pre>

# Reinstall the stock Nokia kernel<pre>apt-get install --reinstall -y kernel kernel-flasher</pre>

# Should it complete successfully (with "SIGTERM received" and "Image flashed successfully" messages), then you can continue with <pre>apt-get remove -y kernel-power kernel-power-modules</pre>

# After uninstallation, the command <pre>ls -l /lib/modules/current</pre>should show: <pre>... /lib/modules/current -> 2.6.28-omap1</pre>

# Shutdown the device (without any USB cable connected) and boot again.

# The stock kernel should now be installed.

If you have a recent kernel (>v27), there is a "Deinstall kernel" application in your menu.

This application 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.

Before upgrading, always make a backup. There are two ways of upgrading the firmware to a new Nokia public release (PR):

# [[Updating the firmware|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.

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:

  root

 

echo kernel-power-flasher hold | dpkg --set-selections

echo kernel-power hold | dpkg --set-selections

echo kernel-power-modules hold | dpkg --set-selections

echo kernel-power-flasher install | dpkg --set-selections

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,

adds kernel-power to your boot menu.

=== Configuring the kernel speed/voltage settings ===

The instructions on the [[Overclocking]] page require the <code>kernel-power-flasher >=v27</code> and <code>kernel-power-settings >=0.8</code>.

If you upgraded from the old stable version the old settings should still work and be loaded during boot.

'''NOTE''': The kernel settings are not loaded after a crash. In that case the file <code>/etc/kernel-power/.notloaded</code> is created

and a notification will be shown after booting. The settings will be loaded at the next boot again unless it crashes again.

'''bq27200.ko module conflicts with bme battery charging! A "fix" temporarily added to I2C driver broke system completely and thus got reverted'''

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

</pre>

*'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

*'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:

With kernel-power-settings >=0.6 the module can be loaded on boot. Just execute this once:

With kernel version >= v47 the bq module is automatically loaded on boot. To disable, blacklist bq27x00_battery module:

echo bq27x00_battery >> /etc/modprobe.d/blacklist</pre>

===JoikuSpot===  

seems to work.  read [http://talk.maemo.org/showpost.php?p=653966&postcount=3592 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.

You can now mount a network drive using Microsoft's CIFS protocol. To do so you need to do the following:

# 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.

# Mount the folder on your device by typing the following into xterm under root:

<pre>mount -t cifs //netbiosname/sharename /media/sharename -o user=winusername,pass=winpassword,ip=destip,direct</pre>

===kexec===  

 

===Boot Options===

 

 

 

====Filesystem Checking and Repair, and pre-mount Scripts====

 

 

# 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.

 

 

IPv6 support is enabled and many users are successfully using it.

 

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.

 

Please share additional experiences here.

[http://talk.maemo.org/showthread.php?t=36172 tutorial]

[http://david.gnedt.eu/blog/2010/05/11/kismet-fully-functional-monitor-mode-for-the-n900/ tutorial] and

[http://talk.maemo.org/showthread.php?t=52393 TMO thread]

===Other Filesystems===

The kernel includes support for many alternative filesystems, including ext4 bugfixes and large file support.

You might want to repartition your eMMC or SD card with [[Repartitioning_the_flash]].

==Notes==

# 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  "<code>echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/ignore_nice_load</code>" [http://talk.maemo.org/showpost.php?p=602687&postcount=185 hint]

# [http://talk.maemo.org/showpost.php?p=597703&postcount=141 the 125 MHz issue]

# The kernel supports 125 MHz but this frequency is [http://talk.maemo.org/showpost.php?p=617488&postcount=3095 disabled by default] in avoid_frequencies. In version <25, it is enabled by specifying "124999", in later versions it is disabled in ''<code>/sys/devices/system/cpu/cpu0/cpufreq/ondemand/avoid_frequencies</code>'' and can be enabled with: <pre>echo > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/avoid_frequencies</pre>similarily, individual frequencies can be disabled in >=v25:<pre>echo 125000 250000 750000 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/avoid_frequencies</pre>