Advanced booting - Revision history

joerg_rw: Undo revision 45769 by 70.135.114.247 (Talk) SPAM

2011-11-22T02:46:43Z

Undo revision 45769 by 70.135.114.247 (Talk) SPAM

← Older revision		Revision as of 02:46, 22 November 2011
Line 177:		Line 177:
	[[Category:Power users]]		[[Category:Power users]]
	[[Category:Diablo]]		[[Category:Diablo]]
-	~~[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html cell phone number lookup]~~

70.135.114.247: /* Devices */

2011-11-21T22:06:14Z

Devices

← Older revision		Revision as of 22:06, 21 November 2011
Line 177:		Line 177:
	[[Category:Power users]]		[[Category:Power users]]
	[[Category:Diablo]]		[[Category:Diablo]]
		+	[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html cell phone number lookup]

amigadave: wikidy slightly

2010-12-06T15:46:08Z

wikidy slightly

← Older revision		Revision as of 15:46, 6 December 2010
Line 1:		Line 1:
		+	{{out of date}}
		+
	This article covers advanced booting procedures and configuration options. For the vast majority of people [[booting from a flash card]] will cover everything they need to know.		This article covers advanced booting procedures and configuration options. For the vast majority of people [[booting from a flash card]] will cover everything they need to know.

Line 23:		Line 25:

	I used this script (which now works fine)		I used this script (which now works fine)
-	<~~pre~~>	+	<source lang="bash">
	#!/bin/bash		#!/bin/bash

Line 67:		Line 69:
	rmdir /tmp/jffs2		rmdir /tmp/jffs2
	rm -rf $IMAGE_DIR		rm -rf $IMAGE_DIR
-		+	</source>
-	</~~pre~~>	+

	== Boot messages ==		== Boot messages ==
Line 79:		Line 80:

	Log into the tablet and remount initfs so you can edit it directly. (If this '''doesn't''' make you nervous then you should stop now!)		Log into the tablet and remount initfs so you can edit it directly. (If this '''doesn't''' make you nervous then you should stop now!)
-	mount -o remount,rw /mnt/initfs	+	mount -o remount,rw /mnt/initfs

	Now grab some kernel modules from here:		Now grab some kernel modules from here:
-	http://fanoush.wz.cz/maemo/modules-diablo-2.6.21-200842maemo1.tar.gz	+	http://fanoush.wz.cz/maemo/modules-diablo-2.6.21-200842maemo1.tar.gz

	and copy the 4 modules you find in		and copy the 4 modules you find in
-	./drivers/video/console/	+	./drivers/video/console/
	to		to
-	/mnt/initfs/lib/modules/`uname -r`/	+	/mnt/initfs/lib/modules/`uname -r`/

	I extracted them on my host and did:		I extracted them on my host and did:
