Estou com problema de instalação via terminal

Kerr · Junho 30, 2026, 10:16pm

estou tentando executar a instalação “sudo apt install git dkms linux-headers-generic” mas sempre ocorre esse problema, tbm testei com outras instalações via terminal e sempre dava esse problema

tijolaum · Julho 1, 2026, 3:25am

Olá! confere os espaço de sua partição EFI, aparentemente vc possui muito kernels instalados. tente rodar um autoremove.

sudo apt autoremove

Kerr · Julho 1, 2026, 9:00pm

ola, usei esse comando mas aconteceu o msm erro

partições abaixo se for ajudar em algo

mobostar0101 · Julho 2, 2026, 10:10am

qual linux esta usando?

swatquest · Julho 2, 2026, 12:29pm

Use

df -h

Use o autoremove como falaram

Kerr · Julho 2, 2026, 3:31pm

mint cinnamon

Kerr · Julho 2, 2026, 3:36pm

continua aparecendo essa lista de erro e no final a instalação falha com autoremove tbm é asssim

mobostar0101 · Julho 2, 2026, 3:48pm

o linux seria o unico SO ou tem o windows instalado?
se tiver somente o linux instalado tente desabilitar o Security Boot na BIOS.

Cassiano · Julho 2, 2026, 3:53pm

Seu problema esta nessa linha:
run-parts: /etc/kernel/postinst.d/dkms exited with return code 1
O DKMS falhou ao compilar algum módulo para o kernel 6.19.9-x64v3-xanmod1.

Apesar de vc estar com o Secure Boot ativo, a falha ocorreu antes.
Executa o dkms status no terminal pra saber qual modulo falhou

Kerr · Julho 2, 2026, 4:14pm

Cassiano · Julho 2, 2026, 4:22pm

Executa:
sudo bash -x /var/lib/dpkg/info/linux-image-6.19.4-x64v3-xanmod1.postinst configure 2>&1 | tee ~/postinst.log

E manda aqui o conteúdo do ~/postinst.log
Aproveita e executa esses caras aqui e mande as saídas:
ls -l /etc/kernel/postinst.d/
ls -l /etc/initramfs/post-update.d/
journalctl -b -0 -p err

Mande tudo em texto em vez de imagem, as vezes alguém esta no celular e é péssimo para ficar vendo respostas em imagem.

swatquest · Julho 2, 2026, 5:02pm


sudo dpkg --configure -a
sudo apt --fix-broken install
sudo apt --autoremove

Execute em sequência cada comando.

Depois coloque o resultado aqui

Kerr · Julho 2, 2026, 11:23pm

sudo bash -x /var/lib/dpkg/info/linux-image-6.19.4-x64v3-xanmod1.postinst configure 2>&1 | tee ~/postinst.log

teve esse resultado: *Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Found Windows Boot Manager on /dev/sda1@/EFI/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for UEFI Firmware Settings ...
done
*
`ls -l /etc/kernel/postinst.d/ `
-rwxr-xr-x 1 root root 195 mai  9  2025 dkms
-rwxr-xr-x 1 root root 863 fev  7  2025 initramfs-tools
-rwxr-xr-x 1 root root 196 jan 26  2024 pm-utils
-rwxr-xr-x 1 root root 882 nov 13  2024 xx-update-initrd-links
-rwxr-xr-x 1 root root 372 jan 24  2024 zz-shim
-rwxr-xr-x 1 root root 646 mar 17  2025 zz-update-grub

ls -l /etc/initramfs/post-update.d/
ls: não foi possível acessar '/etc/initramfs/post-update.d/': Arquivo ou diretório inexistente

