Alpine Linux - User contributions [en]

Setting up ZFS on LUKS

2022-07-27T14:27:07Z

La9: native encryption

= Native Encryption =

ZFS now has native support for encryption. This has many advantages over ZFS on LUKS including multi-disk, encrypted zfs send, portable across *BSD/Linux and others.

For a Root on ZFS guide with native encryption, see [https://openzfs.github.io/openzfs-docs/Getting%20Started/Alpine%20Linux/Root%20on%20ZFS/1-preparation.html here].

= Introduction =

This documentation describes how to set up Alpine Linux using ZFS with a pool that is located in an encrypted partition. To encrypt the partition the Device Mapper crypt (dm-crypt) module and Linux Unified Key Setup (LUKS) is used.

Note that you must install the <code>/boot/</code> directory on an unecrypted partition to boot correctly.

We'll be using the syslinux bootloader and traditional BIOS booting.

== Requirements ==

* An instance Alpine on a medium other than the one you'll boot from, see [[Installation|official installation guide.]]
{{Note|We can't use the live environment from the installation isos, because we'll install the ZFS kernel module and that isn't possible with a read-only /boot (as provided by the iso).}}

== Hard Disk Device Name ==

The following documentation uses the <code>/dev/sda</code> device as the installation destination. If your environment uses a different device name for your hard disk, use the corresponding device name in the examples.

= Setting up Alpine Linux Using ZFS on Top of a LUKS Partition =

To install Alpine Linux in a ZFS pool on top of a LUKS encrypted partition, you cannot use the [[Installation|official installation]] procedure. The installation requires several manual steps you must run in the Alpine Linux Live CD environment.

== Preparing the Installation Environment ==

Before you begin to install Alpine Linux on the medium you intend to boot from, prepare the installation you already have:

* Update the <code>apk</code> cache:

# apk update

* Install the following packages required to set up ZFS and LUKS:

# apk add haveged cryptsetup e2fsprogs syslinux zfs zfs-$(uname -r | rev | cut -d'-' -f1 | rev)
# modprobe zfs

* Optionally, start the <code>haveged</code> service for unpredictable random numbers used for encryption:

# rc-service haveged start

== Creating the Partition Layout ==

Linux requires an unencrypted <code>/boot/</code> partition to boot. You can assign the remaining space for the encrypted ZFS pool.

* Start the <code>fdisk</code> utility to set up partitions:

# fdisk /dev/sda

:* Create the <code>/boot/</code> partition:
::* Enter <code>n</code> → <code>p</code> → <code>1</code> → <code>1</code> → <code>100m</code> to create a new 100 MB primary partition.

:* Set the <code>/boot/</code> partition active:
::* Enter <code>a</code> → <code>1</code>.

:* Create the LUKS partition:
::* Enter <code>n</code> → <code>p</code> → <code>2</code> to start creating the next partition. Press <code>Enter</code> to select the default start cylinder. Enter the partition size. For example, <code>512m</code> for 512 MB or <code>5g</code> for 5 GB. Alternatively, press <code>Enter</code> to set the maximum available size.

:* To verify the settings, press <code>p</code>. The output should look similar to this:
<pre>
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 206847 204800 100M 83 Linux
/dev/sda2 206848 41943039 41736192 19.9G 83 Linux
</pre>
* Press <code>w</code> to save the changes.

* Optionally, fill the LUKS partition with random values:

# haveged -n 0 | dd of=/dev/sda2

{{Note|Depending on the size of the partition, this process can take from several minutes to many hours.}}

== Encrypting the ZFS Partition ==

* To encrypt the partition which will later contain the LVM PV:

# cryptsetup luksFormat /dev/sda2

:{{Note|Alpine Linux uses the <code>en-us</code> keyboard mapping when prompting for the password to encrypt the partition at boot time. If you changed the keyboard map in the temporary environment, the password you enter during encrypting the partition in this step, may not match the password you will enter during the system boots.}}
: If you prefer setting an individual hashing algorithm and hashing schema:
:* To run a benchmark:

# cryptsetup benchmark

:* To encrypt the partition using individual settings, enter, for example:

# cryptsetup -v -c serpent-xts-plain64 -s 512 --hash whirlpool --iter-time 5000 --use-random luksFormat /dev/sda2

== Creating the filesystems ==

* Open the LUKS partition:

# cryptsetup open --type luks /dev/sda2 crypt

=== Creating the ZFS pool ===

# zpool create -o ashift=12 -O normalization=formD -O atime=off -m none -R /mnt -O compression=lz4 tank /dev/mapper/crypt

Meaning of the <code>zpool create</code> options:

{| cellpadding="5" border="1" class="wikitable"
|-
! Option
! Meaning
|-
| zpool create
| Creating the zpool
|-
| -o ashift=12
| 4K blocks
|-
| -O normalization=formD
| Set the default Unicode (UTF-8) normalization to 'formD'
|-
| -O atime=off
| Disabling updates to file access time. This reduces writes to disk, but might cause issues with mailers, like <code>mutt</code>.
|-
| -m none
| No mountpoint, as we'll handle this later.
|-
| -R /mnt
| Set the altroot to <code>/mnt</code>. It's like a temporary mountpoint for the pool.
|-
| -O compression=lz4
| Use lz4 compression for the pool. Is generally recommended.
|-
| tank
| The pool name. <code>tank</code> will be used in throughout this guide.
|-
| /dev/mapper/crypt
| The path to the block device ZFS will use.
|}

After completing this, confirm that the pool has been created:

# zpool status

Should return something like:
<pre>
pool: tank
state: ONLINE
scan: none requested
config:

NAME STATE READ WRITE CKSUM
tank ONLINE 0 0 0
crypt ONLINE 0 0 0

errors: No known data errors
</pre>

=== Creating the required datasets ===

# zfs create -o mountpoint=none -o canmount=off tank/ROOT
# zfs create -o mountpoint=/ tank/ROOT/alpine

=== Creating optional datasets (feel free to add your own) ===

# zfs create -o mountpoint=/home tank/HOME
# zfs create -o mountpoint=/var/log tank/LOG

== Creating the <code>/boot</code> filesystem ==

# mkfs.ext4 /dev/sda1

== Mounting the <code>/boot</code> filesystem ==

* Create <code>/mnt/boot/</code> directory and mount the <code>/dev/sda1</code> partition in this directory:

# mkdir /mnt/boot/
# mount -t ext4 /dev/sda1 /mnt/boot/

== Installing Alpine Linux ==

In this step you will install Alpine Linux in the <code>/mnt/</code> directory, which contains the mounted file system structure.

* Install Alpine Linux:

# setup-disk -m sys /mnt/

: The installer downloads the latest packages to install the base installation. Additionally, the installer automatically creates the entries for the mount points in the <code>fstab</code> file (but we'll have to edit it manually later), which are currently mounted in the <code>/mnt/</code> directory.

: {{Note|The automatic writing of the master boot record (MBR) fails in this step. Later, you'll write the MBR to the disk manually.}}

* To enable the operating system to decrypt the LUKS partition at boot time, create the <code>/mnt/etc/crypttab</code> file. Enter the following line into the file to decrypt the <code>/dev/sda2</code> partition using the <code>luks</code> module and map it to the <code>lvmcrypt</code> name:

crypt /dev/sda2 none luks

* Delete the zfs entries in <code>/mnt/etc/fstab</code> as ZFS mounts them automagically. Your fstab should look similar to this:

UUID=6b4f2c9c-0a0f-4a8c-a73b-d2b47920ad6f /boot ext4 rw,relatime,stripe=4,data=ordered 0 2

* Edit the <code>/mnt/etc/mkinitfs/mkinitfs.conf</code> file and append the <code>cryptsetup</code> and <code>zfs</code> module to the <code>features</code> parameter:

features="ata base ide scsi usb virtio ext4 lvm <u>cryptsetup zfs</u>"

* Rebuild the initial RAM disk:

# mkinitfs -c /mnt/etc/mkinitfs/mkinitfs.conf -b /mnt/ $(ls /mnt/lib/modules/)

: The command uses the settings from the <code>mkinitfs.conf</code> file set in the <code>-c</code> parameter to generate the RAM disk. The command is executed in the <code>/mnt/</code> directory and the RAM disk is generated using the modules for the installed kernel. Without setting the kernel version using the <code>$(ls /mnt/lib/modules/</code>) option, <code>mkinitfs</code> tries to generate the RAM disk using the kernel version installed in the temporary environment, which can differ from the latest one installed by the <code>setup-disk</code> utility.

* Edit the <code>/mnt/etc/update-extlinux.conf</code> file, set the root ZFS dataset and append the following kernel options to the <code>default_kernel_opts</code> parameter:

root=tank/ROOT/alpine
default_kernel_opts="... <u>cryptroot=/dev/sda2 cryptdm=crypt rootfstype=zfs</u>"

: The <code>cryptroot</code> parameter sets the name of the device that contains the root file system. The <code>cryptdm</code> parameter sets the name of the mapping previously set in the <code>crypttab</code> file. The <code>rootfstype</code> option sets the root filesystem type to zfs.

* Because the <code>update-extlinux</code> utility operates only on the <code>/boot/</code> directory, temporarily change the root to the <code>/mnt/</code> directory and update the boot loader configuration:

# chroot /mnt/
# update-extlinux
# exit

: Ignore the errors the <code>update-extlinux</code> utility displays.

* Write the MBR to the <code>/dev/sda</code> device:

# dd bs=440 count=1 conv=notrunc if=/mnt/usr/share/syslinux/mbr.bin of=/dev/sda

== Unmounting the filesystems ==

* Unmount <code>/mnt/boot/</code>:

# umount /mnt/boot/

* Unmount all zfs filesystems:

# zfs unmount -a

* Export all zfs pools:

# zpool export -a

* Close the <code>lvmcrypt</code> device:

# cryptsetup luksClose crypt

* Reboot the system:

# reboot

= Troubleshooting =

== General Procedure ==

In case your system fails to boot, you can verify the settings and fix incorrect configurations:

* [[#Preparing_the_Temporary_Installation_Environment|Prepare the temporary installation environment]]

* Load the ZFS kernel module:

# modprobe zfs

* [[#Mounting_the_File_Systems|Mount the file systems]]

# zpool import -R /mnt tank
# mount -t ext4 /dev/sda1 /mnt/boot

* Verify that you run the steps described in the [[#Installing_Alpine_Linux|Installing Alpine Linux]] section correctly. Update the configuration if necessary.

* [[#Unmounting_the_Volumes_and_Partitions|Unmount the volumes and partitions]]

{{Todo|Multiple Disk ZFS on LUKS?}}

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

Root on ZFS with native encryption

2022-07-27T14:24:20Z

La9: update openzfs docs

This is a guide for installing Alpine Linux with its root partition on an encrypted ZFS volume, using ZFS's own encryption capabilities. The system will be encrypted when powered off and will need to be unlocked by typing a passphrase at boot. To be able to boot the system, the `/boot` partition remains unencrypted.

= OpenZFS Guide =

A guide on OpenZFS website supports native encryption, UEFI boot and legacy boot, and multi-disk. See [https://openzfs.github.io/openzfs-docs/Getting%20Started/Alpine%20Linux/Root%20on%20ZFS/1-preparation.html here].

= Downloading Alpine =

Download the '''extended''' release from https://www.alpinelinux.org/downloads/ as only it contains the zfs kernel modules at the time of writing (2022-02-12).

Write it to a USB device and boot from it.

= Initial Setup =

Run the following to start the installation procedure:

setup-alpine

Answer all the questions, and hit ctrl-c when promted for which disk you'd like to use.

== Optional: SSH access ==

This section is optional and it assumes internet connectivity. You may enable sshd so you can ssh into the box and copy and paste the rest of the commands from these instructions into a terminal window.

Edit `/etc/ssh/sshd_config` and search for `Permit`. Change the value after `PermitRootLogin` to read `yes`

save and exit to shell. Run `service sshd restart`

Now you can ssh in as root. Do not forget to go back and comment this line out when you're done since it will be enabled on the resulting machine. You will be reminded again at the end of this doc.

= Add required packages =

apk add zfs sfdisk e2fsprogs syslinux

= Partition setup =

We're assuming that `/dev/sda` is the target storage device here and in the rest of the document, but the name of the storage device you wish to install to may be different. To see a list of storage devices and determine the correct one, type `sfdisk -l`.

echo -e "/dev/sda1: start=1M,size=100M,bootable\n/dev/sda2: start=101M" | sfdisk --quiet --label dos /dev/sda

== Create device nodes ==

mdev -s

== Create the /boot filesystem ==

mkfs.ext4 /dev/sda1

= ZFS setup =
== Create the root zpool ==

modprobe zfs
zpool create -f -o ashift=12 \
-O acltype=posixacl -O canmount=off -O compression=lz4 \
-O dnodesize=auto -O normalization=formD -O relatime=on -O xattr=sa \
-O encryption=aes-256-gcm -O keylocation=prompt -O keyformat=passphrase \
-O mountpoint=/ -R /mnt \
rpool /dev/sda2

You will have to enter your passphrase at this point. Choose wisely, as your passphrase is most likely [https://gitlab.com/cryptsetup/cryptsetup/wikis/FrequentlyAskedQuestions#5-security-aspects the weakest link in this setup].

A few notes on the options supplied to zpool:

- `ashift=12` is recommended here because many drives today have 4KiB (or larger) physical sectors, even though they present 512B logical sectors

- `acltype=posixacl` enables POSIX ACLs globally

- `normalization=formD` eliminates some corner cases relating to UTF-8 filename normalization. It also enables `utf8only=on`, meaning that only files with valid UTF-8 filenames will be accepted.

- `xattr=sa` vastly improves the performance of extended attributes, but is Linux-only. If you care about using this pool on other OpenZFS implementation don't specify this option.

After completing this, confirm that the pool has been created:

# zpool status

Should return something like:

pool: rpool
state: ONLINE
scan: none requested
config:

NAME STATE READ WRITE CKSUM
rpool ONLINE 0 0 0
sda2 ONLINE 0 0 0

errors: No known data errors

== Create the required datasets and mount root ==

zfs create -o mountpoint=none -o canmount=off rpool/ROOT
zfs create -o mountpoint=legacy rpool/ROOT/alpine
mount -t zfs rpool/ROOT/alpine /mnt/

== Mount the `/boot` filesystem ==

mkdir /mnt/boot/
mount -t ext4 /dev/sda1 /mnt/boot/

== Enable ZFS' services ==

rc-update add zfs-import sysinit
rc-update add zfs-mount sysinit

= Install Alpine Linux =

setup-disk /mnt
dd if=/usr/share/syslinux/mbr.bin of=/dev/sda # write mbr so we can boot

= Reboot and enjoy! =

😉

'''NOTE:'''
If you went with the optional step, be sure to disable root login after you reboot.

User:R3/Root on ZFS with Native Encryption

2022-07-27T14:19:16Z

La9: update

== Official OpenZFS Documentation ==

A guide is available for Root on ZFS installation on OpenZFS website:

https://openzfs.github.io/openzfs-docs/Getting%20Started/Alpine%20Linux/Root%20on%20ZFS/1-preparation.html

PipeWire

2022-07-27T06:20:16Z

La9: /* Installation and configuration */ rm refs to pipewire-media-session

{{Draft|The instructions below have not been thoroughly tested and may break things.}}

[https://pipewire.org/ PipeWire] is a multimedia processing engine that aims to improve audio and video handling on Linux.

== Prerequisites ==

=== Audio Group ===

When elogind is not available, the user has to be added to the <code>audio</code> group. The user must re-log-in in for this to take effect.

<pre>
# addgroup <user> audio
</pre>

=== D-Bus ===

PipeWire requires a running [https://www.freedesktop.org/wiki/Software/dbus/ D-Bus] session. If you use a full desktop environment this will probably be started automatically, but with minimal window managers it must be done manually.

<pre>
# apk add dbus dbus-openrc
# rc-service dbus start
# rc-update add dbus default
</pre>

Then use <code>dbus-run-session</code> whenever you start an X or Wayland session. For example:
<pre>
$ dbus-run-session -- sway
</pre>

=== XDG_RUNTIME_DIR ===

If you are not using a Desktop Manager, ensure that your <code>XDG_RUNTIME_DIR</code> is set to a user-writable location. By default for pulseaudio this is {{Path|/run/user/1000/}} or {{Path|/tmp}}. If this is not set, pipewire will create a directory in your home folder instead, called <code>~/pulse</code>, and on attempting to run Pavucontrol or pactl, you will get the following error:

<pre>
$ pactl list
Connection failure: Connection refused
pa_context_connect() failed: Connection refused
</pre>

== Installation and configuration ==

<pre>
# apk add pipewire wireplumber
</pre>

{{Note|Using [https://gitlab.freedesktop.org/pipewire/wireplumber WirePlumber] rather than the pipewire-media-session (which comes with pipewire) is [https://gitlab.freedesktop.org/pipewire/media-session/-/blob/master/README.md recommended] but not required.}}

=== Realtime scheduling ===

For realtime scheduling, it is recommended to use rtkit,

<pre>
# apk add rtkit
</pre>

and then add your user to the `rtkit` group.

Alternatively, ensure your user has the right ulimit permissions. You generally need (limits.conf format):

<pre>
@audio - memlock 256
@audio - nice -11
@audio - rtprio 88
</pre>

This allows a member of the audio group to have the right permissions for PipeWire to use realtime scheduling without rtkit.

=== ALSA ===

<pre>
# apk add pipewire-alsa
</pre>

ALSA support works out of the box if you have the pipewire-alsa package. You may need the <code>snd_seq</code> kernel module.

=== PulseAudio ===

PipeWire can run a [https://www.freedesktop.org/wiki/Software/PulseAudio/ PulseAudio] daemon which should allow all existing PulseAudio applications to be used with the PipeWire backend. You need to have <code>pipewire-pulse</code> installed.

=== JACK ===

If you will be using PipeWire for [https://jackaudio.org/ JACK] applications install the required package (pipewire-jack). Things should work with just that.

=== Video ===

Video should work out-of-the-box with v4l2 devices (e.g. a lot of webcams) and [https://gstreamer.freedesktop.org/ GStreamer] applications.

=== Bluetooth audio ===

* Enable PulseAudio support as described above
* Install bluetooth service packages: <code>bluez bluez-openrc pipewire-spa-bluez</code>
* Optional: install GUI manager for bluetooth <code>blueman</code>
* Enable and start bluetooth service: <code>rc-update add bluetooth; rc-service bluetooth start</code>
* Restart PipeWire
* Use commandline program <code>bluetoothctl</code> or GUI program <code>blueman-manager</code> to scan and pair bluetooth audio devices.
* Use pavucontrol to adjust volume and manually select high definition bluetooth codecs.

== Screen sharing on Wayland ==

You will need the right [https://github.com/flatpak/xdg-desktop-portal xdg-desktop-portal] backend for your desktop environment. Screen sharing is known to work on:
* GNOME with <code>xdg-desktop-portal-gtk</code>
* KDE Plasma with <code>xdg-desktop-portal-kde</code> and Firefox
* Sway with <code>xdg-desktop-portal-wlr</code> and Firefox, see [[Sway]] for details

== Usage ==

Start the PipeWire media server. You'll probably get quite a few errors but just ignore them for now.

<pre>
$ /usr/libexec/pipewire-launcher
</pre>

{{Note| PipeWire doesn't auto-start a session manager anymore.
In 3.14 and earlier, the PipeWire default config was edited in packaging to auto-start pipewire-media-session as the default session manager. Since we now have wireplumber available as an alternative session manager, this has been changed in favor of a launch wrapper for pipewire at /usr/libexec/pipewire-launcher. When executed, this will launch pipewire, pipewire-media-session or wireplumber, and pipewire-pulse, depending on what modules are available. If you were launching /usr/bin/pipewire and the session manager manually before, please use the new launcher wrapper instead. WirePlumber can now also be used as a proper alternative for pipewire-media-session.}}

In a different terminal window check the default output device. I don't yet know how this default can be changed for all applications, so you'd better hope it's right!

wireplumber:
<pre>
$ wpctl status
</pre>

Test sound is working using an audio file in a format supported by [http://www.mega-nerd.com/libsndfile/ libsndfile] (e.g. flac, opus, ogg, wav).

<pre>
# apk add pipewire-tools
$ pw-cat -p test.flac
</pre>

If you have a microphone test audio recording is working.

<pre>
$ pw-cat -r --list-targets
$ pw-cat -r recording.flac
(Speak for a while then stop it with Ctrl+c)
$ pw-cat -p recording.flac
</pre>

Test PulseAudio clients using a media player (most use PulseAudio) and if you use JACK test that too:

<pre>
# apk add jack-example-clients
$ jack_simple_client
</pre>

You should hear a sustained beep.

If you are happy everything is working, make PipeWire start automatically when your X or Wayland session starts. For example, you could add the <code>/usr/libexec/pipewire-launcher</code> command to <code>~/.xinitrc</code> or your window manager's config file.

== Troubleshooting ==

=== `wpctl status` shows no targets ===

First, check whether ALSA knows about your sound card:

<pre>
aplay -l
</pre>

If sound devices are found, the issue is with your pipewire configuration. Consider double-checking the instructions above.

Otherwise, your sound card may not be supported in the version of the Linux Kernel you're running. You should search online for fixes relating to your current kernel version and the codec of your sound card. You can find each of these with:

<pre>
uname -r
cat /proc/asound/card0/codec* | grep Codec
</pre>

== Quick Configuration ==

You might want to use pavucontrol to have a simple GUI app for controlling sound, outputs, etc, in which case:
<pre>
# apk add pavucontrol
</pre>

== See Also ==

* [https://gitlab.freedesktop.org/pipewire/pipewire PipeWire source repository]
* [https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/home PipeWire Wiki]
* [https://wiki.archlinux.org/index.php/PipeWire PipeWire on the ArchWiki]
* [https://wiki.gentoo.org/wiki/Pipewire PipeWire on the Gentoo Wiki]

[[Category:Desktop]]
[[Category:Multimedia]]
[[Category:Sound]]

Talk:Sway

2022-07-27T06:12:07Z

La9: re

== Setting up eudev ==
Hi, first-time user here. While following this page's instructions I found that setup-udev command doesn't exist, and couldn't find anything about which package provides it. My guess is it's old and the page is just out of date. However, my own quest to get sway working took me through so much confusion that I'm not sure which steps were actually necessary for me, so I don't know for certain what to replace it with. I suspect what setup-udev did was start all of the udev services (udev, udev-postmount, udev-settle, and udev-trigger).

Hello. The package '''eudev''', which should be installed by the very first command in the page, provides /sbin/setup-udev. [[User:La9|La9]] ([[User talk:La9|talk]]) 06:09, 27 July 2022 (UTC)

: Alternatively you can try '''setup-devd udev''', this will auto install packages for you. [[User:La9|La9]] ([[User talk:La9|talk]]) 06:12, 27 July 2022 (UTC)

Talk:Sway

2022-07-27T06:09:49Z

La9: re

Elogind

2022-07-24T11:06:49Z

La9: configure display manager

'''elogind''' is a login manager and provides support for

* setting up necessary permissions for the desktop environment or window manager
* handling poweroff, reboot, suspend and hibernate via '''loginctl''' command

== Installation ==

<pre>
# apk add elogind polkit-elogind
# rc-update add elogind
# rc-service elogind start
</pre>

== Configuration ==

=== logind.conf ===

Edit <code>/etc/elogind/logind.conf</code> to configure handling of power events, such as suspending the computer when power button is pressed:

<pre>
sed -i 's|#HandlePowerKey=poweroff|HandlePowerKey=suspend|' /etc/elogind/logind.conf
</pre>

=== Working with Desktop Environments ===

If using a Window Manager or Desktop Environment, such as [[Sway]], the user must ensure that login session is correctly configured. When correctly configured, loginctl command should output the following:

<pre>
# using sway and sddm
localhost:~$ loginctl
SESSION UID USER SEAT TTY
c1 105 sddm seat0
c2 1000 User seat0 tty8

2 sessions listed.
</pre>

If the output is <code>No session available.</code>, such as in the case of launching Sway from tty, suspend and many other functionality will not work. The user then must configure a display manager such as greetd, sddm or lightdm.

Sway

2022-07-23T15:45:47Z

La9: dbus

[http://swaywm.org Sway] is a tiling [[Wayland]] compositor. It's a drop-in replacement for the i3 window manager.

== Installation ==

eudev:

<pre>
# apk add eudev
# setup-udev
</pre>

Graphics drivers:

* [[Intel Video]]
* [[Radeon Video]]
* [[Nvidia Video]]
Add user to the input and video groups:

<pre>
# adduser $USER input
# adduser $USER video
</pre>

Install some TTF fonts:

<pre>
# apk add ttf-dejavu
</pre>

seatd daemon:

<pre>
# apk add seatd
# rc-update add seatd
# rc-service seatd start
# adduser $USER seat
</pre>

[[elogind]], optional for suspend on lid close support.

Install sway:

<pre>
# apk add sway sway-doc
# apk add \ # Install optional dependencies:
xwayland \ # recommended for compatibility reasons
foot \ # default terminal emulator
bemenu \ # wayland menu
swaylock swaylockd \ # lockscreen tool
swaybg \ # wallpaper daemon
swayidle # idle management (DPMS) daemon
</pre>

Configure XDG_RUNTIME_DIR. Add the following to shell init scripts, for the default ash shell it is ~/.profile:

<pre>
if test -z "${XDG_RUNTIME_DIR}"; then
export XDG_RUNTIME_DIR=/tmp/$(id -u)-runtime-dir
if ! test -d "${XDG_RUNTIME_DIR}"; then
mkdir "${XDG_RUNTIME_DIR}"
chmod 0700 "${XDG_RUNTIME_DIR}"
fi
fi
</pre>

For inter-program communication and functionality such as screensharing, install and enable dbus and PipeWire, see [[PipeWire]].

Re-login or reboot to allow above modifications to take effect.

Launch Sway with dbus support:

<pre>
dbus-launch --exit-with-session sway
</pre>

== Configuration ==

An example config is provided at <code>/etc/sway/config</code>. Copy it to <code>~/.config/sway/config</code> and read through it to learn the default keybindings.

For additional information, start at <code>man 5 sway</code> and read the [https://github.com/swaywm/sway/wiki upstream wiki].

=== Firefox screensharing ===

For some programs, additional configuration is needed to launch them natively under Wayland and to support special features such as screen sharing.

To launch Firefox natively under Wayland and to enable support for screensharing, you need:

* Install and configure [[PipeWire]]
* Install xdg-desktop-portal and xdg-desktop-portal-wlr package
* Install wofi for screen selection
* Launch support programs on sway startup:
<pre>
exec pipewire #pipewire must be launched first
exec /usr/libexec/xdg-desktop-portal-wlr
</pre>
* Export the following variables:

<pre>
export MOZ_ENABLE_WAYLAND="1"
export XDG_CURRENT_DESKTOP=sway
export XDG_SESSION_TYPE=wayland
export QT_QPA_PLATFORM="wayland-egl"
</pre>

=== Scaling for high resolution screens ===

Without further configuration, program interfaces might be too small to use on high resolution screens.

==== Via sway ====

Sway supports the per-display configuration of

* fractional (e.g., 1.5x), and
* integer scaling (e.g., 2x)

However, fractional scaling is discouraged due to both the performance impact and the blurry output it produces. In this case, where 1x scaling is too small and 2x scaling is too large, program-specific GTK/QT based scaling is recommended. See below.

To enable Sway scaling, the user can first preview different scaling factors with <code>wdisplays</code> package. Note the output name (eDP-1, LVDS-1) and try apply scaling factors such as 1 and 2. To make changes permanent, add

<pre>
output <name> scale <factor>
</pre>

to ~/.config/sway/config.

==== Via GTK/Qt ====

<pre>
# for GTK-based programs such as firefox and emacs:
export GDK_DPI_SCALE=2

# for QT-based programs
export QT_WAYLAND_FORCE_DPI="physical"
# or if still too small, use a custom DPI
export QT_WAYLAND_FORCE_DPI=192 # 2x scaling
export QT_QPA_PLATFORM="wayland-egl"
</pre>

=== Make clipboard content persistent ===
By default the clipboard content does not persist after terminating the program: you copy some text from Firefox and then exit Firefox, the copied text is also lost.

Install clipman from test repo and add the following to sway config:

<pre>
exec wl-paste --type text/plain --watch clipman store --histpath="~/.local/state/clipman-primary.json"
bindsym $mod+h exec clipman pick --tool wofi --histpath="~/.local/state/clipman-primary.json"
</pre>

[[Category:Desktop]]

Sway

2022-07-22T06:31:01Z

La9: preview

[http://swaywm.org Sway] is a tiling [[Wayland]] compositor. It's a drop-in replacement for the i3 window manager.

== Installation ==

eudev:

<pre>
# apk add eudev
# setup-udev
</pre>

Graphics drivers:

* [[Intel Video]]
* [[Radeon Video]]
* [[Nvidia Video]]
Add user to the input and video groups:

<pre>
# adduser $USER input
# adduser $USER video
</pre>

Install some TTF fonts:

<pre>
# apk add ttf-dejavu
</pre>

seatd daemon:

<pre>
# apk add seatd
# rc-update add seatd
# rc-service seatd start
# adduser $USER seat
</pre>

[[elogind]], optional for suspend on lid close support.

Install sway:

<pre>
# apk add sway sway-doc
# apk add \ # Install optional dependencies:
xwayland \ # recommended for compatibility reasons
foot \ # default terminal emulator
bemenu \ # wayland menu
swaylock swaylockd \ # lockscreen tool
swaybg \ # wallpaper daemon
swayidle # idle management (DPMS) daemon
</pre>

Configure XDG_RUNTIME_DIR. Add the following to shell init scripts, for the default ash shell it is ~/.profile:

<pre>
if test -z "${XDG_RUNTIME_DIR}"; then
export XDG_RUNTIME_DIR=/tmp/$(id -u)-runtime-dir
if ! test -d "${XDG_RUNTIME_DIR}"; then
mkdir "${XDG_RUNTIME_DIR}"
chmod 0700 "${XDG_RUNTIME_DIR}"
fi
fi
</pre>

Re-login or reboot to allow above modifications to take effect.

Launch Sway with dbus support:

<pre>
dbus-launch --exit-with-session sway
</pre>

== Configuration ==

An example config is provided at <code>/etc/sway/config</code>. Copy it to <code>~/.config/sway/config</code> and read through it to learn the default keybindings.

For additional information, start at <code>man 5 sway</code> and read the [https://github.com/swaywm/sway/wiki upstream wiki].

=== Launching program under Wayland ===

For some programs, additional configuration is needed to launch them natively under Wayland and to support special features such as screen sharing.

To launch Firefox natively under Wayland and to enable support for screensharing, you need:

* Install and configure [[PipeWire]]
* Install xdg-desktop-portal and xdg-desktop-portal-wlr package
* Install wofi for screen selection
* Launch support programs on sway startup: Add <code>exec pipewire</code> and <code>/usr/libexec/xdg-desktop-portal-wlr</code> to ~/.config/sway/config
* Export the following variables:

<pre>
export MOZ_ENABLE_WAYLAND="1"
export XDG_CURRENT_DESKTOP=sway
export XDG_SESSION_TYPE=wayland
export QT_QPA_PLATFORM="wayland-egl"
</pre>

=== Scaling for high resolution screens ===

Without further configuration, program interfaces might be too small to use on high resolution screens.

==== Via sway ====

Sway supports the per-display configuration of

* fractional (e.g., 1.5x), and
* integer scaling (e.g., 2x)

However, fractional scaling is discouraged due to both the performance impact and the blurry output it produces. In this case, where 1x scaling is too small and 2x scaling is too large, program-specific GTK/QT based scaling is recommended. See below.

To enable Sway scaling, the user can first preview different scaling factors with <code>wdisplays</code> package. Note the output name (eDP-1, LVDS-1) and try apply scaling factors such as 1 and 2. To make changes permanent, add

<pre>
output <name> scale <factor>
</pre>

to ~/.config/sway/config.

==== Via GTK/Qt ====

<pre>
# for GTK-based programs such as firefox and emacs:
export GDK_DPI_SCALE=2

# for QT-based programs
export QT_WAYLAND_FORCE_DPI="physical"
# or if still too small, use a custom DPI
export QT_WAYLAND_FORCE_DPI=192 # 2x scaling
export QT_QPA_PLATFORM="wayland-egl"
</pre>

=== Make clipboard content persistent ===
By default the clipboard content does not persist after terminating the program: you copy some text from Firefox and then exit Firefox, the copied text is also lost.

Install clipman from test repo and add the following to sway config:

<pre>
exec wl-paste --type text/plain --watch clipman store --histpath="~/.local/state/clipman-primary.json"
bindsym $mod+h exec clipman pick --tool wofi --histpath="~/.local/state/clipman-primary.json"
</pre>

[[Category:Desktop]]

Sway

2022-07-22T06:28:37Z

La9: relogin to take effect

[http://swaywm.org Sway] is a tiling [[Wayland]] compositor. It's a drop-in replacement for the i3 window manager.

== Installation ==

eudev:

<pre>
# apk add eudev
# setup-udev
</pre>

Graphics drivers:

* [[Intel Video]]
* [[Radeon Video]]
* [[Nvidia Video]]
Add user to the input and video groups:

<pre>
# adduser $USER input
# adduser $USER video
</pre>

Install some TTF fonts:

<pre>
# apk add ttf-dejavu
</pre>

seatd daemon:

<pre>
# apk add seatd
# rc-update add seatd
# rc-service seatd start
# adduser $USER seat
</pre>

[[elogind]], optional for suspend on lid close support.

Install sway:

<pre>
# apk add sway sway-doc
# apk add \ # Install optional dependencies:
xwayland \ # recommended for compatibility reasons
foot \ # default terminal emulator
bemenu \ # wayland menu
swaylock swaylockd \ # lockscreen tool
swaybg \ # wallpaper daemon
swayidle # idle management (DPMS) daemon
</pre>

Configure XDG_RUNTIME_DIR. Add the following to shell init scripts, for the default ash shell it is ~/.profile:

<pre>
if test -z "${XDG_RUNTIME_DIR}"; then
export XDG_RUNTIME_DIR=/tmp/$(id -u)-runtime-dir
if ! test -d "${XDG_RUNTIME_DIR}"; then
mkdir "${XDG_RUNTIME_DIR}"
chmod 0700 "${XDG_RUNTIME_DIR}"
fi
fi
</pre>

Re-login or reboot to allow above modifications to take effect.

Launch Sway with dbus support:

<pre>
dbus-launch --exit-with-session sway
</pre>

== Configuration ==

An example config is provided at <code>/etc/sway/config</code>. Copy it to <code>~/.config/sway/config</code> and read through it to learn the default keybindings.

For additional information, start at <code>man 5 sway</code> and read the [https://github.com/swaywm/sway/wiki upstream wiki].

=== Launching program under Wayland ===

For some programs, additional configuration is needed to launch them natively under Wayland and to support special features such as screen sharing.

To launch Firefox natively under Wayland and to enable support for screensharing, you need:

* Install and configure [[PipeWire]]
* Install xdg-desktop-portal and xdg-desktop-portal-wlr package
* Install wofi for screen selection
* Launch support programs on sway startup: Add <code>exec pipewire</code> and <code>/usr/libexec/xdg-desktop-portal-wlr</code> to ~/.config/sway/config
* Export the following variables:

<pre>
export MOZ_ENABLE_WAYLAND="1"
export XDG_CURRENT_DESKTOP=sway
export XDG_SESSION_TYPE=wayland
export QT_QPA_PLATFORM="wayland-egl"
</pre>

=== Scaling for high resolution screens ===

Without further configuration, program interfaces might be too small to use on high resolution screens.

==== Via sway ====

Sway supports the per-display configuration of

* fractional (e.g., 1.5x), and
* integer scaling (e.g., 2x)

However, fractional scaling is discouraged due to both the performance impact and the blurry output it produces. In this case, where 1x scaling is too small and 2x scaling is too large, program-specific GTK/QT based scaling is recommended. See below.

To enable Sway scaling, the user can first try out different scaling factors with <code>wdisplays</code> package. Note the output name (eDP-1, LVDS-1) and try apply scaling factors such as 1 and 2. To make changes permanent, add

<pre>
output <name> scale <factor>
</pre>

to ~/.config/sway/config.

==== Via GTK/Qt ====

<pre>
# for GTK-based programs such as firefox and emacs:
export GDK_DPI_SCALE=2

# for QT-based programs
export QT_WAYLAND_FORCE_DPI="physical"
# or if still too small, use a custom DPI
export QT_WAYLAND_FORCE_DPI=192 # 2x scaling
export QT_QPA_PLATFORM="wayland-egl"
</pre>

=== Make clipboard content persistent ===
By default the clipboard content does not persist after terminating the program: you copy some text from Firefox and then exit Firefox, the copied text is also lost.

Install clipman from test repo and add the following to sway config:

<pre>
exec wl-paste --type text/plain --watch clipman store --histpath="~/.local/state/clipman-primary.json"
bindsym $mod+h exec clipman pick --tool wofi --histpath="~/.local/state/clipman-primary.json"
</pre>

[[Category:Desktop]]

Sway

2022-07-22T05:36:47Z

La9: qt qpa platform

[http://swaywm.org Sway] is a tiling [[Wayland]] compositor. It's a drop-in replacement for the i3 window manager.

== Installation ==

eudev:

<pre>
# apk add eudev
# setup-udev
</pre>

Graphics drivers:

* [[Intel Video]]
* [[Radeon Video]]
* [[Nvidia Video]]
Add user to the input and video groups:

<pre>
# adduser $USER input
# adduser $USER video
</pre>

Install some TTF fonts:

<pre>
# apk add ttf-dejavu
</pre>

seatd daemon:

<pre>
# apk add seatd
# rc-update add seatd
# rc-service seatd start
# adduser $USER seat
</pre>

[[elogind]], optional for suspend on lid close support.

Install sway:

<pre>
# apk add sway sway-doc
# apk add \ # Install optional dependencies:
xwayland \ # recommended for compatibility reasons
foot \ # default terminal emulator
wofi \ # wayland menu for application selection and screensharing
swaylock swaylockd \ # lockscreen tool
swaybg \ # wallpaper daemon
swayidle # idle management (DPMS) daemon
</pre>

Configure XDG_RUNTIME_DIR. Add the following to shell init scripts, for the default ash shell it is ~/.profile:

<pre>
if test -z "${XDG_RUNTIME_DIR}"; then
export XDG_RUNTIME_DIR=/tmp/$(id -u)-runtime-dir
if ! test -d "${XDG_RUNTIME_DIR}"; then
mkdir "${XDG_RUNTIME_DIR}"
chmod 0700 "${XDG_RUNTIME_DIR}"
fi
fi
</pre>

Launch Sway with dbus support:

<pre>
dbus-launch --exit-with-session sway
</pre>

== Configuration ==

An example config is provided at <code>/etc/sway/config</code>. Copy it to <code>~/.config/sway/config</code> and read through it to learn the default keybindings.

For additional information, start at <code>man 5 sway</code> and read the [https://github.com/swaywm/sway/wiki upstream wiki].

=== Launching program under Wayland ===

For some programs, additional configuration is needed to launch them natively under Wayland and to support special features such as screen sharing.

To launch Firefox natively under Wayland and to enable support for screensharing, you need:

* Install and configure [[PipeWire]]
* Install xdg-desktop-portal and xdg-desktop-portal-wlr package
* Install wofi for screen selection
* Launch support programs on sway startup: Add <code>exec pipewire</code> and <code>/usr/libexec/xdg-desktop-portal-wlr</code> to ~/.config/sway/config
* Export the following variables:

<pre>
export MOZ_ENABLE_WAYLAND="1"
export XDG_CURRENT_DESKTOP=sway
export XDG_SESSION_TYPE=wayland
export QT_QPA_PLATFORM="wayland-egl"
</pre>

=== Scaling for high resolution screens ===

Without further configuration, program interfaces might be too small to use on high resolution screens.

==== Via sway ====

Sway supports the per-display configuration of

* fractional (e.g., 1.5x), and
* integer scaling (e.g., 2x)

However, fractional scaling is discouraged due to both the performance impact and the blurry output it produces. In this case, where 1x scaling is too small and 2x scaling is too large, program-specific GTK/QT based scaling is recommended. See below.

To enable Sway scaling, the user can first try out different scaling factors with <code>wdisplays</code> package. Note the output name (eDP-1, LVDS-1) and try apply scaling factors such as 1 and 2. To make changes permanent, add

<pre>
output <name> scale <factor>
</pre>

to ~/.config/sway/config.

==== Via GTK/Qt ====

<pre>
# for GTK-based programs such as firefox and emacs:
export GDK_DPI_SCALE=2

# for QT-based programs
export QT_WAYLAND_FORCE_DPI="physical"
# or if still too small, use a custom DPI
export QT_WAYLAND_FORCE_DPI=192 # 2x scaling
export QT_QPA_PLATFORM="wayland-egl"
</pre>

=== Make clipboard content persistent ===
By default the clipboard content does not persist after terminating the program: you copy some text from Firefox and then exit Firefox, the copied text is also lost.

Install clipman from test repo and add the following to sway config:

<pre>
exec wl-paste --type text/plain --watch clipman store --histpath="~/.local/state/clipman-primary.json"
bindsym $mod+h exec clipman pick --tool wofi --histpath="~/.local/state/clipman-primary.json"
</pre>

[[Category:Desktop]]

Sway

2022-07-22T05:35:04Z

La9: remove spurious whitespace

[http://swaywm.org Sway] is a tiling [[Wayland]] compositor. It's a drop-in replacement for the i3 window manager.

== Installation ==

eudev:

<pre>
# apk add eudev
# setup-udev
</pre>

Graphics drivers:

* [[Intel Video]]
* [[Radeon Video]]
* [[Nvidia Video]]
Add user to the input and video groups:

<pre>
# adduser $USER input
# adduser $USER video
</pre>

Install some TTF fonts:

<pre>
# apk add ttf-dejavu
</pre>

seatd daemon:

<pre>
# apk add seatd
# rc-update add seatd
# rc-service seatd start
# adduser $USER seat
</pre>

[[elogind]], optional for suspend on lid close support.

Install sway:

<pre>
# apk add sway sway-doc
# apk add \ # Install optional dependencies:
xwayland \ # recommended for compatibility reasons
foot \ # default terminal emulator
wofi \ # wayland menu for application selection and screensharing
swaylock swaylockd \ # lockscreen tool
swaybg \ # wallpaper daemon
swayidle # idle management (DPMS) daemon
</pre>

Configure XDG_RUNTIME_DIR. Add the following to shell init scripts, for the default ash shell it is ~/.profile:

<pre>
if test -z "${XDG_RUNTIME_DIR}"; then
export XDG_RUNTIME_DIR=/tmp/$(id -u)-runtime-dir
if ! test -d "${XDG_RUNTIME_DIR}"; then
mkdir "${XDG_RUNTIME_DIR}"
chmod 0700 "${XDG_RUNTIME_DIR}"
fi
fi
</pre>

Launch Sway with dbus support:

<pre>
dbus-launch --exit-with-session sway
</pre>

== Configuration ==

An example config is provided at <code>/etc/sway/config</code>. Copy it to <code>~/.config/sway/config</code> and read through it to learn the default keybindings.

For additional information, start at <code>man 5 sway</code> and read the [https://github.com/swaywm/sway/wiki upstream wiki].

=== Launching program under Wayland ===

For some programs, additional configuration is needed to launch them natively under Wayland and to support special features such as screen sharing.

To launch Firefox natively under Wayland and to enable support for screensharing, you need:

* Install and configure [[PipeWire]]
* Install xdg-desktop-portal and xdg-desktop-portal-wlr package
* Install wofi for screen selection
* Launch support programs on sway startup: Add <code>exec pipewire</code> and <code>/usr/libexec/xdg-desktop-portal-wlr</code> to ~/.config/sway/config
* Export the following variables:

<pre>
export MOZ_ENABLE_WAYLAND="1"
export XDG_CURRENT_DESKTOP=sway
export XDG_SESSION_TYPE=wayland
</pre>

=== Scaling for high resolution screens ===

Without further configuration, program interfaces might be too small to use on high resolution screens.

==== Via sway ====

Sway supports the per-display configuration of

* fractional (e.g., 1.5x), and
* integer scaling (e.g., 2x)

However, fractional scaling is discouraged due to both the performance impact and the blurry output it produces. In this case, where 1x scaling is too small and 2x scaling is too large, program-specific GTK/QT based scaling is recommended. See below.

To enable Sway scaling, the user can first try out different scaling factors with <code>wdisplays</code> package. Note the output name (eDP-1, LVDS-1) and try apply scaling factors such as 1 and 2. To make changes permanent, add

<pre>
output <name> scale <factor>
</pre>

to ~/.config/sway/config.

==== Via GTK/Qt ====

<pre>
# for GTK-based programs such as firefox and emacs:
export GDK_DPI_SCALE=2

# for QT-based programs
export QT_WAYLAND_FORCE_DPI="physical"
# or if still too small, use a custom DPI
export QT_WAYLAND_FORCE_DPI=192 # 2x scaling
export QT_QPA_PLATFORM="wayland-egl"
</pre>

=== Make clipboard content persistent ===
By default the clipboard content does not persist after terminating the program: you copy some text from Firefox and then exit Firefox, the copied text is also lost.

Install clipman from test repo and add the following to sway config:

<pre>
exec wl-paste --type text/plain --watch clipman store --histpath="~/.local/state/clipman-primary.json"
bindsym $mod+h exec clipman pick --tool wofi --histpath="~/.local/state/clipman-primary.json"
</pre>

[[Category:Desktop]]

NVIDIA

2022-07-22T05:24:46Z

La9: nouveau

== Nouveau ==
'''Nouveau''' is the open-source driver for NVIDIA GPUs.

=== Wayland ===

Install the following packages as needed:

* <code>mesa-dri-gallium</code>: '''necessary''' Mesa drivers.
* <code>mesa-va-gallium</code>: 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=nouveau</code>

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

== Proprietary Driver ==

Sway

2022-07-22T05:21:06Z

La9: Nvidia Video

[http://swaywm.org Sway] is a tiling [[Wayland]] compositor. It's a drop-in replacement for the i3 window manager.

== Installation ==

eudev:

<pre>
# apk add eudev
# setup-udev
</pre>

Graphics drivers:

* [[Intel Video]]
* [[Radeon Video]]
* [[Nvidia Video]]
Add user to the input and video groups:

<pre>
# adduser $USER input
# adduser $USER video
</pre>

Install some TTF fonts:

<pre>
# apk add ttf-dejavu
</pre>

seatd daemon:

<pre>
# apk add seatd
# rc-update add seatd
# rc-service seatd start
# adduser $USER seat
</pre>

[[elogind]], optional for suspend on lid close support.

Install sway:

<pre>
# apk add sway sway-doc
# apk add \ # Install optional dependencies:
xwayland \ # recommended for compatibility reasons
foot \ # default terminal emulator
wofi \ # wayland menu for application selection and screensharing
swaylock swaylockd \ # lockscreen tool
swaybg \ # wallpaper daemon
swayidle # idle management (DPMS) daemon
</pre>

Configure XDG_RUNTIME_DIR. Add the following to shell init scripts, for the default ash shell it is ~/.profile:

<pre>
if test -z "${XDG_RUNTIME_DIR}"; then
export XDG_RUNTIME_DIR=/tmp/$(id -u)-runtime-dir
if ! test -d "${XDG_RUNTIME_DIR}"; then
mkdir "${XDG_RUNTIME_DIR}"
chmod 0700 "${XDG_RUNTIME_DIR}"
fi
fi
</pre>

Launch Sway with dbus support:

<pre>
dbus-launch --exit-with-session sway
</pre>

== Configuration ==

An example config is provided at <code>/etc/sway/config</code>. Copy it to <code>~/.config/sway/config</code> and read through it to learn the default keybindings.

For additional information, start at <code>man 5 sway</code> and read the [https://github.com/swaywm/sway/wiki upstream wiki].

=== Launching program under Wayland ===

For some programs, additional configuration is needed to launch them natively under Wayland and to support special features such as screen sharing.

To launch Firefox natively under Wayland and to enable support for screensharing, you need:

* Install and configure [[PipeWire]]
* Install xdg-desktop-portal and xdg-desktop-portal-wlr package
* Install wofi for screen selection
* Launch support programs on sway startup: Add <code>exec pipewire</code> and <code>/usr/libexec/xdg-desktop-portal-wlr</code> to ~/.config/sway/config
* Export the following variables:

<pre>
export MOZ_ENABLE_WAYLAND="1"
export XDG_CURRENT_DESKTOP=sway
export XDG_SESSION_TYPE=wayland
</pre>

=== Scaling for high resolution screens ===

Without further configuration, program interfaces might be too small to use on high resolution screens.

==== Via sway ====

Sway supports the per-display configuration of

* fractional (e.g., 1.5x), and
* integer scaling (e.g., 2x)

However, fractional scaling is discouraged due to both the performance impact and the blurry output it produces. In this case, where 1x scaling is too small and 2x scaling is too large, program-specific GTK/QT based scaling is recommended. See below.

To enable Sway scaling, the user can first try out different scaling factors with <code>wdisplays</code> package. Note the output name (eDP-1, LVDS-1) and try apply scaling factors such as 1 and 2. To make changes permanent, add

<pre>
output <name> scale <factor>
</pre>

to ~/.config/sway/config.

==== Via GTK/Qt ====

<pre>
# for GTK-based programs such as firefox and emacs:
export GDK_DPI_SCALE=2

# for QT-based programs
export QT_WAYLAND_FORCE_DPI="physical"
# or if still too small, use a custom DPI
export QT_WAYLAND_FORCE_DPI=192 # 2x scaling
export QT_QPA_PLATFORM="wayland-egl"
</pre>

=== Make clipboard content persistent ===
By default the clipboard content does not persist after terminating the program: you copy some text from Firefox and then exit Firefox, the copied text is also lost.

Install clipman from test repo and add the following to sway config:

<pre>
exec wl-paste --type text/plain --watch clipman store --histpath="~/.local/state/clipman-primary.json"
bindsym $mod+h exec clipman pick --tool wofi --histpath="~/.local/state/clipman-primary.json"
</pre>

[[Category:Desktop]]

Radeon Video

2022-07-22T05:19:52Z

La9: wayland update

== Wayland ==

Install the following packages as needed:

* <code>mesa-dri-gallium</code>: '''necessary''' Mesa drivers.
* <code>mesa-va-gallium</code>: 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 ==

Install either the Free Software driver <code>xf86-video-ati</code> or the proprietary amdgpu firmware <code>linux-firmware-amdgpu</code>.

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

[[Category:Drivers]]

Radeon Video

2022-07-22T05:18:50Z

La9: wayland update

{{TOC right}}

== Wayland ==

Install the following packages as needed:

* <code>mesa-dri-gallium</code>: '''necessary''' Mesa drivers.
* <code>mesa-va-gallium</code>: 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 ==

Install either the Free Software driver <code>xf86-video-ati</code> or the proprietary amdgpu firmware <code>linux-firmware-amdgpu</code>.

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

[[Category:Drivers]]

Sway

2022-07-22T04:55:27Z

La9: hidpi

[http://swaywm.org Sway] is a tiling [[Wayland]] compositor. It's a drop-in replacement for the i3 window manager.

== Installation ==

eudev:

<pre>
# apk add eudev
# setup-udev
</pre>

Graphics drivers:

* [[Intel Video]]
* [[Radeon Video]]

Add user to the input and video groups:

<pre>
# adduser $USER input
# adduser $USER video
</pre>

Install some TTF fonts:

<pre>
# apk add ttf-dejavu
</pre>

seatd daemon:

<pre>
# apk add seatd
# rc-update add seatd
# rc-service seatd start
# adduser $USER seat
</pre>

[[elogind]], optional for suspend on lid close support.

Install sway:

<pre>
# apk add sway sway-doc
# apk add \ # Install optional dependencies:
xwayland \ # recommended for compatibility reasons
foot \ # default terminal emulator
wofi \ # wayland menu for application selection and screensharing
swaylock swaylockd \ # lockscreen tool
swaybg \ # wallpaper daemon
swayidle # idle management (DPMS) daemon
</pre>

Configure XDG_RUNTIME_DIR. Add the following to shell init scripts, for the default ash shell it is ~/.profile:

<pre>
if test -z "${XDG_RUNTIME_DIR}"; then
export XDG_RUNTIME_DIR=/tmp/$(id -u)-runtime-dir
if ! test -d "${XDG_RUNTIME_DIR}"; then
mkdir "${XDG_RUNTIME_DIR}"
chmod 0700 "${XDG_RUNTIME_DIR}"
fi
fi
</pre>

Launch Sway with dbus support:

<pre>
dbus-launch --exit-with-session sway
</pre>

== Configuration ==

An example config is provided at <code>/etc/sway/config</code>. Copy it to <code>~/.config/sway/config</code> and read through it to learn the default keybindings.

For additional information, start at <code>man 5 sway</code> and read the [https://github.com/swaywm/sway/wiki upstream wiki].

=== Launching program under Wayland ===

For some programs, additional configuration is needed to launch them natively under Wayland and to support special features such as screen sharing.

To launch Firefox natively under Wayland and to enable support for screensharing, you need:

* Install and configure [[PipeWire]]
* Install xdg-desktop-portal and xdg-desktop-portal-wlr package
* Install wofi for screen selection
* Launch support programs on sway startup: Add <code>exec pipewire</code> and <code>/usr/libexec/xdg-desktop-portal-wlr</code> to ~/.config/sway/config
* Export the following variables:

<pre>
export MOZ_ENABLE_WAYLAND="1"
export XDG_CURRENT_DESKTOP=sway
export XDG_SESSION_TYPE=wayland
</pre>

=== Scaling for high resolution screens ===

Without further configuration, program interfaces might be too small to use on high resolution screens.

==== Via sway ====

Sway supports the per-display configuration of

* fractional (e.g., 1.5x), and
* integer scaling (e.g., 2x)

However, fractional scaling is discouraged due to both the performance impact and the blurry output it produces. In this case, where 1x scaling is too small and 2x scaling is too large, program-specific GTK/QT based scaling is recommended. See below.

To enable Sway scaling, the user can first try out different scaling factors with <code>wdisplays</code> package. Note the output name (eDP-1, LVDS-1) and try apply scaling factors such as 1 and 2. To make changes permanent, add

<pre>
output <name> scale <factor>
</pre>

to ~/.config/sway/config.

==== Via GTK/Qt ====

<pre>
# for GTK-based programs such as firefox and emacs:
export GDK_DPI_SCALE=2

# for QT-based programs
export QT_WAYLAND_FORCE_DPI="physical"
# or if still too small, use a custom DPI
export QT_WAYLAND_FORCE_DPI=192 # 2x scaling
export QT_QPA_PLATFORM="wayland-egl"
</pre>

=== Make clipboard content persistent ===
By default the clipboard content does not persist after terminating the program: you copy some text from Firefox and then exit Firefox, the copied text is also lost.

Install clipman from test repo and add the following to sway config:

<pre>
exec wl-paste --type text/plain --watch clipman store --histpath="~/.local/state/clipman-primary.json"
bindsym $mod+h exec clipman pick --tool wofi --histpath="~/.local/state/clipman-primary.json"
</pre>

[[Category:Desktop]]

Sway

2022-07-21T17:30:09Z

La9: custom dpi for qt applications

[http://swaywm.org Sway] is a tiling [[Wayland]] compositor. It's a drop-in replacement for the i3 window manager.

== Installation ==

eudev:

<pre>
# apk add eudev
# setup-udev
</pre>

Graphics drivers:

* [[Intel Video]]
* [[Radeon Video]]

Add user to the input and video groups:

<pre>
# adduser $USER input
# adduser $USER video
</pre>

Install some TTF fonts:

<pre>
# apk add ttf-dejavu
</pre>

seatd daemon:

<pre>
# apk add seatd
# rc-update add seatd
# rc-service seatd start
# adduser $USER seat
</pre>

[[elogind]], optional for suspend on lid close support.

Install sway:

<pre>
# apk add sway sway-doc
# apk add \ # Install optional dependencies:
xwayland \ # recommended for compatibility reasons
foot \ # default terminal emulator
wofi \ # wayland menu for application selection and screensharing
swaylock swaylockd \ # lockscreen tool
swaybg \ # wallpaper daemon
swayidle # idle management (DPMS) daemon
</pre>

Configure XDG_RUNTIME_DIR. Add the following to shell init scripts, for the default ash shell it is ~/.profile:

<pre>
if test -z "${XDG_RUNTIME_DIR}"; then
export XDG_RUNTIME_DIR=/tmp/$(id -u)-runtime-dir
if ! test -d "${XDG_RUNTIME_DIR}"; then
mkdir "${XDG_RUNTIME_DIR}"
chmod 0700 "${XDG_RUNTIME_DIR}"
fi
fi
</pre>

Launch Sway with dbus support:

<pre>
dbus-launch --exit-with-session sway
</pre>

== Launching program under Wayland ==

For some programs, additional configuration is needed to launch them natively under Wayland and to support special features such as screen sharing.

To launch Firefox natively under Wayland and to enable support for screensharing, you need:

* Install and configure [[PipeWire]]
* Install xdg-desktop-portal and xdg-desktop-portal-wlr package
* Install wofi for screen selection
* Launch support programs on sway startup: Add <code>exec pipewire</code> and <code>/usr/libexec/xdg-desktop-portal-wlr</code> to ~/.config/sway/config
* Export the following variables:

<pre>
export MOZ_ENABLE_WAYLAND="1"
export XDG_CURRENT_DESKTOP=sway
export XDG_SESSION_TYPE=wayland
</pre>

== HiDPI ==

<pre>
# for GTK-based programs such as firefox and emacs:
export GDK_DPI_SCALE=2

# for QT-based programs
export QT_WAYLAND_FORCE_DPI="physical"
# or if still too small, use a custom DPI
export QT_WAYLAND_FORCE_DPI=192 # 2x scaling
export QT_QPA_PLATFORM="wayland-egl"
</pre>

== Configuration ==

An example config is provided at <code>/etc/sway/config</code>. Copy it to <code>~/.config/sway/config</code> and read through it to learn the default keybindings.

For additional information, start at <code>man 5 sway</code> and read the [https://github.com/swaywm/sway/wiki upstream wiki].

== Make clipboard content persistent ==
By default the clipboard content does not persist after terminating the program: you copy some text from Firefox and then exit Firefox, the copied text is also lost.

Install clipman from test repo and add the following to sway config:

<pre>
exec wl-paste --type text/plain --watch clipman store --histpath="~/.local/state/clipman-primary.json"
bindsym $mod+h exec clipman pick --tool wofi --histpath="~/.local/state/clipman-primary.json"
</pre>

[[Category:Desktop]]

Bluetooth audio

2022-07-21T16:13:15Z

La9: redirect to pipewire

== PulseAudio ==

Before you can connect your device to Bluetooth speakers or headphones, you'll have to make sure {{Pkg|pulseaudio-bluez}} is installed.

== PipeWire ==

See [[PipeWire]] page.

Sway

2022-07-21T16:12:00Z

La9: fix formatting

[http://swaywm.org Sway] is a tiling [[Wayland]] compositor. It's a drop-in replacement for the i3 window manager.

== Installation ==

eudev:

<pre>
# apk add eudev
# setup-udev
</pre>

Graphics drivers:

* [[Intel Video]]
* [[Radeon Video]]

Add user to the input and video groups:

<pre>
# adduser $USER input
# adduser $USER video
</pre>

Install some TTF fonts:

<pre>
# apk add ttf-dejavu
</pre>

seatd daemon:

<pre>
# apk add seatd
# rc-update add seatd
# rc-service seatd start
# adduser $USER seat
</pre>

[[elogind]], optional for suspend on lid close support.

Install sway:

<pre>
# apk add sway sway-doc
# apk add \ # Install optional dependencies:
xwayland \ # recommended for compatibility reasons
foot \ # default terminal emulator
wofi \ # wayland menu for application selection and screensharing
swaylock swaylockd \ # lockscreen tool
swaybg \ # wallpaper daemon
swayidle # idle management (DPMS) daemon
</pre>

Configure XDG_RUNTIME_DIR. Add the following to shell init scripts, for the default ash shell it is ~/.profile:

<pre>
if test -z "${XDG_RUNTIME_DIR}"; then
export XDG_RUNTIME_DIR=/tmp/$(id -u)-runtime-dir
if ! test -d "${XDG_RUNTIME_DIR}"; then
mkdir "${XDG_RUNTIME_DIR}"
chmod 0700 "${XDG_RUNTIME_DIR}"
fi
fi
</pre>

Launch Sway with dbus support:

<pre>
dbus-launch --exit-with-session sway
</pre>

== Launching program under Wayland ==

For some programs, additional configuration is needed to launch them natively under Wayland and to support special features such as screen sharing.

To launch Firefox natively under Wayland and to enable support for screensharing, you need:

* Install and configure [[PipeWire]]
* Install xdg-desktop-portal and xdg-desktop-portal-wlr package
* Install wofi for screen selection
* Launch support programs on sway startup: Add <code>exec pipewire</code> and <code>/usr/libexec/xdg-desktop-portal-wlr</code> to ~/.config/sway/config
* Export the following variables:

<pre>
export MOZ_ENABLE_WAYLAND="1"
export XDG_CURRENT_DESKTOP=sway
export XDG_SESSION_TYPE=wayland
</pre>

== HiDPI ==

<pre>
# for GTK-based programs such as firefox and emacs:
export GDK_DPI_SCALE=2

# for QT-based programs
export QT_WAYLAND_FORCE_DPI="physical"
export QT_QPA_PLATFORM="wayland-egl"
</pre>

== Configuration ==

An example config is provided at <code>/etc/sway/config</code>. Copy it to <code>~/.config/sway/config</code> and read through it to learn the default keybindings.

For additional information, start at <code>man 5 sway</code> and read the [https://github.com/swaywm/sway/wiki upstream wiki].

== Make clipboard content persistent ==
By default the clipboard content does not persist after terminating the program: you copy some text from Firefox and then exit Firefox, the copied text is also lost.

Install clipman from test repo and add the following to sway config:

<pre>
exec wl-paste --type text/plain --watch clipman store --histpath="~/.local/state/clipman-primary.json"
bindsym $mod+h exec clipman pick --tool wofi --histpath="~/.local/state/clipman-primary.json"
</pre>

[[Category:Desktop]]

Sway

2022-07-21T16:11:35Z

La9: persistent clipboard

[http://swaywm.org Sway] is a tiling [[Wayland]] compositor. It's a drop-in replacement for the i3 window manager.

== Installation ==

eudev:

<pre>
# apk add eudev
# setup-udev
</pre>

Graphics drivers:

* [[Intel Video]]
* [[Radeon Video]]

Add user to the input and video groups:

<pre>
# adduser $USER input
# adduser $USER video
</pre>

Install some TTF fonts:

<pre>
# apk add ttf-dejavu
</pre>

seatd daemon:

<pre>
# apk add seatd
# rc-update add seatd
# rc-service seatd start
# adduser $USER seat
</pre>

[[elogind]], optional for suspend on lid close support.

Install sway:

<pre>
# apk add sway sway-doc
# apk add \ # Install optional dependencies:
xwayland \ # recommended for compatibility reasons
foot \ # default terminal emulator
wofi \ # wayland menu for application selection and screensharing
swaylock swaylockd \ # lockscreen tool
swaybg \ # wallpaper daemon
swayidle # idle management (DPMS) daemon
</pre>

Configure XDG_RUNTIME_DIR. Add the following to shell init scripts, for the default ash shell it is ~/.profile:

<pre>
if test -z "${XDG_RUNTIME_DIR}"; then
export XDG_RUNTIME_DIR=/tmp/$(id -u)-runtime-dir
if ! test -d "${XDG_RUNTIME_DIR}"; then
mkdir "${XDG_RUNTIME_DIR}"
chmod 0700 "${XDG_RUNTIME_DIR}"
fi
fi
</pre>

Launch Sway with dbus support:

<pre>
dbus-launch --exit-with-session sway
</pre>

== Launching program under Wayland ==

For some programs, additional configuration is needed to launch them natively under Wayland and to support special features such as screen sharing.

To launch Firefox natively under Wayland and to enable support for screensharing, you need:

* Install and configure [[PipeWire]]
* Install xdg-desktop-portal and xdg-desktop-portal-wlr package
* Install wofi for screen selection
* Launch support programs on sway startup: Add <code>exec pipewire</code> and <code>/usr/libexec/xdg-desktop-portal-wlr</code> to ~/.config/sway/config
* Export the following variables:

<pre>
export MOZ_ENABLE_WAYLAND="1"
export XDG_CURRENT_DESKTOP=sway
export XDG_SESSION_TYPE=wayland
</pre>

== HiDPI ==

<pre>
# for GTK-based programs such as firefox and emacs:
export GDK_DPI_SCALE=2

# for QT-based programs
export QT_WAYLAND_FORCE_DPI="physical"
export QT_QPA_PLATFORM="wayland-egl"
</pre>

== Configuration ==

An example config is provided at <code>/etc/sway/config</code>. Copy it to <code>~/.config/sway/config</code> and read through it to learn the default keybindings.

For additional information, start at <code>man 5 sway</code> and read the [https://github.com/swaywm/sway/wiki upstream wiki].

== Make clipboard content persistent ==
By default the clipboard content does not persist after terminating the program: you copy some text from Firefox and then exit Firefox, the copied text is also lost.

Install clipman from test repo and add the following to sway config:

<code>
exec wl-paste --type text/plain --watch clipman store --histpath="~/.local/state/clipman-primary.json"
bindsym $mod+h exec clipman pick --tool wofi --histpath="~/.local/state/clipman-primary.json"
</code>

[[Category:Desktop]]

PipeWire

2022-07-21T16:07:41Z

La9: /* Installation and configuration */ bluetooth

{{Draft|The instructions below have not been thoroughly tested and may break things.}}

[https://pipewire.org/ PipeWire] is a multimedia processing engine that aims to improve audio and video handling on Linux.

== Prerequisites ==

=== Audio Group ===

When elogind is not available, the user has to be added to the <code>audio</code> group. The user must log in for this to take effect.

<pre>
# addgroup <user> audio
</pre>

=== D-Bus ===

PipeWire requires a running [https://www.freedesktop.org/wiki/Software/dbus/ D-Bus] session. If you use a full desktop environment this will probably be started automatically, but with minimal window managers it must be done manually.

<pre>
# apk add dbus dbus-openrc dbus-x11
# rc-service dbus start
# rc-update add dbus default
</pre>

Then use <code>dbus-launch</code> whenever you start an X or Wayland session. For example:
<pre>
$ dbus-launch --exit-with-session sway
</pre>

=== XDG_RUNTIME_DIR ===

If you are not using a Desktop Manager, ensure that your <code>XDG_RUNTIME_DIR</code> is set to a user-writable location. By default for pulseaudio this is {{Path|/run/user/1000/}} or {{Path|/tmp}}. If this is not set, pipewire will create a directory in your home folder instead, called <code>~/pulse</code>, and on attempting to run Pavucontrol or pactl, you will get the following error:

<pre>
$ pactl list
Connection failure: Connection refused
pa_context_connect() failed: Connection refused
</pre>

== Installation and configuration ==

<pre>
# apk add pipewire wireplumber
</pre>

{{Note|Using [https://gitlab.freedesktop.org/pipewire/wireplumber WirePlumber] rather than the pipewire-media-session (which comes with pipewire) is [https://gitlab.freedesktop.org/pipewire/media-session/-/blob/master/README.md recommended] but not required.}}

Create a custom configuration file in {{Path|/etc/pipewire/pipewire.conf}}:

<pre>
# mkdir /etc/pipewire
# cp /usr/share/pipewire/pipewire.conf /etc/pipewire/
</pre>

Replace pipewire-media-session with wireplumber:

<pre>
# sed -i 's|#*{ path = "/usr/bin/pipewire-media-session.*|{ path = "wireplumber" args = "" }|' /etc/pipewire/pipewire.conf
</pre>

Enable the <code>snd_seq</code> kernel module for ALSA support.

<pre>
# modprobe snd_seq
# echo snd_seq >> /etc/modules
</pre>

=== Realtime scheduling ===

For realtime scheduling, it is recommended to use rtkit,

<pre>
# apk add rtkit
</pre>

and then add your user to the `rtkit` group.

Alternatively, ensure your user has the right ulimit permissions. You generally need (limits.conf format):

<pre>
@audio - memlock 256
@audio - nice -11
@audio - rtprio 88
</pre>

This allows a member of the audio group to have the right permissions for PipeWire to use realtime scheduling without rtkit.

=== ALSA ===

<pre>
# apk add pipewire-alsa
</pre>

ALSA support works out of the box if you have the pipewire-alsa package

=== PulseAudio ===

PipeWire can run a [https://www.freedesktop.org/wiki/Software/PulseAudio/ PulseAudio] daemon which should allow all existing PulseAudio applications to be used with the PipeWire backend.

<pre>
# apk add pipewire-pulse
# sed -i 's|#*{ path = "/usr/bin/pipewire" args = "-c pipewire-pulse.conf" }|{ path = "/usr/bin/pipewire" args = "-c pipewire-pulse.conf" }|' /etc/pipewire/pipewire.conf
</pre>

=== JACK ===

If you will be using PipeWire for [https://jackaudio.org/ JACK] applications install the required package and make system wide links to the PipeWire replacement JACK libraries (I have not had success using <code>pw-jack</code>). You will not need to start a JACK server.

<pre>
# apk add pipewire-jack
# ln -sf /usr/lib/pipewire-0.3/jack/libjackserver.so.0 /usr/lib/libjackserver.so.0
# ln -sf /usr/lib/pipewire-0.3/jack/libjacknet.so.0 /usr/lib/libjacknet.so.0
# ln -sf /usr/lib/pipewire-0.3/jack/libjack.so.0 /usr/lib/libjack.so.0
</pre>

{{Note|These symlinks might be overwritten during updates.}}

=== Video ===

Video should work out-of-the-box with v4l2 devices (e.g. a lot of webcams) and [https://gstreamer.freedesktop.org/ GStreamer] applications.

=== Bluetooth audio ===

* Enable PulseAudio support as described above
* Install bluetooth service packages: <code>bluez bluez-openrc pipewire-spa-bluez</code>
* Optional: install GUI manager for bluetooth <code>blueman</code>
* Enable and start bluetooth service: <code>rc-update add bluetooth; rc-service bluetooth start</code>
* Restart PipeWire
* Use commandline program <code>bluetoothctl</code> or GUI program <code>blueman-manager</code> to scan and pair bluetooth audio devices.
* Use pavucontrol to adjust volume and manually select high definition bluetooth codecs.

=== Automatic bluetooth profile selection ===

To automatically switch between HSP/HFP and A2DP profiles when an input stream is detected, set the bluez5.autoswitch-profile property to true:
<pre>
/etc/pipewire/media-session.d/bluez-monitor.conf

...
rules = [
{
...
actions = {
update-props = {
...
bluez5.autoswitch-profile = true
...
</pre>

== Screen sharing on Wayland ==

You will need the right [https://github.com/flatpak/xdg-desktop-portal xdg-desktop-portal] backend for your desktop environment. Screen sharing is known to work on:
* GNOME with <code>xdg-desktop-portal-gtk</code>
* KDE Plasma with <code>xdg-desktop-portal-kde</code> and Firefox
* Sway with <code>xdg-desktop-portal-wlr</code> and Firefox, see [[Sway]] for details

== Usage ==

Start the PipeWire media server. You'll probably get quite a few errors but just ignore them for now.

<pre>
$ pipewire
</pre>

{{Note| PipeWire doesn't auto-start a session manager anymore.
In 3.14 and earlier, the PipeWire default config was edited in packaging to auto-start pipewire-media-session as the default session manager. Since we now have wireplumber available as an alternative session manager, this has been changed in favor of a launch wrapper for pipewire at /usr/libexec/pipewire-launcher. When executed, this will launch pipewire, pipewire-media-session or wireplumber, and pipewire-pulse, depending on what modules are available. If you were launching /usr/bin/pipewire and the session manager manually before, please use the new launcher wrapper instead. WirePlumber can now also be used as a proper alternative for pipewire-media-session.}}

In a different terminal window check the default output device. I don't yet know how this default can be changed for all applications, so you'd better hope it's right!

<pre>
# apk add pipewire-tools
$ pw-cat -p --list-targets
</pre>

{{Note| pw-cat doesn't have --list-targets option anymore.
The version of pipewire used in Alpine 3.16 and later has the --list-targets option removed. You should now use '''pw-cli list-objects''' or '''wpctl status''' (if you use wireplumber).}}

Test sound is working using an audio file in a format supported by [http://www.mega-nerd.com/libsndfile/ libsndfile] (e.g. flac, opus, ogg, wav).

<pre>
$ pw-cat -p test.flac
</pre>

If you have a microphone test audio recording is working.

<pre>
$ pw-cat -r --list-targets
$ pw-cat -r recording.flac
(Speak for a while then stop it with Ctrl+c)
$ pw-cat -p recording.flac
</pre>

Test PulseAudio clients using a media player (most use PulseAudio) and if you use JACK test that too:

<pre>
# apk add jack-example-clients
$ jack_simple_client
</pre>

You should hear a sustained beep.

If you are happy everything is working, make PipeWire start automatically when your X or Wayland session starts. For example, you could add the <code>pipewire</code> command to <code>~/.xinitrc</code> or your window manager's config file.

== Troubleshooting ==

=== `pw-cat -p --list-targets` shows no targets ===

First, check whether ALSA knows about your sound card:

<pre>
aplay -l
</pre>

If sound devices are found, the issue is with your pipewire configuration. Consider double-checking the instructions above.

Otherwise, your sound card may not be supported in the version of the Linux Kernel you're running. You should search online for fixes relating to your current kernel version and the codec of your sound card. You can find each of these with:

<pre>
uname -r
cat /proc/asound/card0/codec* | grep Codec
</pre>

== Quick Configuration ==

You might want to use pavucontrol to have a simple GUI app for controlling sound, outputs, etc, in which case:
<pre>
# apk add pavucontrol
</pre>

== See Also ==

* [https://gitlab.freedesktop.org/pipewire/pipewire PipeWire source repository]
* [https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/home PipeWire Wiki]
* [https://wiki.archlinux.org/index.php/PipeWire PipeWire on the ArchWiki]
* [https://wiki.gentoo.org/wiki/Pipewire PipeWire on the Gentoo Wiki]

[[Category:Desktop]]
[[Category:Multimedia]]
[[Category:Sound]]

Sway

2022-07-21T15:55:54Z

La9: firefox screensharing support, hidpi

Intel Video

2022-07-21T15:26:27Z

La9: mesa gallium and libva intel driver

Install the following packages as needed:

* <code>mesa-dri-gallium</code>: '''necessary''' Mesa drivers for all Intel Graphics
* <code>libva-intel-driver</code>: VAAPI drivers, for hardware accelerated video encoding and decoding

== Note ==

For all Intel Graphics up to Haswell, the user must manually select '''crocus''' Mesa driver in order to let the graphics work properly:

<pre>
export MESA_LOADER_DRIVER_OVERRIDE=crocus
</pre>

For newer Intel Graphics, if automatic driver selection does not work and bugs such as missing mouse cursor under [[Sway]] occur (no hardware graphics acceleration), the user can manually select '''iris''' driver:

<pre>
export MESA_LOADER_DRIVER_OVERRIDE=iris
</pre>

Elogind

2022-07-21T15:11:03Z

La9: create page with installation instructions

'''elogind''' is a login manager and provides support for

* setting up necessary permissions for the desktop environment or window manager
* handling poweroff, reboot, suspend and hibernate via '''loginctl''' command

== Installation ==

<pre>
# apk add elogind polkit-elogind
# rc-update add elogind
# rc-service elogind start
</pre>

== Configuration ==

=== logind.conf ===

Edit <code>/etc/elogind/logind.conf</code> to configure handling of power events, such as suspending the computer when power button is pressed:

<pre>
sed -i 's|#HandlePowerKey=poweroff|HandlePowerKey=suspend|' /etc/elogind/logind.conf
</pre>

=== polkit policies ===

elogind package does not ship with any polkit policies by default, meaning that no one is allowed to use '''loginctl''' command.

We need to add custom polkit rules to allow specific users to execute '''loginctl'''.

Example for allowing all users in the user group <code>wheel</code> to suspend the computer with '''loginctl suspend''':

<pre>
tee -a /etc/polkit-1/rules.d/88-suspend.rules <<EOF
polkit.addRule(function(action, subject) {
if (action.id == "org.freedesktop.login1.suspend" &&
subject.isInGroup("wheel")) {
return polkit.Result.YES;
}
});
EOF
</pre>

Sway

2022-07-20T00:24:33Z

La9: to work with gallium, crocus is needed for older graphics

[http://swaywm.org Sway] is a tiling [[Wayland]] compositor. It's a drop-in replacement for the i3 window manager.

== Prerequisites ==

First, install & configure eudev:

<pre>
# apk add eudev
# setup-udev
</pre>

Then install the mesa graphics drivers:

<pre>
# apk add mesa-dri-gallium
## older intel graphics need
# MESA_LOADER_DRIVER_OVERRIDE=crocus
</pre>

The following links contain guides for setting up the video stack.

* [[Intel Video]]
* [[Radeon Video]]

Add yourself to the input and video groups:

<pre>
# adduser $USER input
# adduser $USER video
</pre>

You have to log out and back in for this to take effect.

Install some TTF fonts:

<pre>
# apk add ttf-dejavu
</pre>

Since sway 1.6.1 (more specifically, since wlroots 0.14), you need to set up libseat backend if you wish to run sway directly (without nesting it in another wayland compositor). To do that, [[Repositories#Enabling_the_community_repository|enable the community repository]] and choose one of the following methods:

<dl>

<dt>Option 1: seatd daemon (recommended)</dt>
<dd>
<pre>
# apk add seatd
# rc-update add seatd
# rc-service seatd start
# adduser $USER seat
</pre>

If you are already logged in as a $USER, you will need to relogin.
</dd>

<dt>Option 2: seatd-launch</dt>
<dd>
<pre>
# apk add seatd-launch
</pre>

When starting sway, you will need to prefix invocation with <code>seatd-launch</code>.
Note: <code>seatd-launch</code> is a suid binary, so it might be wise to use one of the other methods from a security perspective.
</dd>

<dt>Option 3: elogind daemon</dt>
<dd>

<pre>
# apk add elogind polkit-elogind
# rc-update add elogind
# rc-service elogind start
</pre>

Using <code>elogind</code> will automatically set the necessary permissions, so you can skip adding groups like <code>seat</code> and <code>video</code>

</dd>

</dl>

== Installation ==

We can now install sway:

<pre>
# apk add sway sway-doc
# apk add \ # Install optional dependencies:
xwayland \ # recommended for compatibility reasons
foot \ # default terminal emulator
dmenu \ # default application launcher
swaylock \ # lockscreen tool
swaybg \ # wallpaper daemon
swayidle # idle management (DPMS) daemon
</pre>

== Running Sway ==

To run sway, first set XDG_RUNTIME_DIR to a suitable location (e.g. create a .run folder in your home directory and set it to ~/.run). Then run sway from the Linux console (dbus-launch is used because pipewire needs it, it is included in dbus-x11 and you may omit it):

<pre>
$ XDG_RUNTIME_DIR=~/.run dbus-launch sway
</pre>

(if you run sway with seatd-launch, you will need to use <code>$ XDG_RUNTIME_DIR=~/.run dbus-launch seatd-launch sway</code>)

You can also create a simple alias in your shell rc file (e.g. .zshrc), like:
<pre>
alias swayinit="XDG_RUNTIME_DIR=~/.run dbus-launch seatd-launch sway"
</pre>

See the [https://wiki.alpinelinux.org/wiki/Wayland Wayland] page for a permanent configuration

{{Note|
swaylock needs to be able to read your <code>/etc/shadow</code> file to be able to validate your password
}}

== Configuration and Usage ==

An example config is provided at <code>/etc/sway/config</code>. Copy it to <code>~/.config/sway/config</code> and read through it to learn the default keybindings.

You might want to have gaps between windows, in which case add:
<pre>
inner_gaps 20
outer_gaps 20
</pre>
(replace 20 with the amount of pixels you want to be used for gaps) in your sway config.

You might have two monitors, and you might want to set their position, so here's an example of how to do it:
<pre>
output eDP-1 mode 1920x1080@60Hz
output eDP-1 position 1920,0
output DP-1 position 0,0
output DP-1 mode 1920x1080@120Hz
</pre>
In this case, eDP-1 is the internal laptop monitor running at 60Hz and DP-1 is the external monitor running at 120Hz. The position of the laptop monitor is where the external monitor's width ends, so if the display is 1920 pixels wide and it is on the left, the laptop's monitor would be on the right, so it's width would start at the end of the second monitor's width, so at 1920. Replace the eDP-1 and DP-1 outputs with your own ones, and to change resolution and refresh rate, change the mode according to your parameters.

For additional information, start at <code>man 5 sway</code> and read the [https://github.com/swaywm/sway/wiki upstream FAQ].

[[Category:Desktop]]

Intel Video

2022-07-19T23:42:03Z

La9:

When running on 3.12 or before, nomodeset must be removed from the [[Kernel parameters]].

Alpine Linux 3.13+: install mesa-dri-gallium package. For older Intel Graphics ranging from Gen4 (GMA Graphics from 2006) to Gen 7 (Haswell Intel HD 4000+ graphics), a newer, more performant driver called "crocus" need to be enabled. Enable "crocus" with "MESA_LOADER_DRIVER_OVERRIDE=crocus".

== See also ==
* [[Kernel Modesetting]]
* [https://wiki.archlinux.org/index.php/Intel_graphics Intel graphics on Arch Linux wiki]

[[Category:Drivers]]