17
May
2024

mSBC Airpods 3

17 May 2024
I recommend to use for this Pipewire. On pulseaudio not tested this method. Add new file sudo subl /etc/wireplumber/wireplumber.conf.d/50-bluez.conf With monitor.bluez.properties = { bluez5.enable-msbc = true } Then systemctl --user restart pipewire pipewire-pulse wireplumber sudo systemctl restart bluetooth TLDR I wondered for two weeks why the method described in the official Arch Linux guide, using the WirePlumber configuration file at <strike> /etc/wireplumber/bluetooth.lua.d/51-bluez-config.lua </strike> and syntax like <strike> bluez_monitor.properties = {</strike> It doesnt'work Instead, use /etc/wireplumber/wireplumber.conf.d/50-bluez.conf and syntax described in the beggining of post and will be fine
16
May
2024

Arch Sound Hires

16 May 2024
Choose on OS installation pipewire sudo pacman -S mpd yay -s cantata Choose for current user mode in Cantata Install flatpak tidal-hifi sudo cp /usr/share/pipewire/pipewire.conf /etc/pipewire/pipewire.conf paste default.clock.rate = 192000 default.clock.allowed-rates = [ 48000 44100 96000 192000 ] then systemctl --user restart pipewire.service maybe you need pw-metadata -n settings 0 clock.force-rate 192000 check cat /proc/asound/card*/pcm*p/sub*/hw_params closed closed closed closed closed closed closed access: MMAP_INTERLEAVED format: S32_LE subformat: STD channels: 2 rate: 192000 (192000/1) period_size: 1024 buffer_size: 32768
11
Mar
2024

Downgrade Plasma 6.0.1 to Plasma 5.2.7

11 Mar 2024
Plasma 6.0.1 is too laggy That is guide how to downgrade: sudo nano /etc/pacman.conf #[core] #Include = /etc/pacman.d/mirrorlist #[extra] #Include = /etc/pacman.d/mirrorlist [core] SigLevel = PackageRequired Server=https://archive.archlinux.org/repos/2024/03/01/$repo/os/$arch [extra] SigLevel = PackageRequired Server=https://archive.archlinux.org/repos/2024/03/01/$repo/os/$arch Then sudo pacman -Syyuu If you have a problem with broken u need to downgrade each package manually with pacman -U. sudo pacman -Qi expat libelf lib32-expat lib32-libelf sudo pacman -U /var/cache/pacman/pkg/lib32-expat-2.6.0-1-x86_64.pkg.tar.zst sudo pacman -U /var/cache/pacman/pkg/lib32-libelf-0.190-1-x86_64.pkg.tar.zst If you have problem with `plasma-framework5 exists in filesystem` sudo pacman -Syyuu --overwrite '*' The final step sudo reboot
10
Jan
2024

GCP autostart

10 Jan 2024
**Kubectl** subl subl /home/USER/.config/systemd/user/kubectl.service [Unit] Description=Kubectl Port Forward [Service] Type=simple ExecStart=/home/USER/Autostart/kubectl_port_forward.sh Restart=on-failure RestartSec=5 [Install] WantedBy=default.target subl /home/USER/Autostart/kubectl_port_forward.sh #!/bin/bash # Set the path to the Google Cloud SDK (adjust the path based on your installation) export PATH="/home/USER/Apps/google-cloud-sdk/bin:$PATH" # Set the path to the gke-gcloud-auth-plugin executable export GKE_GCLOUD_AUTH_PLUGIN="/home/USER/Apps/google-cloud-sdk/bin/gke-gcloud-auth-plugin" # Set the Kubernetes configuration file path (adjust the path based on your configuration) export KUBECONFIG="/home/USER/.kube/config" # Set the path to your service account key file export GOOGLE_APPLICATION_CREDENTIALS="/home/USER/.config/gcloud/application_default_credentials.json" # Authenticate with Google Cloud using the service account gcloud auth activate-service-account --key-file="$GOOGLE_APPLICATION_CREDENTIALS" # Run kubectl port-forward with the necessary authentication kubectl port-forward svc/mysql-stage-v8-k8sqlv3-stage-v8 -n mysql 3321:3306 systemctl --user enable kubectl_port_forward systemctl --user start kubectl_port_forward **Cloud SQL Proxy** subl /home/USER/.config/systemd/user/cloud-sql-proxy.service [Unit] Description=Cloud SQL Proxy [Service] Type=simple ExecStart=/home/USER/cloud_sql_proxy -instances=autodoc-XXXXXXX:europe-west3:slave-11=tcp:3311 #master Restart=on-failure RestartSec=5 [Install] WantedBy=default.target
4
Sep
2023

Artix impressions

04 Sep 2023
1. Openrc is sux because mpd and etc. Resolving by systemctl 2. After upgrade - Chrome update problem in build 3. After upgrade syslog-ng failing on boot