Troubleshooting/FAQ - Revision history

Tech64DD: add some FAQs about wiimotes

2026-02-22T22:03:42Z

add some FAQs about wiimotes

← Older revision		Revision as of 22:03, 22 February 2026
Line 1:		Line 1:
	This page contains some fixes for common issues with [[Wii-Linux]].		This page contains some fixes for common issues and frequently asked questions with [[Wii-Linux]].

	== [[Gumboot]] isn't loading! What's going on? ==		== [[Gumboot]] isn't loading! What's going on? ==
Line 52:		Line 52:
	== Why is my Wii Remote unpaired after going back to the Wii Menu? ==		== Why is my Wii Remote unpaired after going back to the Wii Menu? ==
	The Linux kernel interacts in some weird way with the Bluetooth module causing Wii Remotes to get unpaired when rebooted into the Wii System Menu (and only the menu, other software like the Homebrew Channel works fine). The exact cause of this problem isn't known yet.<br>You'll have to simply pair the Wii Remote(s) again with the console.		The Linux kernel interacts in some weird way with the Bluetooth module causing Wii Remotes to get unpaired when rebooted into the Wii System Menu (and only the menu, other software like the Homebrew Channel works fine). The exact cause of this problem isn't known yet.<br>You'll have to simply pair the Wii Remote(s) again with the console.

			== Can I use a Wii Remote as a mouse? ==
			Yes but no. The software to do this (xwiimote) has not seen any actual updates since 2013 and does not work on modern systems. You can use cwiid, which is packaged, to interact with a Wii Remote, but it does not give you mouse emulation.

			== Why is pairing my Wii Remote to Linux so finnicky? ==
			Linux currently has crippling issues with USB support, and the internal Broadcom 2045A Bluetooth card in the Wii is connected over USB, so it inherits these issues. There is nothing that can currently be done to work around or fix this.

	== Why do package downloads sometimes fail / "Operation too slow"? ==		== Why do package downloads sometimes fail / "Operation too slow"? ==
	The Wii's WiFi connection is ''incredibly'' slow. This leads to downloads sometimes just failing due to timeout. Newer Wii-Linux builds have <code>DisableDownloadTimeout</code> set in <code>/etc/pacman.conf</code>, so this issue should be mitigated. Existing Wii-Linux installs can set this either with ConfigMii, or by manually editing the config file.		The Wii's WiFi connection is ''incredibly'' slow. This leads to downloads sometimes just failing due to timeout. Newer Wii-Linux builds have <code>DisableDownloadTimeout</code> set in <code>/etc/pacman.conf</code>, so this issue should be mitigated. Existing Wii-Linux installs can set this either with ConfigMii, or by manually editing the config file.

Tech64DD: Tech64DD moved page Troubleshooting to Troubleshooting/FAQ

2026-02-22T22:00:26Z

Tech64DD moved page Troubleshooting to Troubleshooting/FAQ

← Older revision	Revision as of 22:00, 22 February 2026
(No difference)

Tech64DD: fix broken code block

2025-08-10T01:22:58Z

fix broken code block

← Older revision		Revision as of 01:22, 10 August 2025
Line 54:		Line 54:

	== Why do package downloads sometimes fail / "Operation too slow"? ==		== Why do package downloads sometimes fail / "Operation too slow"? ==
	The Wii's WiFi connection is ''incredibly'' slow. This leads to downloads sometimes just failing due to timeout. Newer Wii-Linux builds have <code>DisableDownloadTimeout</code> set in </etc/pacman.conf</code>, so this issue should be mitigated. Existing Wii-Linux installs can set this either with ConfigMii, or by manually editing the config file.		The Wii's WiFi connection is ''incredibly'' slow. This leads to downloads sometimes just failing due to timeout. Newer Wii-Linux builds have <code>DisableDownloadTimeout</code> set in <code>/etc/pacman.conf</code>, so this issue should be mitigated. Existing Wii-Linux installs can set this either with ConfigMii, or by manually editing the config file.

Techflash: use inline codeblocks

2025-08-10T01:21:05Z

use inline codeblocks

← Older revision		Revision as of 01:21, 10 August 2025
Line 54:		Line 54:

	== Why do package downloads sometimes fail / "Operation too slow"? ==		== Why do package downloads sometimes fail / "Operation too slow"? ==
	The Wii's WiFi connection is ''incredibly'' slow. This leads to downloads sometimes just failing due to timeout. Newer Wii-Linux builds have DisableDownloadTimeout set in /etc/pacman.conf, so this issue should be mitigated. Existing Wii-Linux installs can set this either with ConfigMii, or by manually editing the config file.		The Wii's WiFi connection is ''incredibly'' slow. This leads to downloads sometimes just failing due to timeout. Newer Wii-Linux builds have <code>DisableDownloadTimeout</code> set in </etc/pacman.conf</code>, so this issue should be mitigated. Existing Wii-Linux installs can set this either with ConfigMii, or by manually editing the config file.

Techflash: Mention pacman download errors

2025-08-10T01:20:21Z

Mention pacman download errors

