Kernel Power - Revision history

122.57.34.193: /* Installing kernel-power */

2016-07-03T01:38:29Z

Installing kernel-power

← Older revision		Revision as of 01:38, 3 July 2016
Line 17:		Line 17:

	'''Note: The power kernel may not be compatible with the currently-installed fcam-drivers package.''' Should you lose camera functionality, you can update them by running as root:<pre>apt-get install fcam-drivers</pre>		'''Note: The power kernel may not be compatible with the currently-installed fcam-drivers package.''' Should you lose camera functionality, you can update them by running as root:<pre>apt-get install fcam-drivers</pre>
		+
		+	'''Note:''' This probably won't work and you'll probably need to install fcam-drivers-1.0.7-2 from extras-devel:
		+	http://repository.maemo.org/extras-devel/pool/fremantle/free/f/fcam-drivers/fcam-drivers_1.0.7-2_armel.deb
		+	install with ''dpkg -i'' command

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

hurrian: Restructured and cleaned up.

2012-06-08T15:52:25Z

Restructured and cleaned up.

Show changes

joerg_rw: borked bq27200, root

2012-04-18T14:12:55Z

borked bq27200, root

← Older revision		Revision as of 14:12, 18 April 2012
Line 13:		Line 13:
	== Installation of the kernel ==		== Installation of the kernel ==

-	'''Note:''' all commands on this page must be [[root access\|run as root]] in [[terminal\|X Terminal]] (install rootsh package and enter "~~sudo gainroot~~")	+	'''Note:''' all commands on this page must be [[root access\|run as root]] in [[terminal\|X Terminal]] (install rootsh package and enter "root")

	'''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:		'''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:
Line 43:		Line 43:
	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>.		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		If you have one of the older packages installed it you need to upgrade in X Terminal
-	~~sudo gainroot~~	+	root
	apt-get install -y kernel-power-flasher		apt-get install -y kernel-power-flasher
	apt-get remove kernel-flasher-maemo		apt-get remove kernel-flasher-maemo
Line 231:		Line 231:
	# 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 [http://talk.maemo.org/showpost.php?p=603938&postcount=196 workaround]. There was a bug in one of the early LV kernels but it should be fixed in more recent versions.		# 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 [http://talk.maemo.org/showpost.php?p=603938&postcount=196 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		# 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~~	+	root
	echo blacklist mousedev > /etc/modprobe.d/blacklist		echo blacklist mousedev > /etc/modprobe.d/blacklist

