Booting up only leads to tty

Hello everyone,

Recently every game I booted up lead to the desktop completely freezing. Bringing up terminal or any other app through short-cuts doesn’t work until more than 4 hours into the freeze.

I tried to figure out if it’s because of faulty kernel (I updated to 6.12 prior to this problem), conflicting nvidia drivers, or xmp activated for RAM in bios.

Either way after forcefully shutting down (yes I didn’t realize I had to type in “root” in tty in order to start using commands), now it only boots up into tty. I looked up every guide I could find related but the results don’t seem to apply in my situation. Would I have to resort to repairing manjaro kde externally?

I think checking for this one and reversing it would be a safe thing to do to easily eliminate one part of the equation.

It is very unusual and even unlikely that simply running some game or other app would destroy the system to the point where the display manager doesn’t start anymore - and leave you with only TTY access.

… you did something else - something a user run program couldn’t have done …
something was run as root, perhaps?

1 Like

Welcome to the Manjaro community.


It seems you are experiencing major difficulty in your choice of commands. Please see the following articles to better understand a few of them:


As an infrequent forum user, please take some time to familiarise yourself with Forum requirements; in particular, the many ways to use the forum to your benefit:

The Update Announcements should be checked frequently for important update related information.

These announcements contain a Known Issues and Solutions section and should generally be checked before posting a request for support.

Output of the following command formatted according to forum requirements (see links above) may be useful for those wishing to help:

inxi --admin --verbosity=8 --filter --no-host --width

Be prepared to provide more information and outputs from other commands when asked.

Regards.


And finally, as your strategy seems to include randomly entering commands with no clear understanding of either the correct syntax or the intended use of such commands, the following article is a valid consideration:

Regards.

3 Likes

Your screenshot does not show any errors, just a bunch of seemingly unrelated commands?
Check your journal for any errors.

So do you get any furhter when booting up the previously used kernel?

I turned off XMP and it looks like that wasn’t the cause since nothing changed.
Now more specifically when I boot up Manjaro, the whole screen is completely black until I hit Ctrl+Alt+F2 to get into TTY. This still means that only TTY is available right?

@freggel.doe

I can’t tell since it still boots into a black screen and can only bring up TTY. I do recall “switching” kernels through the settings manager as seen here as an example.

Sometime earlier I suspected maybe it was Nvidia drivers causing the big freezes so I thought installing open-source drivers through Manjaro’s Hardware configuration would help.

This is a proper mess. I’ve made mention recently that - unless you’re very confident (and I mean confident as in - a reliable actor who other folks regard as competent) - it’s often best just to avoid being a sudo spammer.