journalctl -b -0 -p err
ul 02 19:35:45 kerrisson-Aspire-Z1-751 kernel: ACPI BIOS Error (bug): Could no>
jul 02 19:35:45 kerrisson-Aspire-Z1-751 kernel: ACPI Error: Aborting method \_S>
jul 02 19:35:45 kerrisson-Aspire-Z1-751 kernel: DMAR: Failed to find handle for>
jul 02 19:35:45 kerrisson-Aspire-Z1-751 kernel: DMAR: Failed to find handle for>
jul 02 19:35:56 kerrisson-Aspire-Z1-751 kernel: spi-nor spi0.0: probe with driv>
jul 02 19:35:56 kerrisson-Aspire-Z1-751 kernel: \[drm:drm_mode_config_cleanup\] \*>
jul 02 19:36:05 kerrisson-Aspire-Z1-751 bluetoothd\[589\]: profiles/audio/avctp.c>
jul 02 19:36:05 kerrisson-Aspire-Z1-751 bluetoothd\[589\]: profiles/sap/server.c:>
jul 02 19:36:05 kerrisson-Aspire-Z1-751 bluetoothd\[589\]: sap-server: Operation >
jul 02 19:36:05 kerrisson-Aspire-Z1-751 bluetoothd\[589\]: Failed to set mode: Fa>
jul 02 19:36:20 kerrisson-Aspire-Z1-751 wpa_supplicant\[722\]: bgscan simple: Fai>
jul 02 19:36:19 kerrisson-Aspire-Z1-751 systemd\[1\]: Failed to start casper-md5c>
jul 02 19:36:40 kerrisson-Aspire-Z1-751 bluetoothd\[589\]: src/profile.c:ext_star>
jul 02 19:36:40 kerrisson-Aspire-Z1-751 bluetoothd\[589\]: src/profile.c:ext_star>
jul 02 19:36:40 kerrisson-Aspire-Z1-751 bluetoothd\[589\]: src/profile.c:ext_star>
jul 02 19:36:40 kerrisson-Aspire-Z1-751 bluetoothd\[589\]: src/profile.c:ext_star>
jul 02 19:36:40 kerrisson-Aspire-Z1-751 bluetoothd\[589\]: src/profile.c:ext_star>
jul 02 20:09:21 kerrisson-Aspire-Z1-751 cinnamon-screensaver-pam-helper\[3313\]: >
lines 1-18/18 (END)...skipping...
jul 02 19:35:45 kerrisson-Aspire-Z1-751 kernel: ACPI BIOS Error (bug): Could not resolve symbol \[\_SB.PCI0.LPCB.EC0.\_REG.CPST\], AE_NOT_FOUND (20250807/psargs-332)
jul 02 19:35:45 kerrisson-Aspire-Z1-751 kernel: ACPI Error: Aborting method \_SB.PCI0.LPCB.EC0.\_REG due to previous error (AE_NOT_FOUND) (20250807/psparse-531)
jul 02 19:35:45 kerrisson-Aspire-Z1-751 kernel: DMAR: Failed to find handle for ACPI object \_SB.PCI0.SDMA
jul 02 19:35:45 kerrisson-Aspire-Z1-751 kernel: DMAR: Failed to find handle for ACPI object \_SB.PCI0.SDHC
jul 02 19:35:56 kerrisson-Aspire-Z1-751 kernel: spi-nor spi0.0: probe with driver spi-nor failed with error -22
jul 02 19:35:56 kerrisson-Aspire-Z1-751 kernel: \[drm:drm_mode_config_cleanup\] *ERROR* connector Unknown-1 leaked!
jul 02 19:36:05 kerrisson-Aspire-Z1-751 bluetoothd\[589\]: profiles/audio/avctp.c:avctp_server_socket() setsockopt(L2CAP_OPTIONS): Invalid argument (22)
jul 02 19:36:05 kerrisson-Aspire-Z1-751 bluetoothd\[589\]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
jul 02 19:36:05 kerrisson-Aspire-Z1-751 bluetoothd\[589\]: sap-server: Operation not permitted (1)
jul 02 19:36:05 kerrisson-Aspire-Z1-751 bluetoothd\[589\]: Failed to set mode: Failed (0x03)
jul 02 19:36:20 kerrisson-Aspire-Z1-751 wpa_supplicant\[722\]: bgscan simple: Failed to enable signal strength monitoring
jul 02 19:36:19 kerrisson-Aspire-Z1-751 systemd\[1\]: Failed to start casper-md5check.service - casper-md5check Verify Live ISO checksums.
jul 02 19:36:40 kerrisson-Aspire-Z1-751 bluetoothd\[589\]: src/profile.c:ext_start_servers() L2CAP server failed for Message Notification: setsockopt(L2CAP_OPTIONS): Invalid argument (22)
jul 02 19:36:40 kerrisson-Aspire-Z1-751 bluetoothd\[589\]: src/profile.c:ext_start_servers() L2CAP server failed for Message Access: setsockopt(L2CAP_OPTIONS): Invalid argument (22)
jul 02 19:36:40 kerrisson-Aspire-Z1-751 bluetoothd\[589\]: src/profile.c:ext_start_servers() L2CAP server failed for Phone Book Access: setsockopt(L2CAP_OPTIONS): Invalid argument (22)
jul 02 19:36:40 kerrisson-Aspire-Z1-751 bluetoothd\[589\]: src/profile.c:ext_start_servers() L2CAP server failed for File Transfer: setsockopt(L2CAP_OPTIONS): Invalid argument (22)
jul 02 19:36:40 kerrisson-Aspire-Z1-751 bluetoothd\[589\]: src/profile.c:ext_start_servers() L2CAP server failed for Object Push: setsockopt(L2CAP_OPTIONS): Invalid argument (22)
jul 02 20:09:21 kerrisson-Aspire-Z1-751 cinnamon-screensaver-pam-helper\[3313\]: pam_ecryptfs: seteuid error