-	scp drivers/video/console/* root@nut:/mnt/initfs/lib/modules/2.6.21-omap1/	+	scp drivers/video/console/* root@nut:/mnt/initfs/lib/modules/2.6.21-omap1/

-	Now, for each bootmenu where you want a bootlog, edit /mnt/initfs/bootmenu.sh and add	+	Now, for each bootmenu where you want a bootlog, edit <code>/mnt/initfs/bootmenu.sh</code> and add
-	softcursor bitblit font fbcon	+	softcursor bitblit font fbcon
	to any MENU_N_MODULES= lines		to any MENU_N_MODULES= lines
	Also add a line like this (where MENU_2 will differ for you):		Also add a line like this (where MENU_2 will differ for you):
-	MENU_2_FBMODE="auto"	+	MENU_2_FBMODE="auto"

	eg:		eg:
-	MENU_4_NAME="Diablo Test"	+	MENU_4_NAME="Diablo Test"
-	MENU_4_ID="mmc5"	+	MENU_4_ID="mmc5"
-	MENU_4_DEVICE="${INT_CARD}p5"	+	MENU_4_DEVICE="${INT_CARD}p5"
-	MENU_4_MODULES="mbcache ext2 softcursor bitblit font fbcon"	+	MENU_4_MODULES="mbcache ext2 softcursor bitblit font fbcon"
-	MENU_4_FSTYPE="ext2"	+	MENU_4_FSTYPE="ext2"
-	MENU_4_FSOPTIONS="noatime"	+	MENU_4_FSOPTIONS="noatime"
-	MENU_4_FBMODE="auto"	+	MENU_4_FBMODE="auto"
-	[ -d "/sys/block/${INT_CARD}/${MENU_4_DEVICE}" ] \|\| MENU_4_NAME="(${MENU_4_NAME}) N/A"	+	[ -d "/sys/block/${INT_CARD}/${MENU_4_DEVICE}" ] \|\| MENU_4_NAME="(${MENU_4_NAME}) N/A"

	Finally, remount the initfs as ro and reboot.		Finally, remount the initfs as ro and reboot.
-	mount -oremount,ro /mnt/initfs/	+	mount -oremount,ro /mnt/initfs/

	Once your system starts, don't forget to run		Once your system starts, don't forget to run
-	/mnt/initfs/usr/bin/fb_update_mode manual	+	/mnt/initfs/usr/bin/fb_update_mode manual
	or the display will run slowly.		or the display will run slowly.

Line 124:		Line 125:

	If you are brave you can edit your initfs directly if you mount initfs read-write:		If you are brave you can edit your initfs directly if you mount initfs read-write:
-	mount -oremount,rw /mnt/initfs	+	mount -oremount,rw /mnt/initfs
-	vi $random_files	+	vi $random_files

	Don't forget to put it back:		Don't forget to put it back:
-	mount -oremount,ro /mnt/initfs	+	mount -oremount,ro /mnt/initfs

	This can be randomly dangerous if initfs partition is almost full (true for anything before Diablo) because your initfs can run out space whilst you are saving due to the way jffs2/flash systems work. Basically you may end in situation when even 'rm file' returns 'no space left on device'. Diablo update enlarged initfs partition from 2MB to 4MB so there is enough free space to make jffs2 garbage collector work properly (unless you fill it up again).		This can be randomly dangerous if initfs partition is almost full (true for anything before Diablo) because your initfs can run out space whilst you are saving due to the way jffs2/flash systems work. Basically you may end in situation when even 'rm file' returns 'no space left on device'. Diablo update enlarged initfs partition from 2MB to 4MB so there is enough free space to make jffs2 garbage collector work properly (unless you fill it up again).

	A safer approach (taken from fanoush's script) is:		A safer approach (taken from fanoush's script) is:
-	cd somewhere_on_a_linux_fs	+	cd somewhere_on_a_linux_fs
-	mkdir initfs.orig	+	mkdir initfs.orig
-	mount -t jffs2 /dev/mtdblock3 initfs.orig	+	mount -t jffs2 /dev/mtdblock3 initfs.orig
-	cp -a initfs.orig initfs	+	cp -a initfs.orig initfs
-	umount initfs.orig	+	umount initfs.orig
-	# edit intifs/...	+	# edit intifs/...

	Then, once it's all edited and ready, you create a jffs2 and burn it.		Then, once it's all edited and ready, you create a jffs2 and burn it.
-	mkfs.jffs2 -r initfs -o my_initfs.jffs2 -e 128 -l -n	+	mkfs.jffs2 -r initfs -o my_initfs.jffs2 -e 128 -l -n
-	sync	+	sync
-	chroot /mnt/initfs mount -t jffs2 -o remount,ro /dev/mtdblock3 /	+	chroot /mnt/initfs mount -t jffs2 -o remount,ro /dev/mtdblock3 /
-	echo " *** caching old initfs to memory (for crash prevention)"	+	echo " *** caching old initfs to memory (for crash prevention)"
-	# block level, probably useless	+	# block level, probably useless
-	dd if=/dev/mtdblock3 of=/dev/null bs=65536 2>/dev/null	+	dd if=/dev/mtdblock3 of=/dev/null bs=65536 2>/dev/null
-	# file level, read all interesting stuff (should be enough to cache dsme and bme)	+	# file level, read all interesting stuff (should be enough to cache dsme and bme)
-	tar cf - /mnt/initfs/usr /mnt/initfs/lib /mnt/initfs/bin /mnt/initfs/sbin >/dev/null 2>/dev/null	+	tar cf - /mnt/initfs/usr /mnt/initfs/lib /mnt/initfs/bin /mnt/initfs/sbin >/dev/null 2>/dev/null
-	flash_eraseall -j /dev/mtd3	+	flash_eraseall -j /dev/mtd3
-	echo " *** flashing $1 image ..."	+	echo " *** flashing $1 image ..."
-	nandwrite -a -p /dev/mtd3 $1	+	nandwrite -a -p /dev/mtd3 $1
-	Then reboot (/sbin/reboot) as soon as possible. dsme and bme daemons are running from (old) initfs and by reflashing underlying filesystem you just cut the branch they are sitting on. Caching done before flashing does not solve it completely.	+	Then reboot (<code>/sbin/reboot</code>) as soon as possible. dsme and bme daemons are running from (old) initfs and by reflashing underlying filesystem you just cut the branch they are sitting on. Caching done before flashing does not solve it completely.

	At this point you will probably realise that grabbing fanoush's script and inserting a few extra commands to drop you to a shell etc is a lot easier than doing it all by hand. Or you may start another shell while initfs_flash script is waiting for your answer (include telnet/dropbear/bootmenu.conf?) and modify stuff in initfs_flasher/initfs/.		At this point you will probably realise that grabbing fanoush's script and inserting a few extra commands to drop you to a shell etc is a lot easier than doing it all by hand. Or you may start another shell while initfs_flash script is waiting for your answer (include telnet/dropbear/bootmenu.conf?) and modify stuff in initfs_flasher/initfs/.
-

	===Devices===		===Devices===

	The standard initfs is missing some devices that may be useful on sd cards with lots of partitions so:		The standard initfs is missing some devices that may be useful on sd cards with lots of partitions so:
-	~~mknod -m600 initfs/dev/mmcblk0p3 b 254 3 2>/dev/null~~
-	~~mknod -m600 initfs/dev/mmcblk0p4 b 254 4 2>/dev/null~~
-	~~mknod -m600 initfs/dev/mmcblk0p5 b 254 5 2>/dev/null~~
-	~~mknod -m600 initfs/dev/mmcblk0p6 b 254 6 2>/dev/null~~
-	~~mknod -m600 initfs/dev/mmcblk0p7 b 254 7 2>/dev/null~~

-	mknod -m600 initfs/dev/~~mmcblk1p3~~ b 254 11 2>/dev/null	+	<pre>
-	mknod -m600 initfs/dev/~~mmcblk1p4~~ b 254 12 2>/dev/null	+	mknod -m600 initfs/dev/mmcblk0p3 b 254 3 2>/dev/null
-	mknod -m600 initfs/dev/~~mmcblk1p5~~ b 254 13 2>/dev/null	+	mknod -m600 initfs/dev/mmcblk0p4 b 254 4 2>/dev/null
-	mknod -m600 initfs/dev/~~mmcblk1p6~~ b 254 14 2>/dev/null	+	mknod -m600 initfs/dev/mmcblk0p5 b 254 5 2>/dev/null
-	mknod -m600 initfs/dev/~~mmcblk1p7~~ b 254 15 2>/dev/null	+	mknod -m600 initfs/dev/mmcblk0p6 b 254 6 2>/dev/null
		+	mknod -m600 initfs/dev/mmcblk0p7 b 254 7 2>/dev/null

		+	mknod -m600 initfs/dev/mmcblk1p3 b 254 11 2>/dev/null
		+	mknod -m600 initfs/dev/mmcblk1p4 b 254 12 2>/dev/null
		+	mknod -m600 initfs/dev/mmcblk1p5 b 254 13 2>/dev/null
		+	mknod -m600 initfs/dev/mmcblk1p6 b 254 14 2>/dev/null
		+	mknod -m600 initfs/dev/mmcblk1p7 b 254 15 2>/dev/null
		+	</pre>

-	~~[[Category:Users]]~~
	[[Category:Power users]]		[[Category:Power users]]
		+	[[Category:Diablo]]

fanoush: /* Initfs hacking */

