Alpine Linux - User contributions [en]

ALSA

2024-10-29T21:58:59Z

Andar1an: Remove added troubleshooting section, the recommendation doesn't work consistently.

== Install ==

First you will need to install the Alsa packages, Linux sound driver and volume adjuster.

{{Cmd|# apk add {{pkg|alsa-utils}} {{pkg|alsaconf}}}}

== Setup ==

Then you will need to add all your users (including root) to the <code>audio</code> group.

{{Cmd|<nowiki># addgroup $USER audio
# addgroup root audio
</nowiki>}}

Find the default sound card.

{{Cmd|# alsamixer}}

The default sound card will show up. Try turning up the volume of Master and the device(s) such as speakers or microphones that you need, and audio should work ({{Key|F1}} - help, {{Key|M}} - toggle mute, ...)

If there are no volume controls visible, try hitting {{Key|F6}} on your keyboard and toggling between the sound cards (which all might have the same name in the context menu that pops up except for the numbers next to and before the names).

Once you've found the sound card name that gives you volume controls, set the unique number that showed up in the {{Key|F6}} context menu as your default soundcard.

{{Cmd|# nano /usr/share/alsa/alsa.conf}}

Scroll down until you find the lines that start with <code>defaults.ctl.card</code> and <code>defaults.pcm.card</code> and put the number (you found in the {{Key|F6}} context menu of the alsamixer command for the soundcard you want as your default) at the end of those lines separated by a space for each. For example, if the default sound card you want is "1".

{{Cat|/usr/share/alsa/alsa.conf|...
defaults.ctl.card 1
defaults.pcm.card 1
...
}}

Save your nano work by pressing {{Key|Ctrl}}+{{Key|O}} and confirm the changes by pressing {{Key|Enter}}. Then exit nano by pressing {{Key|Ctrl}}+{{Key|X}}.

Try turning up the volume of Master and the device(s) such as speakers or microphones that you need with the <code>alsamixer</code> command, and audio should work.

Alsa service is not started on install, you need to start it and to add it on [[OpenRC]].
{{Cmd|rc-service alsa start
rc-update add alsa
}}

Gstreamer can now catch the device and the audio mixer is working.

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

ALSA

2024-10-29T18:46:31Z

Andar1an: add option, as empty string doesn't always work for troubleshooting warning about alsactl_opts.

== Install ==

First you will need to install the Alsa packages, Linux sound driver and volume adjuster.

{{Cmd|# apk add {{pkg|alsa-utils}} {{pkg|alsaconf}}}}

== Setup ==

Then you will need to add all your users (including root) to the <code>audio</code> group.

{{Cmd|<nowiki># addgroup $USER audio
# addgroup root audio
</nowiki>}}

Find the default sound card.

{{Cmd|# alsamixer}}

The default sound card will show up. Try turning up the volume of Master and the device(s) such as speakers or microphones that you need, and audio should work ({{Key|F1}} - help, {{Key|M}} - toggle mute, ...)

If there are no volume controls visible, try hitting {{Key|F6}} on your keyboard and toggling between the sound cards (which all might have the same name in the context menu that pops up except for the numbers next to and before the names).

Once you've found the sound card name that gives you volume controls, set the unique number that showed up in the {{Key|F6}} context menu as your default soundcard.

{{Cmd|# nano /usr/share/alsa/alsa.conf}}

Scroll down until you find the lines that start with <code>defaults.ctl.card</code> and <code>defaults.pcm.card</code> and put the number (you found in the {{Key|F6}} context menu of the alsamixer command for the soundcard you want as your default) at the end of those lines separated by a space for each. For example, if the default sound card you want is "1".

{{Cat|/usr/share/alsa/alsa.conf|...
defaults.ctl.card 1
defaults.pcm.card 1
...
}}

Save your nano work by pressing {{Key|Ctrl}}+{{Key|O}} and confirm the changes by pressing {{Key|Enter}}. Then exit nano by pressing {{Key|Ctrl}}+{{Key|X}}.

Try turning up the volume of Master and the device(s) such as speakers or microphones that you need with the <code>alsamixer</code> command, and audio should work.

Alsa service is not started on install, you need to start it and to add it on [[OpenRC]].
{{Cmd|rc-service alsa start
rc-update add alsa
}}

Gstreamer can now catch the device and the audio mixer is working.

== Troubleshooting ==

If you are experiencing a warning when alsa service is starting that states <code>alsactl does not have an option '-' </code> while attempting to restore state, it can be simply remedied by setting the alsactl_opts variable in /etc/conf.d/alsa.
For example: <code>alsactl_opts="-F"</code>. -F is the default option --force, and tries to restore the matching control elements as much as possible. As it is default, it won't change anything, but will remove the boot warning.

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

ALSA

2024-10-29T18:35:10Z

Andar1an: correct typo for config file reference in troubleshooting

== Install ==

First you will need to install the Alsa packages, Linux sound driver and volume adjuster.

{{Cmd|# apk add {{pkg|alsa-utils}} {{pkg|alsaconf}}}}

== Setup ==

Then you will need to add all your users (including root) to the <code>audio</code> group.

{{Cmd|<nowiki># addgroup $USER audio
# addgroup root audio
</nowiki>}}

Find the default sound card.

{{Cmd|# alsamixer}}

The default sound card will show up. Try turning up the volume of Master and the device(s) such as speakers or microphones that you need, and audio should work ({{Key|F1}} - help, {{Key|M}} - toggle mute, ...)

If there are no volume controls visible, try hitting {{Key|F6}} on your keyboard and toggling between the sound cards (which all might have the same name in the context menu that pops up except for the numbers next to and before the names).

Once you've found the sound card name that gives you volume controls, set the unique number that showed up in the {{Key|F6}} context menu as your default soundcard.

{{Cmd|# nano /usr/share/alsa/alsa.conf}}

Scroll down until you find the lines that start with <code>defaults.ctl.card</code> and <code>defaults.pcm.card</code> and put the number (you found in the {{Key|F6}} context menu of the alsamixer command for the soundcard you want as your default) at the end of those lines separated by a space for each. For example, if the default sound card you want is "1".

{{Cat|/usr/share/alsa/alsa.conf|...
defaults.ctl.card 1
defaults.pcm.card 1
...
}}

Save your nano work by pressing {{Key|Ctrl}}+{{Key|O}} and confirm the changes by pressing {{Key|Enter}}. Then exit nano by pressing {{Key|Ctrl}}+{{Key|X}}.

Try turning up the volume of Master and the device(s) such as speakers or microphones that you need with the <code>alsamixer</code> command, and audio should work.

Alsa service is not started on install, you need to start it and to add it on [[OpenRC]].
{{Cmd|rc-service alsa start
rc-update add alsa
}}

Gstreamer can now catch the device and the audio mixer is working.

== Troubleshooting ==

If you are experiencing a warning when alsa service is starting that states <code>alsactl does not have an option '-' </code> while attempting to restore state, it can be simply remedied by setting the alsactl_opts variable in /etc/conf.d/alsa.
For example: <code>alsactl_opts=""</code>

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

ALSA

2024-10-28T21:41:55Z

Andar1an: mention possible solution to alsa warning on service start during boot when alsa tries to restore state and alsactl_opts are not defined.

== Install ==

First you will need to install the Alsa packages, Linux sound driver and volume adjuster.

{{Cmd|# apk add {{pkg|alsa-utils}} {{pkg|alsaconf}}}}

== Setup ==

Then you will need to add all your users (including root) to the <code>audio</code> group.

{{Cmd|<nowiki># addgroup $USER audio
# addgroup root audio
</nowiki>}}

Find the default sound card.

{{Cmd|# alsamixer}}

The default sound card will show up. Try turning up the volume of Master and the device(s) such as speakers or microphones that you need, and audio should work ({{Key|F1}} - help, {{Key|M}} - toggle mute, ...)

If there are no volume controls visible, try hitting {{Key|F6}} on your keyboard and toggling between the sound cards (which all might have the same name in the context menu that pops up except for the numbers next to and before the names).

Once you've found the sound card name that gives you volume controls, set the unique number that showed up in the {{Key|F6}} context menu as your default soundcard.

{{Cmd|# nano /usr/share/alsa/alsa.conf}}

Scroll down until you find the lines that start with <code>defaults.ctl.card</code> and <code>defaults.pcm.card</code> and put the number (you found in the {{Key|F6}} context menu of the alsamixer command for the soundcard you want as your default) at the end of those lines separated by a space for each. For example, if the default sound card you want is "1".

{{Cat|/usr/share/alsa/alsa.conf|...
defaults.ctl.card 1
defaults.pcm.card 1
...
}}

Save your nano work by pressing {{Key|Ctrl}}+{{Key|O}} and confirm the changes by pressing {{Key|Enter}}. Then exit nano by pressing {{Key|Ctrl}}+{{Key|X}}.

Try turning up the volume of Master and the device(s) such as speakers or microphones that you need with the <code>alsamixer</code> command, and audio should work.

Alsa service is not started on install, you need to start it and to add it on [[OpenRC]].
{{Cmd|rc-service alsa start
rc-update add alsa
}}

Gstreamer can now catch the device and the audio mixer is working.

== Troubleshooting ==

If you are experiencing a warning when alsa service is starting that states <code>alsactl does not have an option '-' </code> while attempting to restore state, it can be simply remedied by setting the alsactl_opts variable in /etc/init.d/alsa.
For example: <code>alsactl_opts=""</code>

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

User:Andar1an

2024-10-03T22:46:18Z

Andar1an: update fstab uuids

# WIP - Lots of references to LVM on LUKS and Secure Boot Alpine wikis - will add links and references later

# TODO:
- Poweroff has some errors related to mounts - look into
- Validate swapfile compression and cow settings - if remounting while installing didn't work use chattrc
- Wiki page formatting

# System:
Alpine 3.20 on Lenovo X1 Yoga Gen 4

# Steps:
setup-keymap
setup-hostname
setup-interfaces
rc-service networking start
passwd
setup-timezone
setup-ntp
setup-sshd

# load btrfs module, or will get missing /dev/btrfs-control warning when creating fs.
modprobe btrfs
setup-apkrepos
apk update
apk add btrfs-progs cryptsetup dosfstools mkinitfs parted

# use optimal partition alignment for disk
parted -a optimal /dev/nvme0n1 -s \
mklabel gpt \
mkpart ESP fat32 1MiB 512MiB \
mkpart luks btrfs 512MiB 100% \
set 1 esp on

# overwrite luks parition with 0's - takes a while, took me 20 min for 476 GiB
# dd if=/dev/urandom of=/dev/nvme0n1p2 bs=1M status=progress

# Luks2 Optimized for security (see cryptsetup notes below):
cryptsetup luksFormat /dev/nvme0n1p2 -v -c aes-xts-plain64 -s 512 --hash sha512 --pbkdf pbkdf2 --iter-time 5000 --use-random

# can verify keyslot has a key
# cryptsetup luksDump /dev/nvme0n1p2

mkfs.fat -F 32 -n ESP /dev/nvme0n1p1
cryptsetup luksOpen /dev/nvme0n1p2 luks
mkfs.btrfs -L ROOT /dev/mapper/luks

# create subvolumes
mount /dev/mapper/luks /mnt
btrfs sub create /mnt/@
btrfs sub create /mnt/@swap
btrfs sub create /mnt/@.snapshots
btrfs sub create /mnt/@tmp
btrfs sub create /mnt/@run
btrfs sub create /mnt/@var
btrfs sub create /mnt/@srv
btrfs sub create /mnt/@home
btrfs sub create /mnt/@opt
umount /mnt

# following mounts will inherit primary mount options until remounted
mount -o ssd,noatime,space_cache=v2,compress-force=zstd:2,discard=async,subvol=@ /dev/mapper/luks /mnt
# Mount the sub volumes:
mkdir -p /mnt/swap /mnt/.snapshots /mnt/tmp /mnt/run /mnt/var /mnt/srv /mnt/home /mnt/opt
mount -o subvol=@home /dev/mapper/luks /mnt/home
mount -o subvol=@opt /dev/mapper/luks /mnt/opt
mount -o subvol=@tmp /dev/mapper/luks /mnt/tmp
mount -o subvol=@var /dev/mapper/luks /mnt/var
mount -o subvol=@run /dev/mapper/luks /mnt/run
mount -o subvol=@srv /dev/mapper/luks /mnt/srv
mount -o subvol=@.snapshots /dev/mapper/luks /mnt/.snapshots
mount -o subvol=@swap /dev/mapper/luks /mnt/swap

mkdir -p /mnt/boot/efi
# Mount the EFI partition
mount /dev/nvme0n1p1 /mnt/boot/efi

# easier to not install bootlader with setup-disk
BOOTLOADER=none setup-disk -m sys /mnt

export UUID=$(blkid -s UUID -o value /dev/dm-0 | sed -n 's/.*UUID=\"$[^\"]*$\".*/\1/p' )
export UUID2=$(blkid -s UUID -o value /dev/nvme0n1p1 | sed -n 's/.*UUID=\"$[^\"]*$\".*/\1/p' )

# Can modify output of setup-disk
cat <<EOF >/mnt/etc/fstab
UUID=$UUID / btrfs rw,noatime,compress-force=zstd:2,ssd,discard=async,space_cache=v2,subvol=/@ 0 0
UUID=$UUID /home btrfs rw,relatime,compress-force=zstd:2,ssd,discard=async,space_cache=v2,subvol=/@home 0 0
UUID=$UUID /opt btrfs rw,relatime,compress-force=zstd:2,ssd,discard=async,space_cache=v2,subvol=/@opt 0 0
UUID=$UUID /tmp btrfs rw,ssd,noatime,nodatacow,space_cache=v2,compress-force=zstd:2,discard=async,subvol=/@tmp 0 0
UUID=$UUID /var btrfs rw,ssd,noatime,nodatacow,space_cache=v2,compress-force=zstd:2,discard=async,subvol=/@var 0 0
UUID=$UUID /run btrfs rw,ssd,noatime,nodatacow,space_cache=v2,compress-force=zstd:2,discard=async,subvol=/@run 0 0
UUID=$UUID /srv btrfs rw,ssd,noatime,nodatacow,space_cache=v2,compress-force=zstd:2,discard=async,subvol=/@srv 0 0
UUID=$UUID /.snapshots btrfs rw,ssd,noatime,nodatacow,space_cache=v2,compress-force=zstd:2,discard=async,subvol=/@.snapshots 0 0
UUID=$UUID /swap btrfs rw,ssd,noatime,nodatacow,compress=none,subvol=/@swap 0 0
UUID=$UUID2 /boot/efi vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=utf8,shortname=mixed,errors=remount-ro 0 2
/dev/cdrom /media/cdrom iso9660 noauto,ro 0 0
/dev/usbdisk /media/usb vfat noauto 0 0
tmpfs /tmp tmpfs nosuid,nodev 0 0
EOF

# remount subvolumes for different mount options to be used
umount /mnt/swap
mount -o rw,ssd,noatime,nodatacow,compress=none,subvol=@swap /dev/mapper/luks /mnt/swap

# Now create swapfile with correct subvolume options
# https://btrfs.readthedocs.io/en/latest/Swapfile.html
btrfs filesystem mkswapfile --size 20G /mnt/swap/swapfile
swapon /mnt/swap/swapfile

# Look into updating to current key options - https://wiki.archlinux.org/title/Dm-crypt/Device_encryption#Keyfiles
# To avoid having to type your decryption password twice every boot (once for GRUB and once for Alpine), add a keyfile to your LUKS partition. The filename is important.
touch /mnt/crypto_keyfile.bin
chmod 600 /mnt/crypto_keyfile.bin
dd bs=512 count=4 if=/dev/urandom of=/mnt/crypto_keyfile.bin
cryptsetup luksAddKey /dev/nvme0n1p2 /mnt/crypto_keyfile.bin

# This keyfile is stored encrypted (it is in your LUKS partition), so its presence does not affect system security.
# Mount the required filesystems for the Grub EFI installer to do the installation:
# rbind is recurrsive, rslave is a mirror mount, the proc file system acts as an interface to internal data structures in the kernel.

# see https://wiki.archlinux.org/title/Chroot section 4.3
mount -t proc /proc /mnt/proc
mount --rbind /dev /mnt/dev
mount --make-rslave /mnt/dev
mount --rbind /sys /mnt/sys

# Then run chroot:
chroot /mnt

# Install GRUB2 for EFI
apk add grub grub-efi efibootmgr

# To get the UUID of your storage device into a file for later use, run this command:
export UUID=$(blkid -s UUID -o value /dev/nvme0n1p2 | sed -n 's/.*UUID=\"$[^\"]*$\".*/\1/p' )

# cryptdm = device name set in cryptsetup
cat <<EOF >/etc/default/grub
GRUB_TIMEOUT=2
GRUB_DISABLE_SUBMENU=y
GRUB_DISABLE_RECOVERY=false
GRUB_CMDLINE_LINUX_DEFAULT="modules=sd-mod,usb-storage,btrfs,nvme cryptroot=UUID=$UUID cryptdm=luks cryptkey quiet rootfstype=btrfs"
GRUB_PRELOAD_MODULES="luks2 cryptodisk part_gpt gcry_sha512 pbkdf2"
GRUB_ENABLE_CRYPTODISK=y
EOF

# # Update mkinitfs conf modules
cat <<EOF >/etc/mkinitfs/mkinitfs.conf
features="ata base ide scsi usb virtio btrfs nvme cryptsetup cryptkey"
EOF

# if more than 1 kernel, explicitly state value
mkinitfs $(ls /lib/modules/)

grub-install --target=x86_64-efi --efi-directory=/boot/efi --boot-directory=/boot --bootloader-id=ALPINE --modules="luks2 part_gpt cryptodisk btrfs gcry_rijndael pbkdf2 gcry_sha512"

grub-mkconfig -o /boot/grub/grub.cfg

User:Andar1an

2024-09-30T17:24:31Z

Andar1an: Full Disk Encryption - BTRFS Subvolumes + LUKS2 - Single Disk, No RAID, No Secure Boot

# WIP - Lots of references to LVM on LUKS and Secure Boot Alpine wikis - will add links and references later

# TODO:
- Poweroff has some errors related to mounts - look into
- Validate swapfile compression and cow settings - if remounting while installing didn't work use chattrc
- Wiki page formatting

# System:
Alpine 3.20 on Lenovo X1 Yoga Gen 4

# Steps:
setup-keymap
setup-hostname
setup-interfaces
rc-service networking start
passwd
setup-timezone
setup-ntp
setup-sshd

# load btrfs module, or will get missing /dev/btrfs-control warning when creating fs.
modprobe btrfs
setup-apkrepos
apk update
apk add btrfs-progs cryptsetup dosfstools mkinitfs parted

# use optimal partition alignment for disk
parted -a optimal /dev/nvme0n1 -s \
mklabel gpt \
mkpart ESP fat32 1MiB 512MiB \
mkpart luks btrfs 512MiB 100% \
set 1 esp on

# overwrite luks parition with 0's - takes a while, took me 20 min for 476 GiB
# dd if=/dev/urandom of=/dev/nvme0n1p2 bs=1M status=progress

# Luks2 Optimized for security (see cryptsetup notes below):
cryptsetup luksFormat /dev/nvme0n1p2 -v -c aes-xts-plain64 -s 512 --hash sha512 --pbkdf pbkdf2 --iter-time 5000 --use-random

# can verify keyslot has a key
# cryptsetup luksDump /dev/nvme0n1p2

mkfs.fat -F 32 -n ESP /dev/nvme0n1p1
cryptsetup luksOpen /dev/nvme0n1p2 luks
mkfs.btrfs -L ROOT /dev/mapper/luks

# create subvolumes
mount /dev/mapper/luks /mnt
btrfs sub create /mnt/@
btrfs sub create /mnt/@swap
btrfs sub create /mnt/@.snapshots
btrfs sub create /mnt/@tmp
btrfs sub create /mnt/@run
btrfs sub create /mnt/@var
btrfs sub create /mnt/@srv
btrfs sub create /mnt/@home
btrfs sub create /mnt/@opt
umount /mnt

# following mounts will inherit primary mount options until remounted
mount -o ssd,noatime,space_cache=v2,compress-force=zstd:2,discard=async,subvol=@ /dev/mapper/luks /mnt
# Mount the sub volumes:
mkdir -p /mnt/swap /mnt/.snapshots /mnt/tmp /mnt/run /mnt/var /mnt/srv /mnt/home /mnt/opt
mount -o subvol=@home /dev/mapper/luks /mnt/home
mount -o subvol=@opt /dev/mapper/luks /mnt/opt
mount -o subvol=@tmp /dev/mapper/luks /mnt/tmp
mount -o subvol=@var /dev/mapper/luks /mnt/var
mount -o subvol=@run /dev/mapper/luks /mnt/run
mount -o subvol=@srv /dev/mapper/luks /mnt/srv
mount -o subvol=@.snapshots /dev/mapper/luks /mnt/.snapshots
mount -o subvol=@swap /dev/mapper/luks /mnt/swap

mkdir -p /mnt/boot/efi
# Mount the EFI partition
mount /dev/nvme0n1p1 /mnt/boot/efi

# easier to not install bootlader with setup-disk
BOOTLOADER=none setup-disk -m sys /mnt

export UUID=$(blkid -s UUID -o value /dev/nvme0n1p2 | sed -n 's/.*UUID=\"$[^\"]*$\".*/\1/p' )
export UUID2=$(blkid -s UUID -o value /dev/dm-0 | sed -n 's/.*UUID=\"$[^\"]*$\".*/\1/p' )
export UUID3=$(blkid -s UUID -o value /dev/nvme0n1p1 | sed -n 's/.*UUID=\"$[^\"]*$\".*/\1/p' )

# Can modify output of setup-disk
cat <<EOF >/mnt/etc/fstab
UUID=$UUID / btrfs rw,noatime,compress-force=zstd:2,ssd,discard=async,space_cache=v2,subvol=/@ 0 0
UUID=$UUID2 /home btrfs rw,relatime,compress-force=zstd:2,ssd,discard=async,space_cache=v2,subvol=/@home 0 0
UUID=$UUID2 /opt btrfs rw,relatime,compress-force=zstd:2,ssd,discard=async,space_cache=v2,subvol=/@opt 0 0
UUID=$UUID2 /tmp btrfs rw,ssd,noatime,nodatacow,space_cache=v2,compress-force=zstd:2,discard=async,subvol=/@tmp 0 0
UUID=$UUID2 /var btrfs rw,ssd,noatime,nodatacow,space_cache=v2,compress-force=zstd:2,discard=async,subvol=/@var 0 0
UUID=$UUID2 /run btrfs rw,ssd,noatime,nodatacow,space_cache=v2,compress-force=zstd:2,discard=async,subvol=/@run 0 0
UUID=$UUID2 /srv btrfs rw,ssd,noatime,nodatacow,space_cache=v2,compress-force=zstd:2,discard=async,subvol=/@srv 0 0
UUID=$UUID2 /.snapshots btrfs rw,ssd,noatime,nodatacow,space_cache=v2,compress-force=zstd:2,discard=async,subvol=/@.snapshots 0 0
UUID=$UUID2 /swap btrfs rw,ssd,noatime,nodatacow,compress=none,subvol=/@swap 0 0
UUID=$UUID3 /boot/efi vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=utf8,shortname=mixed,errors=remount-ro 0 2
/dev/cdrom /media/cdrom iso9660 noauto,ro 0 0
/dev/usbdisk /media/usb vfat noauto 0 0
tmpfs /tmp tmpfs nosuid,nodev 0 0
EOF

# remount subvolumes for different mount options to be used
umount /mnt/swap
mount -o rw,ssd,noatime,nodatacow,compress=none,subvol=@swap /dev/mapper/luks /mnt/swap

# Now create swapfile with correct subvolume options
# https://btrfs.readthedocs.io/en/latest/Swapfile.html
btrfs filesystem mkswapfile --size 20G /mnt/swap/swapfile
swapon /mnt/swap/swapfile

# Look into updating to current key options - https://wiki.archlinux.org/title/Dm-crypt/Device_encryption#Keyfiles
# To avoid having to type your decryption password twice every boot (once for GRUB and once for Alpine), add a keyfile to your LUKS partition. The filename is important.
touch /mnt/crypto_keyfile.bin
chmod 600 /mnt/crypto_keyfile.bin
dd bs=512 count=4 if=/dev/urandom of=/mnt/crypto_keyfile.bin
cryptsetup luksAddKey /dev/nvme0n1p2 /mnt/crypto_keyfile.bin

# This keyfile is stored encrypted (it is in your LUKS partition), so its presence does not affect system security.
# Mount the required filesystems for the Grub EFI installer to do the installation:
# rbind is recurrsive, rslave is a mirror mount, the proc file system acts as an interface to internal data structures in the kernel.

# see https://wiki.archlinux.org/title/Chroot section 4.3
mount -t proc /proc /mnt/proc
mount --rbind /dev /mnt/dev
mount --make-rslave /mnt/dev
mount --rbind /sys /mnt/sys

# Then run chroot:
chroot /mnt

# Install GRUB2 for EFI
apk add grub grub-efi efibootmgr

# To get the UUID of your storage device into a file for later use, run this command:
export UUID=$(blkid -s UUID -o value /dev/nvme0n1p2 | sed -n 's/.*UUID=\"$[^\"]*$\".*/\1/p' )

# cryptdm = device name set in cryptsetup
cat <<EOF >/etc/default/grub
GRUB_TIMEOUT=2
GRUB_DISABLE_SUBMENU=y
GRUB_DISABLE_RECOVERY=false
GRUB_CMDLINE_LINUX_DEFAULT="modules=sd-mod,usb-storage,btrfs,nvme cryptroot=UUID=$UUID cryptdm=luks cryptkey quiet rootfstype=btrfs"
GRUB_PRELOAD_MODULES="luks2 cryptodisk part_gpt gcry_sha512 pbkdf2"
GRUB_ENABLE_CRYPTODISK=y
EOF

# # Update mkinitfs conf modules
cat <<EOF >/etc/mkinitfs/mkinitfs.conf
features="ata base ide scsi usb virtio btrfs nvme cryptsetup cryptkey"
EOF

# if more than 1 kernel, explicitly state value
mkinitfs $(ls /lib/modules/)

grub-install --target=x86_64-efi --efi-directory=/boot/efi --boot-directory=/boot --bootloader-id=ALPINE --modules="luks2 part_gpt cryptodisk btrfs gcry_rijndael pbkdf2 gcry_sha512"

grub-mkconfig -o /boot/grub/grub.cfg

Printer Setup

2024-09-04T17:35:15Z

Andar1an: Add note about requiring root user in SystemGroup configuration for CUPS to manage printers in KDE Settings.

First, you'll need [https://en.wikipedia.org/wiki/CUPS CUPS]. If you have a ''Hewlett-Packard'' (''HP'') printer, add the [https://en.wikipedia.org/wiki/HP_Linux_Imaging_and_Printing HPLIP] package. Some of these packages are outside of main, and the appropriate repos will need to be configured. See tip below.

{{cmd|# apk add cups cups-pdf cups-filters hplip}}

{{Tip|As with all installation processes, Alpine's [[Alpine_Linux_package_management|package management]] can guide you on the need to pull various packages from other repositories (e.g.''@testing'') other than the enabled ''main'' or ''edge'' repositories throughout this wiki page, as long as the other repos have been [https://wiki.alpinelinux.org/wiki/Alpine_Linux_package_management#Repository_pinning pinned]. For example, for Alpine version 3.7.0 on x86_64 systems, '''apk''' would have guided you to substitute in <code>cups-pdf@testing</code> and <code>hplip@testing</code>.}}

Confirm cups starts. You may also set it to run at boot-up.

{{cmd|# rc-service cupsd start}}
{{cmd|# rc-update add cupsd boot}}

Go to <code><nowiki>http://localhost:631</nowiki></code> with your web browser and follow the steps to "Add Printer". It will ask you to log in to add a printer. Log in as root, then finish the steps. Once you're done, you should be able to print.

If that doesn't work, you may also need to add HPLIP's dependencies separately. There are currently no packages for '''CUPS DDK''', <code>hp-setup</code> or <code>foomatic</code>.

{{cmd|# apk add ghostscript py3-reportlab libjpeg net-snmp}}

{{Expand|Modifications/sections required e.g. to address container user-case scenarios, etc.}}

== configure mdev for USB printers ==

By default USB printer with [[mdev]] would have ownership ''root:root'' and permission ''0660''. As ''cupsd'' would try to open a libusb-based printer as ''lp'' user, it won't have permission to use the device in ''/dev/bus/usb''.

First let's get some info about our USB printer.

# lsusb.py -uU | grep Printer
3-2 04b8:0007 00 1IF [USB 2.00, 480 Mbps, 2mA] (EPSON USB2.0 Printer (Hi-speed) 55PKAZZ15776790829)

# grep -H "" /sys/bus/usb/devices/usb3/3-2/{id{Vendor,Product},bcdDevice}
/sys/bus/usb/devices/usb3/3-2/idVendor:04b8
/sys/bus/usb/devices/usb3/3-2/idProduct:0007
/sys/bus/usb/devices/usb3/3-2/bcdDevice:0100

These are important for us to distinguish our printer.

# cat >> /etc/mdev.conf <<EOF
SUBSYSTEM=usb;PRODUCT=4b8/7/100;.* root:lp 660 */lib/mdev/usbdev
EOF

Unplug the USB cable and plug it in again. Now the USB printer device at ''/dev/bus/usb/'' will have valid ownership and permissions.

# ls -l /dev/bus/usb/002/011
crw-rw---- 1 root lp 189, 138 Apr 14 21:19 /dev/bus/usb/002/011

CUPS will be able now to use libusb to discover the local USB printer.

== Desktop Environment ==

Additionally, in a desktop environment you could proceed as follows.

Check whether ''root'' and the user's username (''yourusername'') are already members of the <code>lp</code> and <code>lpadmin</code> groups. Note: ''yourusername'' can be added to the <code>lpadmin</code> group if they should be able to administer the CUPS system with their password.

$ groups root
root bin daemon sys adm disk wheel floppy dialout tape video
$ groups ''yourusername''
yourusername disk wheel audio cdrom dialout video users plugdev

If not, add them:

{{Cmd|# adduser root lp
# adduser root lpadmin
# adduser ''yourusername'' lp
# adduser ''yourusername'' lpadmin}}

Start CUPS ('''cupsd''') and make it persist between boots; then reboot:

{{Cmd|# rc-service cupsd start
# rc-update add cupsd
# reboot}}

== Managing Printers via KDE Plasma Settings ==

To manage printers from KDE Plasma Settings, it is required to add "root" to SystemGroup in '''''/etc/cups/cups-files.conf'''''.

e.g.
{{Cmd|
SystemGroup root lpadmin}}

== Managing Printers via Command Line ==

Credit to ArchWiki's excellent [https://wiki.archlinux.org/index.php/CUPS CUPS] page for guidance with the following basic steps.

=== Locate your printer ===

With your printer connected and powered on, determine the ''URI'' for your printer. Depending on whether the connection is via '''usb''' or '''parallel''' ports, the URI will carry a <code>usb://</code> or <code>parallel:/</code> prefix.

$ lpinfo -v #
network lpd
network socket
network beh
file cups-brf:/
direct usb://HP/LaserJet%202200
network ipp
network ipps
network https
network http
direct hp

In the example above, the URI is <code>usb://HP/LaserJet%202200</code>

=== Find a .ppd or .ppd.gz ''driver'' ===

If your printer supports ''IPP Everywhere'' -- most recent models do -- see the ''driverless'' command in ''cups-filters'':

$ driverless ipp_uri > printer.ppd

or just pass ''-m everywhere'' to ''lpadmin''.

Otherwise, you could list all the drivers available by running <code>lpinfo -m</code> and then searching through the results to find a .ppd or .ppd.gz specific to your printer. A quick solution is to use the <code>--make-and-model</code> flag and <code>grep</code> to filter the results by plugging in your printer's make, model and series in this fashion:

$ lpinfo --make-and-model "''make_and_model_names''" -m | grep -i ''printer_series''

{{Tip|
*Search for the term ''HP'' to find instances of ''Hewlett-Packard''.
*You do not need to state the <code>printer_series</code> in whole if at all e.g. ''2200'' may be preferable to searching for ''2200M'', etc.}}

For example, type:

$ lpinfo --make-and-model "HP LaserJet" -m | grep -i 2200

From the results, you might select the following .ppd ''driver'':

drv:///hp/hpcups.drv/hp-laserjet_2200_series.ppd

If required, additional drivers can be obtained by installing {{Pkg|gutenprint}}, and running the <code>lpinfo</code> search again. These may not specify <code>.ppd</code> names.

{{Cmd|# apk add gutenprint gutenprint-doc}}

=== Configure a queue ===

Create a queue using a ''queue_name'' of your choice. Your selected printer's name is an obvious choice, but do not use spaces. 
You will also need to be root or use <code>sudo</code>, and you will also need to plug in the ''URI'' and the .ppd ''driver'':

# lpadmin -p ''queue_name'' -E -v "''uri''" -m ''driver''

With this example, you could set as follows, but there are other solutions.

# lpadmin -p HP_LaserJet_2200 -E -v "usb://HP/LaserJet%202200" -m drv:///hp/hpcups.drv/hp-laserjet_2200-pcl3.ppd

This printer queue could be set as '''default''':

# lpoptions -d HP_LaserJet_2200

Printer settings can typically be set in your GUI application's '''Print''' menu or by examining the CUPS [https://www.cups.org/doc/man-lpoptions.html lpoptions] page. If you have a single queue, the setting options available (such as page type, duplex, etc.) for your queue can simply be '''listed''' by using the '''-l''' flag. Asterisks(*) indicate current settings:

# lpoptions -l
PageSize/Media Size: Card3x5 Hagaki Photo4x6 A6 Photo5x7 Card5x8 Oufuku A5 B5 JB5 Executive 16k Letter *A4 ExecutiveJIS FLSA Legal EnvA2 EnvC6 EnvChou4 EnvMonarch EnvDL Env10 EnvChou3 EnvC5 EnvB5 Custom.WIDTHxHEIGHT
Duplex/Double-Sided Printing: DuplexNoTumble DuplexTumble *None
InputSlot/Media Source: *Auto PhotoTray Upper Lower Envelope LargeCapacity Manual MPTray
ColorModel/Output Mode: *Gray
MediaType/Media Type: *Plain
OutputMode/Print Quality: *Normal Draft Best
OptionDuplex/Duplexer Installed: *False True

If there is only one queue, '''options''' can be set by simply using '''-o''' flags for each setting:

# lpoptions -o PageSize=Legal -o Duplex=DuplexNoTumble

== See also ==

* [https://www.cups.org/documentation.html CUPS documentation]

[[Category:Printers]]
[[Category:Installation]]

Bluetooth

2024-08-26T18:22:56Z

Andar1an:

{{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.}}

=== 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 `br-connection-profile-unavailable` is sometimes produced when trying to connect a device which requires the <code>uhid</code> kernel module.

Try running <code>modprobe uhid</code>.

The <code>modprobe uhid</code> kernel module is required for devices with drives that are implemented in userspace. This often includes keyboards and the volume buttons on headphones (which are sometimes presented to the OS as a keyboard).

=== 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]]

NetworkManager

2024-08-25T19:58:04Z

Andar1an: Add todo item for autoconnect of wifi network on boot

[https://networkmanager.dev/ NetworkManager] is a program that provides automatic detection and configuration for systems to connect to networks.

== Installation ==

{{Cmd|# apk add {{Pkg|networkmanager}}}}

 

{{Note|
Networkmanager needs to have [[eudev|udev]] to be setup properly. The busybox implementation mdev is not sufficient. You can set up proper udev with:
{{Cmd|# setup-devd udev}}
Otherwise your network devices can be listed as (strictly-)unmanaged.
}}

There are multiple interfaces available for NetworkManager:

* TUI: {{Pkg|networkmanager-tui}}, a curses-based interface (run <code>nmtui</code>)
* Command line: {{Pkg|networkmanager-cli}} (run <code>nmcli</code>)
* GUI: {{Pkg|plasma-nm}} for Plasma integration and applet
* GUI: {{Pkg|network-manager-applet}} for a GTK system tray applet

 

You will need to install an additional package if you want NetworkManager to connect to wifi:
{{Cmd|# apk add {{Pkg|networkmanager-wifi}}}}

 

After installation start NetworkManager:
{{Cmd|# rc-service networkmanager start}}

 

Then set it to autostart the service on boot:
{{Cmd|# rc-update add networkmanager default}}

 

Also your user needs to be in the <code>plugdev</code> group:
{{Cmd|# adduser <YourUsername> plugdev}}

{{Note|you will need to log out for the new group to take effect}}

 

== Wired networks ==

If wired networks do not appear or you get an error message like "Could not activate connection: Connection 'Ethernet connection 1' is not available on device eth0 because device is strictly unmanaged", add the following to {{path|/etc/NetworkManager/NetworkManager.conf}}:

<pre>
[ifupdown]
managed=true
</pre>

 

== Wireless networks ==

==== wpa_supplicant backend ====

{{Todo|([[KDE|KDE Plasma]] Desktop) find out if it is possible to prevent requesting the password for '''KDE Wallet''' on login}}
{{Todo|([[KDE|KDE Plasma]] Desktop) for autoconnect to wifi network on start, it appears that the "all users may connect to this network" option must be selected in settings, as root is not a choice to allow. There are likely better workarounds}}

* Follow: [[Wi-Fi#wpa supplicant]] and [[Wi-Fi#Automatic Configuration on System Boot]]
{{Note|{{Pkg|wpa_supplicant}} configuration might not be required, if it isn't it may be a good idea to have it setup just as a fallback}}

 

Now open {{path|/etc/NetworkManager/NetworkManager.conf}} in a text editor and change it to something like this:

{{Cat|/etc/NetworkManager/NetworkManager.conf|<nowiki>[main]
dhcp=internal
plugins=ifupdown,keyfile

[ifupdown]
managed=true

[device]
wifi.scan-rand-mac-address=yes
wifi.backend=wpa_supplicant</nowiki>}}

{{Note|if these options dont work on your system you can change them as necessary}}

 

Now you need to stop conflicting services:

{{Cmd|# rc-service networking stop}}
{{Cmd|# rc-service wpa_supplicant stop}}

 

Now restart NetworkManager:

{{Cmd|# rc-service networkmanager restart}}

 

Now connect to a network using one of the interfaces mentioned in [[NetworkManager#Installation|Installation]]

 

If that connects and stays connected with no issues enable the <code>networkmanager</code> service and disable the <code>networking</code> and <code>wpa_supplicant</code> boot services:

{{Cmd|# rc-update add networkmanager}}
{{Cmd|# rc-update del networking boot}}
{{Cmd|# rc-update del wpa_supplicant boot}}

 

==== iwd backend ====

NetworkManager supports wireless networks through {{Pkg|iwd}}, however, consider [https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues?scope=all&utf8=%E2%9C%93&state=opened&search=iwd existing issues] before using it. After installation, enable the server and restart NetworkManager:
<pre>
rc-service iwd start
rc-service networkmanager restart
</pre>

To use {{Pkg|iwd}} though, you've have to edit NetworkManager's configuration because it still defaults to {{Pkg|wpa_supplicant}} instead. Add the following to {{Path|/etc/NetworkManager/NetworkManager.conf}}:

<pre>
[device]
wifi.backend=iwd
</pre>

 

== VPN support ==
Since version 1.16, NetworkManager has support for Wireguard[https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?id=1.16.0].

Support for other VPN types is provided by plugins. They are provided in the following packages:
* {{Pkg|networkmanager-openvpn}} for OpenVPN

== nm-applet ==
=== not authorized to control networking ===

You can enable all users to edit connections without adding polkit.
First, make the <code>conf.d</code> directory for networkmanager:

{{Cmd|# mkdir -p /etc/NetworkManager/conf.d}}

Then, add following content to {{path|/etc/NetworkManager/conf.d/any-user.conf}}:

<pre>
[main]
auth-polkit=false
</pre>

Finally, restart networkmanager:

{{Cmd|# rc-service networkmanager restart}}

[[Category:Networking]]