All perguntas(ubuntu)

Estou tentando instalar o Anbox. Não sou proficiente com Linux e sou como um usuário final que é meio decente com a pesquisa do Google quando se trata da plataforma Linux.

Seguindo as instruções aqui, tentei instruções de vários sites e obtive os mesmos resultados.

Chego no passo sudo add-apt-repository ppa:morphis/anbox-supporte recebo o erroERROR: ppa 'morphis/anbox-support' not found (use --login if private)

Tentei encontrar a solução sozinho, mas falhei. De tudo que li até agora, devo conseguir instalar o Anbox.

snap 2.66.1+24.04
snapd 2.66.1+24.04
série 16
ubuntu 24.04
kernel 6.8.0-51-generic
uname -msaída = x86_64

Eu tentei sudo apt update && sudo apt install android-sdkpensar que isso acrescentaria o que estava faltando. Eu também corri sudo apt updateesudo apt upgrade

Tenho um laptop HP Victus com Ryzen 8645HS e RTX 4050. Decidi instalar uma distro Linux nele, alguns meses atrás, mas quando instalei o Ubuntu, descobri que o kernel tem esse bug no meu laptop e não consigo usar o Ubuntu. Então, desinstalei o Ubuntu.

Até alguns dias atrás eu entendi que o problema do kworker foi resolvido na versão 6.13 do kernel. (Eu sei que essa versão do kernel é RC.) Portanto, eu reinstalei o Ubuntu 24.04 e mudei o kernel para 6.13rc. Agora o uso da CPU está OK e tudo funciona bem, exceto o driver da Nvidia.

Tentei reinstalar o driver usando o aplicativo Drivers Adicionais , mas descobri que o driver não funciona corretamente, porque o pacote linux-modules-nvidia-550-6.13.0-061300rc1-generic está faltando, e não há pacote para minha versão do kernel nos repositórios! Também tentei instalar o driver nvidia usando o arquivo .run . Mas falhou.

Agora o que devo fazer? Posso resolver esse problema sozinho ou devo esperar o Ubuntu lançar o pacote acima?

Fim do arquivo de log do nvidia-installer: /var/log/nvidia-installer.log

x86_64-linux-gnu-gcc-14 (Ubuntu 14.2.0-4ubuntu2) 14.2.0, GNU ld (GNU Binutils for Ubuntu) 2.43.1

does not match the compiler used here:

cc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
Copyright (C) 2023 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.


It is recommended to set the CC environment variable
to the compiler that was used to compile the kernel.

To skip the test and silence this warning message, set
the IGNORE_CC_MISMATCH environment variable to "1".
However, mixing compiler versions between the kernel
and kernel modules can result in subtle bugs that are
difficult to diagnose.