← Older revision		Revision as of 01:20, 10 August 2025
Line 52:		Line 52:
	== Why is my Wii Remote unpaired after going back to the Wii Menu? ==		== Why is my Wii Remote unpaired after going back to the Wii Menu? ==
	The Linux kernel interacts in some weird way with the Bluetooth module causing Wii Remotes to get unpaired when rebooted into the Wii System Menu (and only the menu, other software like the Homebrew Channel works fine). The exact cause of this problem isn't known yet.<br>You'll have to simply pair the Wii Remote(s) again with the console.		The Linux kernel interacts in some weird way with the Bluetooth module causing Wii Remotes to get unpaired when rebooted into the Wii System Menu (and only the menu, other software like the Homebrew Channel works fine). The exact cause of this problem isn't known yet.<br>You'll have to simply pair the Wii Remote(s) again with the console.

			== Why do package downloads sometimes fail / "Operation too slow"? ==
			The Wii's WiFi connection is ''incredibly'' slow. This leads to downloads sometimes just failing due to timeout. Newer Wii-Linux builds have DisableDownloadTimeout set in /etc/pacman.conf, so this issue should be mitigated. Existing Wii-Linux installs can set this either with ConfigMii, or by manually editing the config file.

Techflash: Note that it's only the sysmenu

2025-05-30T21:09:16Z

Note that it's only the sysmenu

← Older revision		Revision as of 21:09, 30 May 2025
Line 51:		Line 51:

	== Why is my Wii Remote unpaired after going back to the Wii Menu? ==		== Why is my Wii Remote unpaired after going back to the Wii Menu? ==
	The Linux kernel interacts in some weird way with the Bluetooth module causing Wii Remotes to get unpaired when rebooted into the ~~regular~~ Wii OS, ~~and~~ the exact cause of this problem isn't known yet.<br>		The Linux kernel interacts in some weird way with the Bluetooth module causing Wii Remotes to get unpaired when rebooted into the Wii System Menu (and only the menu, other software like the Homebrew Channel works fine). The exact cause of this problem isn't known yet.<br>You'll have to simply pair the Wii Remote(s) again with the console.
	You'll have to simply pair the Wii Remote(s) again with the console.

Tech64DD: added the wii remote unpairing bug

2025-05-30T21:07:21Z

added the wii remote unpairing bug

← Older revision		Revision as of 21:07, 30 May 2025
Line 49:		Line 49:
	There's no graphics acceleration of any kind, so it'll be rendering on the emulated x86 CPU, and then drawing to the screen w/ native PPC code, but still on the CPU		There's no graphics acceleration of any kind, so it'll be rendering on the emulated x86 CPU, and then drawing to the screen w/ native PPC code, but still on the CPU
	So, yes, it may execute the game's code, technically, but you sure as hell won't be "playing" it.		So, yes, it may execute the game's code, technically, but you sure as hell won't be "playing" it.

			== Why is my Wii Remote unpaired after going back to the Wii Menu? ==
			The Linux kernel interacts in some weird way with the Bluetooth module causing Wii Remotes to get unpaired when rebooted into the regular Wii OS, and the exact cause of this problem isn't known yet.<br>
			You'll have to simply pair the Wii Remote(s) again with the console.

Tech64DD: formatting

2025-05-08T10:04:49Z

formatting

← Older revision		Revision as of 10:04, 8 May 2025
Line 38:		Line 38:

	== Why I get out-of-memory errors despite turning on a swapfile/swap partition? ==		== Why I get out-of-memory errors despite turning on a swapfile/swap partition? ==
	This is a bug in the default Wii-Linux configuration that was shipped for quite some time, but eventually fixed.		This is a bug in the default Wii-Linux configuration that was shipped for quite some time, but eventually fixed.<br>
	You can either:		You can either:<br>
	A) Update your system (the latest wii-linux-meta fixes it)		A) Update your system (the latest wii-linux-meta fixes it)<br>
	B) Delete, or fix, <code>/etc/udev/rules.d/99-zram.rules</code> to not have 100M allocated		B) Delete, or fix, <code>/etc/udev/rules.d/99-zram.rules</code> to not have 100M allocated

Tech64DD: formatting

2025-05-08T09:56:55Z

formatting