2009-11-26T09:27:16Z

Initfs hacking

← Older revision		Revision as of 09:27, 26 November 2009
Line 152:		Line 152:
	echo " *** flashing $1 image ..."		echo " *** flashing $1 image ..."
	nandwrite -a -p /dev/mtd3 $1		nandwrite -a -p /dev/mtd3 $1
		+	Then reboot (/sbin/reboot) as soon as possible. dsme and bme daemons are running from (old) initfs and by reflashing underlying filesystem you just cut the branch they are sitting on. Caching done before flashing does not solve it completely.

	At this point you will probably realise that grabbing fanoush's script and inserting a few extra commands to drop you to a shell etc is a lot easier than doing it all by hand. Or you may start another shell while initfs_flash script is waiting for your answer (include telnet/dropbear/bootmenu.conf?) and modify stuff in initfs_flasher/initfs/.		At this point you will probably realise that grabbing fanoush's script and inserting a few extra commands to drop you to a shell etc is a lot easier than doing it all by hand. Or you may start another shell while initfs_flash script is waiting for your answer (include telnet/dropbear/bootmenu.conf?) and modify stuff in initfs_flasher/initfs/.

fanoush: /* Boot messages */

2009-11-26T09:13:40Z

Boot messages

← Older revision		Revision as of 09:13, 26 November 2009
Line 82:		Line 82:

	Now grab some kernel modules from here:		Now grab some kernel modules from here:
-	http://fanoush.wz.cz/maemo/modules-2.~~2007~~.~~50-2~~-~~custom~~.tar.gz	+	http://fanoush.wz.cz/maemo/modules-diablo-2.6.21-200842maemo1.tar.gz

	and copy the 4 modules you find in		and copy the 4 modules you find in

ossipena at 12:55, 1 November 2009

2009-11-01T12:55:03Z

← Older revision		Revision as of 12:55, 1 November 2009
Line 173:		Line 173:

	[[Category:Users]]		[[Category:Users]]
		+	[[Category:Power users]]

79.240.142.110: /* Boot messages */

2009-10-27T15:28:29Z

Boot messages

← Older revision		Revision as of 15:28, 27 October 2009
Line 92:		Line 92:
	scp drivers/video/console/* root@nut:/mnt/initfs/lib/modules/2.6.21-omap1/		scp drivers/video/console/* root@nut:/mnt/initfs/lib/modules/2.6.21-omap1/

-	Now, for each bootmenu where you want a bootlog, edit /mnt/initfs/bootmenu.~~conf~~ and add	+	Now, for each bootmenu where you want a bootlog, edit /mnt/initfs/bootmenu.sh and add
	softcursor bitblit font fbcon		softcursor bitblit font fbcon
-	to any ~~MODULE_N_MODULES~~= lines	+	to any MENU_N_MODULES= lines
	Also add a line like this (where MENU_2 will differ for you):		Also add a line like this (where MENU_2 will differ for you):
	MENU_2_FBMODE="auto"		MENU_2_FBMODE="auto"

jeremiah: /* Multi-boot */

2009-06-01T11:15:29Z

Multi-boot

← Older revision		Revision as of 11:15, 1 June 2009
Line 3:		Line 3:
	== Multi-boot ==		== Multi-boot ==