*** Failed CC version check. ***

  CC [M]  nvidia/nv.o
  CC [M]  nvidia/nv-pci.o
  CC [M]  nvidia/nv-dmabuf.o
  CC [M]  nvidia/nv-nano-timer.o
  CC [M]  nvidia/nv-acpi.o
  CC [M]  nvidia/nv-cray.o
  CC [M]  nvidia/nv-dma.o
  CC [M]  nvidia/nv-i2c.o
  CC [M]  nvidia/nv-mmap.o
  CC [M]  nvidia/nv-p2p.o
  CC [M]  nvidia/nv-pat.o
  CC [M]  nvidia/nv-procfs.o
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/nv-dmabuf.o] Error 1
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/nv-pci.o] Error 1
  CC [M]  nvidia/nv-usermap.o
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
  CC [M]  nvidia/nv-vm.o
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/nv.o] Error 1
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
  CC [M]  nvidia/nv-vtophys.o
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/nv-acpi.o] Error 1
  CC [M]  nvidia/os-interface.o
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/nv-cray.o] Error 1
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
  CC [M]  nvidia/os-mlock.o
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/nv-nano-timer.o] Error 1
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/nv-dma.o] Error 1
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
  CC [M]  nvidia/os-pci.o
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
  CC [M]  nvidia/os-registry.o
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/nv-i2c.o] Error 1
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
  CC [M]  nvidia/os-usermap.o
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/nv-mmap.o] Error 1
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/nv-p2p.o] Error 1
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
  CC [M]  nvidia/nv-modeset-interface.o
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/nv-pat.o] Error 1
  CC [M]  nvidia/nv-pci-table.o
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
  CC [M]  nvidia/nv-kthread-q.o
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/nv-procfs.o] Error 1
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/nv-usermap.o] Error 1
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
  CC [M]  nvidia/nv-memdbg.o
  CC [M]  nvidia/nv-ibmnpu.o
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/nv-vm.o] Error 1
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
  CC [M]  nvidia/nv-report-err.o
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/nv-vtophys.o] Error 1
  CC [M]  nvidia/nv-rsync.o
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/os-interface.o] Error 1
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/os-mlock.o] Error 1
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/os-registry.o] Error 1
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/nv-modeset-interface.o] Error 1
  CC [M]  nvidia/nv-msi.o
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/os-pci.o] Error 1
  CC [M]  nvidia/nv-caps.o
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
  CC [M]  nvidia/nv-caps-imex.o
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/os-usermap.o] Error 1
  CC [M]  nvidia/nv_uvm_interface.o
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
  CC [M]  nvidia/libspdm_aead.o
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/nv-pci-table.o] Error 1
  CC [M]  nvidia/libspdm_ecc.o
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/nv-kthread-q.o] Error 1
  CC [M]  nvidia/libspdm_hkdf.o
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/nv-ibmnpu.o] Error 1
  CC [M]  nvidia/libspdm_rand.o
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
  CC [M]  nvidia/libspdm_shash.o
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/nv-memdbg.o] Error 1
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/nv-report-err.o] Error 1
  CC [M]  nvidia/libspdm_rsa.o
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
  CC [M]  nvidia/libspdm_aead_aes_gcm.o
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/nv-rsync.o] Error 1
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/nv-caps.o] Error 1
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
  CC [M]  nvidia/libspdm_sha.o
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/nv-msi.o] Error 1
  CC [M]  nvidia/libspdm_hmac_sha.o
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
  CC [M]  nvidia/libspdm_internal_crypt_lib.o
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/nv-caps-imex.o] Error 1
  CC [M]  nvidia/libspdm_hkdf_sha.o
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/nv_uvm_interface.o] Error 1
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/libspdm_aead.o] Error 1
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
  CC [M]  nvidia/libspdm_ec.o
  CC [M]  nvidia/libspdm_x509.o
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/libspdm_ecc.o] Error 1
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/libspdm_hkdf.o] Error 1
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/libspdm_rand.o] Error 1
  CC [M]  nvidia/libspdm_rsa_ext.o
  CC [M]  nvidia/nvlink_linux.o
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/libspdm_shash.o] Error 1
  CC [M]  nvidia/nvlink_caps.o
  CC [M]  nvidia/linux_nvswitch.o
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/libspdm_aead_aes_gcm.o] Error 1
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
  CC [M]  nvidia/procfs_nvswitch.o
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/libspdm_rsa.o] Error 1
  CC [M]  nvidia/i2c_nvswitch.o
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/libspdm_sha.o] Error 1
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/libspdm_hmac_sha.o] Error 1
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/libspdm_internal_crypt_lib.o] Error 1
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/libspdm_hkdf_sha.o] Error 1
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/libspdm_x509.o] Error 1
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/libspdm_ec.o] Error 1
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/libspdm_rsa_ext.o] Error 1
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/nvlink_caps.o] Error 1
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/nvlink_linux.o] Error 1
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/procfs_nvswitch.o] Error 1
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/linux_nvswitch.o] Error 1
cc: error: unrecognized command-line option '-fmin-function-alignment=16'; did you mean '-flimit-function-alignment'?
make[4]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/scripts/Makefile.build:194: nvidia/i2c_nvswitch.o] Error 1
make[4]: Target './' not remade because of errors.
make[3]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/Makefile:1995: .] Error 2
make[3]: Target 'modules' not remade because of errors.
make[2]: *** [/usr/src/linux-headers-6.13.0-061300rc1-generic/Makefile:251: __sub-make] Error 2
make[2]: Target 'modules' not remade because of errors.
make[2]: Leaving directory '/tmp/selfgz1085/NVIDIA-Linux-x86_64-550.142/kernel'
make[1]: *** [Makefile:251: __sub-make] Error 2
make[1]: Target 'modules' not remade because of errors.
make[1]: Leaving directory '/usr/src/linux-headers-6.13.0-061300rc1-generic'
make: *** [Makefile:115: modules] Error 2
ERROR: The nvidia kernel module was not created.
ERROR: Installation has failed.  Please see the file '/var/log/nvidia-installer.log' for details.  You may find suggestions on fixing installation problems in the README available on the Linux driver download page at www.nvidia.com.

