Alpine Linux - User contributions [en]

Initramfs init

2025-09-28T07:33:45Z

Realroot: Add command when running outside system

[https://gitlab.alpinelinux.org/alpine/mkinitfs '''mkinitfs'''] is a tool to create initramfs images. Initramfs images are small images which contain a small filesystem with everything required to boot Alpine. For example, when booting a setup with [[Setting up encrypted volumes with LUKS|full disk encryption]], the initramfs contains the binaries required to prompt for a password and mount the encrypted disk.

== Usage ==
Under a running alpine machine, the following command can be used if for some reason the initramfs has not been created properly for a new kernel.
{{cmd|# mkinitfs -c /etc/mkinitfs/mkinitfs.conf -b / <kernelvers>}}
The script is located in {{path|/sbin/}} and is created with ash. It expects {{path|/lib/modules}} to be populated with the <code><kernelvers></code> listed. 
Therefore normally just running <code>mkinitfs</code> should be enough if you need to rebuild it.

Sometimes, e.g. to fix a non booting installation or when installing, you may have to rebuild the initramfs from another system, you do not need to chroot. 
Mount <code>/</code>, <code>/boot</code> etc. and then run:
{{cmd|# mkinitfs -c /mnt/etc/mkinitfs/mkinitfs.conf -b /mnt/ $(ls /mnt/lib/modules/)}}

== Initramfs init cmdline options ==

In addition to the [https://www.kernel.org/doc/html/v4.14/admin-guide/kernel-parameters.html kernel boot parameters] are a number of parameters that the init script understands. These are documented in the <code>mkinitfs-bootparam(7)</code> man page.

Depending on your HDD type and filesystem used, the file appears as follows:
{{cat|/etc/mkinitfs/mkinitfs.conf|features{{=}}"ata base ide scsi usb virtio ext4 nvme"}}

Although you may specify your own init script when building an initramfs, these parameters allow for extensive control over the initial startup of an Alpine Linux system.

== Troubleshooting ==

To troubleshoot booting issues, when using [[Bootloaders#GRUB|grub]], replace <code>quiet</code> with <code>debug_init single</code> in the boot command line.

== See Also ==
* [https://wiki.postmarketos.org/wiki/The_initramfs PostmarketOS Wiki]
* [https://wiki.archlinux.org/title/Arch_boot_process#initramfs ArchWiki boot process]

[[category:Kernel]]
[[Category:Booting]]

F2FS

2025-09-24T17:36:58Z

Realroot: Edit f2fs modules

{{TOC right}}

F2FS (Flash-Friendly File System) is a flash file system initially developed by Samsung Electronics for the Linux kernel.

The motive for F2FS was to build a file system that, from the start, takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.

{{Warning| Using F2FS for the rootfs will cause fsck service to fail, see https://gitlab.alpinelinux.org/alpine/aports/-/issues/17543}}

== Installation ==

Out of the box Alpine Linux doesnt support making F2FS partitions, that can be added with:

{{Cmd|# apk add {{Pkg|f2fs-tools}}}}

== Formatting a partiton using F2FS ==

You can format a partition using F2FS with the following command:

{{Note|'''<code>/dev/sda1</code>''' is used as a example}}

{{Cmd|# mkfs.f2fs /dev/sda1}}

== f2fs module ==
<code>f2fs</code> needs to be manually added to <code>/etc/mkinitfs/mkinitfs.conf</code> if you are using it for rootfs.

Otherwise add it to /etc/modules:
{{Cmd|echo f2fs >> /etc/modules}}
You need the module to mount partitions that are not rootfs.

== See also ==

* [https://en.wikipedia.org/wiki/F2FS Wikipedia Entry on F2FS]

[[Category:Storage]]
[[Category:Filesystems]]

F2FS

2025-09-24T17:24:53Z

Realroot: Add warning about using it for rootfs

{{TOC right}}

F2FS (Flash-Friendly File System) is a flash file system initially developed by Samsung Electronics for the Linux kernel.

The motive for F2FS was to build a file system that, from the start, takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.

{{Warning| Using F2FS for the rootfs will cause fsck service to fail, see https://gitlab.alpinelinux.org/alpine/aports/-/issues/17543}}

== Installation ==

Out of the box Alpine Linux doesnt support making F2FS partitions, that can be added with:

{{Cmd|# apk add {{Pkg|f2fs-tools}}}}

== Formatting a partiton using F2FS ==

You can format a partition using F2FS with the following command:

{{Note|'''<code>/dev/sda1</code>''' is used as a example}}

{{Cmd|# mkfs.f2fs /dev/sda1}}

== f2fs module ==

{{Warning|This section isn't tested (yet): USE AT YOUR OWN RISK}}

<code>f2fs</code> may need to be manually added to <code>/etc/mkinitfs/mkinitfs.conf</code>

or?

{{Cmd|echo f2fs >> /etc/modules}}

== See also ==

* [https://en.wikipedia.org/wiki/F2FS Wikipedia Entry on F2FS]

[[Category:Storage]]
[[Category:Filesystems]]

Bluetooth

2025-06-25T14:39:42Z

Realroot: fix name of the package for file transfer

{{Draft|work in progress}}

[https://en.wikipedia.org/wiki/Bluetooth Bluetooth] is a standard for the short-range wireless interconnection of cellular phones, computers, and other electronic devices. [https://www.bluez.org/ BlueZ] is an implementation of the Bluetooth protocol stack for Linux, and it is provided by the {{Pkg|bluez}} package.

This article describes the basic installation of Bluetooth controllers and devices.

== Prerequisites and Basic Installation ==

=== Prerequisites ===
{{todo|test bluetooth with [[mdev]]}}

{{Pkg|eudev}} should be installed and setup:

{{Cmd|# setup-devd udev}}

=== Basic Installation ===

Basic installation is as follows:

# Install {{Pkg|bluez}}
#* Optionally install {{Pkg|bluez-deprecated}} if you need deprecated tools like <code>hcitool</code>
# Load the <code>btusb</code> kernel module
# Add user to the <code>lp</code> group
# Start and enable the Bluetooth service

{{Cmd|# apk add bluez
# apk add bluez-deprecated
# modprobe btusb
# adduser $USER lp
# rc-service bluetooth start
# rc-update add bluetooth default}}

Now, check the state of the Bluetooth radio transmitter using <code>rfkill</code>:

{{Cmd|$ rfkill list bluetooth}}

It should return something similar to:

0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

If the device is listed as blocked, it can be unblocked using the same tool:

{{Cmd|# rfkill unblock bluetooth}}

{{Note|It may be necessary to restart the Bluetooth service before continuing.}}

=== File transfer ===
Install the {{Pkg|openobex}} package.

=== Front-ends ===

There are several front-ends available:

* The {{Pkg|bluez}} comes with the <code>bluetoothctl</code> front-end
* {{Pkg|blueman}}: a full-featured Bluetooth manager
* {{Pkg|bluedevil}}: the [[KDE]] Bluetooth manager
* {{Pkg|bluetuith}}: simple text-based bluetooth management user interface
* {{Pkg|gnome-bluetooth}}: the [[GNOME]] Bluetooth manager

== Pairing ==

=== Using <code>bluetoothctl</code> ===

Begin by starting <code>bluetoothctl</code> and follow these basic steps:

{{Cmd|$ bluetoothctl}}

The prompt should display:

[bluetooth]#

List the available controllers:

[bluetooth]# list

Display information about a controller:

[bluetooth]# show ''controller_mac_address''

Set the default controller:

[bluetooth]# select ''controller_mac_address''

Power on the controller:

[bluetooth]# power on

Enable the agent and set it as default:

[bluetooth]# agent on
[bluetooth]# default-agent

Set the controller as discoverable (temporarily for 3 minutes) and pairable:

[bluetooth]# discoverable on
[bluetooth]# pairable on

Scan for devices:

[bluetooth]# scan on

Put the device into pairing mode. This generally involves pressing a button or a combinations of buttons, usually for several seconds.

Discover the device MAC address:

[bluetooth]# devices

Pair with the device:

[bluetooth]# pair ''device_mac_address''

Enter the PIN if prompted:

[agent] PIN code: ####

Trust the device:

[bluetooth]# #trust ''device_mac_address''

Connect to the device:

[bluetooth]# connect ''device_mac_address''

Display information about the device:

[bluetooth]# info ''device_mac_address''

The device is now paired:

[bluetooth]# quit

== Configuration ==

=== Set adapter power state ===

If you would like the adapter to not be automatically enabled (e.g. on a portable device where you wish to save battery), set <code>AutoEnable=false</code> in <code>/etc/bluetooth/main.conf</code> in the <code>[Policy]</code> section:

{{Cat|/etc/bluetooth/main.conf|[Policy]
...
AutoEnable=false
...}}

=== Battery Reporting ===

An experimental feature can be enabled in order to report device battery level:

{{Cat|/etc/bluetooth/main.conf|[General]
...
Experimental=true
...}}

== Troubleshooting ==

Due to the variety of available Bluetooth hardware it is possible that you receive errors while attempting to install, activate, or find your Bluetooth device.

=== "No default controller available" error ===

After having followed these instructions, or others, you run <code>bluetoothctl</code> and encounter the following scenario:

[bluetooth]# list
[bluetooth]# show
No default controller available

One possible solution is that you are missing firmware drivers.

Try running the following command to discover the source of the issue:

{{Cmd|# dmesg | grep -i bluetooth | grep -i firmware}}

There are many firmware packages available that could likely solve the this problem (see {{Pkg|linux-firmware-*}}).

Another possible solution is to install {{Pkg|hidapi}} and add load the module:

{{Cmd|# apk add hidapi
# modprobe uhid}}

It may also be necessary to create configuration to load the uhid and btusb kernel modules on boot:

{{Cmd|cat <<EOF > /etc/modules-load.d/uhid.conf
#Load uhid kernel module:
uhid
EOF}}

{{Cmd|cat <<EOF > /etc/modules-load.d/btusb.conf
#Load btusb kernel module:
btusb
EOF}}

=== "org.bluez.Error.NotAvailable br-connection-profile-unavailable" ===

The error <code>br-connection-profile-unavailable</code> is sometimes produced when trying to connect a Bluetooth HID device but the <code>uhid</code> kernel module is not loaded. HID devices include keyboards and the volume buttons on headphones (which are sometimes presented to the OS as a keyboard), mice, game controllers, alphanumeric displays, etc.

The <code>uhid</code> kernel module is required for USB HID devices with drivers that are implemented in userspace, when userspace HID support is enabled.

Loading <code>uhid</code> with <code>modprobe</code> after encountering this error does not always fix the problem.

Try setting up <code>uhid</code> to load at boot, and then rebooting:

{{Cmd|# cat <<EOF > /etc/modules-load.d/uhid.conf
#Load uhid kernel module:
uhid
EOF
# reboot}}

Alternatively, the userspace HID feature can be disabled entirely in favour of kernel HIDP drivers in <code>/etc/bluetooth/input.conf</code>:

{{Cmd|1=UserspaceHID=false}}

If running pipewire, you may also try installing {{Pkg|pipewire-spa-bluez}} to see if that solves the issue.

=== Unable to control Bluetooth speaker volume / Bluetooth output is muted (Pulseaudio) ===

It is possible to automatically switch audio output and volume control to last connected device.

This can solve the problem of controlling the speaker volume when switching between Bluetooth devices.

Append the following lines at the end of the {{Path|/etc/pulse/default.pa}}:

{{Cat|/etc/pulse/default.pa|...
###Automatically switch audio to the most recently connected device (Bluetooth, HDMI, USB)
load-module module-switch-on-connect}}

== See Also ==

* [[PulseAudio#Bluetooth|PulseAudio with Bluetooth]]
* [[PipeWire#Bluetooth_audio|PipeWire with Bluetooth]]
* [https://wiki.postmarketos.org/wiki/Bluetooth Bluetooth entry on PostmarketOS Wiki]
* [https://wiki.gentoo.org/wiki/Bluetooth Bluetooth entry on Gentoo Wiki]
* [https://wiki.archlinux.org/title/Bluetooth Bluetooth entry on ArchWiki]

[[Category:Multimedia]]
[[Category:Hardware]]
[[Category:Sound]]
[[Category:Drivers]]

Bluetooth

2025-06-25T14:37:54Z

Realroot: Add openobex for file transfer

{{Draft|work in progress}}

[https://en.wikipedia.org/wiki/Bluetooth Bluetooth] is a standard for the short-range wireless interconnection of cellular phones, computers, and other electronic devices. [https://www.bluez.org/ BlueZ] is an implementation of the Bluetooth protocol stack for Linux, and it is provided by the {{Pkg|bluez}} package.

This article describes the basic installation of Bluetooth controllers and devices.

== Prerequisites and Basic Installation ==

=== Prerequisites ===
{{todo|test bluetooth with [[mdev]]}}

{{Pkg|eudev}} should be installed and setup:

{{Cmd|# setup-devd udev}}

=== Basic Installation ===

Basic installation is as follows:

# Install {{Pkg|bluez}}
#* Optionally install {{Pkg|bluez-deprecated}} if you need deprecated tools like <code>hcitool</code>
# Load the <code>btusb</code> kernel module
# Add user to the <code>lp</code> group
# Start and enable the Bluetooth service

{{Cmd|# apk add bluez
# apk add bluez-deprecated
# modprobe btusb
# adduser $USER lp
# rc-service bluetooth start
# rc-update add bluetooth default}}

Now, check the state of the Bluetooth radio transmitter using <code>rfkill</code>:

{{Cmd|$ rfkill list bluetooth}}

It should return something similar to:

0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

If the device is listed as blocked, it can be unblocked using the same tool:

{{Cmd|# rfkill unblock bluetooth}}

{{Note|It may be necessary to restart the Bluetooth service before continuing.}}

=== File transfer ===
Install the {{Pkg|openbluez}}.

=== Front-ends ===

There are several front-ends available:

* The {{Pkg|bluez}} comes with the <code>bluetoothctl</code> front-end
* {{Pkg|blueman}}: a full-featured Bluetooth manager
* {{Pkg|bluedevil}}: the [[KDE]] Bluetooth manager
* {{Pkg|bluetuith}}: simple text-based bluetooth management user interface
* {{Pkg|gnome-bluetooth}}: the [[GNOME]] Bluetooth manager

== Pairing ==

=== Using <code>bluetoothctl</code> ===

Begin by starting <code>bluetoothctl</code> and follow these basic steps:

{{Cmd|$ bluetoothctl}}

The prompt should display:

[bluetooth]#

List the available controllers:

[bluetooth]# list

Display information about a controller:

[bluetooth]# show ''controller_mac_address''

Set the default controller:

[bluetooth]# select ''controller_mac_address''

Power on the controller:

[bluetooth]# power on

Enable the agent and set it as default:

[bluetooth]# agent on
[bluetooth]# default-agent

Set the controller as discoverable (temporarily for 3 minutes) and pairable:

[bluetooth]# discoverable on
[bluetooth]# pairable on

Scan for devices:

[bluetooth]# scan on

Put the device into pairing mode. This generally involves pressing a button or a combinations of buttons, usually for several seconds.

Discover the device MAC address:

[bluetooth]# devices

Pair with the device:

[bluetooth]# pair ''device_mac_address''

Enter the PIN if prompted:

[agent] PIN code: ####

Trust the device:

[bluetooth]# #trust ''device_mac_address''

Connect to the device:

[bluetooth]# connect ''device_mac_address''

Display information about the device:

[bluetooth]# info ''device_mac_address''

The device is now paired:

[bluetooth]# quit

== Configuration ==

=== Set adapter power state ===

If you would like the adapter to not be automatically enabled (e.g. on a portable device where you wish to save battery), set <code>AutoEnable=false</code> in <code>/etc/bluetooth/main.conf</code> in the <code>[Policy]</code> section:

{{Cat|/etc/bluetooth/main.conf|[Policy]
...
AutoEnable=false
...}}

=== Battery Reporting ===

An experimental feature can be enabled in order to report device battery level:

{{Cat|/etc/bluetooth/main.conf|[General]
...
Experimental=true
...}}

== Troubleshooting ==

Due to the variety of available Bluetooth hardware it is possible that you receive errors while attempting to install, activate, or find your Bluetooth device.

=== "No default controller available" error ===

After having followed these instructions, or others, you run <code>bluetoothctl</code> and encounter the following scenario:

[bluetooth]# list
[bluetooth]# show
No default controller available

One possible solution is that you are missing firmware drivers.

Try running the following command to discover the source of the issue:

{{Cmd|# dmesg | grep -i bluetooth | grep -i firmware}}

There are many firmware packages available that could likely solve the this problem (see {{Pkg|linux-firmware-*}}).

Another possible solution is to install {{Pkg|hidapi}} and add load the module:

{{Cmd|# apk add hidapi
# modprobe uhid}}

It may also be necessary to create configuration to load the uhid and btusb kernel modules on boot:

{{Cmd|cat <<EOF > /etc/modules-load.d/uhid.conf
#Load uhid kernel module:
uhid
EOF}}

{{Cmd|cat <<EOF > /etc/modules-load.d/btusb.conf
#Load btusb kernel module:
btusb
EOF}}

=== "org.bluez.Error.NotAvailable br-connection-profile-unavailable" ===

The error <code>br-connection-profile-unavailable</code> is sometimes produced when trying to connect a Bluetooth HID device but the <code>uhid</code> kernel module is not loaded. HID devices include keyboards and the volume buttons on headphones (which are sometimes presented to the OS as a keyboard), mice, game controllers, alphanumeric displays, etc.

The <code>uhid</code> kernel module is required for USB HID devices with drivers that are implemented in userspace, when userspace HID support is enabled.

Loading <code>uhid</code> with <code>modprobe</code> after encountering this error does not always fix the problem.

Try setting up <code>uhid</code> to load at boot, and then rebooting:

{{Cmd|# cat <<EOF > /etc/modules-load.d/uhid.conf
#Load uhid kernel module:
uhid
EOF
# reboot}}

Alternatively, the userspace HID feature can be disabled entirely in favour of kernel HIDP drivers in <code>/etc/bluetooth/input.conf</code>:

{{Cmd|1=UserspaceHID=false}}

If running pipewire, you may also try installing {{Pkg|pipewire-spa-bluez}} to see if that solves the issue.

=== Unable to control Bluetooth speaker volume / Bluetooth output is muted (Pulseaudio) ===

It is possible to automatically switch audio output and volume control to last connected device.

This can solve the problem of controlling the speaker volume when switching between Bluetooth devices.

Append the following lines at the end of the {{Path|/etc/pulse/default.pa}}:

{{Cat|/etc/pulse/default.pa|...
###Automatically switch audio to the most recently connected device (Bluetooth, HDMI, USB)
load-module module-switch-on-connect}}

== See Also ==

* [[PulseAudio#Bluetooth|PulseAudio with Bluetooth]]
* [[PipeWire#Bluetooth_audio|PipeWire with Bluetooth]]
* [https://wiki.postmarketos.org/wiki/Bluetooth Bluetooth entry on PostmarketOS Wiki]
* [https://wiki.gentoo.org/wiki/Bluetooth Bluetooth entry on Gentoo Wiki]
* [https://wiki.archlinux.org/title/Bluetooth Bluetooth entry on ArchWiki]

[[Category:Multimedia]]
[[Category:Hardware]]
[[Category:Sound]]
[[Category:Drivers]]

Setting up encrypted volumes with LUKS

2025-06-25T14:34:39Z

Realroot: Add localmount service note

[https://en.wikipedia.org/wiki/Linux%20Unified%20Key%20Setup LUKS] allows encrypting a partition and mapping it as a virtual block device, which can then be used as a normal partition. Guides for other Linux distributions should serve as a general references for installing Alpine onto a LUKS encrypted disk.

The following approaches are known to work:

* Plain LUKS
* [[LVM on LUKS]]

The installer has built-in support for encryption. The default installer will not encrypt the swap partition and the boot partition. To setup Alpine Linux with an encrypted swap partition, refer to [[LVM on LUKS]]. The [[Bootloaders#GRUB|GRUB]] bootloader supports BIOS and EFI boot with an encrypted boot partition.

== mkinitfs and LUKS ==

For those familiar with setting up FDE on other Linux distributions, this section contains only Alpine-specific knowledge required and understanding [[mkinitfs]].

First of all, the <code>cryptsetup</code> feature needs to be added to {{path|/etc/mkinitfs/mkinitfs.conf}}. Additionally, the following kernel parameters are required:

* <code>cryptroot</code> kernel parameter should point to the encrypted block device.
* <code>cryptdm</code>: the name that will be given to the device.
* <code>root</code> kernel parameter should point to the mapped block device: <code>/dev/mapper/<name used in cryptdm></code>.
* <code>rootfstype</code>: the filesystem type of the root partition (e.g.: <code>btrfs</code>).

For example, if you use grub with GPT partition table using ext4 without LVM the {{path|/etc/default/grub}} file will be as follows:{{Cat|/etc/default/grub|<nowiki>GRUB_TIMEOUT=2
GRUB_DISABLE_SUBMENU=y
GRUB_DISABLE_RECOVERY=true
GRUB_CMDLINE_LINUX_DEFAULT="modules=sd-mod,usb-storage,ext4 quiet rootfstype=ext4 cryptroot=UUID=a7dc90c4-6746-417e-b25b-cb8769ee6334 cryptdm=alpine-rootfs root=/dev/mapper/alpine-rootfs"
GRUB_PRELOAD_MODULES="luks cryptodisk part_gpt"
GRUB_ENABLE_CRYPTODISK=y
</nowiki>}}

== Decrypting non-root volumes during boot ==
{{Main|LVM on LUKS#Mounting additional encrypted filesystems at boot}}
To have an encrypted non-root volume be decrypted prior to automatically mounting it somewhere via <code>/etc/fstab</code>, configure <code>dmcrypt</code> in the {{path|/etc/conf.d/dmcrypt}} file. The comments inside that file should guide you, but as a simple example, here's what you should include in that file to decrypt and map a partition to some volume named, say, “<code>myvolume</code>”, given its UUID (here represented using a series of <code>X</code>s), using a passphrase {{Cat|/etc/conf.d/dmcrypt|<nowiki>...
target=myvolume
source=UUID=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXX
key=/etc/keys/myvolume.key #not needed as passphrase is used in this example
...</nowiki>}}

In {{path|/etc/fstab}} file, then, you would include the following line as follows:{{Cat|/etc/fstab|<nowiki>...
/dev/mapper/myvolume <path> <fstype> <options>
...</nowiki>}}

substituting in the proper parameters.

Do not forget to enable the <code>localmount</code> service:

<code>rc-update add localmount</code>

Otherwise they will not be mounted automatically.

== See also ==

* [[LVM on LUKS]]
* [[mkinitfs|Initramfs init]]
* [[Full disk encryption secure boot]]
* [[Setting up a laptop|Setting up a secured laptop]]
* [https://wiki.archlinux.org/index.php/Dm-crypt dm-crypt on ArchWiki]

[[Category:Storage]]
[[Category:Security]]

Radeon Video

2025-06-12T14:24:53Z

Realroot: Add command to find amdgpu or radeon module

{{TOC right}}

The following instructions are for modern AMD GPU chipsets covered by the <code>radeon</code> and <code>amdgpu</code> drivers.

== Firmware ==

For [https://en.wikipedia.org/wiki/List%20of%20AMD%20graphics%20processing%20units Vega and later], the {{Pkg|linux-firmware-amdgpu}} package is required. Otherwise, the {{Pkg|linux-firmware-radeon}} should be used.

See [https://wiki.gentoo.org/wiki/AMDGPU the relevant section on the Gentoo Wiki] for a more granular list of product names and microarchitecture names.

== Kernel Modesetting (KMS) ==

To enable [[KMS]] at boot:

# Run <code>lspci -k | grep amdgpu</code> and <code>lspci -k | grep radeon</code> to find your module. For example it will return <code>Kernel driver in use: amdgpu</code> for the <code>amdgpu</code> module when running the first command.
# Add the <code>radeon</code> or <code>amdgpu</code> and <code>fbcon</code> modules to {{Path|/etc/modules}}: {{Cmd|$ echo radeon >> /etc/modules $ echo fbcon >> /etc/modules}} or {{Cmd|$ echo amdgpu >> /etc/modules $ echo fbcon >> /etc/modules}}
# Install <code>mkinitfs</code>: {{Cmd|apk add mkinitfs}}
# Enable the <code>kms</code> feature in the <code>mkinitfs</code> configuration by adding it to the <var>features</var> variable, e.g., {{cat|/etc/mkinitfs/mkinitfs.conf|features{{=}}"keymap cryptsetup kms ata base ide scsi usb virtio ext4"}}
# Run <code>mkinitfs</code>.
# Reboot to test the configuration.

== Wayland ==

Install the following packages as needed:

* {{Pkg|mesa-dri-gallium}}: '''necessary''' Mesa drivers.
* {{Pkg|mesa-va-gallium}}: VA-API drivers, for hardware accelerated video encoding and decoding

If driver auto-selection does not work, e.g. no mouse cursor under Sway, manual driver selection might be needed:

* <code>export MESA_LOADER_DRIVER_OVERRIDE=r300</code>: for AMD's Radeon R300, R400, and R500 GPUs.
* <code>export MESA_LOADER_DRIVER_OVERRIDE=r600</code>: for AMD's Radeon R600 GPUs up to Northern Islands. Officially supported by AMD.
* <code>export MESA_LOADER_DRIVER_OVERRIDE=radeonsi</code>: for AMD's Southern Island GPUs and later. Officially supported by AMD.

For VA-API:
* <code>export LIBVA_DRIVER_NAME=r600</code>
* <code>export LIBVA_DRIVER_NAME=radeonsi</code>

== Xorg ==
{{Main|Xorg}}
Install either the Free Software driver {{Pkg|xf86-video-ati}} or the proprietary amdgpu firmware {{Pkg|linux-firmware-amdgpu}}.

<code>modprobe fbcon</code> might be needed to avoid black screen when leaving Xorg.

== See also ==

* [https://wiki.archlinux.org/title/AMDGPU AMDGPU - ArchWiki]
* [https://wiki.archlinux.org/title/ATI ATI - ArchWiki]

[[Category:Drivers]]
[[Category:Graphics]]

Setting up encrypted volumes with LUKS

2025-03-09T15:07:45Z

Realroot: Add grub file example

Setting up encrypted volumes with LUKS

2025-03-09T13:08:14Z

Realroot: Add missing parameter and grub instructions