This FAQ attempts to cover assorted questions not covered in the other chapters.
- Virtual Machines
- Broken colors in ASpeed VGA on big endian
- Rendering issues with Qt-based desktops (KDE, LXQt, ...) on big endian
- Rendering issues with WebKit on big endian
- System hangs shortly after boot/Xorg on older kernels (at least 4.4) and Radeon AGP
- System hangs in complex OpenGL applications on late PowerBooks (Radeon 9600/9700)
- Console is 800x600 rectangle on Mac Mini G4
- Xfce/Xfwm4 crashes on big endian
No, it is not planned. However, the compiler is built as bi-arch, which
-m32 works, and you can have it emit 32-bit code. This is useful for
low level stuff (e.g. GRUB, which needs to emit 32-bit big endian code
independent on a libc) while not burdening the higher level infrastructure.
If you really need to build or use 32-bit software, use a 32-bit chroot, it
should work just fine.
yaboot project is deprecated. Void uses
GRUB, which covers pretty much
all of the use cases plus more (that is, on systems that don't use
but there it uses at least the GRUB configuration file).
If you get an issue like this (and GRUB has loaded fine):
mount: /run/initramfs/live: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error. dracut: FATAL: Failed to mount block device of live image dracut: Refusing to continue
you might be dealing with a backup partition table of some system that was
previously on that USB stick overriding the new one. In that case, first do
the following before
dding your ISO image onto the USB stick:
# wipefs -a /dev/sdN
sdN is your USB stick.
If your error looks like this:
Welcome to GRUB! error: unrecognized number. Decrementer exception at $SRR0: ...
You are most likely on an iBook/PowerBook with BootROM
4.8.7f1. Since GRUB
will fall back to OpenFirmware console, you can see the model and BootROM
version before the console comes up.
The issue also seems to affect at least some iMacs G5 and possibly other models (though you might not see a decrementer exception), so proceed anyway if you see the error, even if you don't have the model listed here.
The problem is a firmware bug, which results in spurious data left in the MMU, which confuses GRUB during number parsing (it doesn't encounter a trailing zero like it should, continues parsing, finds junk and fails).
The solution is to type this in the OpenFirmware console that comes up:
dev /memory@0 100000 1000 do-unmap
and reboot. GRUB should come up afterwards.
It is possible that this issue may manifest in different ways as well, as there are multiple places in GRUB where this could potentially be a problem. So far this is the only one we've come across, though.
You might have forgotten to mark the PReP boot partition as bootable when
partitioning. In that case, boot the live image again, open the drive with
cfdisk, set the bootable flag, and save the changes. Your system should
This generally happens when reinitializing the partition table. The
utility does not properly wipe the previous partition table. Therefore, run the
# wipefs -a /dev/sdN
sdN is your target drive. Then initialize and partition the drive from
You should not need this when modifying an existing APM (e.g. resizing partitions or creating new ones in free space).
There are multiple reasons:
- 64 KiB pages are only supported starting with POWER8 and older archs will emulate them
- Software is generally more compatible with 4 KiB, since other architectures use 4 KiB page size as well
- On desktop/workstation oriented systems, 4 KiB will generally perform better thanks to finer granularity (which leads to lower fragmentation etc.)
- The systems that benefit from larger kernel pages are mostly single-purpose servers with huge amounts of RAM, which Void does not primarily target (other distros primarily aim at servers)
- Guard pages become viable again, without wasting virtual memory
- Transparent hugepages mostly allow addressing scenarios which would benefit from bigger pages than default
There are some drawbacks, which typically have workarounds, and have their own FAQ entries.
By default it is not possible to boot directly from a Btrfs volume on OpenPOWER systems because Btrfs volumes are tied to the page size of the kernel they were created on.
Since the Skiroot kernel on OpenPOWER systems typically uses 64 KiB pages and Void kernels use 4kB pages, the firmware will not see the volume. Conversely, Void will not see Btrfs volumes created on 64kB page hosts, just like e.g. x86 systems won't see it.
The same thing applies to big endian vs little endian systems - Btrfs is also tied to endianness.
There have also been reports about higher resource usage and lower reliability with Btrfs volumes on 64 KiB page hosts.
- Use a separate
/bootpartition with a filesystem other than Btrfs
- Compile your own kernel with 64 KiB pages
For things such as 4 KiB page virtualization troubles, we have an entire page (no pun intended) dedicated to it here.
Also see the dedicated page.
This is a problem with the kernel
ast driver. Since the fix appears
to be non-trivial and there is no proper patch available, this is WONTFIX from
our side. Either use a dedicated GPU (ideally PCIe, USB2 DisplayLink is known
to work) or use little endian if you really need the
ast to work properly.
This may manifest as the panel or menus behaving strangely and so on.
The workaround is to start the desktop with
exported. The cause here is some endianness related bug(s) in the default
Note: This should no longer be needed since the latest build of
in the repos, as the code has been patched to always use
software on big endian
by default (you can still override it back to the old default via the environment
variable). This is not an upstream change, however.
Drivers on big endian are more buggy than usual, so with some cards you might be having rendering issues with accelerated compositing, which is on by default. Whether you are affected or not depends on the specific card. Old cards that do not support unified shaders are more likely to be affected.
To use WebKit without accelerated compositing, export the following:
Then start the web browser of your choice again.
You might have to append
radeon.agpmode=-1 to kernel command line to disable
AGP GART. This has always been unstable on PowerPC and has been disabled in
mainline kernel for at least 2 years, but older branches still have it.
This is a known issue and there is currently no workaround available. It doesn't
seem to be the AGP mode, and basic OpenGL works (e.g.
glxgears, or menus in
video games). This will be updated if something is found.
On Mac Mini G4, the console may by default display only on a portion of the screen. This is seemingly because there is an S-Video port connected and used by Linux by default.
To work around this, edit
/etc/default/grub and add the following parameter
If you run into the same problem on another machine, the output port name
might be different. You can check by listing the contents of
You can also set the console video mode with something like:
You need to combine the two if you do.
This turns out to be a graphics driver issue. Xfce turned on their compositor by
default in the 4.16 release, which now uses OpenGL, and that makes the issue show
up; while we currently patch
xfwm4 to disable compositing on big endian out of
box, you may still run into it if you manually enable it or if you caught a
package where it was still enabled.
To disable compositing from command line, you should be able to run something like:
xfconf-query -c xfwm4 -p /general/use_compositing -t bool -s false
Alternatively, you can start Xfce with
LIBGL_ALWAYS_SOFTWARE=1 exported in your
environment, disable the compositor in GUI (Window Manager Tweaks) and restart with
accelerated driver afterwards.
If you want compositing on affected machines, you should still be able to use an
alternative compositor such as
picom, given proper configuration.
See the relevant section.
Your date/time may be set wrong (common trouble on Apple machines). Use
to check it. If that is the case, use this:
# date -s "YYYY-MM-DD HH:mm:ss"
Replace the letters with the current date and time. After that, it is recommended that you set up NTP.