User:Jebba/Kernel - Revision history

imported_>jebba: /* Installing my custom kernel */

2010-03-15T23:03:04Z

Installing my custom kernel

← Older revision		Revision as of 23:03, 15 March 2010
Line 12:		Line 12:

	==Installing my custom kernel==		==Installing my custom kernel==

	~~'''FOR THE LATEST "PR1.1" UPDATE I CANNOT BUILD FLASHABLE KERNELS BECAUSE NOKIA HAS ADDED AN UNAVAILABLE BINARY NEEDED TO CREATE FLASHABLE KERNEL'''~~

	~~Gah, see:~~
	~~https://bugs.maemo.org/show_bug.cgi?id=7972~~

imported_>jebba: /* Installing my custom kernel */ not certain it's proprietary yet, actually.

2010-01-14T13:18:15Z

Installing my custom kernel: not certain it's proprietary yet, actually.

← Older revision		Revision as of 13:18, 14 January 2010
Line 13:		Line 13:
	==Installing my custom kernel==		==Installing my custom kernel==

	'''FOR THE LATEST "PR1.1" UPDATE I CANNOT BUILD FLASHABLE KERNELS BECAUSE NOKIA HAS ADDED AN UNAVAILABLE ~~PROPRIETARY~~ BINARY NEEDED TO CREATE FLASHABLE KERNEL'''		'''FOR THE LATEST "PR1.1" UPDATE I CANNOT BUILD FLASHABLE KERNELS BECAUSE NOKIA HAS ADDED AN UNAVAILABLE BINARY NEEDED TO CREATE FLASHABLE KERNEL'''

	Gah, see:		Gah, see:

imported_>jebba: /* Installing my custom kernel */ can't build flashable pr1.1 kernel

2010-01-14T13:14:40Z

Installing my custom kernel: can't build flashable pr1.1 kernel

← Older revision		Revision as of 13:14, 14 January 2010
Line 12:		Line 12:

	==Installing my custom kernel==		==Installing my custom kernel==

			'''FOR THE LATEST "PR1.1" UPDATE I CANNOT BUILD FLASHABLE KERNELS BECAUSE NOKIA HAS ADDED AN UNAVAILABLE PROPRIETARY BINARY NEEDED TO CREATE FLASHABLE KERNEL'''

			Gah, see:
			https://bugs.maemo.org/show_bug.cgi?id=7972


	Linux Nokia-N900-42-11 2.6.28-omap1-jebba9-g649dffc #1 PREEMPT Mon Jan 11 16:25:16 MST 2010 armv7l unknown		Linux Nokia-N900-42-11 2.6.28-omap1-jebba9-g649dffc #1 PREEMPT Mon Jan 11 16:25:16 MST 2010 armv7l unknown

imported_>jebba: /* Installing my custom kernel */ update uname -a

2010-01-12T01:38:38Z

Installing my custom kernel: update uname -a

← Older revision		Revision as of 01:38, 12 January 2010
Line 12:		Line 12:

	==Installing my custom kernel==		==Installing my custom kernel==
	Linux Nokia-N900-42-11 2.6.28-omap1-~~jebba8~~-~~g0929a26-dirty~~ #1 PREEMPT Mon Jan 11 09:54:26 MST 2010 armv7l unknown		Linux Nokia-N900-42-11 2.6.28-omap1-jebba9-g649dffc #1 PREEMPT Mon Jan 11 16:25:16 MST 2010 armv7l unknown

imported_>jebba: /* Installing my custom kernel */ update to 2.6.28-20094102.6+0m14

2010-01-12T00:35:39Z

Installing my custom kernel: update to 2.6.28-20094102.6+0m14

imported_>jebba: /* Kernel */ update to: kernel-flasher_2.6.28-20094102.6+0m12_armel.deb

2010-01-11T19:32:01Z

Kernel: update to: kernel-flasher_2.6.28-20094102.6+0m12_armel.deb

