pedda's questions

Espero que alguém tenha uma dica, se o fscrypt servir para mim como um substituto para o ecyryptfs propenso a erros para minha pasta inicial de backup (que está em um grupo PV diferente, luks encrypted, pasta inicial ecryptfs):

   +-----------------------------------+        +-----------------------------------+
   |          Source: Home             |        |         Destination: Backup       |
   |     (eCryptfs on Home Partition)  |        |     (fscrypt on Backup Partition) |
   +-----------------------------------+        +-----------------------------------+
                \|/               |                   ^         \|/
                 |                |___________________|          |
                 |              (rsync from Home to Backup)      | 
                 v                                               v
   +-----------------------------------+        +-----------------------------------+
   |   eCryptfs Layer (Home Folder)    |        | fscrypt Layer (BackupHome)        |
   +-----------------------------------+        +-----------------------------------+
   |       Home Partition              |        |       BackupHome Partition        |
   +-----------------------------------+        +-----------------------------------+   
   |   LVM Volume (Home)               |        |   LVM Volume (BackupHome)         |
   +-----------------------------------+        +-----------------------------------+ 
   |   LVM: PV Group (Main SSD)        |        |   LVM: PV Group (USB Stick)       |
   +-----------------------------------+        +-----------------------------------+   
   |   LUKS Encrypted (Main SSD)       |        |   LUKS Encrypted (µSD Slot 1)     |
   +-----------------------------------+        +-----------------------------------+ 
   |   Physical Layer (Main SSD)       |        |   LUKS Encrypted (µSD Slot 2)     |
   +-----------------------------------+        +-----------------------------------+
                 \|/                            |           Physical Layer          |
                  |                             +-----------------------------------+
                  |                                             \|/
   +-----------------------------------+        +-----------------------------------+
   | Physical Layer (4 TB SSD)         |        |   Physical Layer (USB Stick)      |
   | Dual Boot Windows/Linux (LVM)     |        |   Combined 2 x 1.5TB µSD with     |
   | LUKS LVM in part.6, part.5 /boot  |        |                                   |
   | (root, home, swap)in 3.1TB Volume |        |   LVM into 2.8TB Volume           |
   +-----------------------------------+        +-----------------------------------+

Agora quero fazer backup dos meus dados com o seguinte comando:

rsync -avvh --inplace --size-only --info=progress2 /home/userXXX/  /backupHome/userXXX/

De vez em quando, recebia mensagens de erro aleatórias diferentes como estas (informações laterais abaixo do log):