Line 238:		Line 238:
	For more details on voltages read [[Overclocking#Voltage_tables]].		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~~".	+	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 "root".

	<ol>		<ol>
Line 334:		Line 334:

	== Battery ==		== Battery ==
		+	'''bq27200.ko module conflicts with bme battery charging! A "fix" temporarily added to I2C driver broke system completely and thus got reverted'''
	In kernels version >=maemo20 you can read out the current battery info:		In kernels version >=maemo20 you can read out the current battery info:

Line 370:		Line 371:

	With kernel-power-settings >=0.6 the module can be loaded on boot. Just execute this once:		With kernel-power-settings >=0.6 the module can be loaded on boot. Just execute this once:
-	~~sudo gainroot~~	+	root
	echo bq27x00_battery >> /etc/modules		echo bq27x00_battery >> /etc/modules

	With kernel version >= v47 the bq module is automatically loaded on boot. To disable, blacklist bq27x00_battery module:		With kernel version >= v47 the bq module is automatically loaded on boot. To disable, blacklist bq27x00_battery module:
-	~~sudo gainroot~~	+	root
	echo bq27x00_battery >> /etc/modprobe.d/blacklist		echo bq27x00_battery >> /etc/modprobe.d/blacklist

Line 410:		Line 411:
	These two options are experimental and may brick your device!		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)		Just install the template with the following commands and edit it (by default the options are disabled)
-	~~sudo gainroot~~	+	root
	cp /usr/share/kernel-power-settings/boot /etc/default/kernel-boot		cp /usr/share/kernel-power-settings/boot /etc/default/kernel-boot

Line 428:		Line 429:
	# if FSCK_HOME is enabled the /home partition (first ext3 on eMMC) will be fscked on boot.		# if FSCK_HOME is enabled the /home partition (first ext3 on eMMC) will be fscked on boot.
	Alternatively		Alternatively
-	~~sudo gainroot~~	+	root
	echo 1 > /etc/kernel-power/force_fsck		echo 1 > /etc/kernel-power/force_fsck
	should check it only during next boot.		should check it only during next boot.
-	~~sudo gainroot~~	+	root
	echo 0 > /etc/kernel-power/force_fsck		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 <code>/etc/kernel-power/pre-mount.log</code>		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 <code>/etc/kernel-power/pre-mount.log</code>

joerg_rw: /* Configuring the kernel speed/voltage settings (of the obsolete version 24) */ root

2012-04-18T14:06:35Z

Configuring the kernel speed/voltage settings (of the obsolete version 24): root

← Older revision		Revision as of 14:06, 18 April 2012
Line 320:		Line 320:

	<pre>		<pre>
-	~~sudo gainroot~~	+	root
	echo 250000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq		echo 250000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
	echo 599000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq		echo 599000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

joerg_rw: /* Upgrading to a new PR */ root is the way

2012-04-18T14:04:25Z

Upgrading to a new PR: root is the way

← Older revision		Revision as of 14:04, 18 April 2012
Line 124:		Line 124:
	OTA upgrade:		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:		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~~	+	root
	apt-get install --reinstall kernel-power kernel-power-modules kernel-power-flasher		apt-get install --reinstall kernel-power kernel-power-modules kernel-power-flasher

joerg_rw: /* Deinstallation */

2012-04-18T14:03:05Z

Deinstallation

← Older revision		Revision as of 14:03, 18 April 2012
Line 68:		Line 68:
	Do not try to deinstall the package in Application Manager! It does not work.		Do not try to deinstall the package in Application Manager! It does not work.

-	'''You never want to ~~DESINSTALL~~ a kernel''', your device can't work without kernel, so you rather replace the kernel. That's what the following instructions actually do.	+	'''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:		For all kernels the safest method for deinstallation is the following:

joerg_rw: /* Deinstallation */ kernel can't deinstall

2012-04-18T14:02:25Z

Deinstallation: kernel can't deinstall

← Older revision		Revision as of 14:02, 18 April 2012
Line 67:		Line 67:
	=== Deinstallation ===		=== Deinstallation ===
	Do not try to deinstall the package in Application Manager! It does not work.		Do not try to deinstall the package in Application Manager! It does not work.
		+
		+	'''You never want to DESINSTALL 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:		For all kernels the safest method for deinstallation is the following:

joerg_rw: /* Deinstallation */ sudo gainroot -> root

2012-04-18T13:57:49Z

Deinstallation: sudo gainroot -> root

← Older revision		Revision as of 13:57, 18 April 2012
Line 82:		Line 82:
	execute the following in X-Terminal		execute the following in X-Terminal
	<pre>		<pre>
-	~~sudo gainroot~~	+	root
	apt-get install --reinstall -y kernel kernel-flasher		apt-get install --reinstall -y kernel kernel-flasher
	</pre>		</pre>

joerg_rw: h-e-n

2012-04-18T13:52:29Z

h-e-n

← Older revision		Revision as of 13:52, 18 April 2012
Line 1:		Line 1:
	The enhanced kernel "kernel-power" is compatible with [[Maemo_5/PR1.2\|PR1.2]] and [[Maemo_5/PR1.3\|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 enhanced kernel "kernel-power" is compatible with [[Maemo_5/PR1.2\|PR1.2]] and [[Maemo_5/PR1.3\|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/IP and generic USB device drivers, battery info, overclocking and kexec support.	+	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.		'''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.

pali: /* Battery */

2011-06-21T13:13:00Z

Battery

← Older revision		Revision as of 13:13, 21 June 2011
Line 340:		Line 340:
	cat /sys/class/power_supply/bq27200-0/current_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/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
	</pre>		</pre>

Line 345:		Line 351:
	*'voltage_now' value in mV of battery voltage level.		*'voltage_now' value in mV of battery voltage level.
	*'current_now' value in microA of battery current consumption.		*'current_now' value in microA of battery current consumption.
-	*'temp' value in degrees C of battery temperature.	+	*'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:		To remove this kernel module use:
Line 356:		Line 370:
	sudo gainroot		sudo gainroot
	echo bq27x00_battery >> /etc/modules		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 ==		== Mobile hotspot ==