Custom Kernels - Revision history

Scoutcamper: Redirected page to Building Apps and Kernels

2011-12-24T08:00:23Z

Redirected page to Building Apps and Kernels

RodWhitby at 06:26, 28 August 2011

2011-08-28T06:26:08Z

RodWhitby at 06:25, 28 August 2011

2011-08-28T06:25:45Z

RodWhitby at 06:25, 28 August 2011

2011-08-28T06:25:33Z

Ice: /* Install the kernel on your Pre (here be dragons) */

2009-10-21T23:39:42Z

Install the kernel on your Pre (here be dragons)

Ice: just a spelling fix

2009-10-21T23:36:48Z

just a spelling fix

StefanSchmidt: Clarify the g_compisite part of the custom kernel

2009-10-15T18:32:03Z

Clarify the g_compisite part of the custom kernel

StefanSchmidt: remove notes to change the LOCALVERSION as they bring more problems then advantage

2009-10-15T18:22:45Z

remove notes to change the LOCALVERSION as they bring more problems then advantage

Hopspitfire: /* The moment of truth */ bolded reboot key sequence

2009-08-01T05:45:05Z

The moment of truth: bolded reboot key sequence

Hopspitfire: Fixed link to 'bootie'.

2009-08-01T05:44:15Z

Fixed link to 'bootie'.

← Older revision		Revision as of 08:00, 24 December 2011
Line 1:		Line 1:
		+	#REDIRECT [[Building_Apps_and_Kernels]]
		+
	= These instructions are obsolete and likely incorrect =		= These instructions are obsolete and likely incorrect =

← Older revision		Revision as of 06:26, 28 August 2011
Line 2:		Line 2:

	See [[Building_Apps_and_Kernels]] instead.		See [[Building_Apps_and_Kernels]] instead.
		+
		+	= Everything below here should be ignored =

	'''Some caveats and warnings:'''		'''Some caveats and warnings:'''

← Older revision		Revision as of 06:25, 28 August 2011
Line 1:		Line 1:
−	== These instructions are obsolete and likely incorrect ==	+	= These instructions are obsolete and likely incorrect =

	See [[Building_Apps_and_Kernels]] instead.		See [[Building_Apps_and_Kernels]] instead.

← Older revision		Revision as of 06:25, 28 August 2011
Line 1:		Line 1:
		+	== These instructions are obsolete and likely incorrect ==
		+
		+	See [[Building_Apps_and_Kernels]] instead.
		+
	'''Some caveats and warnings:'''		'''Some caveats and warnings:'''

@@ Line 155: / Line 155: @@
 . Prepare modules for new kernel
-The above mentioned modules will only load when we have the same LOCALVERSION set. Thje defconfig does that for you. Still the g_composite module did not load for me with a custom kernel due to symbol problems. Luckily the source is included in the kernel patch and already built as module. We need to make a backup of our modules directory and then replace the old g_composite.ko with our selfbuild one.
+The above mentioned modules will only load when we have the same LOCALVERSION set. The defconfig does that for you. Still the g_composite module did not load for me with a custom kernel due to symbol problems. Luckily the source is included in the kernel patch and already built as module. We need to make a backup of our modules directory and then replace the old g_composite.ko with our selfbuild one.
 <pre><nowiki>

@@ Line 21: / Line 21: @@
 </nowiki></pre>
-. To use the toolchain properly for kernel builds (and anything else you want to cross-compile for the Pre) you'll want to have some environment variables set.  The following, based on the setup-env script from the opennoko toolchain, is what I use to setup my Pre cross-compile environment.
+. To use the toolchain properly for kernel builds (and anything else you want to cross-compile for the Pre) you'll want to have some environment variables set.  The following, based on the setup-env script from the openmoko toolchain, is what I use to setup my Pre cross-compile environment.
 <pre><nowiki>

@@ Line 142: / Line 142: @@
 <pre><nowiki>
 scp -P 222 arch/arm/boot/uImage userid@1.2.3.4:/tmp/uImage-2.6.24-palm-joplin-3430-custom
-scp -P 222 System.map userid@1.2.3.4:/tmp/System.map-2.6.24-palm-joplin-3430-custom
+scp -P 222 drivers/usb/gadget/composite/g_composite.ko userid@1.2.3.4:/tmp/
 </nowiki></pre>
@@ Line 151: / Line 151: @@
 <pre><nowiki>
 sudo chown root:root /tmp/uImage-2.6.24-palm-joplin-3430-custom /tmp/System.map-2.6.24-palm-joplin-3430-custom
 </nowiki></pre>
