Building Kernel Guide - Revision history

SuperbeeLavaman: fix typo

2025-11-13T19:02:00Z

fix typo

← Older revision		Revision as of 19:02, 13 November 2025
Line 30:		Line 30:
	#** Example 1 (copy to local machine's SD Card on /mnt): <code>./copy-ssh.sh root@localhost /mnt v4_19325 kernel</code>		#** Example 1 (copy to local machine's SD Card on /mnt): <code>./copy-ssh.sh root@localhost /mnt v4_19325 kernel</code>
	#** Example 2 (copy to Wii with SD Card on /boot): <code>./copy-ssh.sh root@wii.local /boot v4_19325 kernel</code>		#** Example 2 (copy to Wii with SD Card on /boot): <code>./copy-ssh.sh root@wii.local /boot v4_19325 kernel</code>
	#* '''Installing the kernel modules'''. The kernel modules are output as <code>modules.tar.gz</code> in your kernel directory. You will need to safely extract these to your Wii-Linux distro's rootfs. ''WARNING'': Extracting directly to the rootfs '''''WILL HOSE YOUR PERMISSIONS - DO NOT DO THAT'''''. It will set the UID/~~HID~~ of the root directory, and /usr, and /usr/lib, to the UID/GID of the user who built the kernel. Instead, you can extract it to a temporary directory, then <code>mv</code> or <code>cp -r</code> the modules (<code>temp_dir/usr/lib/modules/[kernel version]-wii+</code>) into your rootfs.		#* '''Installing the kernel modules'''. The kernel modules are output as <code>modules.tar.gz</code> in your kernel directory. You will need to safely extract these to your Wii-Linux distro's rootfs. ''WARNING'': Extracting directly to the rootfs '''''WILL HOSE YOUR PERMISSIONS - DO NOT DO THAT'''''. It will set the UID/GID of the root directory, and /usr, and /usr/lib, to the UID/GID of the user who built the kernel. Instead, you can extract it to a temporary directory, then <code>mv</code> or <code>cp -r</code> the modules (<code>temp_dir/usr/lib/modules/[kernel version]-wii+</code>) into your rootfs.

SuperbeeLavaman: add "git clone" to beginning of command to run

2025-11-13T18:41:07Z

add "git clone" to beginning of command to run

← Older revision		Revision as of 18:41, 13 November 2025
Line 18:		Line 18:
	# After you have added it to your path, go back to the main directory and run <code>git clone https://github.com/Wii-Linux/build-stack && cd build-stack</code>.		# After you have added it to your path, go back to the main directory and run <code>git clone https://github.com/Wii-Linux/build-stack && cd build-stack</code>.
	# Once you're in the build-stack folder, run <code>./setup.sh</code> and follow it's instructions, to make sure that you have all the necessary requirements installed. If it asks to clone and build various requirements, answer Yes unless you have a very specific reason not to.		# Once you're in the build-stack folder, run <code>./setup.sh</code> and follow it's instructions, to make sure that you have all the necessary requirements installed. If it asks to clone and build various requirements, answer Yes unless you have a very specific reason not to.
	# After setup.sh finishes successfully, go back to the main directory, and now finally run <code>https://github.com/Wii-Linux/wii-linux-ngx -b <Branch You want></code>.		# After setup.sh finishes successfully, go back to the main directory, and now finally run <code>git clone https://github.com/Wii-Linux/wii-linux-ngx -b <Branch You want></code>.
	#* The branch you clone is the source code to the kernel branch you are going to compile (this could be specialized kernels (like for [[OpenWRT]], or just various versions of the main one). The following kernel branches are the ones currently supported:		#* The branch you clone is the source code to the kernel branch you are going to compile (this could be specialized kernels (like for [[OpenWRT]], or just various versions of the main one). The following kernel branches are the ones currently supported:
	#** <code>wii-v4.5</code>		#** <code>wii-v4.5</code>

Techflash: Clean up a bit of formatting and update to new method

2025-07-01T22:14:27Z

Clean up a bit of formatting and update to new method