[..]
testdaten/shrinkMpegxxDB.log
          9,02G   0%  117,23MB/s    0:01:13 (xfr#915, to-chk=655/497427)
testdaten/yyy.zzz/
testdaten/scripts/
rsync: [receiver] open "/backupHome/userXXX/testdaten/shrinkMpegxxDB.log" failed: Required key not available (126)
          9,02G   0%  117,23MB/s    0:01:13 (xfr#915, to-chk=0/497427)  

sent 9,04G bytes  received 42,04K bytes  121,37M bytes/sec
total size is 1,75T  speedup is 194,06
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1338) [sender=3.2.7]


[..]

rsync: [generator] recv_generator: mkdir "/backupHome/userXXX/.config/menus" failed: Required key not available (126)
*** Skipping any contents from this failed directory ***
rsync: [generator] recv_generator: mkdir "/backupHome/xxxx/.config/mpv" failed: Required key not available (126)
*** Skipping any contents from this failed directory ***
rsync: [generator] recv_generator: mkdir "/backupHome/userXXX/.config/nautilus" failed: Required key not available (126)
*** Skipping any contents from this failed directory ***
rsync: [generator] recv_generator: mkdir "/backupHome/userXXX/.config/nemo" failed: Required key not available (126)
*** Skipping any contents from this failed directory ***
rsync: [generator] recv_generator: mkdir "/backupHome/userXXX/.config/nomacs" failed: Required key not available (126)
*** Skipping any contents from this failed directory ***
rsync: [generator] recv_generator: mkdir "/backupHome/userXXX/.config/procps" failed: Required key not available (126)
*** Skipping any contents from this failed directory ***
rsync: [generator] recv_generator: mkdir "/backupHome/userXXX/.config/pulse" failed: Required key not available (126)
*** Skipping any contents from this failed directory ***
rsync: [generator] recv_generator: mkdir "/backupHome/userXXX/.config/qimgv" failed: Required key not available (126)
*** Skipping any contents from this failed directory ***
rsync: [generator] recv_generator: mkdir "/backupHome/userXXX/.config/remmina" failed: Required key not available (126)
*** Skipping any contents from this failed directory ***
rsync: [generator] recv_generator: mkdir "/backupHome/userXXX/.config/simple-scan" failed: Required key not available (126)
*** Skipping any contents from this failed directory ***
rsync: [generator] recv_generator: mkdir "/backupHome/userXXX/.config/systemd" failed: Required key not available (126)
*** Skipping any contents from this failed directory ***
rsync: [generator] recv_generator: mkdir "/backupHome/userXXX/.config/teamviewer" failed: Required key not available (126)

[..]

        103,23M   0%    2,26MB/s    0:00:43 (xfr#1034, ir-chk=1028/476659)
[sender] expand file_list pointer array to 1024 bytes, did move
[sender] expand file_list pointer array to 1024 bytes, did move
[sender] expand file_list pointer array to 1024 bytes, did move
[sender] expand file_list pointer array to 1024 bytes, did move
[sender] expand file_list pointer array to 4096 bytes, did not move
[sender] expand file_list pointer array to 16384 bytes, did not move
[sender] expand file_list pointer array to 32768 bytes, did move
        103,23M   0%    2,24MB/s    0:00:44 (xfr#1034, ir-chk=2841/479500)
[..]
total: matches=0  hash_hits=0  false_alarms=0 data=103226155

sent 124,32M bytes  received 46,81M bytes  3,20M bytes/sec
total size is 1,75T  speedup is 10.254,91
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1338) [sender=3.2.7]

O backup completo foi de 1,8 TB. Com o primeiro "pedaço" de dados transmitidos, cada vez interrompido por um erro, foi de 747 GB. O acesso ao arquivo foi proibido. Tentei com comandos bash, mas falhei da mesma forma, então estava relacionado a fscrypt.

Cada vez que eu destranquei a casa de novo e de novo (após cada cancelamento), ele funciona. Como o USB Stick ficou muito quente, eu o resfriei com um pouco de gelo refrescante da geladeira:

fscrypt unlock /backupHome/userXXX

Então, quais são suas ideias? Minhas sugestões para a causa do erro:

• o dispositivo esquentou muito (depois de esfriar e desbloquear novamente, ele transferiu 1 TB de uma só vez)
• Eu cometi um erro acidentalmente ao desbloquear a pasta fscrypted backupHome?
• A configuração LUKS/LVM/2µSD vinculada em um módulo USB de expansão µSD é problemática?

Espero que alguém possa ajudar aqui!

[EDITAR] De acordo com @SteffenUlrich e minhas próprias suposições, isso pode indicar fortemente um problema de HW devido a

• SD talvez não seja compatível com ext4fs, principalmente, e suporta apenas FAT/FAT32/exFat
• superaquecimento do sistema (porque o resfriamento ajudou a carregar pelo menos um pedaço de 1 TB de dados sem falhas. (mas não foi comprovado para mim, porque não consegui avaliar adequadamente as outras fontes de erro. Então, o diário daquele dia para o dispositivo dm-7 mostra algumas dicas:

# journalctl -k | grep -Ei "excryptfs|error"
Oct 17 19:15:16 HP-ENVY-Laptop-13-aq1176ng kernel: pcieport 0000:00:1c.4: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
Oct 17 19:15:16 HP-ENVY-Laptop-13-aq1176ng kernel: pcieport 0000:00:1d.4: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
Oct 17 19:15:16 HP-ENVY-Laptop-13-aq1176ng kernel: RAS: Correctable Errors collector initialized.
Feb 20 00:05:30 HP-ENVY-Laptop-13-aq1176ng kernel: hp_wmi: query 0x4c returned error 0x6
Feb 20 00:05:36 HP-ENVY-Laptop-13-aq1176ng kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_TZ.ETMD], AE_NOT_FOUND (20230628/psargs-332)
Feb 20 00:05:36 HP-ENVY-Laptop-13-aq1176ng kernel: ACPI Error: Aborting method \_SB.IETM._OSC due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
Feb 20 09:41:07 HP-ENVY-Laptop-13-aq1176ng kernel: Buffer I/O error on dev dm-7, logical block 0, async page read
Feb 20 09:41:07 HP-ENVY-Laptop-13-aq1176ng kernel: Buffer I/O error on dev dm-7, logical block 0, async page read
Feb 20 09:41:07 HP-ENVY-Laptop-13-aq1176ng kernel: Buffer I/O error on dev dm-7, logical block 0, async page read

[.. many more ..]

Feb 20 09:41:52 HP-ENVY-Laptop-13-aq1176ng kernel: buffer_io_error: 6 callbacks suppressed

[.. many more ..]

Feb 20 09:42:01 HP-ENVY-Laptop-13-aq1176ng kernel: Buffer I/O error on dev dm-7, logical block 8192, async page read
Feb 20 09:42:01 HP-ENVY-Laptop-13-aq1176ng kernel: Buffer I/O error on dev dm-7, logical block 8192, async page read
Feb 20 09:42:01 HP-ENVY-Laptop-13-aq1176ng kernel: Buffer I/O error on dev dm-7, logical block 16384, async page read
Feb 20 09:42:01 HP-ENVY-Laptop-13-aq1176ng kernel: Buffer I/O error on dev dm-7, logical block 16384, async page read
Feb 20 09:42:01 HP-ENVY-Laptop-13-aq1176ng kernel: Buffer I/O error on 

[.. many more ..]

Feb 23 14:43:21 HP-ENVY-Laptop-13-aq1176ng kernel:  filemap_fdatawait_range_keep_errors+0x12/0x50
Feb 23 16:19:36 HP-ENVY-Laptop-13-aq1176ng kernel:  filemap_fdatawait_range_keep_errors+0x12/0x50
Feb 23 20:43:48 HP-ENVY-Laptop-13-aq1176ng kernel:  filemap_fdatawait_range_keep_errors+0x12/0x50
Feb 25 04:04:24 HP-ENVY-Laptop-13-aq1176ng kernel: ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4]
Feb 25 04:04:24 HP-ENVY-Laptop-13-aq1176ng kernel: ecryptfs_read_folio: Error decrypting page; rc = [-4]
ecryptfs_read_folio: Error decrypting page; rc = [-4]

[.. man more ..]

Minha configuração: Pré-requisitos:

• Dual Boot Windows 10/anteriormente Ubuntu 24.04 (vindo de 22.04)
• Tabela de partição:

  /dev/nvme0n1p7                   202G   96M  202G   1% 
  /ntfs_data
  /dev/nvme0n1p3                   230G   54G  177G  24% 
  /windows
  /dev/nvme0n1p5                   3,0G  288M  2,6G  11% /boot
  /dev/mapper/ubuntu--vg-home      2,8T  1,7T  964G  64% /home
  /dev/nvme0n1p1                   256M  158M   99M  62% 
  /boot/efi
  tmpfs                            1,6G  300K  1,6G   1% /run/user/1000
  /home/xxx/.Private               2,8T  1,7T  964G  64% /home/xxx
  /dev/mapper/usb1TB_202304_crypt  938G  890G  559M 100% 
  /backup1TB
  /backup1TB/home_xxx_bck          938G  890G  559M 100% 
  /backup1TB/home_xxx_bck
  

  
• /dev/nvme0n1p6 é o dispositivo criptografado luks com LVM configurado:
  • raiz (243 GB)
  • casa (2,8 TB)
  • trocar (16 GB)

Etapas de instalação para produzir erro no initramfs:

Usei o instalador USB do Linux Mint 22 (Imagem baixada em janeiro de 2025). Consegui instalar o LVM2 e o pacote cryptsetup para obter assistência para LVM e LUKS. Configurei em 2022 no Ubuntu 22.04 o LVM como o seguinte:

# vgs
  WARNING: Couldn't find device with uuid CQVk01-WJQL-pjIi-opcT-oESN-UOb1-judhlH.
  WARNING: Couldn't find device with uuid I5OUXJ-OkxW-403c-rEVJ-BmyG-Rd4M-r7SSFs.
  WARNING: VG ubuntu-vg is missing PV CQVk01-WJQL-pjIi-opcT-oESN-UOb1-judhlH (last written to /dev/mapper/ubuntu-vg1).
  WARNING: VG ubuntu-vg is missing PV I5OUXJ-OkxW-403c-rEVJ-BmyG-Rd4M-r7SSFs (last written to /dev/mapper/ubuntu-vg2).
  VG        #PV #LV #SN Attr   VSize  VFree   
  ubuntu-vg   3   4   0 wz-pn- <6,01t <180,97g

# pvs
  WARNING: Couldn't find device with uuid CQVk01-WJQL-pjIi-opcT-oESN-UOb1-judhlH.
  WARNING: Couldn't find device with uuid I5OUXJ-OkxW-403c-rEVJ-BmyG-Rd4M-r7SSFs.
  WARNING: VG ubuntu-vg is missing PV CQVk01-WJQL-pjIi-opcT-oESN-UOb1-judhlH (last written to /dev/mapper/ubuntu-vg1).
  WARNING: VG ubuntu-vg is missing PV I5OUXJ-OkxW-403c-rEVJ-BmyG-Rd4M-r7SSFs (last written to /dev/mapper/ubuntu-vg2).
  PV                      VG        Fmt  Attr PSize  PFree   
  /dev/mapper/ubuntu-luks ubuntu-vg lvm2 a--   3,21t <180,97g
  [unknown]               ubuntu-vg lvm2 a-m  <1,40t       0 
  [unknown]               ubuntu-vg lvm2 a-m  <1,40t       0 

# lvs
  LV         VG        Attr       LSize    Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  backupHome ubuntu-vg -wi-----p-    2,79t                                                    
  home       ubuntu-vg -wi-ao----    2,78t                                                    
  root       ubuntu-vg -wi-ao---- <247,33g                                                    
  swap_1     ubuntu-vg -wi-ao----   16,00g  

Abri um bash, abri o LUKS e ativei o LVM (o LVM foi criado anteriormente na versão 22.04 em 2022):

# cryptsetup luksOpen /dev/nvmeon1p6 ubuntu-luks
# lvchange -ay ubuntu-vg

Então iniciei o aplicativo de instalação e escolhi o modo manual para atribuir as partições, que configurei conforme mostrado acima, com formatação de root e /dev/nvme0n1p5 como partição /boot (não criptografada).

Depois disso, inicializei essas novas instalações instaladas do Linux Mint 22. Mas, além disso, curiosamente, na primeira vez, o diálogo de senha gráfica na sequência de inicialização no início só apareceu uma vez e descriptografou os luks, mas não conseguiu atribuir a partição LVM corretamente. Depois disso, nem mesmo o volume criptografado LUKS foi encontrado ou detectado e em todos os casos acabei depois de um longo tempo de espera no initramfs em caixa ocupado.

Aqui eu sempre tive que repetir as duas instruções acima antes de poder sair do initramfs e continuar inicializando meu sistema.

Descobri que não havia crypttab em /etc/crypttab e instalei um como

# cat /etc/crypttab 
# <target name>         <source device>                           <key file>      <options>
# mounted /, /home, swap_1
ubuntu-luks             UUID=b910aded-9314-403f-a350-7892ba95ffd5 none            luks
# mounted as /backupHome LV part1, partial Loading (mustn't be present during boot)
ubuntu-luks_backupHome1 UUID=b1d9ec9c-7dac-445f-998b-695b2ddf6daa none            luks
#ubuntu-luks_backupHome1 UUID=b1d9ec9c-7dac-445f-998b-695b2ddf6daa none            luks,noauto
# mounted as /backupHome LV part2, partial loading (mustn't be present during boot)
ubuntu-luks_backupHome2 UUID=9c5b65e8-5785-44be-85c7-3009cbc1e02a none            luks
#ubuntu-luks_backupHome2 UUID=9c5b65e8-5785-44be-85c7-3009cbc1e02a none            luks,noauto
usb1TB_202304_luks      UUID=4c4b603f-9146-4cb0-9621-9aa098ec592c none            luks

# ubuntu-luks             UUID=b910aded-9314-403f-a350-7892ba95ffd5 none            luks  # mounted on /
# ubuntu-luks_backupHome1 UUID=b1d9ec9c-7dac-445f-998b-695b2ddf6daa none            luks,noauto  # mounted as /backupHome, part1
# ubuntu-luks_backupHome2 UUID=9c5b65e8-5785-44be-85c7-3009cbc1e02a none            luks,noauto  # mounted as /backupHome, part2

e /etc/fstab:

# cat /etc/fstab 
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system>                           <mount point>   <type>  <options>                 <dump>  <pass>
/dev/mapper/ubuntu--vg-root               /               ext4    errors=remount-ro         0       1
# /boot was on /dev/nvme0n1p5 during installation
UUID=712868f5-29cc-429a-b535-375a3d868fa3 /boot           ext4    defaults                  0       2
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=E079-2792                            /boot/efi       vfat    umask=0077                0       1
/dev/mapper/ubuntu--vg-home               /home           ext4    defaults                  0       2
# /ntfs_data was on /dev/nvme0n1p7 during installation
UUID=3B269E2A1843CA0B                     /ntfs_data      ntfs    defaults,umask=007,gid=46 0       0
# /windows was on /dev/nvme0n1p3 during installation
UUID=4C30FF1730FF06AC                     /windows        ntfs    defaults,umask=007,gid=46 0       0
/dev/mapper/ubuntu--vg-swap_1             none            swap    sw                        0       0
/dev/mapper/ubuntu--vg-backupHome         /backupHome     ext4    defaults,nofail           0       2

então atualizei o initramfs com $ sudo update-initramfs -k all -c

Agora eu consertei permanentemente a criptografia do luks (então o diálogo aparece toda vez durante a inicialização, como descrito), mas a ativação do lvm $ lvchange -ay ubuntu-vg não é feita no initramfs!

Como eu poderia realizar esse último passo - ativar o grupo LV?

• Observação: a mídia lvm de backup, que é uma unidade USB, normalmente não está presente durante a inicialização!!!

  # mounted as /backupHome LV part1, partial Loading (mustn't be present during boot)
  ubuntu-luks_backupHome1  UUID=xxx none            luks
  #ubuntu-luks_backupHome1 UUID=xxx none            luks,noauto
  # mounted as /backupHome LV part2, partial loading (mustn't be present during boot) 
  ubuntu-luks_backupHome2  UUID=xxx none            luks
  #ubuntu-luks_backupHome2 UUID=xxx none            luks,noauto
  

[EDIT 101502013]: Hoje ele inicializou com erro algo como

/sbin/lvchange not found

no initramfs. Uma coisa que descobri que era diferente no initrams, era que lvmos comandos do como lvs, pvs, vgs, lvchange, lvcreateetc. funcionavam apenas com o comando principal lvmcomo prefixo. Também descobri que no /sbinin initramfstem apenas um link simbólico como um alias estranho lvm -> vgchange, parece que arg0 se torna arg1 após aplicar o link. É isso que tento em seguida, colocando esse link no initramfs.

[EDIT2] Coloquei meu script lvm start e activating primeiro em local-top, depois em init-bottom, por último em local-bottom, e atualizei o initramfs de acordo, update-initramfs -k all -c mas sem sucesso, o LUKS é descriptografado, mas o script não é executado ou é executado muito cedo, e cada vez que ele acaba finalmente no console initramfs com seu busybox. Quando eu executo manualmente o script e saio, ele continua inicializando todas as vezes. Mas isso é muito desconfortável e, na mesma medida, demorado por causa dos muitos atrasos de tempo, em vez de executar o script, ele produz repetidamente esta linha de saída:

mdadm: No array found in config file or automatically

Este é o local real do meu script:

# tree /etc/initramfs-tools/
/etc/initramfs-tools/
├── conf.d
│   └── cryptsetup
├── hooks
├── initramfs.conf
├── modules
├── scripts
│   ├── init-bottom
│   ├── init-premount
│   ├── init-top
│   ├── local-bottom
│   │   └── lvm
│   ├── local-premount
│   ├── local-top
│   ├── nfs-bottom
│   ├── nfs-premount
│   ├── nfs-top
│   └── panic
└── update-initramfs.conf

14 directories, 5 files

o script parece executável assim:

#!/bin/sh
# Check and activate LVM volumes regardless of input arguments

# Log the intention to activate LVM volumes
echo "Activating LVM volumes..." > /dev/console

# Activate the volume group
if /sbin/vgchange -ay ubuntu-vg; then
    echo "Logical volume group ubuntu-vg successfully activated." > /dev/console
    /sbin/lvm lvchange -ay ubuntu-vg --activationmode partial
else
    echo "Failed to activate logical volume group ubuntu-vg." > /dev/console
fi

No meio tempo, esvaziei uma imagem initrd para ver onde o comando cryptsetup é executado, mas parece um pouco complicado: unmkinitramfs -v initrd.img-6.8.0-53-generic /tmp/initrd e pesquisei por cryptsetup :

# find /tmp/initrd/ -type f -iname "*" -exec grep -Hn "cryptsetup " {} \;
grep: /tmp/initrd/main/usr/sbin/cryptsetup: binary file matches
grep: /tmp/initrd/main/usr/lib/x86_64-linux-gnu/libcryptsetup.so.12.10.0: binary file matches
grep: /tmp/initrd/main/usr/lib/x86_64-linux-gnu/libmount.so.1.1.0: binary file matches
/tmp/initrd/main/usr/lib/cryptsetup/functions:320:        if [ -e "$CRYPTTAB_OPTION_header" ] && /sbin/cryptsetup isLuks -- "$CRYPTTAB_OPTION_header"; then
/tmp/initrd/main/usr/lib/cryptsetup/functions:324:        if /sbin/cryptsetup isLuks -- "$s"; then
/tmp/initrd/main/usr/lib/cryptsetup/functions:366:    /sbin/cryptsetup -T1 \
/tmp/initrd/main/usr/lib/cryptsetup/functions:396:    /sbin/cryptsetup -T1 \
/tmp/initrd/main/usr/bin/cryptroot-unlock:89:# birth date) of the cryptsetup process with same $CRYPTTAB_NAME.
/tmp/initrd/main/usr/bin/cryptroot-unlock:118:  # find the cryptsetup process with same $CRYPTTAB_NAME
/tmp/initrd/main/usr/bin/cryptroot-unlock:173:      echo "cryptsetup: cryptsetup failed, bad password or options?" >&2
/tmp/initrd/main/scripts/local-top/cryptroot:127:    # our `cryptroot-unlock` script searches for cryptsetup processes
/tmp/initrd/main/scripts/local-top/cryptroot:164:            cryptsetup_message "ERROR: $CRYPTTAB_NAME: cryptsetup failed, bad password or options?"
/tmp/initrd/main/scripts/local-top/cryptroot:177:                /sbin/cryptsetup remove -- "$CRYPTTAB_NAME"

**Alguma ideia? O que eu fiz errado, ou poderia ter feito diferente? **

Primeiro: som virtual através de RDP ( Remote Desktop Connection ) iE NoMachine funciona brilhantemente, apenas os alto-falantes internos e fones de ouvido não emitem som. Drivers de som ( firmware aberto de som são instalados pelo github source v2.2 (antes da maioria dos últimos v2.12) ). A placa de som é intels snd_hda_intel .

Segui alguns links encontrados na net sobre Linux Mint ou Ubuntu 22, que sempre são parecidos como:

• instalar ALSA
• Reinstalando o sistema de som e reiniciando o alsa
• (re)instalar fio de tubulação
• instalar e configurar hdajackretask (esta é a maneira menos promissora na minha humilde opinião)

incl. reiniciando alsa,

# dmesg | grep snd
[  659.315312] snd_hda_intel 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100
[  659.315388] snd_hda_intel 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver
[  659.678692] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC285: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
[  659.678695] snd_hda_codec_realtek ehdaudio0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[  659.678697] snd_hda_codec_realtek ehdaudio0D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
[  659.678698] snd_hda_codec_realtek ehdaudio0D0:    mono: mono_out=0x0
[  659.678699] snd_hda_codec_realtek ehdaudio0D0:    inputs:
[  659.678699] snd_hda_codec_realtek ehdaudio0D0:      Mic=0x19

Obtendo informações sobre o sistema ( últimas duas linhas de áudio ):

# inxi -SMA
System:
  Host: HP-ENVY-Laptop-13-aq1176ng Kernel: 6.8.0-52-generic arch: x86_64
    bits: 64
  Desktop: Cinnamon v: 6.4.6 Distro: Linux Mint 22.1 Xia
Machine:
  Type: Laptop System: HP product: HP ENVY Laptop 13-aq1xxx
    v: Type1ProductConfigId serial: 8CG0165VNF
  Mobo: HP model: 86AE v: 83.18 serial: PJEKT1DHCDM061 UEFI: Insyde v: F.22
    date: 11/24/2023
Audio:
  Device-1: Intel Comet Lake PCH-LP cAVS driver: sof-audio-pci-intel-cnl
  API: ALSA v: k6.8.0-52-generic status: kernel-api

O diário que revisou as descobertas de 'snd' durante a inicialização parece bom para mim:

$ journalctl -b -x | grep -i snd
Oct 17 19:15:17 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_intel 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100
Oct 17 19:15:17 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_intel 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver
Feb 20 00:05:30 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC285: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
Feb 20 00:05:30 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_codec_realtek ehdaudio0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Feb 20 00:05:30 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_codec_realtek ehdaudio0D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
Feb 20 00:05:30 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_codec_realtek ehdaudio0D0:    mono: mono_out=0x0
Feb 20 00:05:30 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_codec_realtek ehdaudio0D0:    inputs:
Feb 20 00:05:30 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_codec_realtek ehdaudio0D0:      Mic=0x19
Feb 20 01:17:31 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_intel 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100
Feb 20 01:17:31 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_intel 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver
Feb 20 01:17:31 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC285: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
Feb 20 01:17:31 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_codec_realtek ehdaudio0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Feb 20 01:17:31 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_codec_realtek ehdaudio0D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
Feb 20 01:17:31 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_codec_realtek ehdaudio0D0:    mono: mono_out=0x0
Feb 20 01:17:31 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_codec_realtek ehdaudio0D0:    inputs:
Feb 20 01:17:31 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_codec_realtek ehdaudio0D0:      Mic=0x19

Até agora, nenhum resultado. A única coisa que está funcionando é que se você conectar via NoMachine o som é transferido para o computador remoto.

Então eu considero que o som é produzido, mas em algum lugar entre as camadas de Abstração do SO até o HW há um problema. Eu imploro por suas ideias, ou soluções (árvores)!

[EDITAR]

aplay -l saída

# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) []
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Saída lspci :

# lspci
00:00.0 Host bridge: Intel Corporation Comet Lake-U v1 4c Host Bridge/DRAM Controller (rev 0c)
00:02.0 VGA compatible controller: Intel Corporation CometLake-U GT2 [UHD Graphics] (rev 02)
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c)
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model
00:12.0 Signal processing controller: Intel Corporation Comet Lake Thermal Subsytem
00:14.0 USB controller: Intel Corporation Comet Lake PCH-LP USB 3.1 xHCI Host Controller
00:14.2 RAM memory: Intel Corporation Comet Lake PCH-LP Shared SRAM
00:14.3 Network controller: Intel Corporation Comet Lake PCH-LP CNVi WiFi
00:14.5 SD Host controller: Intel Corporation Comet Lake PCH-LP SCS3
00:15.0 Serial bus controller: Intel Corporation Serial IO I2C Host Controller
00:15.1 Serial bus controller: Intel Corporation Comet Lake Serial IO I2C Host Controller
00:16.0 Communication controller: Intel Corporation Comet Lake Management Engine Interface
00:17.0 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode]
00:1c.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #1 (rev f0)
00:1c.4 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #5 (rev f0)
00:1d.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #9 (rev f0)
00:1d.4 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #13 (rev f0)
00:1f.0 ISA bridge: Intel Corporation Comet Lake PCH-LP LPC Premium Controller/eSPI Controller
00:1f.3 Multimedia audio controller: Intel Corporation Comet Lake PCH-LP cAVS
00:1f.4 SMBus: Intel Corporation Comet Lake PCH-LP SMBus Host Controller
00:1f.5 Serial bus controller: Intel Corporation Comet Lake SPI (flash) Controller
02:00.0 3D controller: NVIDIA Corporation GP108BM [GeForce MX250] (rev a1)
04:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller S4LV008[Pascal]