-. Duplicate the modules directory from the original kernel
+. Prepare modules for new kernel
-Technically, we should be copying over our custom-compiled kernel modules here, but the Pre seems to have some closed source modules that we can't build ourselves, particularly the Marvell sd8xxx wi-fi driver.  So, I just copied the modules directory for the replacement kernel:
+The above mentioned modules will only load when we have the same LOCALVERSION set. Thje defconfig does that for you. Still the g_composite module did not load for me with a custom kernel due to symbol problems. Luckily the source is included in the kernel patch and already built as module. We need to make a backup of our modules directory and then replace the old g_composite.ko with our selfbuild one.
 <pre><nowiki>
 cd /lib/modules
-sudo cp -rp 2.6.24-palm-joplin-3430 2.6.24-palm-joplin-3430-custom
+sudo cp -rp 2.6.24-palm-joplin-3430 2.6.24-palm-joplin-3430-backup
 </nowiki></pre>
@@ Line 181: / Line 181: @@
 <pre><nowiki>
 -rw-r--r--    1 root     root      1098470 May 22 16:24 System.map-2.6.24-palm-joplin-3430
 drwxr-xr-x    2 root     root         4096 Dec 31  1999 bin
 -rw-r--r--    1 root     root        53756 Jun 16 21:47 boot.bin
@@ Line 194: / Line 193: @@
 drwxr-xr-x    2 root     root         4096 Dec 31  1999 sbin
 drwxr-xr-x    2 root     root         4096 Dec 31  1999 sys
-lrwxrwxrwx    1 root     root           30 Jun 24 12:16 uImage -> uImage-2.6.24-palm-joplin-3430-custom
+lrwxrwxrwx    1 root     root           30 Jun 24 12:16 uImage -> uImage-2.6.24-palm-joplin-3430
 -rw-r--r--    1 root     root      2217848 May 22 16:24 uImage-2.6.24-palm-joplin-3430
--rw-r--r--    1 root     root      2226296 Jun 24 00:17 uImage-2.6.24-palm-joplin-3430-custom
+-rw-r--r--    1 root     root      2226296 Jun 24 00:17 uImage-2.6.24-palm-joplin-3430-backup
 drwxr-xr-x    5 root     root         4096 Dec 31  1999 usr
 </nowiki></pre>

@@ Line 1: / Line 1: @@
 '''Some caveats and warnings:'''
-At this point, the kernels I've compiled seem to work fine, with one big limitation -- the power switch doesn't dim the display.  I've narrowed the problem down to a kernel module (g_composite.ko) that can't be loaded by the custom-built kernels. '''NOTE:''' The module can't be loaded because you built your kernel with a different vermagic (see the part about CONFIG_LOCALVERSION).
+At this point, the kernels I've compiled seem to work fine.
 These steps assume that root access is enabled on your Pre, and a secure ssh access mechanism is available.
-This procedure has only been verified to work on WebOS 1.0.3 through 1.0.4.  Any prior or future releases may not work.
+This procedure has only been verified to work on WebOS 1.0.3 through 1.0.4 and 1.1.3.  Any prior or future releases may not work.
 If anything goes wrong during the installation, your device may end up in a state where the kernel can't boot, in which case you can use [[bootie]] to change the boot kernel to the previous one.
@@ Line 108: / Line 107: @@
 Your Pre should have a config file in the /boot directory that is ostensibly what was used to build the original kernel.  This file is virtually identical to the file arch/arm/configs/omap_sirloin_3430_defconfig in the patched kernel tree.  Copy either file (I used the defconfig) to a file named ".config" in the top level of your source tree.
 '''NOTE:''' if you change the vermagic, you won't be able to load binary-only modules. Until you can rebuild all the modules, it's probably a good idea to leave CONFIG_LOCALVERSION="-joplin-3430"
 '''Modules'''

← Older revision		Revision as of 05:45, 1 August 2009
Line 211:		Line 211:
	1. Reset your Pre		1. Reset your Pre

−	Hold Orange-Sym-R to reboot. If all goes well, you'll see the flashing Palm logo and eventually WebOS will come up. ssh into your Pre and run uname -a to confirm that the new kernel is indeed running. If it is, congrats, you're running your own kernel. Happy hunting!	+	Hold '''Orange-Sym-R''' to reboot. If all goes well, you'll see the flashing Palm logo and eventually WebOS will come up. ssh into your Pre and run uname -a to confirm that the new kernel is indeed running. If it is, congrats, you're running your own kernel. Happy hunting!

@@ Line 7: / Line 7: @@
 This procedure has only been verified to work on WebOS 1.0.3 through 1.0.4.  Any prior or future releases may not work.
-If anything goes wrong during the installation, your device may end up in a state where the kernel can't boot, in which case you can use [bootie] to change the boot kernel to the previous one.
+If anything goes wrong during the installation, your device may end up in a state where the kernel can't boot, in which case you can use [[bootie]] to change the boot kernel to the previous one.
 '''NOTE:''' currently, unless you plan to do that just out of scientific interest, there's no real reason to build a custom kernel as everything is available in the "standard" one. In fact these instructions should build exactly (well, not //exactly// because Palm may be using a different version of the compiler) the same kernel you already have on the device.