← Older revision		Revision as of 19:32, 11 January 2010
Line 12:		Line 12:

	==Installing my custom kernel==		==Installing my custom kernel==
	Linux Nokia-N900-42-11 2.6.28-omap1-~~jebba6~~ #1 PREEMPT ~~Sat~~ Jan ~~2 13~~:04:25 MST 2010 armv7l unknown		Linux Nokia-N900-42-11 2.6.28-omap1-jebba8-g0929a26-dirty #1 PREEMPT Mon Jan 11 09:54:26 MST 2010 armv7l unknown


	I have built custom kernel packages closely based on the standard kernel that ships with the N900. Differences:		I have built custom kernel packages closely based on the standard kernel that ships with the N900. Differences:

	* NOTE: this kernel now has NAT and a bunch of filesystems and other misc. See [http://www.freemoe.org/users/jebba/dists/unstable/main/source/kernel_2.6.28-20094102.3+~~0m11~~/kernel_2.6.28-20094102.3+~~0m11_armel~~.changes the latest changes]		* NOTE: this kernel now has NAT and a bunch of filesystems and other misc. See [http://www.freemoe.org/users/jebba/dists/unstable/main/source/kernel_2.6.28-20094102.6+0m12/kernel_2.6.28-20094102.6+0m12_armel.changes the latest changes]

	* FRAMEBUFFER_CONSOLE=y - This fantastic option means you can see console when the kernel boots up, so you see all the text you usually see when booting up a Linux kernel.		* FRAMEBUFFER_CONSOLE=y - This fantastic option means you can see console when the kernel boots up, so you see all the text you usually see when booting up a Linux kernel.
Line 26:		Line 26:
	* CONFIG_LOGO=y, CONFIG_LOGO_LINUX_CLUT224=y - Tux, the Linux penguin, at boot! :)		* CONFIG_LOGO=y, CONFIG_LOGO_LINUX_CLUT224=y - Tux, the Linux penguin, at boot! :)

	* The kernel name is 2.6.28-omap1-~~jebba6~~ so as to not confuse it with the stock kernel.		* The kernel name is 2.6.28-omap1-jebba8 so as to not confuse it with the stock kernel.

	You can install this kernel via my repo with apt-get (untested), or manually, which is recommended for now. Procedure (assuming you are running the kernel that ships with the device):		You can install this kernel via my repo with apt-get (untested), or manually, which is recommended for now. Procedure (assuming you are running the kernel that ships with the device):
Line 35:		Line 35:
	* Grab my kernels with wget or whatever (check the dir for more recent versions too).		* Grab my kernels with wget or whatever (check the dir for more recent versions too).
	wget \		wget \
	http://www.freemoe.org/users/jebba/dists/unstable/main/binary-armel/kernel_2.6.28-20094102.3+~~0m11_armel~~.deb \		http://www.freemoe.org/users/jebba/dists/unstable/main/binary-armel/kernel_2.6.28-20094102.6+0m12_armel.deb \
	http://www.freemoe.org/users/jebba/dists/unstable/main/binary-armel/kernel-modules_2.6.28-20094102.3+~~0m11_armel~~.deb \		http://www.freemoe.org/users/jebba/dists/unstable/main/binary-armel/kernel-modules_2.6.28-20094102.6+0m12_armel.deb \
	http://www.freemoe.org/users/jebba/dists/unstable/main/binary-armel/kernel-flasher_2.6.28-20094102.3+~~0m11_armel~~.deb		http://www.freemoe.org/users/jebba/dists/unstable/main/binary-armel/kernel-flasher_2.6.28-20094102.6+0m12_armel.deb

	* Install the .debs with dpkg. Note the flasher has to be installed last. If you install them with dpkg all at once, dpkg will prioritize the flasher first, so it won't move the kernel into place. Point of no return:		* Install the .debs with dpkg. Note the flasher has to be installed last. If you install them with dpkg all at once, dpkg will prioritize the flasher first, so it won't move the kernel into place. Point of no return:
	dpkg -i \		dpkg -i \
	kernel_2.6.28-20094102.3+~~0m11_armel~~.deb \		kernel_2.6.28-20094102.6+0m12_armel.deb \
	kernel-modules_2.6.28-20094102.3+~~0m11_armel~~.deb		kernel-modules_2.6.28-20094102.6+0m12_armel.deb

	* Now install the flasher, which will automatically flash when installed:		* Now install the flasher, which will automatically flash when installed:
	dpkg -i kernel-flasher_2.6.28-20094102.3+~~0m11_armel~~.deb		dpkg -i kernel-flasher_2.6.28-20094102.6+0m12_armel.deb

	* Ok, so the kernel is there, but lets move the original stock modules back into place so you can flash the zImage via flasher-3.5 and USB cable should it be necessary. First we need to remove the mostly empty old dir, then copy the backup:		* Ok, so the kernel is there, but lets move the original stock modules back into place so you can flash the zImage via flasher-3.5 and USB cable should it be necessary. First we need to remove the mostly empty old dir, then copy the backup:

