Bram's questions

Não estou recebendo miniaturas para imagens da Fujifilm RAF.

Tentei adicionar às /usr/share/thumbnailers/gdk-pixbuf-thumbnailer.thumbnailerentradas:

image/x-raf;image/x-fuji-raf;

Saí do Nautilus e excluí, .cache/thumbnails/mas ainda não vejo a geração de miniaturas para arquivos RAF.

O utilitário de arquivo reconhece os arquivos RAF perfeitamente:

$ file ~/Pictures/DSCF8520.RAF
/home/bram/Pictures/DSCF8520.RAF: Fujifilm RAF raw image data, format version 0201, camera GFX 50R

SO: Ubuntu 24.04.1 LTS

Tenho duas GPUs em meu laptop: GPU Radeon integrada e GPU NVIDIA discreta, conforme mostrado pelo inxi:

$ inxi -G
Graphics:
  Device-1: NVIDIA GA106M [GeForce RTX 3060 Mobile / Max-Q] driver: nvidia
    v: 535.86.05
  Device-2: AMD Cezanne [Radeon Vega Series / Radeon Mobile Series]
    driver: amdgpu v: kernel
  Device-3: Quanta HD User Facing type: USB driver: uvcvideo
  Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.8 driver: X:
    loaded: amdgpu,nvidia unloaded: fbdev,modesetting,nouveau,radeon,vesa
    dri: radeonsi gpu: amdgpu resolution: 1920x1080~144Hz
  API: OpenGL v: 4.6 Mesa 23.0.4-0ubuntu1~23.04.1 renderer: AMD Radeon
    Graphics (renoir LLVM 15.0.7 DRM 3.49 6.2.0-32-generic)

Mas se eu pedir clinfopara listar os drivers OpenCL, ele encontrará apenas um para NVIDIA, e não um para Radeon.

