Manjaro se congela GNOME

Que tal amigos del foro estoy probando la distro de Manjaro y me gustó demasiado pero tengo un gran problema y es que se congela aleatoriamente, no puedo mover el cursor ni escribir nada en el teclado tampoco abrir la terminal. Espero me puedan ayudar
Nvidia 1650 super con drivers open source

un poco de información que tal vez pueda ayudar

export LANG=C; inxi --admin --verbosity=7 --filter --no-host --width

System:
  Kernel: 5.10.56-1-MANJARO x86_64 bits: 64 compiler: gcc v: 11.1.0 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.10-x86_64 
  root=UUID=84082bde-f80d-447a-8992-1e21bc2bd9e7 rw quiet splash apparmor=1 
  security=apparmor resume=UUID=049b2c2d-2445-4ed5-8ed3-34838c65ba53 
  udev.log_priority=3 
  Desktop: GNOME 40.3 tk: GTK 3.24.30 info: plank wm: gnome-shell dm: GDM 40.1 
  Distro: Manjaro Linux base: Arch Linux 
Machine:
  Type: Desktop Mobo: ASUSTeK model: PRIME H310M-E R2.0 v: Rev X.0x 
  serial: <filter> UEFI: American Megatrends v: 1002 date: 05/24/2019 
Battery:
  Message: No system battery data found. Is one present? 
Memory:
  RAM: total: 15.57 GiB used: 1.56 GiB (10.0%) 
  RAM Report: permissions: Unable to run dmidecode. Root privileges required. 
CPU:
  Info: Quad Core model: Intel Core i3-9100F bits: 64 type: MCP 
  arch: Kaby Lake note: check family: 6 model-id: 9E (158) stepping: A (10) 
  microcode: EA cache: L2: 6 MiB bogomips: 28808 
  Speed: 810 MHz min/max: 800/4200 MHz Core speeds (MHz): 1: 810 2: 1825 
  3: 964 4: 1330 
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat arch_perfmon art 
  avx avx2 bmi1 bmi2 bts clflush clflushopt cmov constant_tsc cpuid 
  cpuid_fault cx16 cx8 de ds_cpl dtes64 dtherm dts epb ept ept_ad erms est 
  f16c flexpriority flush_l1d fma fpu fsgsbase fxsr ht hwp hwp_act_window 
  hwp_epp hwp_notify ibpb ibrs ida intel_pt invpcid invpcid_single lahf_lm lm 
  mca mce md_clear mmx monitor movbe mpx msr mtrr nonstop_tsc nopl nx pae pat 
  pbe pcid pclmulqdq pdcm pdpe1gb pebs pge pln pni popcnt pse pse36 pti pts 
  rdrand rdseed rdtscp rep_good sdbg sep smap smep ss ssbd sse sse2 sse4_1 
  sse4_2 ssse3 stibp syscall tm tm2 tpr_shadow tsc tsc_adjust 
  tsc_deadline_timer vme vmx vnmi vpid x2apic xgetbv1 xsave xsavec xsaveopt 
  xsaves xtopology xtpr 
  Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
  Type: l1tf 
  mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled 
  Type: mds mitigation: Clear CPU buffers; SMT disabled 
  Type: meltdown mitigation: PTI 
  Type: spec_store_bypass 
  mitigation: Speculative Store Bypass disabled via prctl and seccomp 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, 
  IBRS_FW, STIBP: disabled, RSB filling 
  Type: srbds mitigation: Microcode 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: NVIDIA TU116 [GeForce GTX 1650 SUPER] vendor: Gigabyte 
  driver: nouveau v: kernel bus-ID: 01:00.0 chip-ID: 10de:2187 class-ID: 0300 
  Device-2: Jieli USB PHY 2.0 type: USB driver: snd-usb-audio,uvcvideo 
  bus-ID: 1-4:4 chip-ID: 1224:2a25 class-ID: 0102 
  Display: x11 server: X.org 1.20.13 compositor: gnome-shell driver: 
  loaded: modesetting,nouveau alternate: fbdev,nv,vesa 
  resolution: <missing: xdpyinfo> 
  OpenGL: renderer: NV168 v: 4.3 Mesa 21.1.6 direct render: Yes 