← Older revision		Revision as of 22:14, 1 July 2025
Line 26:		Line 26:
	#* Example: <code>./build-kernel.sh wii-linux-ngx</code>.		#* Example: <code>./build-kernel.sh wii-linux-ngx</code>.
	#* The <code>--standalone</code> argument can be used to build a kernel that doesn't require a loader, <code>arch/powerpc/boot/dts/wii.dts</code> needs to be edited accordingly with the boot device that will be used.		#* The <code>--standalone</code> argument can be used to build a kernel that doesn't require a loader, <code>arch/powerpc/boot/dts/wii.dts</code> needs to be edited accordingly with the boot device that will be used.
	# After the kernel compiles, you have to build the loader (small squashfs that the kernel boots, provides the boot menu). In the build-stack run <code>./build-loader.sh ../v<kernel version short>.ldr</code>.
	~~#* Example: <code>./build-loader.sh ../v4_19325.ldr</code>.~~
	# After the loader is done, you need to go install it. This consists of 2 parts:		# After the loader is done, you need to go install it. This consists of 2 parts:
	#* '''Installing the kernel+loader'''. A script has been provided to make this easier, <code>build-stack/copy-ssh.sh</code>. This provides an easy way to copy the kernel+loader to a remote machine in any directory. This could even be a Wii-Linux install.		#* '''Installing the kernel+loader'''. A script has been provided to make this easier, <code>build-stack/copy-ssh.sh</code>. This provides an easy way to copy the kernel+loader to a remote machine in any directory. This could even be a Wii-Linux install.
	#** Example 1 (copy to local machine's SD Card on /mnt): <code>./copy-ssh.sh root@localhost /mnt v4_19325 ~~4.19.325-wii+~~ kernel ~~v4_19325.ldr~~</code>		#** Example 1 (copy to local machine's SD Card on /mnt): <code>./copy-ssh.sh root@localhost /mnt v4_19325 kernel</code>
	#** Example 2 (copy to Wii with SD Card on /boot): <code>./copy-ssh.sh root@wii.local /boot v4_19325 ~~4.19.325-wii+~~ kernel ~~v4_19325.ldr~~</code>		#** Example 2 (copy to Wii with SD Card on /boot): <code>./copy-ssh.sh root@wii.local /boot v4_19325 kernel</code>
	#* ''''Installing the kernel modules''. The kernel modules are output as <code>modules.tar.gz</code> in your kernel directory. You will need to safely extract these to your Wii-Linux distro's rootfs. ''WARNING'': Extracting directly to the rootfs '''''WILL HOSE YOUR PERMISSIONS - DO NOT DO THAT'''''. It will set the UID/HID of the root directory, and /usr, and /usr/lib, to the UID/GID of the user who built the kernel. Instead, you can extract it to a temporary directory, then <code>mv</code> or <code>cp -r</code> the modules (<code>temp_dir/usr/lib/modules/[kernel version]-wii+</code> into your rootfs.		#* '''Installing the kernel modules'''. The kernel modules are output as <code>modules.tar.gz</code> in your kernel directory. You will need to safely extract these to your Wii-Linux distro's rootfs. ''WARNING'': Extracting directly to the rootfs '''''WILL HOSE YOUR PERMISSIONS - DO NOT DO THAT'''''. It will set the UID/HID of the root directory, and /usr, and /usr/lib, to the UID/GID of the user who built the kernel. Instead, you can extract it to a temporary directory, then <code>mv</code> or <code>cp -r</code> the modules (<code>temp_dir/usr/lib/modules/[kernel version]-wii+</code>) into your rootfs.

Tech64DD: standalone argument

2025-05-19T21:32:40Z

standalone argument

← Older revision		Revision as of 21:32, 19 May 2025
Line 25:		Line 25:
	# After you cloned the kernel that you want to build go back into <code>build-stack</code> and run <code>./build-kernel.sh [name of your kernel directory]</code>.		# After you cloned the kernel that you want to build go back into <code>build-stack</code> and run <code>./build-kernel.sh [name of your kernel directory]</code>.
	#* Example: <code>./build-kernel.sh wii-linux-ngx</code>.		#* Example: <code>./build-kernel.sh wii-linux-ngx</code>.
			#* The <code>--standalone</code> argument can be used to build a kernel that doesn't require a loader, <code>arch/powerpc/boot/dts/wii.dts</code> needs to be edited accordingly with the boot device that will be used.
	# After the kernel compiles, you have to build the loader (small squashfs that the kernel boots, provides the boot menu). In the build-stack run <code>./build-loader.sh ../v<kernel version short>.ldr</code>.		# After the kernel compiles, you have to build the loader (small squashfs that the kernel boots, provides the boot menu). In the build-stack run <code>./build-loader.sh ../v<kernel version short>.ldr</code>.
	#* Example: <code>./build-loader.sh ../v4_19325.ldr</code>.		#* Example: <code>./build-loader.sh ../v4_19325.ldr</code>.