$ clinfo -l
Platform #0: NVIDIA CUDA
 `-- Device #0: NVIDIA GeForce RTX 3060 Laptop GPU

O que preciso fazer para tornar a Radeon utilizável para OpenCL?

Estou executando o Ubuntu 23.04 e X11.

Informações de DRM:

$ drm_info | grep Driver
├───Driver: amdgpu (AMD GPU) version 3.49.0 (20150101)
├───Driver: nvidia-drm (NVIDIA DRM driver) version 0.0.0 (20160202)

O Apport registrou uma falha /usr/bin/gnome-shellno meu sistema.

Posso descompactar o .crasharquivo que encontrei /var/crash/e dar uma olhada no core dump com gdb, que me dá:

(gdb) where
#0  __pthread_kill_implementation (no_tid=0, signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:44
#1  __pthread_kill_internal (signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:78
#2  __GI___pthread_kill (threadid=<optimized out>, signo=signo@entry=6) at ./nptl/pthread_kill.c:89
#3  0x00007f60a3a3c406 in __GI_raise (sig=6) at ../sysdeps/posix/raise.c:26
#4  0x0000555b78a65aea in  ()
#5  0x00007f60a3a3c4b0 in <signal handler called> () at /lib/x86_64-linux-gnu/libc.so.6
#6  __pthread_kill_implementation (no_tid=0, signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:44
#7  __pthread_kill_internal (signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:78
#8  __GI___pthread_kill (threadid=<optimized out>, signo=signo@entry=6) at ./nptl/pthread_kill.c:89
#9  0x00007f60a3a3c406 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#10 0x00007f60a3a2287c in __GI_abort () at ./stdlib/abort.c:79
#11 0x00007f60a4306d1e in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x00007f60a436e22e in g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x00007f60a3ed9336 in  () at /lib/x86_64-linux-gnu/libmutter-12.so.0
#14 0x00007f60a3efcc8c in  () at /lib/x86_64-linux-gnu/libmutter-12.so.0
#15 0x00007f60a3effdcd in  () at /lib/x86_64-linux-gnu/libmutter-12.so.0
#16 0x00007f60a434236f in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x00007f60a439d178 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007f60a4341bdf in g_main_loop_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007f60a3ebde19 in meta_context_run_main_loop () at /lib/x86_64-linux-gnu/libmutter-12.so.0
#20 0x0000555b78a64fa1 in  ()
#21 0x00007f60a3a23a90 in __libc_start_call_main (main=main@entry=0x555b78a64b10, argc=argc@entry=1, argv=argv@entry=0x7fff6a9da2c8)
    at ../sysdeps/nptl/libc_start_call_main.h:58
#22 0x00007f60a3a23b49 in __libc_start_main_impl
    (main=0x555b78a64b10, argc=1, argv=0x7fff6a9da2c8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff6a9da2b8) at ../csu/libc-start.c:360
#23 0x0000555b78a65275 in  ()

Então eu sei que é uma falha de asserção.

Mas como descubro qual afirmação falhou? Porque a pilha de chamadas tem informações limitadas. Não há argumentos listados para as chamadas de função, por exemplo

A mensagem de asserção pode ser recuperada de qualquer lugar nesses arquivos?

ApportVersion         Disassembly          InstallationMedia    ProcCpuinfoMinimal      separator                   ThreadStacktrace
Architecture          DisplayManager       JournalErrors        ProcCwd                 ShellJournal                Title
CasperMD5CheckResult  DistroRelease        _MarkForUpload       ProcEnviron             Signal                      Uname
CoreDump              ExecutablePath       monitors.xml         ProcMaps                SourcePackage               UpgradeStatus
CrashCounter          ExecutableTimestamp  Package              ProcStatus              Stacktrace                  UserGroups
CurrentDesktop        GsettingsChanges     PackageArchitecture  ProcVersionSignature    StacktraceAddressSignature
Date                  _HooksRun            ProblemType          Registers               StacktraceTop
Dependencies          InstallationDate     ProcCmdline          RelatedPackageVersions  Tags

Atualização 1

Por que os votos negativos? É uma pergunta simples... foi gerado um relatório de travamento de uma aplicação que teve uma falha de asserção. Como posso obter a mensagem de falha de asserção? Não consigo entender por que isso é votado negativamente.

Atualização 2

Conforme sugerido pelo comentário de Thomas: o texto da afirmação foi realmente registrado no diário. A execução journalctl -b -p5produziu esta entrada:

Apr 24 10:49:21 deca gnome-shell[97980]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed

O que significa que é mais fácil encontrar a causa no log do sistema atual do que no arquivo de travamento.

Atualização 3

Ok, agora fica realmente misterioso. Descobri que posso fazer com que o gdb baixe os símbolos de um servidor de depuração. E com isso, posso ver o conteúdo da mensagem assert.

E não combina com o do syslog!

falha na asserção: (window->display->focus_window != window)

(gdb) where
#0  __pthread_kill_implementation (no_tid=0, signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:44
#1  __pthread_kill_internal (signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:78
#2  __GI___pthread_kill (threadid=<optimized out>, signo=signo@entry=6) at ./nptl/pthread_kill.c:89
#3  0x00007f60a3a3c406 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#4  0x0000555b78a65aea in dump_gjs_stack_on_signal_handler (signo=6) at ../src/main.c:495
#5  0x00007f60a3a3c4b0 in <signal handler called> () at /lib/x86_64-linux-gnu/libc.so.6
#6  __pthread_kill_implementation (no_tid=0, signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:44
#7  __pthread_kill_internal (signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:78
#8  __GI___pthread_kill (threadid=<optimized out>, signo=signo@entry=6) at ./nptl/pthread_kill.c:89
#9  0x00007f60a3a3c406 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#10 0x00007f60a3a2287c in __GI_abort () at ./stdlib/abort.c:79
#11 0x00007f60a4306d1e in g_assertion_message
    (domain=domain@entry=0x7f60a3f87752 "libmutter", file=file@entry=0x7f60a3f9eb09 "../src/core/window.c", line=line@entry=1533, func=func@entry=0x7f60a3fa10d0 <__func__.53> "meta_window_unmanage", message=message@entry=0x555b7c8a2950 "assertion failed: (window->display->focus_window != window)") at ../../../glib/gtestutils.c:3450
#12 0x00007f60a436e22e in g_assertion_message_expr
    (domain=domain@entry=0x7f60a3f87752 "libmutter", file=file@entry=0x7f60a3f9eb09 "../src/core/window.c", line=line@entry=1533, func=func@entry=0x7f60a3fa10d0 <__func__.53> "meta_window_unmanage", expr=expr@entry=0x7f60a3fa0960 "window->display->focus_window != window") at ../../../glib/gtestutils.c:3476
#13 0x00007f60a3ed9336 in meta_window_unmanage (window=0x555b80df26b0, timestamp=<optimized out>) at ../src/core/window.c:1533
#14 0x00007f60a3efcc8c in meta_x11_display_handle_xevent (event=<optimized out>, x11_display=<optimized out>) at ../src/x11/events.c:1981
#15 xevent_func (xevent=0x7fff6a9d9ee0, data=0x555b7c1fdce0) at ../src/x11/events.c:2021
#16 0x00007f60a3effdcd in meta_x11_event_source_dispatch (source=0x555b7f14b0c0, callback=0x7f60a3efc410 <xevent_func>, user_data=0x555b7c1fdce0) at ../src/x11/meta-x11-event-source.c:64
#17 0x00007f60a434236f in g_main_dispatch (context=0x555b791a83b0) at ../../../glib/gmain.c:3460
#18 g_main_context_dispatch (context=0x555b791a83b0) at ../../../glib/gmain.c:4200
#19 0x00007f60a439d178 in g_main_context_iterate.constprop.0 (context=0x555b791a83b0, block=<optimized out>, dispatch=1, self=<optimized out>) at ../../../glib/gmain.c:4276
#20 0x00007f60a4341bdf in g_main_loop_run (loop=0x555b7b53a060) at ../../../glib/gmain.c:4479
#21 0x00007f60a3ebde19 in meta_context_run_main_loop (context=context@entry=0x555b791a6780, error=error@entry=0x7fff6a9da128) at ../src/core/meta-context.c:482
#22 0x0000555b78a64fa1 in main (argc=<optimized out>, argv=<optimized out>) at ../src/main.c:765

Eu quero criar um pacote fonte debian que seja adequado para vários lançamentos de sistema operacional.

Inicialmente, eu estava visando a cinética e tinha este formato de changelog:

gfxi (1.3-1) kinetic; urgency=medium

  * Add install and uninstall targets to Makefile.

...

Do manual :

 distributions lists one or more space-separated distributions where this version should be
       installed when it is uploaded; it is copied to the Distribution field in the .changes
       file.  distributions must be terminated by a semicolon (U+003B ‘;’).

Então mudei minha entrada no changelog para:

gfxi (1.3-2) jammy kinetic lunar; urgency=medium

  * Add jammy and lunar releases.
...

O debuild -Scomando é bem-sucedido, mas quando carrego o pacote de origem debian para meu PPA usando dput, o construtor retorna com:

Rejected:
Unable to find distroseries: jammy kinetic lunar
Further error processing not possible because of a critical previous error.

gfxi (1.3-2) jammy kinetic lunar; urgency=medium

  * Add jammy and lunar releases.

Estou lendo o manual incorretamente? Por que não consigo listar as versões do sistema operacional em meu arquivo changelog?

Eu tenho uma GPU RX580 conectada a um monitor (AORUS FO48U) com alto-falantes embutidos que funcionam bem com Intel iGPU.

Quando uso a GPU AMD, não consigo selecionar um dispositivo de áudio HDMI nas configurações.

A única saída que pode ser selecionada é o áudio embutido S/PDIF de saída digital.

Informações de áudio:

$ inxi -A
Audio:
  Device-1: Intel driver: snd_hda_intel
  Device-2: AMD Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]
    driver: snd_hda_intel
  Sound Server-1: ALSA v: k5.15.0-58-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes

Informações gráficas:

$ inxi -G
Graphics:
  Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
    driver: amdgpu v: kernel
  Display: server: X.Org v: 1.21.1.3 driver: X: loaded: amdgpu,ati
    unloaded: fbdev,modesetting,radeon,vesa gpu: amdgpu
    resolution: 1920x1080~60Hz
  OpenGL: renderer: AMD Radeon RX 580 Series (polaris10 LLVM 15.0.6 DRM
    3.42 5.15.0-58-generic)
    v: 4.6 Mesa 22.2.5

SO: Ubuntu 22.04

GPU: RX580

Driver: amdgpu de código aberto

Processador: 12600k

Exibição: AORUS FO48U

O dmesg só mostra as entradas encontradas?

$ dmesg  | grep -i hdmi
[    0.157772] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[    3.898404] input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input14
[    3.898424] input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input15
[    3.898438] input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input16
[    3.898460] input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input17
[    3.898474] input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input18
[    3.898486] input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input19

Atualizar

Durante a inicialização, o kernel relata:

snd_hda_intel 0000:01:00.1: bound 0000:01:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])

Se eu disser ao meu computador para desligar, ele reiniciará imediatamente em vez de desligar.

Isso é uma coisa do BIOS ou um problema do Ubuntu?

Eu tentei olhar na minha bios ASUS, mas não consigo encontrar uma opção para isso.

Ubuntu 21.10 no i5-12600K.

Eu tenho um kernel construído a partir da fonte:

Linux deca 5.16.5bram #13 SMP PREEMPT Wed Feb 9 15:08:08 PST 2022 x86_64 x86_64 x86_64 GNU/Linux

NOTA: A suspensão do sistema funciona conforme o esperado e desliga todos os ventiladores.

ATUALIZAR

$ sudo shutdown -P nowapresenta o mesmo comportamento.

$ sudo systemctl poweroff --forcenão funciona: ele tenta desligar, mas fica preso depois de alternar para o console de texto e fica lá.

ATUALIZAÇÃO 2

Definir a configuração do BIOS "Fast Boot" para desativado, não ajudou.

Quando tento modprobe nouveau, sou recebido com:

modprobe: ERROR: ../libkmod/libkmod-module.c:838 kmod_module_insert_module() could not find module by name='off'
modprobe: ERROR: could not insert 'off': Unknown symbol in module, or unknown parameter (see dmesg)

Não há lista negra para nouveau, /etc/modprobe.d/então não sei por que isso falha?

bram@Workstation:/etc/modprobe.d$ grep off *
blacklist-rare-network.conf:alias net-pf-3 off
blacklist-rare-network.conf:alias net-pf-6 off
blacklist-rare-network.conf:alias net-pf-9 off
blacklist-rare-network.conf:alias net-pf-11 off
blacklist-rare-network.conf:alias net-pf-12 off
blacklist-rare-network.conf:alias net-pf-19 off
blacklist-rare-network.conf:alias net-pf-21 off
blacklist-rare-network.conf:alias net-pf-36 off

A razão pela qual eu quero o nouveau é que eu gostaria de usá-lo para alternar os modos de vídeo para mim, para o framebuffer linux.

Eu não estou tentando executar o X nele.

Atualmente, o framebuffer EFI VGA não me permite alternar entre os modos.

kernel: 5.13.0-28-genérico

SO: Ubuntu: 21.10

GPU: RTX 3070

Eu tenho uma nova instalação 21.10 em um sistema Alder Lake (12ª geração intel.)

Percebi que a resolução da minha tela não era nativa e não consegui alterá-la.

Examinei o arquivo de log do Xorg, mas não acho que esteja usando um driver Intel?

Existe algo especial que preciso fazer para usar uma GPU Intel da CPU Alder Lake?

$ cat /var/log/Xorg.0.log
[    22.164] (--) Log file renamed from "/var/log/Xorg.pid-1122.log" to "/var/log/Xorg.0.log"
[    22.164] 
X.Org X Server 1.20.13
X Protocol Version 11, Revision 0
[    22.164] Build Operating System: linux Ubuntu
[    22.164] Current Operating System: Linux deca 5.13.0-28-generic #31-Ubuntu SMP Thu Jan 13 17:41:06 UTC 2022 x86_64
[    22.164] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=51edf4df-659c-4b90-9fcd-2e45ca0064db ro intel_pstate=passive
[    22.164] Build Date: 14 December 2021  02:07:57PM
[    22.164] xorg-server 2:1.20.13-1ubuntu1.1 (For technical support please see http://www.ubuntu.com/support) 
[    22.164] Current version of pixman: 0.40.0
[    22.164]    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
[    22.164] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    22.164] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Feb  2 17:23:36 2022
[    22.164] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    22.165] (==) No Layout section.  Using the first Screen section.
[    22.165] (==) No screen section available. Using defaults.
[    22.165] (**) |-->Screen "Default Screen Section" (0)
[    22.165] (**) |   |-->Monitor "<default monitor>"
[    22.165] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
[    22.165] (==) Automatically adding devices
[    22.165] (==) Automatically enabling devices
[    22.165] (==) Automatically adding GPU devices
[    22.165] (==) Automatically binding GPU devices
[    22.165] (==) Max clients allowed: 256, resource mask: 0x1fffff
[    22.166] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[    22.166]    Entry deleted from font path.
[    22.166] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[    22.166]    Entry deleted from font path.
[    22.166] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[    22.166]    Entry deleted from font path.
[    22.166] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[    22.166]    Entry deleted from font path.
[    22.166] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[    22.166]    Entry deleted from font path.
[    22.166] (==) FontPath set to:
    /usr/share/fonts/X11/misc,
    /usr/share/fonts/X11/Type1,
    built-ins
[    22.166] (==) ModulePath set to "/usr/lib/xorg/modules"
[    22.166] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
[    22.166] (II) Loader magic: 0x5638467fd020
[    22.166] (II) Module ABI versions:
[    22.166]    X.Org ANSI C Emulation: 0.4
[    22.166]    X.Org Video Driver: 24.1
[    22.166]    X.Org XInput driver : 24.1
[    22.166]    X.Org Server Extension : 10.0
[    22.166] (++) using VT number 2

[    22.167] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_31
[    22.168] (--) PCI:*(0@0:2:0) 8086:4680:1043:8694 rev 12, Mem @ 0x6002000000/16777216, 0x4000000000/268435456, I/O @ 0x00006000/64, BIOS @ 0x????????/131072
[    22.168] (II) LoadModule: "glx"
[    22.168] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    22.170] (II) Module glx: vendor="X.Org Foundation"
[    22.170]    compiled for 1.20.13, module version = 1.0.0
[    22.170]    ABI class: X.Org Server Extension, version 10.0
[    22.170] (==) Matched modesetting as autoconfigured driver 0
[    22.170] (==) Matched fbdev as autoconfigured driver 1
[    22.170] (==) Matched vesa as autoconfigured driver 2
[    22.170] (==) Assigned the driver to the xf86ConfigLayout
[    22.170] (II) LoadModule: "modesetting"
[    22.170] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[    22.170] (II) Module modesetting: vendor="X.Org Foundation"
[    22.170]    compiled for 1.20.13, module version = 1.20.13
[    22.170]    Module class: X.Org Video Driver
[    22.170]    ABI class: X.Org Video Driver, version 24.1
[    22.170] (II) LoadModule: "fbdev"
[    22.170] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[    22.170] (II) Module fbdev: vendor="X.Org Foundation"
[    22.170]    compiled for 1.20.13, module version = 0.5.0
[    22.171]    Module class: X.Org Video Driver
[    22.171]    ABI class: X.Org Video Driver, version 24.1
[    22.171] (II) LoadModule: "vesa"
[    22.171] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[    22.171] (II) Module vesa: vendor="X.Org Foundation"
[    22.171]    compiled for 1.20.13, module version = 2.5.0
[    22.171]    Module class: X.Org Video Driver
[    22.171]    ABI class: X.Org Video Driver, version 24.1
[    22.171] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    22.171] (II) FBDEV: driver for framebuffer: fbdev
[    22.171] (II) VESA: driver for VESA chipsets: vesa
[    22.171] (EE) open /dev/dri/card0: No such file or directory
[    22.171] (WW) Falling back to old probe method for modesetting
[    22.171] (EE) open /dev/dri/card0: No such file or directory
[    22.171] (II) Loading sub module "fbdevhw"
[    22.171] (II) LoadModule: "fbdevhw"
[    22.171] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[    22.171] (II) Module fbdevhw: vendor="X.Org Foundation"
[    22.171]    compiled for 1.20.13, module version = 0.0.2
[    22.171]    ABI class: X.Org Video Driver, version 24.1
[    22.171] (**) FBDEV(1): claimed PCI slot 0@0:2:0
[    22.171] (II) FBDEV(1): using default device
[    22.171] (EE) Screen 0 deleted because of no matching config section.
[    22.171] (II) UnloadModule: "modesetting"
[    22.171] (II) FBDEV(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
[    22.171] (==) FBDEV(0): Depth 24, (==) framebuffer bpp 32
[    22.171] (==) FBDEV(0): RGB weight 888
[    22.171] (==) FBDEV(0): Default visual is TrueColor
[    22.171] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
[    22.171] (II) FBDEV(0): hardware: EFI VGA (video memory: 3072kB)
[    22.171] (II) FBDEV(0): checking modes against framebuffer device...
[    22.171] (II) FBDEV(0): checking modes against monitor...
[    22.171] (II) FBDEV(0): Virtual size is 1024x768 (pitch 1024)
[    22.171] (**) FBDEV(0):  Built-in mode "current": 78.7 MHz, 59.9 kHz, 75.7 Hz
[    22.171] (II) FBDEV(0): Modeline "current"x0.0   78.65  1024 1056 1184 1312  768 772 776 792 -hsync -vsync -csync (59.9 kHz b)
[    22.171] (==) FBDEV(0): DPI set to (96, 96)
[    22.171] (II) Loading sub module "fb"
[    22.171] (II) LoadModule: "fb"
[    22.171] (II) Loading /usr/lib/xorg/modules/libfb.so
[    22.171] (II) Module fb: vendor="X.Org Foundation"
[    22.171]    compiled for 1.20.13, module version = 1.0.0
[    22.171]    ABI class: X.Org ANSI C Emulation, version 0.4
[    22.171] (**) FBDEV(0): using shadow framebuffer
[    22.171] (II) Loading sub module "shadow"
[    22.171] (II) LoadModule: "shadow"
[    22.171] (II) Loading /usr/lib/xorg/modules/libshadow.so
[    22.172] (II) Module shadow: vendor="X.Org Foundation"
[    22.172]    compiled for 1.20.13, module version = 1.1.0
[    22.172]    ABI class: X.Org ANSI C Emulation, version 0.4
[    22.172] (II) UnloadModule: "vesa"
[    22.172] (II) Unloading vesa
[    22.172] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by kernel - disabling)
[    22.172] (==) FBDEV(0): Backing store enabled
[    22.172] (==) FBDEV(0): DPMS enabled
[    22.173] (II) Initializing extension Generic Event Extension
[    22.173] (II) Initializing extension SHAPE
[    22.173] (II) Initializing extension MIT-SHM
[    22.173] (II) Initializing extension XInputExtension
[    22.173] (II) Initializing extension XTEST
[    22.173] (II) Initializing extension BIG-REQUESTS
[    22.173] (II) Initializing extension SYNC
[    22.173] (II) Initializing extension XKEYBOARD
[    22.173] (II) Initializing extension XC-MISC
[    22.173] (II) Initializing extension SECURITY
[    22.173] (II) Initializing extension XFIXES
[    22.173] (II) Initializing extension RENDER
[    22.173] (II) Initializing extension RANDR
[    22.173] (II) Initializing extension COMPOSITE
[    22.173] (II) Initializing extension DAMAGE
[    22.173] (II) Initializing extension MIT-SCREEN-SAVER
[    22.173] (II) Initializing extension DOUBLE-BUFFER
[    22.174] (II) Initializing extension RECORD
[    22.174] (II) Initializing extension DPMS
[    22.174] (II) Initializing extension Present
[    22.174] (II) Initializing extension DRI3
[    22.174] (II) Initializing extension X-Resource
[    22.174] (II) Initializing extension XVideo
[    22.174] (II) Initializing extension XVideo-MotionCompensation
[    22.174] (II) Initializing extension SELinux
[    22.174] (II) SELinux: Disabled on system
[    22.174] (II) Initializing extension GLX
[    22.174] (II) AIGLX: Screen 0 is not DRI2 capable
[    22.209] (II) IGLX: Loaded and initialized swrast
[    22.209] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[    22.209] (II) Initializing extension XFree86-VidModeExtension
[    22.209] (II) Initializing extension XFree86-DGA
[    22.209] (II) Initializing extension XFree86-DRI
[    22.209] (II) Initializing extension DRI2
[    22.224] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[    22.224] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[    22.224] (II) LoadModule: "libinput"
[    22.224] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
[    22.225] (II) Module libinput: vendor="X.Org Foundation"
[    22.225]    compiled for 1.20.13, module version = 1.1.0
[    22.225]    Module class: X.Org XInput Driver
[    22.225]    ABI class: X.Org XInput driver, version 24.1
[    22.225] (II) Using input driver 'libinput' for 'Power Button'
[    22.225] (II) systemd-logind: got fd for /dev/input/event2 13:66 fd 24 paused 0
[    22.225] (**) Power Button: always reports core events
[    22.225] (**) Option "Device" "/dev/input/event2"
[    22.226] (**) Option "_source" "server/udev"
[    22.228] (II) event2  - Power Button: is tagged by udev as: Keyboard
[    22.228] (II) event2  - Power Button: device is a keyboard
[    22.228] (II) event2  - Power Button: device removed
[    22.228] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2"
[    22.228] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[    22.228] (**) Option "xkb_model" "pc105"
[    22.228] (**) Option "xkb_layout" "us"
[    22.228] (II) event2  - Power Button: is tagged by udev as: Keyboard
[    22.228] (II) event2  - Power Button: device is a keyboard
[    22.228] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[    22.228] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[    22.228] (II) Using input driver 'libinput' for 'Power Button'
[    22.229] (II) systemd-logind: got fd for /dev/input/event1 13:65 fd 27 paused 0
[    22.229] (**) Power Button: always reports core events
[    22.229] (**) Option "Device" "/dev/input/event1"
[    22.229] (**) Option "_source" "server/udev"
[    22.229] (II) event1  - Power Button: is tagged by udev as: Keyboard
[    22.229] (II) event1  - Power Button: device is a keyboard
[    22.229] (II) event1  - Power Button: device removed
[    22.229] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1/event1"
[    22.229] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[    22.229] (**) Option "xkb_model" "pc105"
[    22.229] (**) Option "xkb_layout" "us"
[    22.229] (II) event1  - Power Button: is tagged by udev as: Keyboard
[    22.229] (II) event1  - Power Button: device is a keyboard
[    22.229] (II) config/udev: Adding input device Sleep Button (/dev/input/event0)
[    22.229] (**) Sleep Button: Applying InputClass "libinput keyboard catchall"
[    22.229] (II) Using input driver 'libinput' for 'Sleep Button'
[    22.230] (II) systemd-logind: got fd for /dev/input/event0 13:64 fd 28 paused 0
[    22.230] (**) Sleep Button: always reports core events
[    22.230] (**) Option "Device" "/dev/input/event0"
[    22.230] (**) Option "_source" "server/udev"
[    22.230] (II) event0  - Sleep Button: is tagged by udev as: Keyboard
[    22.230] (II) event0  - Sleep Button: device is a keyboard
[    22.230] (II) event0  - Sleep Button: device removed
[    22.230] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0/event0"
[    22.230] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 8)
[    22.230] (**) Option "xkb_model" "pc105"
[    22.230] (**) Option "xkb_layout" "us"
[    22.230] (II) event0  - Sleep Button: is tagged by udev as: Keyboard
[    22.230] (II) event0  - Sleep Button: device is a keyboard
[    22.230] (II) config/udev: Adding input device PixArt USB Optical Mouse (/dev/input/event3)
[    22.230] (**) PixArt USB Optical Mouse: Applying InputClass "libinput pointer catchall"
[    22.230] (II) Using input driver 'libinput' for 'PixArt USB Optical Mouse'
[    22.231] (II) systemd-logind: got fd for /dev/input/event3 13:67 fd 29 paused 0
[    22.231] (**) PixArt USB Optical Mouse: always reports core events
[    22.231] (**) Option "Device" "/dev/input/event3"
[    22.231] (**) Option "_source" "server/udev"
[    22.231] (II) event3  - PixArt USB Optical Mouse: is tagged by udev as: Mouse
[    22.231] (II) event3  - PixArt USB Optical Mouse: device set to 1000 DPI
[    22.231] (II) event3  - PixArt USB Optical Mouse: device is a pointer
[    22.231] (II) event3  - PixArt USB Optical Mouse: device removed
[    22.231] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.0/0003:093A:2510.0002/input/input3/event3"
[    22.231] (II) XINPUT: Adding extended input device "PixArt USB Optical Mouse" (type: MOUSE, id 9)
[    22.231] (**) Option "AccelerationScheme" "none"
[    22.231] (**) PixArt USB Optical Mouse: (accel) selected scheme none/0
[    22.231] (**) PixArt USB Optical Mouse: (accel) acceleration factor: 2.000
[    22.231] (**) PixArt USB Optical Mouse: (accel) acceleration threshold: 4
[    22.232] (II) event3  - PixArt USB Optical Mouse: is tagged by udev as: Mouse
[    22.232] (II) event3  - PixArt USB Optical Mouse: device set to 1000 DPI
[    22.232] (II) event3  - PixArt USB Optical Mouse: device is a pointer
[    22.232] (II) config/udev: Adding input device PixArt USB Optical Mouse (/dev/input/mouse0)
[    22.232] (II) No input driver specified, ignoring this device.
[    22.232] (II) This device may have been added with another device file.
[    22.232] (II) config/udev: Adding input device Eee PC WMI hotkeys (/dev/input/event4)
[    22.232] (**) Eee PC WMI hotkeys: Applying InputClass "libinput keyboard catchall"
[    22.232] (II) Using input driver 'libinput' for 'Eee PC WMI hotkeys'
[    22.232] (II) systemd-logind: got fd for /dev/input/event4 13:68 fd 30 paused 0
[    22.232] (**) Eee PC WMI hotkeys: always reports core events
[    22.232] (**) Option "Device" "/dev/input/event4"
[    22.232] (**) Option "_source" "server/udev"
[    22.232] (II) event4  - Eee PC WMI hotkeys: is tagged by udev as: Keyboard
[    22.232] (II) event4  - Eee PC WMI hotkeys: device is a keyboard
[    22.232] (II) event4  - Eee PC WMI hotkeys: device removed
[    22.232] (**) Option "config_info" "udev:/sys/devices/platform/eeepc-wmi/input/input4/event4"
[    22.232] (II) XINPUT: Adding extended input device "Eee PC WMI hotkeys" (type: KEYBOARD, id 10)
[    22.233] (**) Option "xkb_model" "pc105"
[    22.233] (**) Option "xkb_layout" "us"
[    22.233] (II) event4  - Eee PC WMI hotkeys: is tagged by udev as: Keyboard
[    22.233] (II) event4  - Eee PC WMI hotkeys: device is a keyboard
[    30.557] (II) config/udev: Adding input device SN TECH    USBGamingMouse (/dev/input/mouse1)
[    30.557] (II) No input driver specified, ignoring this device.
[    30.558] (II) This device may have been added with another device file.
[    30.582] (II) config/udev: Adding input device SN TECH    USBGamingMouse (/dev/input/event5)
[    30.583] (**) SN TECH    USBGamingMouse: Applying InputClass "libinput keyboard catchall"
[    30.583] (II) Using input driver 'libinput' for 'SN TECH    USBGamingMouse'
[    30.583] (II) systemd-logind: got fd for /dev/input/event5 13:69 fd 45 paused 0
[    30.583] (**) SN TECH    USBGamingMouse: always reports core events
[    30.583] (**) Option "Device" "/dev/input/event5"
[    30.583] (**) Option "_source" "server/udev"
[    30.585] (II) event5  - SN TECH    USBGamingMouse: is tagged by udev as: Keyboard
[    30.585] (II) event5  - SN TECH    USBGamingMouse: device is a keyboard
[    30.586] (II) event5  - SN TECH    USBGamingMouse: device removed
[    30.586] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/0003:258A:0013.0003/input/input5/event5"
[    30.586] (II) XINPUT: Adding extended input device "SN TECH    USBGamingMouse" (type: KEYBOARD, id 11)
[    30.586] (**) Option "xkb_model" "pc105"
[    30.586] (**) Option "xkb_layout" "us"
[    30.586] (WW) Option "xkb_variant" requires a string value
[    30.586] (WW) Option "xkb_options" requires a string value
[    30.587] (II) event5  - SN TECH    USBGamingMouse: is tagged by udev as: Keyboard
[    30.587] (II) event5  - SN TECH    USBGamingMouse: device is a keyboard
[    30.618] (II) config/udev: Adding input device SN TECH    USBGamingMouse (/dev/input/event6)
[    30.618] (**) SN TECH    USBGamingMouse: Applying InputClass "libinput pointer catchall"
[    30.618] (II) Using input driver 'libinput' for 'SN TECH    USBGamingMouse'
[    30.643] (II) systemd-logind: got fd for /dev/input/event6 13:70 fd 46 paused 0
[    30.643] (**) SN TECH    USBGamingMouse: always reports core events
[    30.643] (**) Option "Device" "/dev/input/event6"
[    30.643] (**) Option "_source" "server/udev"
[    30.644] (II) event6  - SN TECH    USBGamingMouse: is tagged by udev as: Mouse
[    30.644] (II) event6  - SN TECH    USBGamingMouse: device is a pointer
[    30.644] (II) event6  - SN TECH    USBGamingMouse: device removed
[    30.644] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.1/0003:258A:0013.0004/input/input6/event6"
[    30.644] (II) XINPUT: Adding extended input device "SN TECH    USBGamingMouse" (type: MOUSE, id 12)
[    30.644] (**) Option "AccelerationScheme" "none"
[    30.644] (**) SN TECH    USBGamingMouse: (accel) selected scheme none/0
[    30.644] (**) SN TECH    USBGamingMouse: (accel) acceleration factor: 2.000
[    30.644] (**) SN TECH    USBGamingMouse: (accel) acceleration threshold: 4
[    30.645] (II) event6  - SN TECH    USBGamingMouse: is tagged by udev as: Mouse
[    30.645] (II) event6  - SN TECH    USBGamingMouse: device is a pointer
[    30.648] (II) config/udev: Adding input device SN TECH    USBGamingMouse Keyboard (/dev/input/event8)
[    30.648] (**) SN TECH    USBGamingMouse Keyboard: Applying InputClass "libinput keyboard catchall"
[    30.648] (II) Using input driver 'libinput' for 'SN TECH    USBGamingMouse Keyboard'
[    30.649] (II) systemd-logind: got fd for /dev/input/event8 13:72 fd 47 paused 0
[    30.649] (**) SN TECH    USBGamingMouse Keyboard: always reports core events
[    30.649] (**) Option "Device" "/dev/input/event8"
[    30.649] (**) Option "_source" "server/udev"
[    30.650] (II) event8  - SN TECH    USBGamingMouse Keyboard: is tagged by udev as: Keyboard
[    30.650] (II) event8  - SN TECH    USBGamingMouse Keyboard: device is a keyboard
[    30.650] (II) event8  - SN TECH    USBGamingMouse Keyboard: device removed
[    30.650] (II) libinput: SN TECH    USBGamingMouse Keyboard: needs a virtual subdevice
[    30.650] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.1/0003:258A:0013.0004/input/input8/event8"
[    30.650] (II) XINPUT: Adding extended input device "SN TECH    USBGamingMouse Keyboard" (type: MOUSE, id 13)
[    30.650] (**) Option "AccelerationScheme" "none"
[    30.651] (**) SN TECH    USBGamingMouse Keyboard: (accel) selected scheme none/0
[    30.651] (**) SN TECH    USBGamingMouse Keyboard: (accel) acceleration factor: 2.000
[    30.651] (**) SN TECH    USBGamingMouse Keyboard: (accel) acceleration threshold: 4
[    30.652] (II) event8  - SN TECH    USBGamingMouse Keyboard: is tagged by udev as: Keyboard
[    30.652] (II) event8  - SN TECH    USBGamingMouse Keyboard: device is a keyboard
[    30.652] (**) SN TECH    USBGamingMouse Keyboard: Applying InputClass "libinput keyboard catchall"
[    30.652] (II) Using input driver 'libinput' for 'SN TECH    USBGamingMouse Keyboard'
[    30.652] (II) systemd-logind: returning pre-existing fd for /dev/input/event8 13:72
[    30.652] (**) SN TECH    USBGamingMouse Keyboard: always reports core events
[    30.652] (**) Option "Device" "/dev/input/event8"
[    30.652] (**) Option "_source" "_driver/libinput"
[    30.653] (II) libinput: SN TECH    USBGamingMouse Keyboard: is a virtual subdevice
[    30.653] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.1/0003:258A:0013.0004/input/input8/event8"
[    30.653] (II) XINPUT: Adding extended input device "SN TECH    USBGamingMouse Keyboard" (type: KEYBOARD, id 14)
[    30.653] (**) Option "xkb_model" "pc105"
[    30.653] (**) Option "xkb_layout" "us"
[    30.653] (WW) Option "xkb_variant" requires a string value
[    30.653] (WW) Option "xkb_options" requires a string value
[    30.653] (II) config/udev: Adding input device SN TECH    USBGamingMouse (/dev/input/event7)
[    30.653] (II) No input driver specified, ignoring this device.
[    30.653] (II) This device may have been added with another device file.
[    64.629] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event10)
[    64.629] (II) No input driver specified, ignoring this device.
[    64.629] (II) This device may have been added with another device file.
[    64.637] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event13)
[    64.637] (II) No input driver specified, ignoring this device.
[    64.637] (II) This device may have been added with another device file.
[    64.637] (II) config/udev: Adding input device HDA Intel PCH Line Out (/dev/input/event12)
[    64.637] (II) No input driver specified, ignoring this device.
[    64.637] (II) This device may have been added with another device file.
[    64.638] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event9)
[    64.638] (II) No input driver specified, ignoring this device.
[    64.638] (II) This device may have been added with another device file.
[    64.638] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event11)
[    64.638] (II) No input driver specified, ignoring this device.
[    64.638] (II) This device may have been added with another device file.
[ 59082.141] (EE) event5  - SN TECH    USBGamingMouse: client bug: event processing lagging behind by 33ms, your system is too slow
[ 59270.876] (EE) event5  - SN TECH    USBGamingMouse: client bug: event processing lagging behind by 16ms, your system is too slow
[ 59290.510] (EE) event5  - SN TECH    USBGamingMouse: client bug: event processing lagging behind by 30ms, your system is too slow
[ 59933.146] (EE) event5  - SN TECH    USBGamingMouse: client bug: event processing lagging behind by 26ms, your system is too slow
[ 60146.789] (EE) event5  - SN TECH    USBGamingMouse: client bug: event processing lagging behind by 25ms, your system is too slow
[ 60146.789] (EE) event5  - SN TECH    USBGamingMouse: WARNING: log rate limit exceeded (5 msgs per 60min). Discarding future messages.

Não há drivers adicionais que eu possa instalar, veja:

Minha CPU i5-11600K está usando a escala de frequência intel_pstate .

Por padrão, o driver está no modo "ativo" e acelerará TODOS os 6 núcleos físicos, mesmo que haja apenas trabalho para um núcleo.

Para corrigir isso, eu faço:

# echo "passive" >  /sys/devices/system/cpu/intel_pstate/status

Mas após uma reinicialização, essa configuração desaparece novamente.

Como posso definir permanentemente o modo intel_pstate para passive?

Parece haver um problema libpulse-devno Ubuntu 21.10 porque se eu quiser instalar o libsdl2-dev em um sistema totalmente atualizado, recebo:

Os seguintes pacotes têm dependências não atendidas:

libpulse-dev : Depende: libpulse0 (= 1:15.0+dfsg1-1ubuntu2) mas 1:15.0+dfsg1-1ubuntu2.1 deve ser instalado

# dpkg --get-selections | grep hold
root@gamer2:/# apt update
Hit:1 https://repo.steampowered.com/steam stable InRelease
Hit:2 http://ca.archive.ubuntu.com/ubuntu impish InRelease                             
Hit:3 http://ca.archive.ubuntu.com/ubuntu impish-updates InRelease                     
Hit:4 http://security.ubuntu.com/ubuntu impish-security InRelease
Hit:5 http://ca.archive.ubuntu.com/ubuntu impish-backports InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
root@gamer2:/# apt dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@gamer2:/# apt install libsdl2-dev
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help resolve the situation:

The following packages have unmet dependencies:
 libpulse-dev : Depends: libpulse0 (= 1:15.0+dfsg1-1ubuntu2) but 1:15.0+dfsg1-1ubuntu2.1 is to be installed
                Depends: libpulse-mainloop-glib0 (= 1:15.0+dfsg1-1ubuntu2) but 1:15.0+dfsg1-1ubuntu2.1 is to be installed
E: Unable to correct problems, you have held broken packages.
root@gamer2:/# dpkg --get-selections | grep hold
root@gamer2:/# 

Como resolvo isso?

Isso está em uma nova instalação do 64b ubuntu21.10.

ATUALIZAR

# apt-cache policy libpulse-dev
libpulse-dev:
  Installed: (none)
  Candidate: 1:15.0+dfsg1-1ubuntu2
  Version table:
     1:15.0+dfsg1-1ubuntu2.2 1 (phased 20%)
        500 http://ca.archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages
     1:15.0+dfsg1-1ubuntu2 500
        500 http://ca.archive.ubuntu.com/ubuntu impish/main amd64 Packages

Versão, kernel e arquitetura do Ubuntu:

root@gamer2:/# cat /etc/issue
Ubuntu 21.10 \n \l

root@gamer2:/# uname -a
Linux gamer2 5.13.0-22-generic #22-Ubuntu SMP Fri Nov 5 13:21:36 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

ATUALIZAÇÃO 2

Parece obter libpulse0 de impish, mas libpulse-dev de impish-updates, mas por quê?

root@gamer2:/# apt-cache policy libpulse0
libpulse0:
  Installed: 1:15.0+dfsg1-1ubuntu2.1
  Candidate: 1:15.0+dfsg1-1ubuntu2.1
  Version table:
     1:15.0+dfsg1-1ubuntu2.2 1 (phased 20%)
        500 http://ca.archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages
 *** 1:15.0+dfsg1-1ubuntu2.1 100
        100 /var/lib/dpkg/status
     1:15.0+dfsg1-1ubuntu2 500
        500 http://ca.archive.ubuntu.com/ubuntu impish/main amd64 Packages
root@gamer2:/# apt install libpulse0
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
libpulse0 is already the newest version (1:15.0+dfsg1-1ubuntu2.1).
libpulse0 set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

ATUALIZAÇÃO 3

Este PC não possui repositórios não padrão, nem nunca teve repositórios não padrão configurados.

Não há retenções:

$ apt-mark showhold
$ 

Minha máquina 21.10 tem o Steam instalado e o steam vem com o emulador Proton . A Valve chama isso de "Steam Play".

Com isso, posso jogar jogos do Windows que recebo do Steam no Ubuntu, muito bem. Mesmo que o editor não tenha publicado um binário linux.

Meus filhos gostam do Roblox e gostariam de jogar isso no Ubuntu.

Mas o Roblox não tem cliente Linux. E o Roblox não está disponível no Steam.

Existe uma maneira de aproveitar o emulador Proton que vem com o Steam, para rodar o Roblox?

Como alternativa, devo instalar um emulador separado para ele? se eu fizer isso, ele entrará em conflito com o Proton que já está presente no sistema para o Steam?

Como quero que meus binários sejam executados em distribuições mais antigas , decidi construir um binário vinculado estaticamente.

Minha aplicação depende do libhid-hidraw e através disso, do libudev .

Eu tenho os pacotes de desenvolvimento instalados:

sudo apt install libudev-dev libhidapi-dev

Quando tento vincular, recebo este erro:

cc -g -Wall -Wextra -static daemon/turboledzd.c -o daemon/turboledzd -lhidapi-hidraw -ludev
/usr/bin/ld: cannot find -ludev
collect2: error: ld returned 1 exit status

No meu sistema, há um libhidapi-hidraw.aarquivo presente:

$ dpkg -S hidraw.a
libhidapi-dev:amd64: /usr/lib/x86_64-linux-gnu/libhidapi-hidraw.a

Mas nenhuma biblioteca estática para udev:

$ dpkg -S libudev.
libudev1:i386: /usr/lib/i386-linux-gnu/libudev.so.1
libudev-dev:amd64: /usr/lib/x86_64-linux-gnu/pkgconfig/libudev.pc
python3-pyudev: /usr/lib/python3/dist-packages/pyudev/_ctypeslib/libudev.py
libudev1:amd64: /usr/lib/x86_64-linux-gnu/libudev.so.1.7.1
libudev-dev:amd64: /usr/lib/x86_64-linux-gnu/libudev.so
libudev1:amd64: /usr/lib/x86_64-linux-gnu/libudev.so.1
libudev-dev:amd64: /usr/include/libudev.h
libudev1:i386: /usr/lib/i386-linux-gnu/libudev.so.1.7.1
libudev-dev:amd64: /usr/share/man/man3/libudev.3.gz

Qual pacote do Ubuntu conterá a libudev.abiblioteca?

Não entendo por que um binário construído em 21.10 não é compatível com um sistema 21.04.

O binário está vinculado ao libc.so.6qual também está disponível na versão 21.04 do sistema operacional.

Mesmo binário, no sistema 21.10:

$ ldd turboledzd
    linux-vdso.so.1 (0x00007ffdc2595000)
    libhidapi-hidraw.so.0 => /lib/x86_64-linux-gnu/libhidapi-hidraw.so.0 (0x00007fdd64057000)
    libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fdd63e2f000)
    libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x00007fdd63e06000)
    /lib64/ld-linux-x86-64.so.2 (0x00007fdd64085000)

E no sistema 21.04:

$ ldd turboledzd 
./turboledzd: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by ./turboledzd)
    linux-vdso.so.1 (0x00007fff9c570000)
    libhidapi-hidraw.so.0 => /lib/x86_64-linux-gnu/libhidapi-hidraw.so.0 (0x00007f37ec402000)
    libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f37ec216000)
    libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x00007f37ec1ed000)
    /lib64/ld-linux-x86-64.so.2 (0x00007f37ec423000)
    libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f37ec1cb000)

Minha pergunta:

Se libc.so.6a partir de 21.04 não for compatível com a libc.so.6partir de 21.10, por que a libc em 21.10 libc.so.7não é chamada?

Ou, melhor, por que não está vinculado a algo chamado libglibc.so.2.34- se isso é uma dependência?

Se eu executar um lsusb -vcomando, recebo um campo chamado idProducte um campo chamado iProduct.

Para muitos dispositivos, iProduct é definido como 0, mas para outros, é definido como um nome de produto.

Por que existem duas entradas de produtos e como elas diferem?

O que determina se o iProduct é 0 ou uma string?

Meu Gigabyte H270-HD3 vem com uma Ethernet integrada.

00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V
        Subsystem: Intel Corporation Ethernet Connection (2) I219-V
        Flags: bus master, fast devsel, latency 0, IRQ 128
        Memory at f7f00000 (32-bit, non-prefetchable) [size=128K]
        Capabilities: [c8] Power Management version 3
        Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
        Capabilities: [e0] PCI Advanced Features
        Kernel driver in use: e1000e
        Kernel modules: e1000e

Mas a coisa estranha: o endereço MAC está preso em um 88:88:88:88:87:88endereço estranho.

Tentei re-flash do BIOS, mas após o re-flash, o problema persiste.

Por que minha Ethernet tem esse endereço MAC estranho? E como posso mudá-lo de volta para o que deveria ser?

enp0s31f6: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.0.3.39  netmask 255.0.0.0  broadcast 10.255.255.255
        inet6 fe80::7b57:d563:8263:6e11  prefixlen 64  scopeid 0x20<link>
        ether 88:88:88:88:87:88  txqueuelen 1000  (Ethernet)
        RX packets 1237  bytes 1072985 (1.0 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 818  bytes 83867 (83.8 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 16  memory 0xf7f00000-f7f20000  

Expirou algo que não deveria?

Estou usando símbolos de depuração na minha instalação do Ubuntu 20.10 e agora recebo isso quando executo o apt-get updatecomando.

W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used.
GPG error: http://ddebs.ubuntu.com groovy Release: The following signatures were invalid:
EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) <[email protected]>

Das minhas mensagens do kernel:

126.016 Gb/s available PCIe bandwidth, limited by 8.0 GT/s PCIe x16 link at 0000:16:00.0 (capable of 252.048 Gb/s with 16.0 GT/s PCIe x16 link)

Meu Supermicro X11-SRM-F tem apenas um slot PCIe 3.0 x16, que é usado por uma nVidia RTX 3070.

O que está limitando a velocidade de 8GT/s em vez de 16GT/s?

Ubuntu : 20.10

Kernel : 5.8.0-43-genérico

GPU : nVidia GTX 3070

Atualização : meu outro PC (core i5 Haswell) tem um limite ainda mais severo:

pci 0000:01:00.0: 32.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s PCIe x16 link at 0000:00:01.0 (capable of 126.016 Gb/s with 8.0 GT/s PCIe x16 link)

É por design que o Ubuntu 18.04 não será atualizado para 20.10 imediatamente?

Eu configurei minha configuração de atualização do sistema operacional para 'normal', o que significa que corresponderá a qualquer atualização do sistema operacional, não apenas lts.

No entanto, a atualização do sistema operacional para 18.04 irá para a versão 20.04 e não para a versão 20.10.

Espero que seja possível atualizar para o mais recente.

Quando tento usar o CUDA com o Blender 2.82.a+dfsg-1 recebo o seguinte erro:

Compiling CUDA kernel ...
"nvcc" -arch=sm_86 --cubin "/usr/share/blender/scripts/addons/cycles/source/kernel/kernels/cuda/kernel.cu" -o "/home/bram/.cache/cycles/kernels/cycles_kernel_sm86_673C3180FADE8EDF0E80E61994C4DC92.cubin" -m64 --ptxas-options="-v" --use_fast_math -DNVCC -I"/usr/share/blender/scripts/addons/cycles/source" 
nvcc fatal   : Value 'sm_86' is not defined for option 'gpu-architecture'
CUDA kernel compilation failed, see console for details.

O CUDA 11.1 está instalado no meu sistema, conforme relatado por nvidia-smi

$ nvidia-smi 
Sun Dec 20 19:34:48 2020       
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 455.38       Driver Version: 455.38       CUDA Version: 11.1     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  GeForce RTX 3070    Off  | 00000000:17:00.0  On |                  N/A |
|  0%   55C    P8    19W / 240W |    610MiB /  7979MiB |     12%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
                                                                               
+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|    0   N/A  N/A       968      G   /usr/lib/xorg/Xorg                 59MiB |
|    0   N/A  N/A      1598      G   /usr/lib/xorg/Xorg                247MiB |
|    0   N/A  N/A      1749      G   /usr/bin/gnome-shell               74MiB |
|    0   N/A  N/A      3855      G   ...e/Steam/ubuntu12_32/steam       17MiB |
|    0   N/A  N/A      3866      G   ./steamwebhelper                    3MiB |
|    0   N/A  N/A      3878      G   ...43331726878339,131072 --d       49MiB |
|    0   N/A  N/A      5384      G   /usr/lib/firefox/firefox            3MiB |
|    0   N/A  N/A      5463      G   /usr/lib/firefox/firefox            3MiB |
|    0   N/A  N/A      5686      G   nvidia-settings                     3MiB |
|    0   N/A  N/A      9586      G   /usr/lib/firefox/firefox            3MiB |
|    0   N/A  N/A      9642      G   blender                           120MiB |
|    0   N/A  N/A      9988      G   /usr/lib/firefox/firefox            3MiB |
+-----------------------------------------------------------------------------+

Como posso forçar o Blender a usar um modelo de shader diferente? porque aparentemente, não gosta de sm_86 .

Eu posso suspender a RAM. A tela fica preta e, em seguida, o monitor também entra em economia de energia.

No entanto, quando suspensos, todos os ventiladores do meu sistema permanecem ligados:

• ventilador da CPU
• Ventilador de gabinete
• Ventilador de GPU

log do kernel ao suspender:

[ 1377.806203] PM: suspend entry (s2idle)
[ 1377.809246] Filesystems sync: 0.003 seconds
[ 1377.809249] PM: Preparing system for sleep (s2idle)
[ 1378.070546] Freezing user space processes ... (elapsed 0.003 seconds) done.
[ 1378.073872] OOM killer disabled.
[ 1378.073873] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 1378.075361] PM: Suspending system (s2idle)
[ 1378.075363] printk: Suspending console(s) (use no_console_suspend to debug)
[ 1380.588027] snd_hda_intel 0000:17:00.1: spurious response 0x80000000:0x0, last cmd=0x6f2f00
[ 1380.588031] snd_hda_intel 0000:17:00.1: spurious response 0x80000000:0x0, last cmd=0x6f2f00
[ 1380.588033] snd_hda_intel 0000:17:00.1: spurious response 0x80000000:0x0, last cmd=0x6f2f00
[ 1380.588035] snd_hda_intel 0000:17:00.1: spurious response 0x80000000:0x0, last cmd=0x6f2f00
[ 1380.588037] snd_hda_intel 0000:17:00.1: spurious response 0x80000000:0x0, last cmd=0x6f2f00
[ 1380.588039] snd_hda_intel 0000:17:00.1: spurious response 0x80000000:0x0, last cmd=0x6f2f00
[ 1380.588040] snd_hda_intel 0000:17:00.1: spurious response 0x80000000:0x0, last cmd=0x6f2f00
[ 1380.588042] snd_hda_intel 0000:17:00.1: spurious response 0x80000000:0x0, last cmd=0x6f2f00
[ 1380.588044] snd_hda_intel 0000:17:00.1: spurious response 0x80000000:0x0, last cmd=0x6f2f00
[ 1380.588046] snd_hda_intel 0000:17:00.1: spurious response 0x80000000:0x0, last cmd=0x6f2f00
[ 1382.604016] snd_hda_intel 0000:17:00.1: azx_get_response timeout, switching to polling mode: last cmd=0x006f0900
[ 1383.324019] xpad 1-4:1.0: timed out waiting for output URB to complete, killing
[ 1383.324624] PM: suspend of devices complete after 5248.932 msecs
[ 1383.324629] PM: start suspend of devices complete after 5249.286 msecs
[ 1383.326763] PM: late suspend of devices complete after 2.130 msecs
[ 1383.383948] PM: noirq suspend of devices complete after 56.985 msecs
[ 1383.383951] PM: suspend-to-idle

log do kernel ao acordar:

[ 1399.984106] PM: Timekeeping suspended for 15.947 seconds
[ 1399.984279] PM: resume from suspend-to-idle
[ 1400.044023] PM: noirq resume of devices complete after 59.737 msecs
[ 1400.045312] PM: early resume of devices complete after 1.170 msecs
[ 1400.045645] pci 0000:16:05.0: disabled boot interrupts on device [8086:2034]
[ 1400.045766] pci 0000:64:05.0: disabled boot interrupts on device [8086:2034]
[ 1400.045831] pci 0000:b2:05.0: disabled boot interrupts on device [8086:2034]
[ 1400.212010] snd_hda_intel 0000:17:00.1: azx_get_response timeout, switching to single_cmd mode: last cmd=0x006f0900
[ 1400.212119] azx_single_wait_for_response: 6309 callbacks suppressed
[ 1400.212220] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD buf size -1
[ 1400.212522] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD buf size -1
[ 1400.212818] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD buf size -1
[ 1400.213112] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD buf size -1
[ 1400.213407] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD buf size -1
[ 1400.213701] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD buf size -1
[ 1400.213996] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD buf size -1
[ 1400.214291] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD buf size -1
[ 1400.292802] nvme nvme0: 16/0/0 default/read/poll queues
[ 1401.944040] pcieport 0000:b2:00.0: pciehp: Timeout on hotplug command 0x07d5 (issued 1960 msec ago)
[ 1401.944044] pcieport 0000:b2:01.0: pciehp: Timeout on hotplug command 0x07d5 (issued 1960 msec ago)
[ 1401.944047] pcieport 0000:b2:03.0: pciehp: Timeout on hotplug command 0x07d5 (issued 1960 msec ago)
[ 1401.944051] pcieport 0000:b2:02.0: pciehp: Timeout on hotplug command 0x07d5 (issued 1960 msec ago)
[ 1401.944114] PM: resume of devices complete after 1898.804 msecs
[ 1401.945342] PM: Finishing wakeup.
[ 1401.945343] OOM killer enabled.
[ 1401.945344] Restarting tasks ... done.
[ 1401.956420] rfkill: input handler enabled
[ 1401.956718] PM: suspend exit
[ 1402.228867] snd_hdac_bus_update_rirb: 430 callbacks suppressed
[ 1402.228874] snd_hda_intel 0000:17:00.1: spurious response 0x80000000:0x0, last cmd=0x6f0900
[ 1402.269012] snd_hda_intel 0000:17:00.1: spurious response 0x0:0x0, last cmd=0x6f0900
[ 1402.285794] rfkill: input handler disabled
[ 1403.352002] snd_hda_intel 0000:17:00.1: spurious response 0x0:0x0, last cmd=0x820000
[ 1403.352037] snd_hda_intel 0000:17:00.1: spurious response 0x0:0x0, last cmd=0x820000
[ 1403.375973] snd_hda_intel 0000:17:00.1: spurious response 0x0:0x0, last cmd=0x1f0500
[ 1403.376011] snd_hda_intel 0000:17:00.1: spurious response 0x233:0x0, last cmd=0x1f0500
[ 1403.449159] snd_hda_intel 0000:17:00.1: spurious response 0x0:0x0, last cmd=0x1f0500
[ 1403.449198] snd_hda_intel 0000:17:00.1: spurious response 0x0:0x0, last cmd=0x4f0015
[ 1403.449239] snd_hda_intel 0000:17:00.1: spurious response 0x3:0x0, last cmd=0x473500
[ 1403.449281] snd_hda_intel 0000:17:00.1: spurious response 0x0:0x0, last cmd=0x470700
[ 1405.084501] igb 0000:04:00.0 eno1: igb: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX

Verifiquei as configurações do BIOS do Supermicro X11SRM-F, mas não há nenhuma opção de suspensão para ram listada. Além disso, a suspensão parece estar funcionando, apenas sem desligar os ventiladores.

Eu tentei com e sem a opção Extended APIC no BIOS, com o mesmo resultado.

ATUALIZAR:

Parece que o tipo de suspensão que o sistema usa está causando isso.

No log do sistema, afirma que s2idle é usado, que é um sono não muito profundo.

A verificação de outros modos suportados me dá:

$ cat /sys/power/mem_sleep 
[s2idle]

...o que infelizmente significa que outros modos não estão disponíveis. Não está claro qual é o fator limitante, aqui. A placa-mãe? A BIOS?

Do núcleo:

ACPI: (supports S0 S4 S5)

Então, sem S3, isso significa que não há suspensão na RAM?

SO: Ubuntu 20.04.1 LTS

Processador: Xeon W2140B

Placa mãe: Supermicro X11XRM-F