~/postinst.log
bash: /home/kerrisson/postinst.log: Permissão negada

Perdão se ficou muita informação mas esta todos os resultados

Kerr · Julho 2, 2026, 11:33pm

Autoinstall on 6.19.9-x64v3-xanmod1 failed for module(s) hid-xpadneo(10).

Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
run-parts: /etc/kernel/postinst.d/dkms exited with return code 1
update-initramfs: Generating /boot/initrd.img-6.19.9-x64v3-xanmod1
Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/50_linuxmint.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.19.10-x64v3-xanmod1
Found initrd image: /boot/initrd.img-6.19.10-x64v3-xanmod1
Found linux image: /boot/vmlinuz-6.19.9-x64v3-xanmod1
Found initrd image: /boot/initrd.img-6.19.9-x64v3-xanmod1
Found linux image: /boot/vmlinuz-6.19.8-x64v3-xanmod1
Found initrd image: /boot/initrd.img-6.19.8-x64v3-xanmod1
Found linux image: /boot/vmlinuz-6.19.7-x64v3-xanmod1
Found initrd image: /boot/initrd.img-6.19.7-x64v3-xanmod1
Found linux image: /boot/vmlinuz-6.19.6-x64v3-xanmod1
Found initrd image: /boot/initrd.img-6.19.6-x64v3-xanmod1
Found linux image: /boot/vmlinuz-6.19.5-x64v3-xanmod1
Found initrd image: /boot/initrd.img-6.19.5-x64v3-xanmod1
Found linux image: /boot/vmlinuz-6.19.4-x64v3-xanmod1
Found initrd image: /boot/initrd.img-6.19.4-x64v3-xanmod1
Found linux image: /boot/vmlinuz-6.17.0-35-generic
Found initrd image: /boot/initrd.img-6.17.0-35-generic
Found linux image: /boot/vmlinuz-6.17.0-29-generic
Found initrd image: /boot/initrd.img-6.17.0-29-generic
Found linux image: /boot/vmlinuz-6.17.0-23-generic
Found initrd image: /boot/initrd.img-6.17.0-23-generic
Found linux image: /boot/vmlinuz-6.17.0-22-generic
Found initrd image: /boot/initrd.img-6.17.0-22-generic
Found linux image: /boot/vmlinuz-6.17.0-20-generic
Found initrd image: /boot/initrd.img-6.17.0-20-generic
Found linux image: /boot/vmlinuz-6.17.0-19-generic
Found initrd image: /boot/initrd.img-6.17.0-19-generic
Found linux image: /boot/vmlinuz-6.14.0-37-generic
Found initrd image: /boot/initrd.img-6.14.0-37-generic
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot
entries.
Found Windows Boot Manager on /dev/sda1@/EFI/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for UEFI Firmware Settings ...
done
dpkg: erro ao processar o pacote linux-image-6.19.9-x64v3-xanmod1 (--configure):
o subprocesso instalado, do pacote linux-image-6.19.9-x64v3-xanmod1, o script p
ost-installation retornou erro do status de saída 1
Configurando linux-image-6.19.6-x64v3-xanmod1 (6.19.6-x64v3-xanmod1-0\~20260304.g
e0b3726) ...
Sign command: /usr/bin/kmodsign
Signing key: /var/lib/shim-signed/mok/MOK.priv
Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