Tentei instalar essas duas versões para amd64:

• https://github.com/mongodb-js/compass/releases/tag/v1.44.7
• https://github.com/mongodb-js/compass/releases/tag/v1.45.0

A instalação ocorre sem erros

sudo apt install ./mongodb-compass_1.45.0_amd64.deb

which mongodb-compass
/usr/bin/mongodb-compass

Mas quando eu inicio os dois, recebo um erro

mongodb-compass --version
Illegal instruction (core dumped)

Minhas informações do sistema, saída curta do fastfetchcomando

OS: Ubuntu 24.10 x86_64
Kernel: Linux 6.11.0-13-generic
DE: GNOME
CPU: Intel(R) Celeron(R) G530 (2) @ 2.40 GHz

Li que pode estar relacionado às instruções do processador

cat /proc/cpuinfo

processor : 0
vendor_id : GenuineIntel
cpu family  : 6
model   : 42
model name  : Intel(R) Celeron(R) CPU G530 @ 2.40GHz
stepping  : 7
microcode : 0x2f
cpu MHz   : 1596.394
cache size  : 2048 KB
physical id : 0
siblings  : 2
core id   : 0
cpu cores : 2
apicid    : 0
initial apicid  : 0
fpu   : yes
fpu_exception : yes
cpuid level : 13
wp    : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt tsc_deadline_timer xsave lahf_lm epb pti ssbd ibrs ibpb stibp tpr_shadow flexpriority ept vpid xsaveopt dtherm arat pln pts vnmi md_clear flush_l1d
vmx flags : vnmi preemption_timer invvpid ept_x_only flexpriority tsc_offset vtpr mtf vapic ept vpid unrestricted_guest
bugs    : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit mmio_unknown
bogomips  : 4789.13
clflush size  : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

processor : 1
vendor_id : GenuineIntel
cpu family  : 6
model   : 42
model name  : Intel(R) Celeron(R) CPU G530 @ 2.40GHz
stepping  : 7
microcode : 0x2f
cpu MHz   : 1596.376
cache size  : 2048 KB
physical id : 0
siblings  : 2
core id   : 1
cpu cores : 2
apicid    : 2
initial apicid  : 2
fpu   : yes
fpu_exception : yes
cpuid level : 13
wp    : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt tsc_deadline_timer xsave lahf_lm epb pti ssbd ibrs ibpb stibp tpr_shadow flexpriority ept vpid xsaveopt dtherm arat pln pts vnmi md_clear flush_l1d
vmx flags : vnmi preemption_timer invvpid ept_x_only flexpriority tsc_offset vtpr mtf vapic ept vpid unrestricted_guest
bugs    : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit mmio_unknown
bogomips  : 4789.13
clflush size  : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

A pedido @waltinator

file $(type -p mongodb-compass)
/usr/bin/mongodb-compass: symbolic link to ../lib/mongodb-compass/MongoDB Compass

lscpu

Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 36 bits physical, 48 bits virtual
Byte order: Little Endian
...

Quero usar " expect" para digitar automaticamente a <Enter>tecla " " quando o script bash solicitar " Country Name (2 letter code) [US]:".

Aqui está o esperado:

/usr/bin/expect << EOF
    set timeout -1
    
    spawn /bin/bash /path/to/generate_openssl_certificate.sh
    
    expect {
        "Country Name (2 letter code) [US]:" {send "\r" ; exp_continue}
    }