Techflash: fix warning formatting

2025-05-18T19:34:13Z

fix warning formatting

← Older revision		Revision as of 19:34, 18 May 2025
Line 31:		Line 31:
	#** Example 1 (copy to local machine's SD Card on /mnt): <code>./copy-ssh.sh root@localhost /mnt v4_19325 4.19.325-wii+ kernel v4_19325.ldr</code>		#** Example 1 (copy to local machine's SD Card on /mnt): <code>./copy-ssh.sh root@localhost /mnt v4_19325 4.19.325-wii+ kernel v4_19325.ldr</code>
	#** Example 2 (copy to Wii with SD Card on /boot): <code>./copy-ssh.sh root@wii.local /boot v4_19325 4.19.325-wii+ kernel v4_19325.ldr</code>		#** Example 2 (copy to Wii with SD Card on /boot): <code>./copy-ssh.sh root@wii.local /boot v4_19325 4.19.325-wii+ kernel v4_19325.ldr</code>
	#* ''''Installing the kernel modules''. The kernel modules are output as <code>modules.tar.gz</code> in your kernel directory. You will need to safely extract these to your Wii-Linux distro's rootfs. ''WARNING'': Extracting directly to the rootfs ''WILL HOSE YOUR PERMISSIONS - DO NOT DO THAT''. It will set the UID/HID of the root directory, and /usr, and /usr/lib, to the UID/GID of the user who built the kernel. Instead, you can extract it to a temporary directory, then <code>mv</code> or <code>cp -r</code> the modules (<code>temp_dir/usr/lib/modules/[kernel version]-wii+</code> into your rootfs.		#* ''''Installing the kernel modules''. The kernel modules are output as <code>modules.tar.gz</code> in your kernel directory. You will need to safely extract these to your Wii-Linux distro's rootfs. ''WARNING'': Extracting directly to the rootfs '''''WILL HOSE YOUR PERMISSIONS - DO NOT DO THAT'''''. It will set the UID/HID of the root directory, and /usr, and /usr/lib, to the UID/GID of the user who built the kernel. Instead, you can extract it to a temporary directory, then <code>mv</code> or <code>cp -r</code> the modules (<code>temp_dir/usr/lib/modules/[kernel version]-wii+</code> into your rootfs.

Techflash: Try to clean up this absolute mess

2025-05-18T19:33:39Z

Try to clean up this absolute mess

← Older revision		Revision as of 19:33, 18 May 2025
Line 1:		Line 1:
	This Guide will teach you how to compile the Wii-Linux kernel ~~for Wii-Linux~~.		This Guide will teach you how to cross-compile the [[Wii-Linux]] kernel and supporting elements.

	== Requirements ==		== Requirements ==

	* ~~A PC~~		* An x86 or AArch64 device running GNU/Linux