← Older revision		Revision as of 09:56, 8 May 2025
Line 44:		Line 44:

	== Can I play [insert game here] on Wii Linux? ==		== Can I play [insert game here] on Wii Linux? ==
	Short Answer: No. Stop trying. You don't want to get it to work.		Short Answer: '''No'''. Stop trying. You don't want to get it to work.<br>
	Long answer: Well.... technically, yes.		Long answer: Well.... technically, yes.
	It's very likely compiled for x86, so it'll need to be emulated. That's already unusably slow on the Wii, but let's carry on.		It's very likely compiled for x86, so it'll need to be emulated. That's already unusably slow on the Wii, but let's carry on.
	There's no graphics acceleration of any kind, so it'll be rendering on the emulated x86 CPU, and then drawing to the screen w/ native PPC code, but still on the CPU		There's no graphics acceleration of any kind, so it'll be rendering on the emulated x86 CPU, and then drawing to the screen w/ native PPC code, but still on the CPU
	So, yes, it may execute the game's code, technically, but you sure as hell won't be "playing" it.		So, yes, it may execute the game's code, technically, but you sure as hell won't be "playing" it.

Techflash: More cleanups

2025-05-07T15:49:50Z

More cleanups

← Older revision		Revision as of 15:49, 7 May 2025
Line 1:		Line 1:
	This page contains some fixes for common issues with [[Wii-Linux]].		This page contains some fixes for common issues with [[Wii-Linux]].

	== Gumboot isn't loading! What's going on? ==		== [[Gumboot]] isn't loading! What's going on? ==
	Depends on what's wrong with it.		Depends on what's wrong with it.
	* '''Black screen? Immediate reboot?''' Check if you have [[BootMii]] installed correctly.		* '''Black screen? Immediate reboot?''' Check if you have [[BootMii]] installed correctly.
Line 12:		Line 12:

	== How do I modify the kernel arguments? ==		== How do I modify the kernel arguments? ==
	Open the kernel binary (wiilinux/vX_X.krn) in a hex editor, search for the ASCII text <code>root=</code>, then user overwrite mode to modify the arguments (tip: overwrite the large chunk of padding, that's what it's there for!)		Open the kernel binary (<code>wiilinux/vX_X.krn</code>) in a hex editor, search for the ASCII text <code>root=</code>, then user overwrite mode to modify the arguments (tip: overwrite the large chunk of padding, that's what it's there for!)

	== The kernel seems to load (green bar on ~~gumboot~~), but then the screen stays on garbled colors, fully black, or black screen with the loader text! What's wrong? ==		== The kernel seems to load (green bar on Gumboot), but then the screen stays on garbled colors, fully black, or black screen with the loader text! What's wrong? ==
	This could be tons of things.		This could be tons of things.
	* If you're getting the garbled colors, it means the kernel failed to initialize very early on, before initializing the [[AVE-RVL]].		* '''If you're getting the garbled colors''', it means the kernel failed to initialize very early on, before initializing the [[AVE-RVL]].
	* If you're getting a fully black screen without even the loader text at the top, that means that it failed after initializing the AVE-RVL, gcnfb, but before displaying the loader text.		* '''If you're getting a fully black screen without even the loader text at the top''', that means that it failed after initializing the AVE-RVL, gcnfb, but before displaying the loader text.
	* If you're getting a black screen with the loader text at the top left, it means the kernel has initialized a decent bit, but something isn't working. Try setting the kernel arguments (see the previous answer, right ~~aove~~ this), replace the loglevel=x parameter with loglevel=7 to get full kernel logs on the screen, or check a USB gecko.		* '''If you're getting a black screen with the loader text at the top left''', it means the kernel has initialized a decent bit, but something isn't working. Try setting the kernel arguments (see the previous answer, right above this), replace the loglevel=x parameter with loglevel=7 to get full kernel logs on the screen, or check a USB gecko.
	For all of these, having a [[USB Gecko]] would be very beneficial.		For all of these, having a [[USB Gecko]] would be very beneficial.

Line 29:		Line 29:

	== Why isn't [some package name here] in the ArchPOWER repos? ==		== Why isn't [some package name here] in the ArchPOWER repos? ==
	I don't maintain the ArchPOWER repos, but I do maintain a small group of extra packages for ArchPOWER in a seperate repo.		I don't maintain the [[ArchPOWER]] repos, but I do maintain a small group of extra packages for ArchPOWER in a seperate repo.
	Ask me, I'll check for you, and build it if possible.		Ask me, I'll check for you, and build it if possible.

	== Why is logging in so slow? ==		== Why is logging in so slow? ==
	Arch (and by extension, ArchPOWER) uses a fairly inefficient (though more secure) hashing algorithm for the password by default, that is quite slow on the Wii's mediocre CPU. If you'd like a better balance between security and speed, you can use SHA256 instead.		Arch (and by extension, ArchPOWER) uses a fairly inefficient (though more secure) hashing algorithm for the password by default, that is quite slow on the Wii's mediocre CPU. If you'd like a better balance between security and speed, you can use SHA256 instead.
	Simply edit /etc/login.defs, then replace YESCRYPT with SHA256, then regenerate the password of each user.		Simply edit <code>/etc/login.defs</code>, then replace <code>YESCRYPT</code> with <code>SHA256</code>, then regenerate the password of each user.
	'''New rootfs's have this by default.'''		'''New rootfs's have this by default.'''

Line 41:		Line 41:
	You can either:		You can either:
	A) Update your system (the latest wii-linux-meta fixes it)		A) Update your system (the latest wii-linux-meta fixes it)
	B) Delete, or fix, /etc/udev/rules.d/99-zram.rules to not have 100M allocated		B) Delete, or fix, <code>/etc/udev/rules.d/99-zram.rules</code> to not have 100M allocated

	== Can I play [insert game here] on Wii Linux? ==		== Can I play [insert game here] on Wii Linux? ==