Advanced booting - Revision history

imported_>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]

imported_>amigadave: wikidy slightly

2010-12-06T15:46:08Z

wikidy slightly

Show changes

imported_>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/.

imported_>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

imported_>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"

imported_>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)

imported_>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/.