Line 9:		Line 9:
	# Install Crosstool-NG via package manager or compile it by cloning <code>git clone https://github.com/crosstool-ng/crosstool-ng</code>.		# Install Crosstool-NG via package manager or compile it by cloning <code>git clone https://github.com/crosstool-ng/crosstool-ng</code>.
	# Make a directory to have all the files/folders to be in		# Make a directory to have all the files/folders to be in
	# In that directory clone the Wii-Linux-Toolchain <code>https://github.com/Wii-Linux/wii-linux-toolchain~~.git~~</code>.		# In that directory clone the Wii-Linux-Toolchain <code>https://github.com/Wii-Linux/wii-linux-toolchain</code>.
	# cd into the wii-linux-toolchain folder and run <code>mv ct-ng.config .config</code> and run <code>ct-ng build</code>.		# cd into the wii-linux-toolchain folder and run <code>mv ct-ng.config .config</code> and run <code>ct-ng build</code>.
	#* The process will take a while depending on how ~~shit~~ your computer is.		#* The process will take a while depending on how bad your computer is.
	# Once it's installed it should make a directory in your home folder called x-tools ~~run~~ <code>echo 'PATH="$PATH:~/x-~~tools~~/powerpc-unknown-linux-gnu/bin"' >> ~/.bashrc && source ~/.bashrc</code>.		# Once it's installed, it should make a directory in your home folder called <code>x-tools</code>.
	# After you ~~ran the previous command~~ go back to the main directory ~~folder~~ and run <code>git clone https://github.com/Wii-Linux/build-stack</code> ~~and cd into it~~.		#* You can optionally move this directory elsewhere first, if you don't find <code>x-tools</code> appealing.
	# Once ~~your~~ in the build-stack folder run setup.sh and follow ~~its~~ instructions ~~and~~ make sure you have all the ~~things u have~~ installed~~, and if~~ it asks to clone and build ~~stuff always~~ answer ~~with Y~~.		# You must now add it to your PATH. This varies per shell, and based on where you put it, but as an example:
	# After setup.sh finishes successfully go back to the main directory and now finally run <code>https://github.com/Wii-Linux/wii-linux-ngx~~.git -~~-~~branch~~ <Branch You want></code>.		#* for bash: <code>echo 'PATH="$PATH:~/<path to ct-ng output>/powerpc-unknown-linux-gnu/bin"' >> ~/.bashrc && source ~/.bashrc</code>.
	#* The branch you clone is the kernel you are going to compile, the following kernel's are the ones currently supported.		# After you have added it to your path, go back to the main directory and run <code>git clone https://github.com/Wii-Linux/build-stack && cd build-stack</code>.
	#** wii-v4.5		# Once you're in the build-stack folder, run <code>./setup.sh</code> and follow it's instructions, to make sure that you have all the necessary requirements installed. If it asks to clone and build various requirements, answer Yes unless you have a very specific reason not to.
	#** wii-v4.6		# After setup.sh finishes successfully, go back to the main directory, and now finally run <code>https://github.com/Wii-Linux/wii-linux-ngx -b <Branch You want></code>.
	~~#** wii~~-~~v4.9~~		#* The branch you clone is the source code to the kernel branch you are going to compile (this could be specialized kernels (like for [[OpenWRT]], or just various versions of the main one). The following kernel branches are the ones currently supported:
	~~#** wii-v4.14~~		#** <code>wii-v4.5</code>
	#** wii-v4.19		#** <code>wii-v4.14-openwrt</code>
	# After you cloned the kernel you want to build go back into build-stack and run <code>./build-kernel.sh [name of your kernel directory ~~will most likely be wii-linux-ngx if you kept it default~~] ~~<kernelversion>-wii+~~</code>.		#** <code>wii-v4.19</code>
	#* Example: <code>./build-kernel.sh wii-linux-ngx ~~4.19.325-wii+~~</code>.		# After you cloned the kernel that you want to build go back into <code>build-stack</code> and run <code>./build-kernel.sh [name of your kernel directory]</code>.
	# After the ~~Kernel~~ compiles you have to build the loader ~~in order to run your~~ kernel ~~so in~~ the build-stack run <code>./build-loader.sh ../v<~~Kernel Version~~>.ldr</code>.		#* Example: <code>./build-kernel.sh wii-linux-ngx</code>.
	#* Example: <code>./build-loader.sh ../~~v4_19_325~~.ldr</code>.		# After the kernel compiles, you have to build the loader (small squashfs that the kernel boots, provides the boot menu). In the build-stack run <code>./build-loader.sh ../v<kernel version short>.ldr</code>.
	# After the loader is done go to ~~your main directory and run~~ <code>~~cp <kernedir>~~/~~arch/powerpc/boot/zImage~~ . ~~&& mv zImage v~~<~~Kernel Version~~>.~~krn<~~/~~code> and~~ <code>~~cp <kerneldir>~~/~~modules~~.~~tar~~.gz .</code>.		#* Example: <code>./build-loader.sh ../v4_19325.ldr</code>.
	#* Example: <code>~~cp <kernedir>~~/~~arch/powerpc~~/boot~~/zImage~~ . ~~&& mv zImage~~ v4_19325.~~krn~~</code> ~~and~~ <code>~~cp wii-linux-ngx/~~modules.tar.gz .</code>		# After the loader is done, you need to go install it. This consists of 2 parts:
	~~# Finally after all of that~~ in your ~~main~~ directory ~~you should have 1 ldr file~~, ~~1 krn file~~, and ~~modules.tar.gz file~~, ~~put~~ the ~~ldr and krn file in~~ the ~~wiilinux folder in your sd card (preassumed that u had~~ the ~~sd card files~~/~~folders zip already in there extracted) and extract~~ the modules~~.tar.gz onto your rootfs under~~ <code>lib/modules</code>.		#* '''Installing the kernel+loader'''. A script has been provided to make this easier, <code>build-stack/copy-ssh.sh</code>. This provides an easy way to copy the kernel+loader to a remote machine in any directory. This could even be a Wii-Linux install.
			#** Example 1 (copy to local machine's SD Card on /mnt): <code>./copy-ssh.sh root@localhost /mnt v4_19325 4.19.325-wii+ kernel v4_19325.ldr</code>
			#** Example 2 (copy to Wii with SD Card on /boot): <code>./copy-ssh.sh root@wii.local /boot v4_19325 4.19.325-wii+ kernel v4_19325.ldr</code>
			#* ''''Installing the kernel modules''. The kernel modules are output as <code>modules.tar.gz</code> in your kernel directory. You will need to safely extract these to your Wii-Linux distro's rootfs. ''WARNING'': Extracting directly to the rootfs ''WILL HOSE YOUR PERMISSIONS - DO NOT DO THAT''. It will set the UID/HID of the root directory, and /usr, and /usr/lib, to the UID/GID of the user who built the kernel. Instead, you can extract it to a temporary directory, then <code>mv</code> or <code>cp -r</code> the modules (<code>temp_dir/usr/lib/modules/[kernel version]-wii+</code> into your rootfs.