I see you trying to log in as root, and you don’t remember the password (a reson most people set their root and admin passwords to be the same, or if different, only slightly d1fferent.

Then AS ROOT you try running sudo paccheck.

As soon as any potentially serious error occurs, it is good to check the time/date of your last Snapshot, and the time/date of your last Backup.

Is it not possible for you to boot a live USB session, and restore your latest snapshot?

Did you take a snapshot at any time during this problem?

1 Like

Not sure whether only TTY is there - I have had it with Gnome in a VM that there was a black screen,
but simply changing to a TTY and back to where the display manager is then showed it.

just try and cycle through - ALT+left or right arrow

You can also:
systemctl restart sddm.service

or

systemctl stop sddm.service
and then
startx
to start an xorg session without the display manager

Do not do this as root!

I don’t know how to start a wayland session in a similar way.

1 Like
startw
1 Like

… that easy, eh? :slightly_smiling_face:
Thank you!

I didn’t know because I never used wayland.
I’m on Xfce4 where it is not yet supported - and in VM’s it doesn’t work that good or not at all - so I don’t use it there either.

1 Like

It remembers my password, manjaro’s terminal just doesn’t display it when I type it in. Logging in as root is the only way to recognize my password and then access terminal so far.

It was already too late AFAIK because the freeze already occupied a lot of resources since it’s coming from a steam game (Warframe and then again with Cyberpunk) in the middle of running. I felt taking a snapshot would’ve just repeated the problem.

I haven’t tried that yet but I prepped a USB boot device with the newest kernel just in case if I have to resort to it

Ok, well - good luck with that.

I don’t understand how ‘it’ remembers your password - surely you should… but if you decide to have a different password to root, then it’s good to make it memorable because you might not use it often - hence the suggestion that if you choose ‘password’ then root could be ‘p@55word’…

You didn’t make it clear if you had ANY snapshots… I’m a fairly lazy troubleshooter, so when it gets messy I sometimes just boot USB, then launch Timeshift and point it to my storage and restore…

Then you have to proceed with caution because if it’s an update, you might bring the problem back - so check journals and see if there were any errors in your snapshot… maybe need to go back to an earlier one.

I keep hourly snapshots for one day, then daily for a few days, plus 2 weekly snapshots so I can go back up to 14 days.

Same story with backups - if I’m using my spreadsheet to follow sales, I can pull up snapshots of that document for the last few hours, last few days, then weekly for 3 weeks.

@revolverswitch

Sam, we’re still waiting for that system information requested 9/10 posts ago. This is typically the minimum required information and will help others to better understand your system.

Have you checked the recommended Wiki pages yet to understand the differences between pamac and pacman?

When you boot and find yourself at a TTY, are you able (have you tried) to Ctrl+Alt+F2 back to SDDM? Also note that logging in as root via a TTY is rarely recommended; use your normal User account and use sudo when you need elevated privileges.

I notice you tried to run fsck; after so many apparent hard resets this was probably a valid choice. However, fsck must only be performed on an unmounted filesystem – preferably after booting from a Manjaro Live ISO – you cannot repair the active / filesystem, for example;

nor can you unmount it; thus the need to boot from the Manjaro Installer and perform these operations.

3 Likes

I should’ve clarified, I can type my password just fine. Terminal just simply doesn’t display what I’m typing when it comes to the password. It’s at the second attempt that I typed my password correctly in the screenshot.

I couldn’t remember if I did or not, right now on the bootable drive, Timeshift says no snapshots available. It automatically accesses the root drive when being launched right?

ctrl + alt + f2 is the only desktop that brings up TTY and allows me to type, while f1 and the rest are either completely black or just a line that doesn’t let me type anything.

I was finally able to get it displayed though this is from a session on the USB boot device, let me know if I should take a picture from the TTY instead since I won’t be able to access firefox outside the USB boot device.

System:
  Kernel: 6.12.4-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=en_US keytable=us tz=UTC
    misobasedir=manjaro misolabel=MANJARO_KDE_2421 quiet systemd.show_status=1
    splash driver=nonfree nouveau.modeset=0 i915.modeset=1 radeon.modeset=1
  Desktop: KDE Plasma v: 6.2.4 tk: Qt v: N/A info: frameworks v: 6.8.0
    wm: kwin_x11 vt: 2 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop Mobo: Micro-Star model: MPG Z690 EDGE WIFI DDR4 (MS-7D31)
    v: 1.0 serial: <superuser required> uuid: <superuser required> UEFI: American
    Megatrends LLC. v: 1.G0 date: 01/10/2024
Battery:
  Message: No system battery data found. Is one present?
Memory:
  System RAM: total: 32 GiB available: 31.13 GiB used: 5.07 GiB (16.3%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 128 GiB slots: 4 modules: 2 EC: None
    max-module-size: 32 GiB note: est.
  Device-1: Controller0-DIMMA1 type: no module installed
  Device-2: Controller0-DIMMA2 type: DDR4 detail: synchronous size: 16 GiB
    speed: 2133 MT/s volts: note: check curr: 1 min: 1 max: 1 width (bits):
    data: 64 total: 64 manufacturer: G Skill Intl part-no: F4-3600C14-16GTZN
    serial: N/A
  Device-3: Controller1-DIMMB1 type: no module installed
  Device-4: Controller1-DIMMB2 type: DDR4 detail: synchronous size: 16 GiB
    speed: 2133 MT/s volts: note: check curr: 1 min: 1 max: 1 width (bits):
    data: 64 total: 64 manufacturer: G Skill Intl part-no: F4-3600C14-16GTZN
    serial: N/A
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: 12th Gen Intel Core i5-12600K bits: 64 type: MST AMCP
    arch: Alder Lake gen: core 12 level: v3 note: check built: 2021+
    process: Intel 7 (10nm ESF) family: 6 model-id: 0x97 (151) stepping: 2
    microcode: 0x37
  Topology: cpus: 1x dies: 1 clusters: 7 cores: 10 threads: 16 mt: 6 tpc: 2
    st: 4 smt: enabled cache: L1: 864 KiB desc: d-4x32 KiB, 6x48 KiB; i-6x32
    KiB, 4x64 KiB L2: 9.5 MiB desc: 6x1.2 MiB, 1x2 MiB L3: 20 MiB
    desc: 1x20 MiB
  Speed (MHz): avg: 800 min/max: 800/4900:3600 scaling: driver: intel_pstate
    governor: powersave cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800
    8: 800 9: 800 10: 800 11: 800 12: 800 13: 800 14: 800 15: 800 16: 800
    bogomips: 118000
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
    arch_capabilities arch_lbr arch_perfmon art avx avx2 avx_vnni bmi1 bmi2
    bts clflush clflushopt clwb cmov constant_tsc cpuid cpuid_fault cx16 cx8
    de ds_cpl dtes64 dtherm dts ept ept_ad erms est f16c flexpriority
    flush_l1d fma fpu fsgsbase fsrm fxsr gfni hfi ht hwp hwp_act_window
    hwp_epp hwp_notify hwp_pkg_req ibpb ibrs ibrs_enhanced ibt ida intel_pt
    invpcid lahf_lm lm mca mce md_clear mmx monitor movbe movdir64b movdiri
    msr mtrr nonstop_tsc nopl nx ospke pae pat pbe pclmulqdq pconfig pdcm
    pdpe1gb pebs pge pku pln pni popcnt pse pse36 pts rdpid rdrand rdseed
    rdtscp rep_good sdbg sep serialize sha_ni smap smep smx split_lock_detect
    ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm tm2 tpr_shadow tsc
    tsc_adjust tsc_deadline_timer tsc_known_freq umip user_shstk vaes vme vmx
    vnmi vpclmulqdq vpid waitpkg x2apic xgetbv1 xsave xsavec xsaveopt xsaves
    xtopology xtpr
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling mitigation: Clear Register File
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Enhanced / Automatic IBRS; IBPB: conditional;
    RSB filling; PBRSB-eIBRS: SW sequence; BHI: BHI_DIS_S
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel AlderLake-S GT1 vendor: Micro-Star MSI driver: i915 v: kernel
    alternate: xe arch: Gen-12.1 process: Intel 10nm built: 2020-21 ports:
    active: none empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2, HDMI-A-3, HDMI-A-4
    bus-ID: 00:02.0 chip-ID: 8086:4680 class-ID: 0380
  Device-2: NVIDIA GA104 [GeForce RTX 3070 Lite Hash Rate] vendor: ASUSTeK
    driver: nvidia v: 550.135 alternate: nouveau,nvidia_drm non-free: 550.xx+
    status: current (as of 2024-09; EOL~2026-12-xx) arch: Ampere code: GAxxx
    process: TSMC n7 (7nm) built: 2020-2023 pcie: gen: 4 speed: 16 GT/s
    lanes: 8 link-max: lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:2488
    class-ID: 0300
  Display: x11 server: X.Org v: 21.1.14 with: Xwayland v: 24.1.4
    compositor: kwin_x11 driver: X: loaded: N/A failed: nvidia gpu: i915,nvidia
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 90 s-size: 542x301mm (21.34x11.85")
    s-diag: 620mm (24.41")
  Monitor-1: Unknown-1 mapped: DP-2 res: 1920x1080 dpi: 90
    size: 544x303mm (21.42x11.93") modes: 1024x768
  API: EGL v: 1.5 hw: drv: intel iris drv: nvidia platforms: device: 0
    drv: nvidia device: 1 drv: iris device: 3 drv: swrast gbm: drv: iris
    surfaceless: drv: nvidia x11: drv: nvidia inactive: wayland,device-2
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.135
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 3070/PCIe/SSE2
    memory: 7.81 GiB
  API: Vulkan v: 1.4.303 layers: 1 device: 0 type: discrete-gpu
    name: NVIDIA GeForce RTX 3070 driver: N/A device-ID: 10de:2488
    surfaces: xcb,xlib
Audio:
  Device-1: Intel Alder Lake-S HD Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel alternate: snd_soc_avs,snd_sof_pci_intel_tgl
    bus-ID: 00:1f.3 chip-ID: 8086:7ad0 class-ID: 0403
  Device-2: NVIDIA GA104 High Definition Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 8
    link-max: lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:228b class-ID: 0403
  Device-3: Focusrite-Novation Scarlett 2i2 4th Gen driver: snd-usb-audio
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-5:5
    chip-ID: 1235:8219 class-ID: 0102 serial: <filter>
  Device-4: Schiit Audio Yggdrasil Unison USB driver: snd-usb-audio type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-9:6 chip-ID: 30be:1001
    class-ID: 0102
  API: ALSA v: k6.12.4-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.2.7 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Alder Lake-S PCH CNVi WiFi driver: iwlwifi v: kernel
    bus-ID: 00:14.3 chip-ID: 8086:7af0 class-ID: 0280
  IF: wlo1 state: up mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: noprefixroute scope: link
  Device-2: Intel Ethernet I225-V vendor: Micro-Star MSI driver: igc
    v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 port: N/A bus-ID: 04:00.0
    chip-ID: 8086:15f3 class-ID: 0200
  IF: enp4s0 state: down mac: <filter>
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
  WAN IP: <filter>
Bluetooth:
  Device-1: Intel AX201 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-14:11 chip-ID: 8087:0026
    class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 7.34 TiB used: 0 KiB (0.0%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Sabrent model: Rocket 4.0 Plus
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: RKT4P1.1 temp: 35.9 C
    scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:5 vendor: Samsung
    model: SSD 970 EVO Plus 1TB size: 931.51 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 4B2QEXM7 temp: 42.9 C scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 vendor: Seagate model: ST3000VN000-1HJ166
    size: 2.73 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 5900 serial: <filter> fw-rev: SC60 scheme: GPT
  ID-4: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 870 EVO 2TB
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 2B6Q scheme: GPT
  ID-5: /dev/sdd maj-min: 8:48 vendor: Samsung model: Flash Drive
    size: 59.75 GiB block-size: physical: 512 B logical: 512 B type: USB rev: 3.1
    spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: SSD serial: <filter>
    fw-rev: 1100 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
  Message: No optical or floppy data found.
Partition:
  Message: No partition data found.
Swap:
  Alert: No swap data was found.
Unmounted:
  ID-1: /dev/nvme0n1p1 maj-min: 259:1 size: 100 MiB fs: vfat label: N/A
    uuid: 92DC-90BC
  ID-2: /dev/nvme0n1p2 maj-min: 259:2 size: 16 MiB fs: <superuser required>
    label: N/A uuid: N/A
  ID-3: /dev/nvme0n1p3 maj-min: 259:3 size: 1.82 TiB fs: ntfs label: N/A
    uuid: 80C2DDCEC2DDC914
  ID-4: /dev/nvme0n1p4 maj-min: 259:4 size: 509 MiB fs: ntfs label: N/A
    uuid: F8AC5BC3AC5B7AD8
  ID-5: /dev/nvme1n1p1 maj-min: 259:6 size: 16 MiB fs: <superuser required>
    label: N/A uuid: N/A
  ID-6: /dev/nvme1n1p2 maj-min: 259:7 size: 931.5 GiB fs: ntfs label: N/A
    uuid: 8024AB3924AB3158
  ID-7: /dev/sda1 maj-min: 8:1 size: 128 MiB fs: <superuser required>
    label: N/A uuid: N/A
  ID-8: /dev/sda2 maj-min: 8:2 size: 2.73 TiB fs: ntfs label: N/A
    uuid: 841499DC1499D192
  ID-9: /dev/sdb1 maj-min: 8:17 size: 300 MiB fs: vfat label: N/A
    uuid: 36BE-DB6F
  ID-10: /dev/sdb2 maj-min: 8:18 size: 1.82 TiB fs: ext4 label: N/A
    uuid: 460a1205-2a14-44f4-aa4c-c94627e6f576
  ID-11: /dev/sdd1 maj-min: 8:49 size: 4.03 GiB fs: iso9660
  ID-12: /dev/sdd2 maj-min: 8:50 size: 4 MiB fs: vfat label: MISO_EFI
    uuid: 97A3-D79B
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 16 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 1-2:2 info: Micro Star MYSTIC LIGHT type: HID
    driver: hid-generic,usbhid interfaces: 1 rev: 1.1 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 500mA chip-ID: 1462:7d31 class-ID: 0300
    serial: <filter>
  Device-2: 1-3:3 info: XP-Pen Xencelabs Dongle type: mouse,HID
    driver: hid-generic,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 100mA chip-ID: 28bd:5203 class-ID: 0300
    serial: <filter>
  Device-3: 1-4:4 info: Cyboard Imprint type: keyboard,HID
    driver: hid-generic,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 500mA chip-ID: 4359:0000 class-ID: 0300
    serial: <filter>
  Device-4: 1-5:5 info: Focusrite-Novation Scarlett 2i2 4th Gen type: audio
    driver: snd-usb-audio interfaces: 4 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s)
    lanes: 1 mode: 2.0 chip-ID: 1235:8219 class-ID: 0102 serial: <filter>
  Device-5: 1-9:6 info: Schiit Audio Yggdrasil Unison USB type: audio
    driver: snd-usb-audio interfaces: 2 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s)
    lanes: 1 mode: 2.0 power: 100mA chip-ID: 30be:1001 class-ID: 0102
  Hub-2: 1-12:8 info: Genesys Logic Hub ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 05e3:0608 class-ID: 0900
  Device-1: 1-12.1:10 info: Logitech G600 Gaming Mouse type: mouse,keyboard
    driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 500mA chip-ID: 046d:c24a class-ID: 0300
    serial: <filter>
  Hub-3: 1-13:9 info: Genesys Logic Hub ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 05e3:0608 class-ID: 0900
  Device-1: 1-14:11 info: Intel AX201 Bluetooth type: bluetooth driver: btusb
    interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1
    power: 100mA chip-ID: 8087:0026 class-ID: e001
  Hub-4: 2-0:1 info: super-speed hub ports: 9 rev: 3.1
    speed: 20 Gb/s (2.33 GiB/s) lanes: 2 mode: 3.2 gen-2x2 chip-ID: 1d6b:0003
    class-ID: 0900
  Device-1: 2-6:2 info: Silicon Motion - Taiwan (formerly Feiya ) Flash Drive
    type: mass storage driver: usb-storage interfaces: 1 rev: 3.1
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 power: 304mA
    chip-ID: 090c:1000 class-ID: 0806 serial: <filter>
Sensors:
  System Temperatures: cpu: 37.0 C mobo: N/A gpu: nvidia temp: 51 C
  Fan Speeds (rpm): N/A gpu: nvidia fan: 0%
Repos:
  Packages: pm: pacman pkgs: 1242 libs: 323 tools: pamac pm: flatpak pkgs: 0
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://manjaro.mirror.garr.it/manjaro/stable/$repo/$arch
    2: https://ipng.mm.fcix.net/manjaro/stable/$repo/$arch
    3: https://mirror.aarnet.edu.au/pub/manjaro/stable/$repo/$arch
    4: https://muug.ca/mirror/manjaro/stable/$repo/$arch
    5: https://repo.iut.ac.ir/repo/manjaro/stable/$repo/$arch
    6: https://mirrors.ft.uam.es/manjaro/stable/$repo/$arch
    7: https://manjaro.c3sl.ufpr.br/stable/$repo/$arch
    8: https://bd.mirror.vanehost.com/Manjaro/stable/$repo/$arch
    9: https://opencolo.mm.fcix.net/manjaro/stable/$repo/$arch
    10: https://mirror.zetup.net/manjaro/stable/$repo/$arch
    11: https://volico.mm.fcix.net/manjaro/stable/$repo/$arch
    12: https://mirror.koddos.net/manjaro/stable/$repo/$arch
    13: https://mirror.2degrees.nz/manjaro/stable/$repo/$arch
    14: https://ba.mirror.garr.it/mirrors/manjaro/stable/$repo/$arch
    15: http://ftp.tsukuba.wide.ad.jp/Linux/manjaro/stable/$repo/$arch
    16: https://mnvoip.mm.fcix.net/manjaro/stable/$repo/$arch
    17: https://mirrors.piconets.webwerks.in/manjaro-mirror/stable/$repo/$arch
    18: http://free.nchc.org.tw/manjaro/stable/$repo/$arch
    19: https://mirror.albony.xyz/manjaro/stable/$repo/$arch
    20: https://ftp.gwdg.de/pub/linux/manjaro/stable/$repo/$arch
    21: https://mirror.archlinux.tw/Manjaro/stable/$repo/$arch
    22: https://mirror.netcologne.de/manjaro/stable/$repo/$arch
    23: https://ftp.psnc.pl/linux/manjaro/stable/$repo/$arch
    24: https://mirror.phoepsilonix.love/manjaro/stable/$repo/$arch
    25: http://manjaro.grena.ge/stable/$repo/$arch
    26: https://mirrors.dotsrc.org/manjaro/stable/$repo/$arch
    27: https://nocix.mm.fcix.net/manjaro/stable/$repo/$arch
    28: https://mirrors.pku.edu.cn/manjaro/stable/$repo/$arch
    29: https://ftp.cc.uoc.gr/mirrors/linux/manjaro/stable/$repo/$arch
    30: https://ftp.nluug.nl/pub/os/Linux/distr/manjaro/stable/$repo/$arch
    31: https://cofractal-ewr.mm.fcix.net/manjaro/stable/$repo/$arch
    32: https://mirror.xenyth.net/manjaro/stable/$repo/$arch
    33: https://mirrors.netix.net/manjaro/stable/$repo/$arch
    34: https://uvermont.mm.fcix.net/manjaro/stable/$repo/$arch
    35: https://mirror.ufro.cl/manjaro/stable/$repo/$arch
    36: https://ask4.mm.fcix.net/manjaro/stable/$repo/$arch
    37: http://ftp.snt.utwente.nl/pub/linux/manjaro/stable/$repo/$arch
    38: https://www.mirrorservice.org/sites/repo.manjaro.org/repos/stable/$repo/$arch
    39: https://mirror.dc.uz/manjaro/stable/$repo/$arch
    40: https://mirrors.gigenet.com/manjaro/stable/$repo/$arch
    41: https://mirror1.sox.rs/manjaro/stable/$repo/$arch
    42: http://ftp.rz.tu-bs.de/pub/mirror/manjaro.org/repos/stable/$repo/$arch
    43: http://ftp.dei.uc.pt/pub/linux/manjaro/stable/$repo/$arch
    44: https://mirror.vinehost.net/manjaro/stable/$repo/$arch
    45: https://fosszone.csd.auth.gr/manjaro/stable/$repo/$arch
    46: https://mirror.easyname.at/manjaro/stable/$repo/$arch
    47: https://manjaro.mirrors.lavatech.top/stable/$repo/$arch
    48: https://mirror.init7.net/manjaro/stable/$repo/$arch
    49: https://manjaro.mirror.liquidtelecom.com/stable/$repo/$arch
    50: http://ftp.uni-kl.de/pub/linux/manjaro/stable/$repo/$arch
    51: https://ohioix.mm.fcix.net/manjaro/stable/$repo/$arch
    52: https://southfront.mm.fcix.net/manjaro/stable/$repo/$arch
    53: http://ftp.free.org/mirrors/repo.manjaro.org/repos/stable/$repo/$arch
    54: https://mirror.alpix.eu/manjaro/stable/$repo/$arch
    55: https://mirror.yandex.ru/mirrors/manjaro/stable/$repo/$arch
    56: https://ftpmirror1.infania.net/mirror/manjaro/stable/$repo/$arch
    57: http://manjaro.mirrors.uk2.net/stable/$repo/$arch
    58: https://mirror.bardia.tech/manjaro/stable/$repo/$arch
    59: https://mirror.math.princeton.edu/pub/manjaro/stable/$repo/$arch
    60: http://mirror.xeonbd.com/manjaro/stable/$repo/$arch
    61: https://mirrors.xtom.ee/manjaro/stable/$repo/$arch
    62: http://mirror.fcix.net/manjaro/stable/$repo/$arch
    63: http://ftp.belnet.be/mirrors/manjaro/repos/stable/$repo/$arch
    64: https://repos.silknet.com/manjaro/stable/$repo/$arch
    65: https://coresite.mm.fcix.net/manjaro/stable/$repo/$arch
    66: https://mirror.ibakerserver.pt/manjaro/stable/$repo/$arch
    67: https://mirror.freedif.org/Manjaro/stable/$repo/$arch
    68: https://codingflyboy.mm.fcix.net/manjaro/stable/$repo/$arch
    69: https://irltoolkit.mm.fcix.net/manjaro/stable/$repo/$arch
    70: https://mirror.dkm.cz/manjaro/stable/$repo/$arch
    71: https://mirror.csclub.uwaterloo.ca/manjaro/stable/$repo/$arch
    72: https://mirror.truenetwork.ru/manjaro/stable/$repo/$arch
    73: https://mirrors.sonic.net/manjaro/stable/$repo/$arch
    74: http://mirror.is.co.za/mirrors/manjaro.org/stable/$repo/$arch
    75: https://mirrors.up.pt/pub/manjaro/stable/$repo/$arch
    76: https://mirrors.ustc.edu.cn/manjaro/stable/$repo/$arch
    77: https://mirrors.xtom.jp/manjaro/stable/$repo/$arch
    78: https://mirror.nju.edu.cn/manjaro/stable/$repo/$arch
    79: https://edgeuno-bog2.mm.fcix.net/manjaro/stable/$repo/$arch
    80: https://mirrors.ocf.berkeley.edu/manjaro/stable/$repo/$arch
    81: https://mirror.alwyzon.net/manjaro/stable/$repo/$arch
    82: https://mirror.futureweb.be/manjaro/stable/$repo/$arch
    83: https://mirror.leitecastro.com/manjaro/stable/$repo/$arch
    84: https://ftp.lysator.liu.se/pub/manjaro/stable/$repo/$arch
    85: https://repo.ialab.dsu.edu/manjaro/stable/$repo/$arch
    86: https://manjaro.mirror.wearetriple.com/stable/$repo/$arch
    87: https://ftp.caliu.cat/pub/distribucions/manjaro/stable/$repo/$arch
    88: https://ftp.linux.org.tr/manjaro/stable/$repo/$arch
    89: http://ftp.tu-chemnitz.de/pub/linux/manjaro/stable/$repo/$arch
    90: https://mirror.23m.com/manjaro/stable/$repo/$arch
    91: http://kartolo.sby.datautama.net.id/manjaro/stable/$repo/$arch
    92: https://mirrors2.manjaro.org/stable/$repo/$arch
    93: https://ct.mirror.garr.it/mirrors/manjaro/stable/$repo/$arch
    94: https://gsl-syd.mm.fcix.net/manjaro/stable/$repo/$arch
    95: https://quantum-mirror.hu/mirrors/pub/manjaro/stable/$repo/$arch
    96: https://manjaro.ipacct.com/manjaro/stable/$repo/$arch
    97: https://mirrors.jlu.edu.cn/manjaro/stable/$repo/$arch
    98: https://mirrors.xtom.de/manjaro/stable/$repo/$arch
    99: http://mirror.terrahost.no/linux/manjaro/stable/$repo/$arch
    100: https://mirrors.aliyun.com/manjaro/stable/$repo/$arch
    101: https://mirror.raiolanetworks.com/manjaro/stable/$repo/$arch
    102: https://mirrors.ucr.ac.cr/manjaro/stable/$repo/$arch
    103: https://nnenix.mm.fcix.net/manjaro/stable/$repo/$arch
    104: https://mirror.nyist.edu.cn/manjaro/stable/$repo/$arch
    105: https://mirror.kku.ac.th/manjaro/stable/$repo/$arch
    106: http://manjaro.mirror.ac.za/stable/$repo/$arch
    107: http://ossmirror.mycloud.services/os/linux/manjaro/stable/$repo/$arch
    108: https://mirror.kamtv.ru/manjaro/stable/$repo/$arch
    109: https://mirrors.manjaro.org/repo/stable/$repo/$arch
    110: https://manjaro.kurdy.org/stable/$repo/$arch
    111: https://ridgewireless.mm.fcix.net/manjaro/stable/$repo/$arch
    112: https://ftp.halifax.rwth-aachen.de/manjaro/stable/$repo/$arch
    113: https://ziply.mm.fcix.net/manjaro/stable/$repo/$arch
    114: http://mirror.datacenter.by/pub/mirrors/manjaro/stable/$repo/$arch
    115: https://mirrors.nic.cz/manjaro/stable/$repo/$arch
    116: https://mirror.bouwhuis.network/manjaro/stable/$repo/$arch
    117: https://mirrors.sjtug.sjtu.edu.cn/manjaro/stable/$repo/$arch
    118: https://mirror.ufam.edu.br/manjaro/stable/$repo/$arch
    119: https://mirrors.atlas.net.co/manjaro/stable/$repo/$arch
    120: https://manjaro.repo.cure.edu.uy/stable/$repo/$arch
    121: https://mirror.telepoint.bg/manjaro/stable/$repo/$arch
    122: https://mirror.it4i.cz/manjaro/stable/$repo/$arch
    123: https://manjaro.ynh.ovh/stable/$repo/$arch
    124: https://mirrors.cicku.me/manjaro/stable/$repo/$arch
    125: https://fastmirror.pp.ua/manjaro/stable/$repo/$arch
    126: https://mirror.funami.tech/manjaro/stable/$repo/$arch
    127: https://linorg.usp.br/manjaro/stable/$repo/$arch
    128: https://mirrors.tuna.tsinghua.edu.cn/manjaro/stable/$repo/$arch
    129: https://forksystems.mm.fcix.net/manjaro/stable/$repo/$arch
    130: https://mirror.seahost.de/manjaro/stable/$repo/$arch
    131: https://manjarolinux-mirror.cloud.mu/stable/$repo/$arch
    132: http://ftp.riken.jp/Linux/manjaro/stable/$repo/$arch
Processes:
  CPU top: 5 of 343
  1: cpu: 45.9% command: firefox pid: 28549 mem: 576.2 MiB (1.8%)
  2: cpu: 21.7% command: plasma-systemmonitor pid: 28489
    mem: 275.8 MiB (0.8%)
  3: cpu: 14.2% command: firefox pid: 28804 mem: 277.5 MiB (0.8%)
  4: cpu: 13.7% command: konsole pid: 29151 mem: 123.4 MiB (0.3%)
  5: cpu: 7.7% command: kwin_x11 pid: 27085 mem: 262.1 MiB (0.8%)
  Memory top: 5 of 343
  1: mem: 716.8 MiB (2.2%) command: plasmashell pid: 27100 cpu: 2.4%
  2: mem: 576.2 MiB (1.8%) command: firefox pid: 28549 cpu: 45.9%
  3: mem: 277.5 MiB (0.8%) command: firefox pid: 28804 cpu: 14.2%
  4: mem: 275.8 MiB (0.8%) command: plasma-systemmonitor pid: 28489
    cpu: 21.7%
  5: mem: 268.5 MiB (0.8%) command: kinfocenter pid: 28459 cpu: 1.7%
Info:
  Processes: 343 Power: uptime: 15m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 12.41 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
    tool: systemctl
  Compilers: N/A Shell: Zsh v: 5.9 running-in: konsole inxi: 3.3.36

Mod edit: Fixed formatting of inxi output. Members are reminded that 3 backticks (```) should be typed before and after any pasted terminal output.

This is fine; there will be minor differences, but nothing that will prevent information being recognised.

It doesn’t seem too healthy.

Is a complete reinstall with the latest available ISO an option for you? Let’s hope it doesn’t come to that, but sometimes it can be the fastest way back to a working system.

I notice this USB device was created using an msdos/mbr partitioning scheme. Is this the USB device you use for your Manjaro Installer USB?

If it is, you will need to recreate it and make sure it uses a GPT partitioning scheme, and boots as UEFI.

Then you would need to reinstall Manjaro from the new USB.

If this device is not your Manjaro Installer USB, you can safely ignore this; though it would be preferable to not have a msdos/mbr device connected while installing a UEFI system.

It’s likely slow in the forum at this time of the year, but check in occasionally to see if anyone has a suggestion or two.

Regards.

1 Like

That is not an option for me since I have lots of data and preferences that haven’t been backed up in some way.
From what I have read on the Manjaro wiki so far, I can only suspect that the source of the problem was when I was installing and uninstalling kernels and nvidia drivers via the hardware manager without synchronizing them. I think I only used shutdown instead of rebooting after making those changes before the big freezes began to happen.

would you like me to display a “# journalctl -b” through TTY in this case?

It’s weird, Rufus says that it couldn’t form a GPT scheme from the Manjaro ISO. It works fine so far but I probably shouldn’t take any more chances, do you recommend another Boot device software that isn’t Rufus and also works on Windows?

Absolutely. Ventoy.
You will understand why as you read on.

Most of the following Ventoy information is geared for use from Linux, but there is also a Windows commandline and GUI version of Ventoy.


Unfortunate, though it would still be possible, if it came to that. Your personal data (with most settings) is generally the main concern; this is why I always have /home on a separate partition – using the manual partitioning method during install is the best way to achieve this – in this way you can opt not to reformat your /home partition, and recovery is fairly easy. Of course, applications would need to be reinstalled (but there are ways to make that less difficult too).

Without a separate partition its also possible to copy your /home content elsewhere and copy it back after a new istall.

If it comes down to either of these scenarios you can open a new thread to seek more information.


It might help someone.

Also, the outputs of sudo blkid and/or lsblk -o full might be useful.


Ventoy

Boot with a Ventoy USB, and ISO files are automatically listed in the Ventoy menu, and can be booted directly. A 32GB capacity USB should allow ample space to store several ISOs of your choice; an 8GB capacity USB might hold one, or two ISO’s; do the math.

Ventoy is available from the official Manjaro extra repository:

sudo pacman -S ventoy

Write the Ventoy system to an empty USB drive;

  • target the device itself /dev/sdX, and not a partition

Create a Ventoy USB (for UEFI mode): :eyes:

sudo sh ventoy -i -r 100 -S -g -L VOLUME /dev/sdX

Create a Ventoy USB (for BIOS mode):

sudo sh ventoy -i -r 100 -S -L VOLUME /dev/sdX

  • Enable -s or disable -S Secure Boot.
  • Substitute VOLUME for a volume label name to use.
  • Substitute /dev/sdX for the location of your USB device.
  • Preserve some space on the target device (example allows 100mb).

Ventoy general usage

Type ventoy (without arguments) to see usage information:

Usage:  Ventoy2Disk.sh CMD [ OPTION ] /dev/sdX  
 CMD:  
  -i  install Ventoy to sdX (fails if disk already installed with Ventoy)  
  -I  force install Ventoy to sdX (no matter if installed or not)  
  -u  update Ventoy in sdX  
  -l  list Ventoy information in sdX  
  
 OPTION: (optional)  
  -r SIZE_MB  preserve some space at the bottom of the disk (only for install)  
  -s/-S       enable/disable secure boot support (default is enabled)  
  -g          use GPT partition style, default is MBR (only for install)  
  -L          Label of the 1st exfat partition (default is Ventoy)  
  -n          try non-destructive installation (only for install)

Update a Ventoy USB:

  • ensure the updated Ventoy version is available in Manjaro; and then:

To update the Ventoy system on an existing Ventoy USB;

sudo ventoy -u /dev/sdX
  • The Ventoy USB update process is non-destructive.

See also: Ventoy (GitHub);


There is a Windows GUI version of Ventoy. If you choose to use it please pay attention to available options in the File menu before creating the Ventoy USB.

Regards.

1 Like

How about my previous post?

when logged in on TTY, stop and disable the display manager
and either reboot and try to startx or startw
or try startx or startw directly after you stopped the display manager.

Result?
After disabling the display manager you should have six or seven TTY’s to choose from - but no display manager.

You can always start and enable it again.
Not as root!

2 Likes

I think I found a similar topic here: Manjaro boots into tty1, graphics disabled - #4 by Lasslos
I know you said no root but for some reason, I don’t know what sign-in I’m supposed to use since root is the only one that doesn’t say “login incorrect” when typing my password. What login account should I have been using other than root?