EOF

Aqui está o erro:

spawn /bin/bash /path/to/generate_openssl_certificate.sh
invalid command name "US"
    while executing
"US"
    invoked from within
"expect {
            "Country Name (2 letter code) [US]:" {send "\r" ; exp_continue}
        }"

Quando tento usar " -re" para corresponder à string, ele não corresponde à string " Country Name (2 letter code) [US]:":

expect {
    -re "Country Name \(2 letter code\) \[US\]:" {send "\r" ; exp_continue}
}

Aqui está a saída, a tela está aguardando a <Enter>tecla " " para prosseguir:

You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
Country Name (2 letter code) [US]:

Como combinar o " Country Name (2 letter code) [US]:" sem usar " -re"? Como combinar o " Country Name (2 letter code) [US]:" com " -re"?

Estou usando um Acer Nitro V ANV15 que usa MediaTek Bluetooth MT7921 para WiFi e Bluetooth. Tenho o Ubuntu 24.04.01 LTS com 6.8.0-51-generic para seu kernel.

Tentei reiniciar e verificar o status do bluetooth e ele diz que o serviço está em execução. No entanto, ao tentar ligar o bluetooth por meio das configurações do GNOME, o toggle se recusa a funcionar. Usar o terminal com bluetoothctl também diz que não há um controlador padrão.

Estranhamente, a parte do WiFi ainda funciona corretamente. Eu até tentei desligá-lo na chance remota de que pudesse estar interferindo no bluetooth, mas isso não funcionou. Eu também executei sudo apt update e upgrade só para ter certeza.

Além disso, estou fazendo dual boot com o Windows e o bluetooth funciona corretamente com esse SO. O WiFi funcionou direto da caixa durante a instalação dual boot (depois de executar sudo apt update e upgrade uma vez).

Parece que esse não é um problema antigo, considerando que vi relatos sobre isso para o kernel Linux ~5.0. Já existe alguma correção para essa versão mais nova?

EDIT: Informações adicionais conforme solicitado por Jeremy31:

lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 0408:403a Quanta Computer, Inc. ACER HD User Facing
Bus 003 Device 003: ID 13d3:3606 IMC Networks Wireless_Device
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

sudo dmesg | egrep -i 'blue|firm'
[    0.149202] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[    2.048553] Bluetooth: Core ver 2.22
[    2.048577] NET: Registered PF_BLUETOOTH protocol family
[    2.048578] Bluetooth: HCI device and connection manager initialized
[    2.048582] Bluetooth: HCI socket layer initialized
[    2.048584] Bluetooth: L2CAP socket layer initialized
[    2.048588] Bluetooth: SCO socket layer initialized
[    2.371476] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/adlp_dmc.bin (v2.20)
[    2.384614] i915 0000:00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin version 70.20.0
[    2.384620] i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3
[    2.743129] mt7921e 0000:3e:00.0: WM Firmware Version: ____010000, Build Time: 20240219111038
[    3.103798] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    3.103803] Bluetooth: BNEP filters: protocol multicast
[    3.103807] Bluetooth: BNEP socket layer initialized
[    3.774665] sof-audio-pci-intel-tgl 0000:00:1f.3: Firmware paths/files for ipc type 0:
[    3.774670] sof-audio-pci-intel-tgl 0000:00:1f.3:  Firmware file:     intel/sof/sof-rpl.ri
[    3.775861] sof-audio-pci-intel-tgl 0000:00:1f.3: Firmware info: version 2:2:0-57864
[    3.775866] sof-audio-pci-intel-tgl 0000:00:1f.3: Firmware: ABI 3:22:1 Kernel ABI 3:23:0
[    3.864754] sof-audio-pci-intel-tgl 0000:00:1f.3: Firmware info: version 2:2:0-57864
[    3.864759] sof-audio-pci-intel-tgl 0000:00:1f.3: Firmware: ABI 3:22:1 Kernel ABI 3:23:0
[    4.450398] Bluetooth: hci0: Opcode 0x0c03 failed: -110
[ 1380.079922] i915 0000:00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin version 70.20.0
[ 1380.079926] i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3
[ 1380.940420] audit: type=1400 audit(1736591719.235:249): apparmor="DENIED" operation="open" class="file" profile="snap.firmware-updater.firmware-notifier" name="/proc/sys/vm/max_map_count" pid=16622 comm="firmware-notifi" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[ 5091.766316] i915 0000:00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin version 70.20.0
[ 5091.766330] i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3
[ 5121.929122] i915 0000:00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin version 70.20.0
[ 5121.929127] i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3
[ 5123.394812] audit: type=1400 audit(1736612644.852:267): apparmor="DENIED" operation="open" class="file" profile="snap.firmware-updater.firmware-notifier" name="/proc/sys/vm/max_map_count" pid=42330 comm="firmware-notifi" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