Audio:
  Device-1: Intel 200 Series PCH HD Audio vendor: ASUSTeK 
  driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a2f0 
  class-ID: 0403 
  Device-2: NVIDIA TU116 High Definition Audio vendor: Gigabyte 
  driver: snd_hda_intel v: kernel bus-ID: 01:00.1 chip-ID: 10de:1aeb 
  class-ID: 0403 
  Device-3: Jieli USB PHY 2.0 type: USB driver: snd-usb-audio,uvcvideo 
  bus-ID: 1-4:4 chip-ID: 1224:2a25 class-ID: 0102 
  Sound Server-1: ALSA v: k5.10.56-1-MANJARO running: yes 
  Sound Server-2: sndio v: N/A running: no 
  Sound Server-3: JACK v: 1.9.19 running: no 
  Sound Server-4: PulseAudio v: 15.0 running: yes 
  Sound Server-5: PipeWire v: 0.3.33 running: yes 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: ASUSTeK PRIME B450M-A driver: r8169 v: kernel port: d000 
  bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200 
  IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
  IP v4: <filter> type: dynamic noprefixroute scope: global 
  broadcast: <filter> 
  IP v6: <filter> type: dynamic noprefixroute scope: global 
  IP v6: <filter> type: noprefixroute scope: link escribe o pega el código aquí
  WAN IP: <filter> 
Bluetooth:
  Message: No bluetooth data found. 
Logical:
  Message: No logical block device data found. 
RAID:
  Message: No RAID data found. 
Drives:
  Local Storage: total: 2.26 TiB used: 14.23 GiB (0.6%) 
  SMART Message: Required tool smartctl not installed. Check --recommends 
  ID-1: /dev/sda maj-min: 8:0 vendor: Kingston model: SA400S37480G 
  size: 447.13 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s 
  type: SSD serial: <filter> rev: K1B3 scheme: GPT 
  ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST2000DM008-2FR102 
  size: 1.82 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s 
  type: HDD rpm: 7200 serial: <filter> rev: 0001 scheme: GPT 
  Message: No optical or floppy data found. 
Partition:
  ID-1: / raw-size: 40 GiB size: 39.08 GiB (97.69%) used: 12.01 GiB (30.7%) 
  fs: ext4 dev: /dev/sda5 maj-min: 8:5 label: N/A 
  uuid: 84082bde-f80d-447a-8992-1e21bc2bd9e7 
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.79%) 
  used: 288 KiB (0.1%) fs: vfat dev: /dev/sda8 maj-min: 8:8 label: NO_LABEL 
  uuid: 3DC5-0674 
  ID-3: /home raw-size: 157.71 GiB size: 154.17 GiB (97.76%) 
  used: 2.22 GiB (1.4%) fs: ext4 dev: /dev/sda6 maj-min: 8:6 label: N/A 
  uuid: 35eea5df-86ae-4f71-bbe1-05c6a2f47f25 
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) 
  ID-1: swap-1 type: partition size: 2 GiB used: 0 KiB (0.0%) priority: -2 
  dev: /dev/sda4 maj-min: 8:4 label: N/A 
  uuid: 049b2c2d-2445-4ed5-8ed3-34838c65ba53 
Unmounted:
  ID-1: /dev/sda1 maj-min: 8:1 size: 100 MiB fs: vfat label: N/A 
  uuid: E622-AD4A 
  ID-2: /dev/sda2 maj-min: 8:2 size: 16 MiB fs: <superuser required> 
  label: N/A uuid: N/A 
  ID-3: /dev/sda3 maj-min: 8:3 size: 246.44 GiB fs: ntfs label: N/A escribe o pega el código aquí
  uuid: 30D226F7D226C148 
  ID-4: /dev/sda7 maj-min: 8:7 size: 586 MiB fs: ntfs label: N/A 
  uuid: BA8618AA86186961 
  ID-5: /dev/sdb1 maj-min: 8:17 size: 16 MiB fs: <superuser required> 
  label: N/A uuid: N/A 
  ID-6: /dev/sdb2 maj-min: 8:18 size: 1.82 TiB fs: ntfs label: Second 
  uuid: 084C8D354C8D1E96 
