Computer unsusable after new install

  • Downloaded Manjaro KDE as ISO file.
  • Created a bootable Live-USB.
  • The boot-up from USB took 3 minutes. Most of the time was spent booting the Simple Desktop Display Manager.
  • After loading, the Desktop periodically freezes for 1-2 minutes.
  • You can turn off-restart the computer only from the Terminal using the “reboot” command. I cannot provide data because the computer is practically unusable.

The upgrade to the main system (hard drive) with the Nvidia340 drivers installed went well.

You mean the install? Or the install to USB? Because you put that sentence after:

  1. Also, please read this:
    [HowTo] Provide System Information
    and press the three dots below your post and press the :pencil2: to give us more information so we can see what’s really going on.
    Now we know the symptom of the disease, but we need some more probing to know where the origin lies… :grin:
  2. An inxi --admin --verbosity=7 --filter --no-host --width would be the minimum required information for us to be able to help you. (Personally Identifiable Information like serial numbers and MAC addresses will be filtered out by the above command)
    Also, please copy-paste that output in-between 3 backticks ``` at the beginning and end of the code/text.


P.S. If you want to notify me that you did provide this information, please :heart: this message and I’ll come back and have another look.

1 Like

The computer with Live-USB started up for 3 minutes.
I cannot provide data, because the computer practically does not work with Live-USB.

1 Like
  1. Did you check the SHA1 hash of your download?
  2. Did you try one of the older versions from the archive?
  3. Did you try with free drivers and proprietary drivers?

Without any data, there is nothing more we can do…


1 Like
  1. Checked SHA1. OK
  2. Older versions of Live-USB work well.
  3. After installing the proprietary drivers, the system works very well.

This is the system data when booting from the hard drive:

inxi --admin --verbosity=7 --filter --no-host --width                         ✔ 
  Kernel: 5.10.60-1-MANJARO x86_64 bits: 64 compiler: gcc v: 11.1.0 
  parameters: BOOT_IMAGE=/vmlinuz-5.10-x86_64 
  root=UUID=a1df36bd-2a12-4bff-bd08-398732a61cb3 rw quiet 
  resume=UUID=ae71bf45-03de-43df-a739-9dcb4e9acf2d udev.log_priority=3 
  Desktop: KDE Plasma 5.22.4 tk: Qt 5.15.2 wm: kwin_x11 vt: 1 dm: SDDM 
  Distro: Manjaro Linux base: Arch Linux 
  Type: Portable System: Dell product: Latitude D630 v: N/A serial: <filter> 
  Chassis: type: 8 serial: <filter> 
  Mobo: Dell model: N/A serial: <filter> BIOS: Dell v: A19 date: 06/04/2013 
  ID-1: BAT0 charge: 46.4 Wh (100.0%) condition: 46.4/48.8 Wh (95.1%) 
  volts: 12.5 min: 11.1 model: GWM DELL 00 type: Li-ion serial: <filter> 
  status: Full 
  RAM: total: 3.84 GiB used: 1.72 GiB (44.8%) 
  RAM Report: permissions: Unable to run dmidecode. Root privileges required. 
  Info: Dual Core model: Intel Core2 Duo T9300 bits: 64 type: MCP arch: Penryn 
  family: 6 model-id: 17 (23) stepping: 6 microcode: 60F cache: L2: 6 MiB 
  bogomips: 9978 
  Speed: 798 MHz min/max: 800/2501 MHz boost: enabled Core speeds (MHz): 
  1: 798 2: 798 
  Flags: acpi aperfmperf apic arch_perfmon bts clflush cmov constant_tsc cpuid 
  cx16 cx8 de ds_cpl dtes64 dtherm dts est flexpriority fpu fxsr ht ida 
  lahf_lm lm mca mce mmx monitor msr mtrr nopl nx pae pat pbe pdcm pebs pge 
  pni pse pse36 pti rep_good sep sse sse2 sse4_1 ssse3 syscall tm tm2 
  tpr_shadow tsc vme vmx vnmi vpid xtpr 
  Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
  Type: l1tf mitigation: PTE Inversion; VMX: EPT disabled 
  Type: mds 
  status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled 
  Type: meltdown mitigation: PTI 
  Type: spec_store_bypass status: Vulnerable 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 
  mitigation: Full generic retpoline, STIBP: disabled, RSB filling 
  Type: srbds status: Not affected 
  Type: tsx_async_abort status: Not affected 
  Device-1: NVIDIA G86M [Quadro NVS 135M] vendor: Dell driver: nvidia 
  v: 340.108 alternate: nouveau bus-ID: 01:00.0 chip-ID: 10de:042b 
  class-ID: 0300 
  Display: x11 server: X.Org 1.20.13 compositor: kwin_x11 driver: 
  loaded: nvidia unloaded: modesetting,nouveau alternate: fbdev,nv,vesa 
  display-ID: :0 screens: 1 
  Screen-1: 0 s-res: 1440x900 s-dpi: 121 s-size: 302x191mm (11.9x7.5") 
  s-diag: 357mm (14.1") 
  OpenGL: renderer: Quadro NVS 135M/PCIe/SSE2 v: 3.3.0 NVIDIA 340.108 
  direct render: Yes 
  Device-1: Intel 82801H HD Audio vendor: Dell Latitude D630 
  driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:284b 
  class-ID: 0403 
  Sound Server-1: ALSA v: k5.10.60-1-MANJARO running: yes 
  Sound Server-2: JACK v: 1.9.19 running: no 
  Sound Server-3: PulseAudio v: 15.0 running: yes 
  Sound Server-4: PipeWire v: 0.3.33 running: yes 
  Device-1: Broadcom NetXtreme BCM5755M Gigabit Ethernet PCI Express 
  vendor: Dell driver: tg3 v: kernel port: ef00 bus-ID: 09:00.0 
  chip-ID: 14e4:1673 class-ID: 0200 
  IF: enp9s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
  IP v4: <filter> type: dynamic noprefixroute scope: global 
  broadcast: <filter> 
  IP v6: <filter> type: noprefixroute scope: link 
  Device-2: Intel PRO/Wireless 3945ABG [Golan] Network driver: iwl3945 
  v: in-tree:ds port: ef00 bus-ID: 0c:00.0 chip-ID: 8086:4222 class-ID: 0280 
  IF: wlp12s0 state: down mac: <filter> 
  WAN IP: <filter> 
  Message: No bluetooth data found. 
  Message: No logical block device data found. 
  Device-1: luks-e53d9caa-21f0-4dcf-8823-c4410e056705 maj-min: 254:0 
  type: LUKS dm: dm-0 size: 138.21 GiB 
  p-1: sda8 maj-min: 8:8 size: 138.21 GiB 
  Message: No RAID data found. 
  Local Storage: total: 238.47 GiB used: 49.97 GiB (21.0%) 
  SMART Message: Unable to run smartctl. Root privileges required. 
  ID-1: /dev/sda maj-min: 8:0 vendor: GOODRAM model: SSDPR-CX400-256 
  size: 238.47 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s 
  type: SSD serial: <filter> rev: 61.3 scheme: MBR 
  Optical-1: /dev/sr0 vendor: HL-DT-ST model: DVD+-RW GSA-T21N rev: A100 
  dev-links: cdrom 
  Features: speed: 24 multisession: yes audio: yes dvd: yes 
  rw: cd-r,cd-rw,dvd-r state: running 
  ID-1: / raw-size: 16 GiB size: 15.99 GiB (99.94%) used: 9.35 GiB (58.5%) 
  fs: xfs dev: /dev/sda6 maj-min: 8:6 label: N/A 
  uuid: a1df36bd-2a12-4bff-bd08-398732a61cb3 
  ID-2: /boot raw-size: 256 MiB size: 250.7 MiB (97.91%) 
  used: 77.3 MiB (30.8%) fs: xfs dev: /dev/sda5 maj-min: 8:5 label: N/A 
  uuid: b83d4bf8-e633-40fc-969e-d3b8969ede17 
  ID-3: /home raw-size: 138.21 GiB size: 138.14 GiB (99.95%) 
  used: 40.54 GiB (29.3%) fs: xfs dev: /dev/dm-0 maj-min: 254:0 
  mapped: luks-e53d9caa-21f0-4dcf-8823-c4410e056705 label: N/A 
  uuid: c0cd1975-6d19-4087-976c-6f8ea83ed172 
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) 
  ID-1: swap-1 type: partition size: 4 GiB used: 0 KiB (0.0%) priority: -2 
  dev: /dev/sda7 maj-min: 8:7 label: N/A 
  uuid: ae71bf45-03de-43df-a739-9dcb4e9acf2d 
  ID-1: /dev/sda1 maj-min: 8:1 size: 50 MiB fs: ntfs 
  label: \xd0\x97\xd0\xb0\xd1\x80\xd0\xb5\xd0\xb7\xd0\xb5\xd1\x80\xd0\xb2\xd0\xb8\xd1\x80\xd0\xbe\xd0\xb2\xd0\xb0\xd0\xbd\xd0\xbe \xd1\x81\xd0\xb8\xd1\x81\xd1\x82\xd0\xb5\xd0\xbc\xd0\xbe\xd0\xb9 
  uuid: C6888B8D888B7B27 
  ID-2: /dev/sda2 maj-min: 8:2 size: 79.44 GiB fs: ntfs label: Windows 
  uuid: 44309DD9309DD272 
  ID-3: /dev/sda3 maj-min: 8:3 size: 520 MiB fs: ntfs label: N/A 
  uuid: 2272443172440C4B 
  ID-4: /dev/sda4 maj-min: 8:4 size: 1 KiB fs: <superuser required> label: N/A 
  uuid: N/A 
  Hub-1: 1-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 
  speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900 
  Hub-2: 2-0:1 info: Full speed (or root) Hub ports: 6 rev: 2.0 
  speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900 
  Hub-3: 3-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s 
  chip-ID: 1d6b:0001 class-ID: 0900 
  Hub-4: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s 
  chip-ID: 1d6b:0001 class-ID: 0900 
  Hub-5: 5-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s 
  chip-ID: 1d6b:0001 class-ID: 0900 
  Hub-6: 6-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s 
  chip-ID: 1d6b:0001 class-ID: 0900 
  Device-1: 6-1:2 
  info: SHARKOON 2.4GHz Wireless rechargeable vertical mouse [More&Better] 
  type: Mouse driver: hid-generic,usbhid interfaces: 1 rev: 1.1 speed: 12 Mb/s 
  power: 100mA chip-ID: 1ea7:0064 class-ID: 0301 
  Hub-7: 7-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s 
  chip-ID: 1d6b:0001 class-ID: 0900 
  Hub-8: 7-1:2 info: O2 Micro Oz776 1.1 Hub ports: 4 rev: 1.1 speed: 12 Mb/s 
  power: 2mA chip-ID: 0b97:7761 class-ID: 0900 
  Device-1: 7-1.2:3 info: O2 Micro OZ776 CCID Smartcard Reader 
  type: Smart Card driver: N/A interfaces: 1 rev: 1.1 speed: 12 Mb/s 
  chip-ID: 0b97:7772 class-ID: 0b00 
  Device-2: 7-2:4 info: STMicro Fingerprint Reader type: <vendor specific> 
  driver: N/A interfaces: 1 rev: 1.0 speed: 12 Mb/s power: 100mA 
  chip-ID: 0483:2016 class-ID: 0000 
  System Temperatures: cpu: 44.0 C mobo: N/A sodimm: SODIMM C 
  Fan Speeds (RPM): cpu: 2535 
  Processes: 201 Uptime: 1h 3m wakeups: 1 Init: systemd v: 248 tool: systemctl 
  Compilers: gcc: 11.1.0 Packages: pacman: 1145 lib: 331 Shell: Zsh v: 5.8 
  default: Bash v: 5.1.8 running-in: konsole inxi: 3.3.06


So you have a working system???

What’s the issue then?


1 Like

Problem in booting from Live-USB. Until the latest update 21.1.1, I successfully booted from Live-USB. :roll_eyes:

Boot from a previous version then?

We’re going round in circles here, so what are you trying to accomplish?

:upside_down_face: :wink:

You clearly boot with free drivers instead of proprietary …

Is either you switched to proprietary boot for live session, and worked, or you installed the system previously with free drivers, but then that contradicts with

Boot what? You boot from USB live system to the installed system? Why?

1 Like

Probably, these are translation errors for non-native speakers.
I want to run a Manjaro 21.1.1 Pahvo Live image from USB.
Run the system from the previous Live image (Manjaro 21.1 Pahvo) was great.

Извини, я не понимаю твою проблему…

21.1 Pahvo работает??? Используйте это!!!


П.с. Я мало понимаю, плохо говорю… :man_shrugging:

Probably user tries to report an issue of non-working system, but doing that like: “I booted it up and it does not work. Any thoughts?”

Are you trying to report about freezing of a LiveCD session or freezing of an installed and loaded OS copy session? If about LiveCD, than what is the exact image name are you talking about?

Why kernel is 5.10? Are you using unstable development builds? Are you skilled enough to figure out issue of which component you may have? Also ISOs builds daily, try newest one (Tags · manjaro-plasma/download · GitHub). Or try latest stable (Manjaro - KDE Plasma) based on 5.13 kernel family.

In bug report please try to be more specific: try to find errors and warnings at least in general logs, one of useful source is


but before use, learn it:

man journalctl

try it:

journalctl --sync --priority=3 --boot=0 --catalog
journalctl --sync --priority=4 --boot=0 --catalog
journalctl --sync --priority=3 --boot=0 --catalog --dmesg
journalctl --sync --priority=4 --boot=0 --catalog --dmesg

improve argument usage and try it with the arguments you learned.

Change your system clock to make it show you seconds also. Remember exact start time of the freezing effect and try to list journal a bit ahead that time:

journalctl --sync --boot=0

Try to find any logged info about that freezing visual effect. Most possible reason is GPU-related issue.

What exactly you did right before freeze (executing somewhat, some app shows you somewhat, switch to somewhat?) or it is completely unpredictable and random event?

May be some software could be executed in more detailed logging/“debug” mode to see what is going on under the hood, but it will be so much info, that actual event could be hidden and it will be hard to find it there, especially if you did not the exact time of the event.


ls --almost-all -1 -l --human /var/lib/systemd/coredump

Core dumps lands there in installed OS copy (I do know about LiveCD sessions). If it is not empty, than it is not a low priority issue.


He might just want a live usb for safety reasons ie to be able to recover a broken system, I always keep an upto date live usb. He has a very old system maybe 21.1.1 has a kernel that his system is struggling with


Perhaps this is due to the mesa package. As of manjaro-kde-21.1.0, the mesa package is version 21.1.6-1. As of manjaro-kde-21.1.1, the mesa package is version 21.2.1-1. The new package might be in conflict with my old graphics card. :confused:

1 Like