No message appears for dkms status after installing it

Quando inicializei meu sistema hoje, recebi as seguintes mensagens de erro:

Jan 07 19:38:25 ubuntu20 systemd[1]: Condition check resulted in System Security Services Daemon being skipped.
Jan 07 19:38:25 ubuntu20 systemd[1]: Reached target User and Group Name Lookups.
Jan 07 19:38:25 ubuntu20 systemd[1]: sssd-nss.socket: Bound to unit sssd.service, but unit isn't active.
Jan 07 19:38:25 ubuntu20 systemd[1]: Dependency failed for SSSD NSS Service responder socket.
Jan 07 19:38:25 ubuntu20 systemd[1]: sssd-nss.socket: Job sssd-nss.socket/start failed with result 'dependency'.
Jan 07 19:38:25 ubuntu20 systemd[1]: sssd-autofs.socket: Bound to unit sssd.service, but unit isn't active.
Jan 07 19:38:25 ubuntu20 systemd[1]: Dependency failed for SSSD AutoFS Service responder socket.
Jan 07 19:38:25 ubuntu20 systemd[1]: sssd-autofs.socket: Job sssd-autofs.socket/start failed with result 'dependency'.
Jan 07 19:38:25 ubuntu20 systemd[1]: sssd-pac.socket: Bound to unit sssd.service, but unit isn't active.
Jan 07 19:38:25 ubuntu20 systemd[1]: Dependency failed for SSSD PAC Service responder socket.
Jan 07 19:38:25 ubuntu20 systemd[1]: sssd-pac.socket: Job sssd-pac.socket/start failed with result 'dependency'.
Jan 07 19:38:25 ubuntu20 systemd[1]: sssd-pam-priv.socket: Bound to unit sssd.service, but unit isn't active.
Jan 07 19:38:25 ubuntu20 systemd[1]: Dependency failed for SSSD PAM Service responder private socket.
Jan 07 19:38:25 ubuntu20 systemd[1]: Dependency failed for SSSD PAM Service responder socket.
Jan 07 19:38:25 ubuntu20 systemd[1]: sssd-pam.socket: Job sssd-pam.socket/start failed with result 'dependency'.
Jan 07 19:38:25 ubuntu20 systemd[1]: sssd-pam-priv.socket: Job sssd-pam-priv.socket/start failed with result 'dependency'.
Jan 07 19:38:25 ubuntu20 systemd[1]: sssd-ssh.socket: Bound to unit sssd.service, but unit isn't active.
Jan 07 19:38:25 ubuntu20 systemd[1]: Dependency failed for SSSD SSH Service responder socket.
Jan 07 19:38:25 ubuntu20 systemd[1]: sssd-ssh.socket: Job sssd-ssh.socket/start failed with result 'dependency'.
Jan 07 19:38:25 ubuntu20 systemd[1]: sssd-sudo.socket: Bound to unit sssd.service, but unit isn't active.
Jan 07 19:38:25 ubuntu20 systemd[1]: Dependency failed for SSSD Sudo Service responder socket.
Jan 07 19:38:25 ubuntu20 systemd[1]: sssd-sudo.socket: Job sssd-sudo.socket/start failed with result 'dependency'.
Jan 07 19:38:25 ubuntu20 systemd[1]: Starting Accounts Service...