Selimgozel1: A semi-simple guide to help compile wii-linux kernel's

2025-05-18T18:16:10Z

A semi-simple guide to help compile wii-linux kernel's

New page

This Guide will teach you how to compile the Wii-Linux kernel for Wii-Linux.

== Requirements ==

* A PC

== Setup and Compile==
# Install Crosstool-NG via package manager or compile it by cloning <code>git clone https://github.com/crosstool-ng/crosstool-ng</code>.
# Make a directory to have all the files/folders to be in
# In that directory clone the Wii-Linux-Toolchain <code>https://github.com/Wii-Linux/wii-linux-toolchain.git</code>.
# cd into the wii-linux-toolchain folder and run <code>mv ct-ng.config .config</code> and run <code>ct-ng build</code>.
#* The process will take a while depending on how shit your computer is.
# Once it's installed it should make a directory in your home folder called x-tools run <code>echo 'PATH="$PATH:~/x-tools/powerpc-unknown-linux-gnu/bin"' >> ~/.bashrc && source ~/.bashrc</code>.
# After you ran the previous command go back to the main directory folder and run <code>git clone https://github.com/Wii-Linux/build-stack</code> and cd into it.
# Once your in the build-stack folder run setup.sh and follow its instructions and make sure you have all the things u have installed, and if it asks to clone and build stuff always answer with Y.
# After setup.sh finishes successfully go back to the main directory and now finally run <code>https://github.com/Wii-Linux/wii-linux-ngx.git --branch <Branch You want></code>.
#* The branch you clone is the kernel you are going to compile, the following kernel's are the ones currently supported.
#** wii-v4.5
#** wii-v4.6
#** wii-v4.9
#** wii-v4.14
#** wii-v4.19
# After you cloned the kernel you want to build go back into build-stack and run <code>./build-kernel.sh [name of your kernel directory will most likely be wii-linux-ngx if you kept it default] <kernelversion>-wii+</code>.
#* Example: <code>./build-kernel.sh wii-linux-ngx 4.19.325-wii+</code>.
# After the Kernel compiles you have to build the loader in order to run your kernel so in the build-stack run <code>./build-loader.sh ../v<Kernel Version>.ldr</code>.
#* Example: <code>./build-loader.sh ../v4_19_325.ldr</code>.
# After the loader is done go to your main directory and run <code>cp <kernedir>/arch/powerpc/boot/zImage . && mv zImage v<Kernel Version>.krn</code> and <code>cp <kerneldir>/modules.tar.gz .</code>.
#* Example: <code>cp <kernedir>/arch/powerpc/boot/zImage . && mv zImage v4_19325.krn</code> and <code>cp wii-linux-ngx/modules.tar.gz .</code>
# Finally after all of that in your main directory you should have 1 ldr file, 1 krn file, and modules.tar.gz file, put the ldr and krn file in the wiilinux folder in your sd card (preassumed that u had the sd card files/folders zip already in there extracted) and extract the modules.tar.gz onto your rootfs under <code>lib/modules</code>.