todos tiveram esse msm resultado

swatquest · Julho 2, 2026, 11:41pm

Parece que é com um pacote específico

6.19.9-x64v3-xanmod1 fail

Qual a saída do comando

sudo apt list | grep *xanmod1

É para descobrir o nome do pacote para ser removido

Pode usar purge

sudo apt purge nomedopacote

Só tome cuidado para não remover mais pacotes

Kerr · Julho 3, 2026, 10:13pm

grep/noble,now 3.11-4build1 amd64 \[instalado\]
grep/noble 3.11-4build1 i386
linux-headers-6.18.13-x64v3-xanmod1/now 6.18.13-x64v3-xanmod1-0\~20260219.g1c34c76 amd64 \[instalado,local\]
linux-headers-6.19.10-x64v3-xanmod1/now 6.19.10-x64v3-xanmod1-0\~20260325.gef8a086 amd64 \[instalado,local\]
linux-headers-6.19.11-x64v3-xanmod1/now 6.19.11-x64v3-xanmod1-0\~20260402.gba86a7b amd64 \[instalado,local\]
linux-headers-6.19.4-x64v3-xanmod1/now 6.19.4-x64v3-xanmod1-0\~20260227.gbe6aded amd64 \[instalado,local\]
linux-headers-6.19.5-x64v3-xanmod1/now 6.19.5-x64v3-xanmod1-0\~20260228.ga462031 amd64 \[instalado,local\]
linux-headers-6.19.6-x64v3-xanmod1/now 6.19.6-x64v3-xanmod1-0\~20260304.ge0b3726 amd64 \[instalado,local\]
linux-headers-6.19.7-x64v3-xanmod1/now 6.19.7-x64v3-xanmod1-0\~20260312.g3118900 amd64 \[instalado,local\]
linux-headers-6.19.8-x64v3-xanmod1/now 6.19.8-x64v3-xanmod1-0\~20260314.g7e750f0 amd64 \[instalado,local\]
linux-headers-6.19.9-x64v3-xanmod1/now 6.19.9-x64v3-xanmod1-0\~20260319.gdd13d1c amd64 \[instalado,local\]
linux-image-6.18.13-x64v3-xanmod1/now 6.18.13-x64v3-xanmod1-0\~20260219.g1c34c76 amd64 \[configuração-residual\]
linux-image-6.19.10-x64v3-xanmod1/now 6.19.10-x64v3-xanmod1-0\~20260325.gef8a086 amd64 \[instalado,local\]
linux-image-6.19.4-x64v3-xanmod1/now 6.19.4-x64v3-xanmod1-0\~20260227.gbe6aded amd64 \[instalado,local\]
linux-image-6.19.5-x64v3-xanmod1/now 6.19.5-x64v3-xanmod1-0\~20260228.ga462031 amd64 \[instalado,local\]
linux-image-6.19.6-x64v3-xanmod1/now 6.19.6-x64v3-xanmod1-0\~20260304.ge0b3726 amd64 \[instalado,local\]
linux-image-6.19.7-x64v3-xanmod1/now 6.19.7-x64v3-xanmod1-0\~20260312.g3118900 amd64 \[instalado,local\]
linux-image-6.19.8-x64v3-xanmod1/now 6.19.8-x64v3-xanmod1-0\~20260314.g7e750f0 amd64 \[instalado,local\]
linux-image-6.19.9-x64v3-xanmod1/now 6.19.9-x64v3-xanmod1-0\~20260319.gdd13d1c amd64 \[instalado,local\]

deu esse resultado, como devo proseguir?

swatquest · Julho 4, 2026, 1:05am

Tente

sudo apt purge linux-headers-6.19.9-x64v3-xanmod1 linux-image-6.19.9-x64v3-xanmod1

Veja se depois de remover os pacotes

Tente

sudo apt --autoremove