Parece que por isso sudotambém parou de funcionar. Agora estou recebendo sudo: 3 incorrect password attempts. Estava tudo bem ontem, não fiz nenhuma alteração no meu sistema nem instalei nenhum software.

Atualizar:

~$ systemctl status sssd
○ sssd.service - System Security Services Daemon
     Loaded: loaded (/lib/systemd/system/sssd.service; enabled; vendor preset: enabled)
     Active: inactive (dead)
  Condition: start condition failed at Tue 2025-01-07 19:38:24 EST; 30min ago
             ├─ ConditionPathExists=|/etc/sssd/sssd.conf was not met
             └─ ConditionDirectoryNotEmpty=|/etc/sssd/conf.d was not met

Jan 07 19:38:25 ubuntu20 systemd[1]: Condition check resulted in System Security Services Daemon being skipped.

~$ systemctl start sssd

O que me levou a dizer: "Autenticação necessária". Minha senha foi aceita.

~$ systemctl status sssd
○ sssd.service - System Security Services Daemon
     Loaded: loaded (/lib/systemd/system/sssd.service; enabled; vendor preset: enabled)
     Active: inactive (dead)
  Condition: start condition failed at Tue 2025-01-07 20:12:37 EST; 15min ago
             ├─ ConditionPathExists=|/etc/sssd/sssd.conf was not met
             └─ ConditionDirectoryNotEmpty=|/etc/sssd/conf.d was not met

Jan 07 19:38:25 ubuntu20 systemd[1]: Condition check resulted in System Security Services Daemon being skipped.
Jan 07 20:12:37 ubuntu20 systemd[1]: Condition check resulted in System Security Services Daemon being skipped.

Agora sudoestá funcionando. Por que o SSSD interfere na sudofuncionalidade?

~$ journalctl -xeu sssd.service
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit sssd.service has finished successfully.
░░ 
░░ The job identifier is 199.
-- Boot 12bc6c7bf6f14ab8a277022b764c4482 --
Jan 07 19:27:30 ubuntu20 systemd[1]: Condition check resulted in System Security Services Daemon being skipped.
░░ Subject: A start job for unit sssd.service has finished successfully
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit sssd.service has finished successfully.
░░ 
░░ The job identifier is 183.
-- Boot 002196eb090942a8bf85fb57d3466b96 --
Jan 07 19:38:25 ubuntu20 systemd[1]: Condition check resulted in System Security Services Daemon being skipped.
░░ Subject: A start job for unit sssd.service has finished successfully
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit sssd.service has finished successfully.
░░ 
░░ The job identifier is 103.
Jan 07 20:12:37 ubuntu20 systemd[1]: Condition check resulted in System Security Services Daemon being skipped.
░░ Subject: A start job for unit sssd.service has finished successfully
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support

se um snap não inclui código-fonte, como posso atender aos requisitos de distribuição de uma licença como GPL v2? Incluir um link para o código-fonte no yaml conta como uma oferta por escrito? Sei que isso é mais uma questão de interpretação, mas apreciaria diferentes perspectivas da comunidade.

Fiquei de férias por 3 semanas e depois retornei. Mas é isso que estou vendo depois de selecionar o Windows Boot Manager no menu Grub.

Lembro que no último dia houve uma atualização do Windows.

Agora não consigo acessar o Windows, mas consigo acessar o Ubuntu.

O que devo fazer?

Eu tentei o Boot-Repair e é isso que ele está dizendo

LegacyWindows detected. Please enable BIOS-compatibility/CSM/Legacy mode in your UEFI firmware, and use this software from a live-CD (or live-USB).

E é isso que meu personalizador grub e parted afirmam. Não fiz nenhuma atualização do sistema ou instalação de nada... então estou um pouco fora de sintonia. /dev/nvme0n1p1 parece ter todas as partições ativas para inicializar.

Eu tentei este link , mas para isso preciso conseguir fazer login no prompt de comando do Windows 11. Eu tentei duas unidades USB diferentes e portas diferentes, mas estou enfrentando este problema agora:

Código de parada DRIVER PNP WATCHDOG

Abri um caso com o Suporte da Microsoft, mas eles não me ajudaram muito depois de duas sessões, exceto por me dizerem "não oferecemos suporte para inicialização dupla" ou "procure ajuda de um técnico local"

Eu realmente quero ir. Estou disposto a reinstalar o Windows 11 se necessário. O Ubuntu Linux está funcionando bem. O Boot-Repair não é bom.

sudo cat /boot/grub/grub.cfg | grep menuentry

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
  menuentry_id_option=""
export menuentry_id_option
menuentry "Ubuntu" --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-4cd02128-ebde-4341-ad07-3620623d26ec' {
menuentry "Ubuntu, with Linux 6.8.0-51-generic" --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.8.0-51-generic-advanced-4cd02128-ebde-4341-ad07-3620623d26ec' {
menuentry "Ubuntu, with Linux 6.8.0-51-generic (recovery mode)" --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.8.0-51-generic-recovery-4cd02128-ebde-4341-ad07-3620623d26ec' {
menuentry "Ubuntu, with Linux 6.2.0-33-generic" --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.2.0-33-generic-advanced-4cd02128-ebde-4341-ad07-3620623d26ec' {
menuentry "Ubuntu, with Linux 6.2.0-33-generic (recovery mode)" --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.2.0-33-generic-recovery-4cd02128-ebde-4341-ad07-3620623d26ec' {
menuentry 'UEFI Firmware Settings' $menuentry_id_option 'uefi-firmware' {

sudo atualização-grub

Sourcing file `/etc/default/grub'

Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...

Found linux image: /boot/vmlinuz-6.8.0-51-generic
Found initrd image: /boot/initrd.img-6.8.0-51-generic
Found linux image: /boot/vmlinuz-6.2.0-33-generic
Found initrd image: /boot/initrd.img-6.2.0-33-generic
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Found linux image: /boot/vmlinuz-6.8.0-51-generic
Found initrd image: /boot/initrd.img-6.8.0-51-generic
Found linux image: /boot/vmlinuz-6.2.0-33-generic
Found initrd image: /boot/initrd.img-6.2.0-33-generic
Memtest86+ needs a 16-bit boot, that is not available on EFI, exiting
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
done

Atualização 2 Consulte minha outra pergunta sobre o mesmo problema. Tenho várias unidades. A unidade SSD interna (Samsung 860 EVO-1 TB) na qual o Windows 11 Pro foi instalado finalmente morreu. Estava se deteriorando (sem nenhum aviso), mas finalmente morreu enquanto eu estava de férias. A instalação do Windows não é tão boa, ela simplesmente não avança por causa de hardware defeituoso (poderia ter escolhido espaço vazio em outras unidades). Só porque há um disco rígido morto, mas outras unidades estão lá com partições/espaço vazios - ele poderia ter avançado. Depois de remover o SSD com falha, consegui instalar o Windows 11 Pro novamente e voltar ao trabalho.

Minha versão do VBox é 7.1.4 hospedada pelo Windows 11 Home, o sistema operacional convidado é o Xubuntu Desktop 24.10. Quero experimentar o gerenciador de janelas Wayland. Depois de instalar tudo o que eu supostamente precisava, selecionei Xubuntu + Wayland na janela de login. A tela apenas piscou para mim uma vez e reapresentou a janela de login novamente. As outras seleções "Xfce4, Xubuntu Desktop, Ubuntu e Ubuntu Desktop" funcionaram. Estou esquecendo de alguma coisa, mas não sei o que é.

Tenho um arquivo .sh que tem isso.

Estou passando um inteiro para o arquivo em $0

...
period=20000
period=period+($0*1000)
echo "$period"
...

O que estou tentando fazer é que period = period + ($0 * 1000) a segunda linha está me dando um erro de sintaxe e eu quero saber como fazer isso corretamente.

Tentei usar (($0*1000)), mas não vi diferença.

Eu também tentei

smth=1000*$3
period=period+smth

e eu entendo

20000000+1000*