Research Pre Boot Process - Revision history

Sbromwich at 16:00, 26 April 2010

2010-04-26T16:00:25Z

Sbromwich: More details on how to recognise if booting works

2010-04-07T14:25:55Z

More details on how to recognise if booting works

Sbromwich: Describe how to recognise if your new kernel is full of fail

2010-04-07T14:23:07Z

Describe how to recognise if your new kernel is full of fail

Sbromwich: Corrected novacom boot method based on actual tested method

2010-04-07T01:12:59Z

Corrected novacom boot method based on actual tested method

Sbromwich: Clarification that the novaterm boot mem method is a one-shot deal

2010-04-07T00:00:39Z

Clarification that the novaterm boot mem method is a one-shot deal

Morphis at 18:47, 11 December 2009

2009-12-11T18:47:51Z

Morphis at 18:40, 11 December 2009

2009-12-11T18:40:58Z

Morphis: different cmdline with nova-installer image

2009-12-11T18:37:58Z

different cmdline with nova-installer image

Morphis: note about cmdline when booting a kernel with novacom

2009-12-09T20:20:15Z

note about cmdline when booting a kernel with novacom

Morphis: style correctness

2009-12-09T20:07:32Z

style correctness

← Older revision		Revision as of 16:00, 26 April 2010
Line 20:		Line 20:
	</source>		</source>

−	novacom loads the kernel into ram and then boots it. The kernel is loaded with the same cmdline as mentioned above. Note that this does not write the kernel to the Pre's storage, and the next time the device is rebooted the original kernel is loaded. If the Palm logo displays but does not start glowing, your kernel has probably locked up during boot. You can also run tail -f /var/log/messages to see if the devices is re-recognised during bootup; as soon as novacom goes online you should be able to novaterm in.	+	novacom loads the kernel into ram and then boots it. The kernel is loaded with the same cmdline as mentioned above. Note that this does not write the kernel to the Pre's storage, and the next time the device is rebooted the original kernel is loaded. If the Palm logo displays but does not start glowing, your kernel has probably locked up during boot. You can also run tail -f /var/log/messages to see if the devices is re-recognised during bootup; as soon as novacom goes online you should be able to novaterm in. Note that if the device is in airline mode (phone disabled) the kernel may fail to boot.

← Older revision		Revision as of 14:25, 7 April 2010
Line 20:		Line 20:
	</source>		</source>

−	novacom loads the kernel into ram and then boots it. The kernel is loaded with the same cmdline as mentioned above. Note that this does not write the kernel to the Pre's storage, and the next time the device is rebooted the original kernel is loaded. If the Palm logo displays but does not start glowing, your kernel has probably locked up during boot.	+	novacom loads the kernel into ram and then boots it. The kernel is loaded with the same cmdline as mentioned above. Note that this does not write the kernel to the Pre's storage, and the next time the device is rebooted the original kernel is loaded. If the Palm logo displays but does not start glowing, your kernel has probably locked up during boot. You can also run tail -f /var/log/messages to see if the devices is re-recognised during bootup; as soon as novacom goes online you should be able to novaterm in.

@@ Line 14: / Line 14: @@
 The nova-installer-image-castle.uImage image uses a initrd an not an initramfs. Somehow bootie detects if the kernel which is loaded has an initrd build in. If yes, then bootie changes the cmdline for the kernel to the env var bootargs-ramdisk.
-You can even boot a kernel from your local host with novacom. First, log in with novaterm and run tellbootie recover. Wait for the USB logot to appear, then boot the kernel as follows:
+You can even boot a kernel from your local host with novacom. First, log in with novaterm and run tellbootie recover. Wait for the USB logo to appear, then boot the kernel as follows:
 <source lang=bash>
@@ Line 20: / Line 20: @@
 </source>
-novacom loads the kernel into ram and then boots it. The kernel is loaded with the same cmdline as mentioned above. Note that this does not write the kernel to the Pre's storage, and the next time the device is rebooted the original kernel is loaded.
+novacom loads the kernel into ram and then boots it. The kernel is loaded with the same cmdline as mentioned above. Note that this does not write the kernel to the Pre's storage, and the next time the device is rebooted the original kernel is loaded. If the Palm logo displays but does not start glowing, your kernel has probably locked up during boot.

@@ Line 14: / Line 14: @@
 The nova-installer-image-castle.uImage image uses a initrd an not an initramfs. Somehow bootie detects if the kernel which is loaded has an initrd build in. If yes, then bootie changes the cmdline for the kernel to the env var bootargs-ramdisk.
-You can even boot a kernel from your local host with novacom:
+You can even boot a kernel from your local host with novacom. First, log in with novaterm and run tellbootie recover. Wait for the USB logot to appear, then boot the kernel as follows:
 <source lang=bash>
-cat uImage-kexecboot-2.6.24-r50-palmpre.bin | novaterm boot mem://
+novacom boot mem:// < uImage-kexecboot-2.6.24-r50-palmpre.bin
 </source>

← Older revision		Revision as of 00:00, 7 April 2010
Line 20:		Line 20:
	</source>		</source>

−	novacom loads the kernel into ram and then boots it. The kernel is loaded with the same cmdline as mentioned above.	+	novacom loads the kernel into ram and then boots it. The kernel is loaded with the same cmdline as mentioned above. Note that this does not write the kernel to the Pre's storage, and the next time the device is rebooted the original kernel is loaded.

← Older revision		Revision as of 20:20, 9 December 2009
Line 12:		Line 12:
	</source>		</source>

−	novacom loads the kernel into ram and then boots it.	+	novacom loads the kernel into ram and then boots it. The kernel is loaded with the same cmdline as mentioned above.

@@ Line 2: / Line 2: @@
 When the pre is starting it loads the boot.bin image into ram. This is the booloader bootie which loads the linux kernel. The Linux kernel is loaded with the following cmdline (which is build out of the env vars from bootie):
-<pre>
+<source lang=bash>
 root=/dev/mmcblk0p2 rootwait ro fb=0x8f600000 fbcon=disable console=tty1 nduid=ea413b0b980b26d75c6658199d532472049644ae klog=0x8ff00000 klog_len=0x100000  boardtype=castle-dvt3 dsp_base=0x8f900000 dsp_len=0x600000
-</pre>
+</source>
 You can even boot a kernel from your local host with novacom:
 <source lang=bash>
-# cat uImage-kexecboot-2.6.24-r50-palmpre.bin | novaterm boot mem://
+cat uImage-kexecboot-2.6.24-r50-palmpre.bin | novaterm boot mem://
 </source>
@@ Line 23: / Line 23: @@
 When upstart is starting it executes a script called usbctrl whichs load the right usb driver and configuration for novacom or usbnetworking. Depending which machine is used the g_composite driver is loaded with a different product id.
-<pre>
+<source lang=bash>
 if [[ "$machineType" == "armv7l" ]];then
                  if [[ -e /var/gadget/usbnet_enabled && -e /var/gadget/novacom_enabled ]]; then
@@ Line 47: / Line 47: @@
                  /sbin/modprobe -q g_composite || true
      fi
-</pre>
+</source>
 Is the g_composite driver is build in the kernel the script changes the configuration of the gadget driver through a sysfs entry.
-<pre>
+<source lang=bash>
 if [[ -e /var/gadget/usbnet_enabled && -e /var/gadget/novacom_enabled ]]; then
    echo 5 > /sys/class/usb_gadget/config_num
@@ Line 60: / Line 60: @@
    echo 1 > /sys/class/usb_gadget/config_num
 fi
-</pre>
+</source>