USB:
  Hub-1: 1-0:1 info: Full speed (or root) Hub ports: 10 rev: 2.0 
  speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900 
  Device-1: 1-1:2 info: Logitech Unifying Receiver type: Keyboard,Mouse 
  driver: logitech-djreceiver,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s 
  power: 98mA chip-ID: 046d:c534 class-ID: 0301 
  Device-2: 1-3:3 info: Logitech G203 Gaming Mouse type: Mouse,HID 
  driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s 
  power: 300mA chip-ID: 046d:c084 class-ID: 0300 serial: <filter> 
  Device-3: 1-4:4 info: Jieli USB PHY 2.0 type: Video,Audio 
  driver: snd-usb-audio,uvcvideo interfaces: 4 rev: 2.0 speed: 480 Mb/s 
  power: 500mA chip-ID: 1224:2a25 class-ID: 0102 
  Hub-2: 2-0:1 info: Full speed (or root) Hub ports: 4 rev: 3.0 speed: 5 Gb/s 
  chip-ID: 1d6b:0003 class-ID: 0900 
  Hub-3: 3-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0 
  speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900 
  Hub-4: 4-0:1 info: Full speed (or root) Hub ports: 4 rev: 3.1 speed: 10 Gb/s 
  chip-ID: 1d6b:0003 class-ID: 0900 
Sensors:
  System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: nouveau temp: 35.0 C 
  Fan Speeds (RPM): N/A gpu: nouveau fan: 1394 
Info:
  Processes: 233 Uptime: 2m wakeups: 0 Init: systemd v: 248 tool: systemctl 
  Compilers: gcc: 11.1.0 Packages: pacman: 1203 lib: 307 flatpak: 0 Shell: Zsh 
  v: 5.8 running-in: gnome-terminal inxi: 3.3.06 

sudo lsblk -f

NAME FSTYPE FSVER LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
sda                                                                         
|-sda1
|    vfat   FAT32       E622-AD4A                                           
|-sda2
|                                                                           
|-sda3
|    ntfs               30D226F7D226C148                                    
|-sda4
|    swap   1           049b2c2d-2445-4ed5-8ed3-34838c65ba53                [SWAP]
|-sda5
|    ext4   1.0         84082bde-f80d-447a-8992-1e21bc2bd9e7     25G    31% /
|-sda6
|    ext4   1.0         35eea5df-86ae-4f71-bbe1-05c6a2f47f25    144G     1% /home
|-sda7
|    ntfs               BA8618AA86186961                                    
`-sda8
     vfat   FAT32 NO_LABEL
                        3DC5-0674                             299.1M     0% /boot/efi
sdb                                                                         
|-sdb1
|                                                                           
`-sdb2
     ntfs         Second
                        084C8D354C8D1E96  

También si se esta escuchando música o viendo un vídeo, el audio se sigue reproduciendo por si ayuda en algo esta información
Lo único que me ha servido es reiniciar

Hay alguna razón por la que quieres los drivers open source? Suelen ser malos esos drivers comparados con los propietarios de NVIDIA.

Si quieres instalar los propietarios,solo ejecuta en la terminal

sudo mhwd -a pci nonfree 0300

Luego reinicia y listo,ya no debería estar congelándose.

2 Likes

Gracias por comentar…
Antes de tener los open source tenia manjaro con los propietarios, recuerdo que te da esa opcion al instalarlo, pero aun así me pasó lo mismo pero no se si sean los mismos que se instalan con el comando o son diferentes, lo reinstale con los open source para ver si era una mejor opción.
Acabo de ejecutar el comando y espero no se congele gracias.

Si son los mismos drivers los que vienen en la instalación o por comandos el que acabas de hacer,si se sigue congelando podría ser otro problema.

Te diría también de revisar los logs justo después de que te pase:

journalctl -b -1 -xe

A ver si así puedes ver algún mensaje significativo que aclare algo, porque de equipo pareces ir bien.

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.