-	The process for setting up a multi-boot is ~~very~~ similar to [[Booting from a flash card]].	+	The process for setting up a multi-boot is similar to [[Booting from a flash card]].
-	It's a good idea to ~~makes sure~~ the first partition is a ~~fat~~/data partition - this keeps things simple.	+	It's a good idea to ensure that the first partition is a FAT/data partition - this keeps things simple.

-	A sample partition layout on an 8Gb card ~~may~~ be:	+	A sample partition layout on an 8Gb card might be:
	* 2GB primary vfat data		* 2GB primary vfat data
	* 2GB primary everyday		* 2GB primary everyday
Line 14:		Line 14:
	* 512MB logical test3 (diablo)		* 512MB logical test3 (diablo)

-	Be aware that the kernel/initfs ~~only~~ supports a limited number of partitions; this can ~~easily~~ be extended to 6 but no further. This requires editing /home/user/local/bin/initfs_flasher/initfs.bootmenu.jffs2 to add the dev nodes using mknod	+	Be aware that the kernel initfs supports a limited number of partitions; this can be extended to 6 but no further. This requires editing /home/user/local/bin/initfs_flasher/initfs.bootmenu.jffs2 to add the dev nodes using mknod
	(eg: mknod -m600 initfs/dev/mmcblk0p5 b 254 5)		(eg: mknod -m600 initfs/dev/mmcblk0p5 b 254 5)

generalantilles: Categorization

2008-10-28T04:37:13Z

Categorization

← Older revision		Revision as of 04:37, 28 October 2008
Line 1:		Line 1:
-	This article covers advanced booting procedures and configuration options.	+	This article covers advanced booting procedures and configuration options. For the vast majority of people [[booting from a flash card]] will cover everything they need to know.

	== Multi-boot ==		== Multi-boot ==
Line 170:		Line 170:
	mknod -m600 initfs/dev/mmcblk1p6 b 254 14 2>/dev/null		mknod -m600 initfs/dev/mmcblk1p6 b 254 14 2>/dev/null
	mknod -m600 initfs/dev/mmcblk1p7 b 254 15 2>/dev/null		mknod -m600 initfs/dev/mmcblk1p7 b 254 15 2>/dev/null
		+
		+
		+	[[Category:Users]]

195.47.111.102: /* Initfs hacking */ few cleanups

2008-08-14T06:54:33Z

Initfs hacking: few cleanups

← Older revision		Revision as of 06:54, 14 August 2008
Line 130:		Line 130:
	mount -oremount,ro /mnt/initfs		mount -oremount,ro /mnt/initfs

-	This can be randomly dangerous because your initfs can run out space whilst you are saving due to the way jffs2/flash systems work.	+	This can be randomly dangerous if initfs partition is almost full (true for anything before Diablo) because your initfs can run out space whilst you are saving due to the way jffs2/flash systems work. Basically you may end in situation when even 'rm file' returns 'no space left on device'. Diablo update enlarged initfs partition from 2MB to 4MB so there is enough free space to make jffs2 garbage collector work properly (unless you fill it up again).

	A safer approach (taken from fanoush's script) is:		A safer approach (taken from fanoush's script) is:
	cd somewhere_on_a_linux_fs		cd somewhere_on_a_linux_fs
-	cp -a /~~mnt~~/initfs initfs	+	mkdir initfs.orig
		+	mount -t jffs2 /dev/mtdblock3 initfs.orig
		+	cp -a initfs.orig initfs
		+	umount initfs.orig
	# edit intifs/...		# edit intifs/...

Line 150:		Line 153:
	nandwrite -a -p /dev/mtd3 $1		nandwrite -a -p /dev/mtd3 $1

-	At this point you will probably realise that grabbing fanoush's script and inserting a few extra commands to drop you to a shell etc is a lot easier than doing it all by hand.	+	At this point you will probably realise that grabbing fanoush's script and inserting a few extra commands to drop you to a shell etc is a lot easier than doing it all by hand. Or you may start another shell while initfs_flash script is waiting for your answer (include telnet/dropbear/bootmenu.conf?) and modify stuff in initfs_flasher/initfs/.