imported_>jebba: /* Compile custom kernel */ FREMANTLE_ARMEL

2010-01-03T20:14:01Z

Compile custom kernel: FREMANTLE_ARMEL

← Older revision		Revision as of 20:14, 3 January 2010
Line 102:		Line 102:


	To unbrick if something goes wrong, unpack the main N900 .bin flash image and flash with the kernel from there. See [[User:Jebba#Unpacking_flash_image\|unpacking flash image]] section.		* To unbrick if something goes wrong, unpack the main N900 .bin flash image and flash with the kernel from there. See [[User:Jebba#Unpacking_flash_image\|unpacking flash image]] section.

			* The MaemoKernel sandbox has apt [https://bugs.maemo.org/show_bug.cgi?id=7598 broken out-of-the-box]

			* stskeeps, the Mer developer, says he builds his kernels fine in FREMANTLE_ARMEL, so perhaps you don't even need to switch to MaemoKernel sandbox. In other words, just build in here:
			sb-conf select FREMANTLE_ARMEL

	==My build scripts and .configs==		==My build scripts and .configs==

imported_>jebba: /* Installing my custom kernel */

2010-01-03T05:49:46Z

Installing my custom kernel

← Older revision		Revision as of 05:49, 3 January 2010
Line 12:		Line 12:

	==Installing my custom kernel==		==Installing my custom kernel==
	Linux Nokia-N900-42-11 2.6.28-omap1-~~jebba5~~ #1 PREEMPT ~~Mon Dec 14 00~~:54:55 MST ~~2009~~ armv7l unknown		Linux Nokia-N900-42-11 2.6.28-omap1-jebba6 #1 PREEMPT Sat Jan 2 13:04:25 MST 2010 armv7l unknown


	I have built custom kernel packages closely based on the standard kernel that ships with the N900. Differences:		I have built custom kernel packages closely based on the standard kernel that ships with the N900. Differences:

			* NOTE: this kernel now has NAT and a bunch of filesystems and other misc. See [http://www.freemoe.org/users/jebba/dists/unstable/main/source/kernel_2.6.28-20094102.3+0m11/kernel_2.6.28-20094102.3+0m11_armel.changes the latest changes]

	* FRAMEBUFFER_CONSOLE=y - This fantastic option means you can see console when the kernel boots up, so you see all the text you usually see when booting up a Linux kernel.		* FRAMEBUFFER_CONSOLE=y - This fantastic option means you can see console when the kernel boots up, so you see all the text you usually see when booting up a Linux kernel.
Line 24:		Line 26:
	* CONFIG_LOGO=y, CONFIG_LOGO_LINUX_CLUT224=y - Tux, the Linux penguin, at boot! :)		* CONFIG_LOGO=y, CONFIG_LOGO_LINUX_CLUT224=y - Tux, the Linux penguin, at boot! :)

	* The kernel name is 2.6.28-omap1-~~jebba5~~ so as to not confuse it with the stock kernel.		* The kernel name is 2.6.28-omap1-jebba6 so as to not confuse it with the stock kernel.

	You can install this kernel via my repo with apt-get (untested), or manually, which is recommended for now. Procedure (assuming you are running the kernel that ships with the device):		You can install this kernel via my repo with apt-get (untested), or manually, which is recommended for now. Procedure (assuming you are running the kernel that ships with the device):
Line 33:		Line 35:
	* Grab my kernels with wget or whatever (check the dir for more recent versions too).		* Grab my kernels with wget or whatever (check the dir for more recent versions too).
	wget \		wget \
	http://www.freemoe.org/users/jebba/dists/unstable/main/binary-armel/kernel_2.6.28-20094102.3+~~0m10_armel~~.deb \		http://www.freemoe.org/users/jebba/dists/unstable/main/binary-armel/kernel_2.6.28-20094102.3+0m11_armel.deb \
	http://www.freemoe.org/users/jebba/dists/unstable/main/binary-armel/kernel-modules_2.6.28-20094102.3+~~0m10_armel~~.deb \		http://www.freemoe.org/users/jebba/dists/unstable/main/binary-armel/kernel-modules_2.6.28-20094102.3+0m11_armel.deb \
	http://www.freemoe.org/users/jebba/dists/unstable/main/binary-armel/kernel-flasher_2.6.28-20094102.3+~~0m10_armel~~.deb		http://www.freemoe.org/users/jebba/dists/unstable/main/binary-armel/kernel-flasher_2.6.28-20094102.3+0m11_armel.deb

	* Install the .debs with dpkg. Note the flasher has to be installed last. If you install them with dpkg all at once, dpkg will prioritize the flasher first, so it won't move the kernel into place. Point of no return:		* Install the .debs with dpkg. Note the flasher has to be installed last. If you install them with dpkg all at once, dpkg will prioritize the flasher first, so it won't move the kernel into place. Point of no return:
	dpkg -i \		dpkg -i \
	kernel_2.6.28-20094102.3+~~0m10_armel~~.deb \		kernel_2.6.28-20094102.3+0m11_armel.deb \
	kernel-modules_2.6.28-20094102.3+~~0m10_armel~~.deb		kernel-modules_2.6.28-20094102.3+0m11_armel.deb

	* Now install the flasher, which will automatically flash when installed:		* Now install the flasher, which will automatically flash when installed:
	dpkg -i kernel-flasher_2.6.28-20094102.3+~~0m10_armel~~.deb		dpkg -i kernel-flasher_2.6.28-20094102.3+0m11_armel.deb

	* Ok, so the kernel is there, but lets move the original stock modules back into place so you can flash the zImage via flasher-3.5 and USB cable should it be necessary. First we need to remove the mostly empty old dir, then copy the backup:		* Ok, so the kernel is there, but lets move the original stock modules back into place so you can flash the zImage via flasher-3.5 and USB cable should it be necessary. First we need to remove the mostly empty old dir, then copy the backup:

imported_>jebba: /* Compile custom kernel */ sb-conf in MaemoKernel -edFL

2010-01-03T01:48:31Z

Compile custom kernel: sb-conf in MaemoKernel -edFL

← Older revision		Revision as of 01:48, 3 January 2010
Line 77:		Line 77:
	sb-conf rs MaemoKernel \		sb-conf rs MaemoKernel \
	/home/jebba/maemo-sdk-rootstrap_5.0_armel.tgz		/home/jebba/maemo-sdk-rootstrap_5.0_armel.tgz

			sb-conf in MaemoKernel -edFL

	# disable other stuff in apt sources.list		# disable other stuff in apt sources.list

imported_>jebba: mv

2010-01-02T23:10:27Z

← Older revision		Revision as of 23:10, 2 January 2010
Line 63:		Line 63:
	* The kernel debs that are installed are: kernel, kernel-flasher ("Linux kernel updater"), kernel-modules.		* The kernel debs that are installed are: kernel, kernel-flasher ("Linux kernel updater"), kernel-modules.

	~~===My build scripts and .configs===~~
	~~I set up a little git repo of the lame scripts I use to build kernel .debs and the configs. You can clone it thusly:~~

	~~git clone http://www.freemoe.org/users/jebba/scratchbox/kernel/.git/~~

	===Compile custom kernel===		===Compile custom kernel===
Line 103:		Line 99:

	To unbrick if something goes wrong, unpack the main N900 .bin flash image and flash with the kernel from there. See [[User:Jebba#Unpacking_flash_image\|unpacking flash image]] section.		To unbrick if something goes wrong, unpack the main N900 .bin flash image and flash with the kernel from there. See [[User:Jebba#Unpacking_flash_image\|unpacking flash image]] section.

			==My build scripts and .configs==
			I set up a little git repo of the lame scripts I use to build kernel .debs and the configs. You can clone it thusly:

			git clone http://www.freemoe.org/users/jebba/scratchbox/kernel/.git/


	==Random kernel notes==		==Random kernel notes==

← Older revision		Revision as of 00:35, 12 January 2010
Line 17:		Line 17:
	I have built custom kernel packages closely based on the standard kernel that ships with the N900. Differences:		I have built custom kernel packages closely based on the standard kernel that ships with the N900. Differences:

	* NOTE: this kernel now has NAT and a bunch of filesystems and other misc. See [http://www.freemoe.org/users/jebba/dists/unstable/main/source/kernel_2.6.28-20094102.6+~~0m12~~/kernel_2.6.28-20094102.6+~~0m12_armel~~.changes the latest changes]		* NOTE: this kernel now has NAT and a bunch of filesystems and other misc. See [http://www.freemoe.org/users/jebba/dists/unstable/main/source/kernel_2.6.28-20094102.6+0m14/kernel_2.6.28-20094102.6+0m14_armel.changes the latest changes]

	* FRAMEBUFFER_CONSOLE=y - This fantastic option means you can see console when the kernel boots up, so you see all the text you usually see when booting up a Linux kernel.		* FRAMEBUFFER_CONSOLE=y - This fantastic option means you can see console when the kernel boots up, so you see all the text you usually see when booting up a Linux kernel.
Line 26:		Line 26:
	* CONFIG_LOGO=y, CONFIG_LOGO_LINUX_CLUT224=y - Tux, the Linux penguin, at boot! :)		* CONFIG_LOGO=y, CONFIG_LOGO_LINUX_CLUT224=y - Tux, the Linux penguin, at boot! :)

	* The kernel name is 2.6.28-omap1-~~jebba8~~ so as to not confuse it with the stock kernel.		* The kernel name is 2.6.28-omap1-jebba9 so as to not confuse it with the stock kernel.

	You can install this kernel via my repo with apt-get (untested), or manually, which is recommended for now. Procedure (assuming you are running the kernel that ships with the device):		You can install this kernel via my repo with apt-get (untested), or manually, which is recommended for now. Procedure (assuming you are running the kernel that ships with the device):
Line 35:		Line 35:
	* Grab my kernels with wget or whatever (check the dir for more recent versions too).		* Grab my kernels with wget or whatever (check the dir for more recent versions too).
	wget \		wget \
	http://www.freemoe.org/users/jebba/dists/unstable/main/binary-armel/kernel_2.6.28-20094102.6+~~0m12_armel~~.deb \		http://www.freemoe.org/users/jebba/dists/unstable/main/binary-armel/kernel_2.6.28-20094102.6+0m14_armel.deb \
	http://www.freemoe.org/users/jebba/dists/unstable/main/binary-armel/kernel-modules_2.6.28-20094102.6+~~0m12_armel~~.deb \		http://www.freemoe.org/users/jebba/dists/unstable/main/binary-armel/kernel-modules_2.6.28-20094102.6+0m14_armel.deb \
	http://www.freemoe.org/users/jebba/dists/unstable/main/binary-armel/kernel-flasher_2.6.28-20094102.6+~~0m12_armel~~.deb		http://www.freemoe.org/users/jebba/dists/unstable/main/binary-armel/kernel-flasher_2.6.28-20094102.6+0m14_armel.deb

	* Install the .debs with dpkg. Note the flasher has to be installed last. If you install them with dpkg all at once, dpkg will prioritize the flasher first, so it won't move the kernel into place. Point of no return:		* Install the .debs with dpkg. Note the flasher has to be installed last. If you install them with dpkg all at once, dpkg will prioritize the flasher first, so it won't move the kernel into place. Point of no return:
	dpkg -i \		dpkg -i \
	kernel_2.6.28-20094102.6+~~0m12_armel~~.deb \		kernel_2.6.28-20094102.6+0m14_armel.deb \
	kernel-modules_2.6.28-20094102.6+~~0m12_armel~~.deb		kernel-modules_2.6.28-20094102.6+0m14_armel.deb

	* Now install the flasher, which will automatically flash when installed:		* Now install the flasher, which will automatically flash when installed:
	dpkg -i kernel-flasher_2.6.28-20094102.6+~~0m12_armel~~.deb		dpkg -i kernel-flasher_2.6.28-20094102.6+0m14_armel.deb

	* Ok, so the kernel is there, but lets move the original stock modules back into place so you can flash the zImage via flasher-3.5 and USB cable should it be necessary. First we need to remove the mostly empty old dir, then copy the backup:		* Ok, so the kernel is there, but lets move the original stock modules back into place so you can flash the zImage via flasher-3.5 and USB cable should it be necessary. First we need to remove the mostly empty old dir, then copy the backup: