HowTo Build Your Own Custom Kernel - Revision history

Maddes: /* Links */ correct link to "Buffalo ARM9 Kernel Port", which is in the same wiki section

Maddes — Mon, 05 Apr 2010 18:51:30 GMT

Links: correct link to "Buffalo ARM9 Kernel Port", which is in the same wiki section

← Older revision		Revision as of 18:51, 5 April 2010
Line 171:		Line 171:

	== Links ==		== Links ==
-	[~~http://buffalo.nas-central.org/wiki/Buffalo_ARM9_Kernel_Port~~ Buffalo ARM9 Kernel Port ~~on NAS-Central~~]	+	[[Buffalo ARM9 Kernel Port]]
-		+

	[[:Category:LSPro\|LS Pro]] and [[:Category:LSLive\|LS Live]].		[[:Category:LSPro\|LS Pro]] and [[:Category:LSLive\|LS Live]].

Maddes: Cross-linking of wiki pages dealing with kernel compilation

Maddes — Fri, 26 Mar 2010 23:06:15 GMT

Cross-linking of wiki pages dealing with kernel compilation

← Older revision		Revision as of 23:06, 26 March 2010
Line 168:		Line 168:

	These instructions for native compilation of a custom kernel have been tested and verified to work with		These instructions for native compilation of a custom kernel have been tested and verified to work with
-	the '''linux-2.6.22_lsp.3.0.5.tar.bz2''' Buffalo sources on a [[:Category:LS-CL\|LS-CL]] running [[GenLink for ARM9\|GenLink]]. The resulting kernel compiles, boots, and runs quite nicely on the box. These instructions should work equally well for the [[:Category:LSPro\|LS Pro]] and [[:Category:LSLive\|LS Live]].	+	the '''linux-2.6.22_lsp.3.0.5.tar.bz2''' Buffalo sources on a [[:Category:LS-CL\|LS-CL]] running [[GenLink for ARM9\|GenLink]]. The resulting kernel compiles, boots, and runs quite nicely on the box. These instructions should work equally well for the
		+
		+	== Links ==
		+	[http://buffalo.nas-central.org/wiki/Buffalo_ARM9_Kernel_Port Buffalo ARM9 Kernel Port on NAS-Central]
		+
		+
		+	[[:Category:LSPro\|LS Pro]] and [[:Category:LSLive\|LS Live]].

	[[Category:Development]]		[[Category:Development]]

Smiley: typography

Smiley — Sat, 15 Aug 2009 06:57:52 GMT

typography

← Older revision		Revision as of 06:57, 15 August 2009
Line 151:		Line 151:
	(In fact, using those was the only way I could get the kernel to compile. Finding this combination took some trial and error, because the Buffalo Kconfig files don't contain proper dependency information for these config variables.)		(In fact, using those was the only way I could get the kernel to compile. Finding this combination took some trial and error, because the Buffalo Kconfig files don't contain proper dependency information for these config variables.)

-	The default .config also has an incorrect value for ~~'''~~CONFIG_MV_ETH_NAME~~'''~~. CONFIG_MV_ETH_NAME should be set as follows:	+	The default .config also has an incorrect value for CONFIG_MV_ETH_NAME. CONFIG_MV_ETH_NAME should be set as follows:
	CONFIG_MV_ETH_NAME="eth"		CONFIG_MV_ETH_NAME="eth"
	The default value for this variable ("egiga") makes the first ethernet device on the LS appear as '''egiga0'''. Since most alternative distributions and initrds assume that the first ethernet device is '''eth0''', your NAS probably won't be accessible from the network unless you change this to '''eth''' (note: that's '''eth''', without no '''0''').		The default value for this variable ("egiga") makes the first ethernet device on the LS appear as '''egiga0'''. Since most alternative distributions and initrds assume that the first ethernet device is '''eth0''', your NAS probably won't be accessible from the network unless you change this to '''eth''' (note: that's '''eth''', without no '''0''').

Smiley: "of"

Smiley — Sat, 15 Aug 2009 06:57:22 GMT

"of"

← Older revision		Revision as of 06:57, 15 August 2009
Line 167:		Line 167:
	The kernel should now be ready at '''arch/arm/boot/uImage''', and the modules should be under '''binaries/lib/modules'''. As always, make sure to keep backup copies of your existing kernel and modules before you replace them with new ones.		The kernel should now be ready at '''arch/arm/boot/uImage''', and the modules should be under '''binaries/lib/modules'''. As always, make sure to keep backup copies of your existing kernel and modules before you replace them with new ones.

-	These instructions for native compilation a custom kernel have been tested and verified to work with	+	These instructions for native compilation of a custom kernel have been tested and verified to work with
	the '''linux-2.6.22_lsp.3.0.5.tar.bz2''' Buffalo sources on a [[:Category:LS-CL\|LS-CL]] running [[GenLink for ARM9\|GenLink]]. The resulting kernel compiles, boots, and runs quite nicely on the box. These instructions should work equally well for the [[:Category:LSPro\|LS Pro]] and [[:Category:LSLive\|LS Live]].		the '''linux-2.6.22_lsp.3.0.5.tar.bz2''' Buffalo sources on a [[:Category:LS-CL\|LS-CL]] running [[GenLink for ARM9\|GenLink]]. The resulting kernel compiles, boots, and runs quite nicely on the box. These instructions should work equally well for the [[:Category:LSPro\|LS Pro]] and [[:Category:LSLive\|LS Live]].

Smiley: report success

Smiley — Sat, 15 Aug 2009 06:54:00 GMT

report success

← Older revision		Revision as of 06:54, 15 August 2009
Line 167:		Line 167:
	The kernel should now be ready at '''arch/arm/boot/uImage''', and the modules should be under '''binaries/lib/modules'''. As always, make sure to keep backup copies of your existing kernel and modules before you replace them with new ones.		The kernel should now be ready at '''arch/arm/boot/uImage''', and the modules should be under '''binaries/lib/modules'''. As always, make sure to keep backup copies of your existing kernel and modules before you replace them with new ones.

-	~~Enjoy!~~	+	These instructions for native compilation a custom kernel have been tested and verified to work with
		+	the '''linux-2.6.22_lsp.3.0.5.tar.bz2''' Buffalo sources on a [[:Category:LS-CL\|LS-CL]] running [[GenLink for ARM9\|GenLink]]. The resulting kernel compiles, boots, and runs quite nicely on the box. These instructions should work equally well for the [[:Category:LSPro\|LS Pro]] and [[:Category:LSLive\|LS Live]].

	[[Category:Development]]		[[Category:Development]]

Smiley: s/egiga/eth/

Smiley — Sat, 15 Aug 2009 06:42:32 GMT

s/egiga/eth/

← Older revision		Revision as of 06:42, 15 August 2009
Line 150:		Line 150:
	CONFIG_BUFFALO_SUPPORT_BOARD_INFO=y		CONFIG_BUFFALO_SUPPORT_BOARD_INFO=y
	(In fact, using those was the only way I could get the kernel to compile. Finding this combination took some trial and error, because the Buffalo Kconfig files don't contain proper dependency information for these config variables.)		(In fact, using those was the only way I could get the kernel to compile. Finding this combination took some trial and error, because the Buffalo Kconfig files don't contain proper dependency information for these config variables.)
		+
		+	The default .config also has an incorrect value for '''CONFIG_MV_ETH_NAME'''. CONFIG_MV_ETH_NAME should be set as follows:
		+	CONFIG_MV_ETH_NAME="eth"
		+	The default value for this variable ("egiga") makes the first ethernet device on the LS appear as '''egiga0'''. Since most alternative distributions and initrds assume that the first ethernet device is '''eth0''', your NAS probably won't be accessible from the network unless you change this to '''eth''' (note: that's '''eth''', without no '''0''').

	You may also want to set a "local version" for your kernel:		You may also want to set a "local version" for your kernel:

Smiley: location of compiled modules

Smiley — Fri, 14 Aug 2009 12:15:59 GMT

location of compiled modules

← Older revision		Revision as of 12:15, 14 August 2009
Line 160:		Line 160:
	And, if you configured any code to load as modules, build the modules:		And, if you configured any code to load as modules, build the modules:
	make modules		make modules
-	The kernel should now be ready at '''arch/arm/boot/uImage'''. As always, make sure to keep a backup ~~copy~~ of your existing kernel before you replace it with ~~the~~ new ~~one~~.	+	make modules_install
		+	The kernel should now be ready at '''arch/arm/boot/uImage''', and the modules should be under '''binaries/lib/modules'''. As always, make sure to keep backup copies of your existing kernel and modules before you replace them with new ones.
		+
		+	Enjoy!

	[[Category:Development]]		[[Category:Development]]

Smiley: reminder to backup old kernel

Smiley — Fri, 14 Aug 2009 05:00:37 GMT

reminder to backup old kernel

← Older revision		Revision as of 05:00, 14 August 2009
Line 160:		Line 160:
	And, if you configured any code to load as modules, build the modules:		And, if you configured any code to load as modules, build the modules:
	make modules		make modules
-	The kernel should now be ready at '''arch/arm/boot/uImage'''.	+	The kernel should now be ready at '''arch/arm/boot/uImage'''. As always, make sure to keep a backup copy of your existing kernel before you replace it with the new one.

	[[Category:Development]]		[[Category:Development]]

Smiley: retitle

Smiley — Fri, 14 Aug 2009 04:54:27 GMT

retitle

← Older revision		Revision as of 04:54, 14 August 2009
Line 3:		Line 3:
	There are two ways to build a custom kernel for the LinkStation/Kurobox. If you have access to an i686 host running some flavor of Linux, you can '''cross-compile''' a kernel for ARM9 on an i686 host. Alternatively, if your NAS has enough RAM, you could compile the kernel on the NAS itself, using the system's native '''gcc'''. Both ways of these approaches to building a custom kernel are described in the instructions that follow.		There are two ways to build a custom kernel for the LinkStation/Kurobox. If you have access to an i686 host running some flavor of Linux, you can '''cross-compile''' a kernel for ARM9 on an i686 host. Alternatively, if your NAS has enough RAM, you could compile the kernel on the NAS itself, using the system's native '''gcc'''. Both ways of these approaches to building a custom kernel are described in the instructions that follow.

-	== Cross-compiling a ~~Custom~~ Kernel ==	+	== Cross-compiling a Kernel ==

	=== Download All the Required Tarballs ===		=== Download All the Required Tarballs ===

Smiley: typography

Smiley — Fri, 14 Aug 2009 04:53:09 GMT

typography

← Older revision		Revision as of 04:53, 14 August 2009
Line 160:		Line 160:
	And, if you configured any code to load as modules, build the modules:		And, if you configured any code to load as modules, build the modules:
	make modules		make modules
-	The kernel should now be ready at arch/arm/boot/uImage.	+	The kernel should now be ready at '''arch/arm/boot/uImage'''.

	[[Category:Development]]		[[Category:Development]]