saída de dmesg|grep audio

# dmesg |grep audio
[   15.060429] sof-audio-pci-intel-cnl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100
[   15.060582] sof-audio-pci-intel-cnl 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver
[   15.060596] sof-audio-pci-intel-cnl 0000:00:1f.3: enabling device (0000 -> 0002)
[   15.060801] sof-audio-pci-intel-cnl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100
[   15.060876] sof-audio-pci-intel-cnl 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[   15.067813] sof-audio-pci-intel-cnl 0000:00:1f.3: use msi interrupt mode
[   15.108086] sof-audio-pci-intel-cnl 0000:00:1f.3: hda codecs found, mask 5
[   15.108092] sof-audio-pci-intel-cnl 0000:00:1f.3: using HDA machine driver skl_hda_dsp_generic now
[   15.108097] sof-audio-pci-intel-cnl 0000:00:1f.3: DMICs detected in NHLT tables: 2
[   15.113689] sof-audio-pci-intel-cnl 0000:00:1f.3: Firmware paths/files for ipc type 0:
[   15.113694] sof-audio-pci-intel-cnl 0000:00:1f.3:  Firmware file:     intel/sof/sof-cml.ri
[   15.113697] sof-audio-pci-intel-cnl 0000:00:1f.3:  Topology file:     intel/sof-tplg/sof-hda-generic-2ch.tplg
[   15.116471] sof-audio-pci-intel-cnl 0000:00:1f.3: Firmware info: version 2:2:0-57864
[   15.116474] sof-audio-pci-intel-cnl 0000:00:1f.3: Firmware: ABI 3:22:1 Kernel ABI 3:23:0
[   15.116481] sof-audio-pci-intel-cnl 0000:00:1f.3: unknown sof_ext_man header type 3 size 0x30
[   15.216153] sof-audio-pci-intel-cnl 0000:00:1f.3: Firmware info: version 2:2:0-57864
[   15.216160] sof-audio-pci-intel-cnl 0000:00:1f.3: Firmware: ABI 3:22:1 Kernel ABI 3:23:0
[   15.236595] sof-audio-pci-intel-cnl 0000:00:1f.3: Topology: ABI 3:22:1 Kernel ABI 3:23:0
[   15.257684] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC285: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
[   15.257692] snd_hda_codec_realtek ehdaudio0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[   15.257695] snd_hda_codec_realtek ehdaudio0D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
[   15.257697] snd_hda_codec_realtek ehdaudio0D0:    mono: mono_out=0x0
[   15.257699] snd_hda_codec_realtek ehdaudio0D0:    inputs:
[   15.257701] snd_hda_codec_realtek ehdaudio0D0:      Mic=0x19
[ 4302.743485] sof-audio-pci-intel-cnl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100
[ 4302.743565] sof-audio-pci-intel-cnl 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver
[ 4302.744012] sof-audio-pci-intel-cnl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100
[ 4302.744080] sof-audio-pci-intel-cnl 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[ 4302.750643] sof-audio-pci-intel-cnl 0000:00:1f.3: use msi interrupt mode
[ 4302.764441] sof-audio-pci-intel-cnl 0000:00:1f.3: hda codecs found, mask 5
[ 4302.764450] sof-audio-pci-intel-cnl 0000:00:1f.3: using HDA machine driver skl_hda_dsp_generic now
[ 4302.764457] sof-audio-pci-intel-cnl 0000:00:1f.3: DMICs detected in NHLT tables: 2
[ 4302.766353] sof-audio-pci-intel-cnl 0000:00:1f.3: Firmware paths/files for ipc type 0:
[ 4302.766357] sof-audio-pci-intel-cnl 0000:00:1f.3:  Firmware file:     intel/sof/sof-cml.ri
[ 4302.766358] sof-audio-pci-intel-cnl 0000:00:1f.3:  Topology file:     intel/sof-tplg/sof-hda-generic-2ch.tplg
[ 4302.768019] sof-audio-pci-intel-cnl 0000:00:1f.3: Firmware info: version 2:2:0-57864
[ 4302.768022] sof-audio-pci-intel-cnl 0000:00:1f.3: Firmware: ABI 3:22:1 Kernel ABI 3:23:0
[ 4302.768029] sof-audio-pci-intel-cnl 0000:00:1f.3: unknown sof_ext_man header type 3 size 0x30
[ 4302.880559] sof-audio-pci-intel-cnl 0000:00:1f.3: Firmware info: version 2:2:0-57864
[ 4302.880569] sof-audio-pci-intel-cnl 0000:00:1f.3: Firmware: ABI 3:22:1 Kernel ABI 3:23:0
[ 4302.881182] sof-audio-pci-intel-cnl 0000:00:1f.3: Topology: ABI 3:22:1 Kernel ABI 3:23:0
[ 4302.897218] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC285: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
[ 4302.897226] snd_hda_codec_realtek ehdaudio0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[ 4302.897229] snd_hda_codec_realtek ehdaudio0D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
[ 4302.897232] snd_hda_codec_realtek ehdaudio0D0:    mono: mono_out=0x0
[ 4302.897233] snd_hda_codec_realtek ehdaudio0D0:    inputs:
[ 4302.897235] snd_hda_codec_realtek ehdaudio0D0:      Mic=0x19

[EDIT 3] Imagem do Alsamixer. O dispositivo está mudo se estiver verde ao redor do número na coluna, ou vice-versa? Mais Lista de placas de som, que na verdade é padrão e sof-hda-default. Mas alterar o volume ou silenciar no alsamixer não altera o som ausente dos alto-falantes e as alterações feitas não sobrevivem a uma inicialização: