System Unresponsive to Input After Update

[Pspritechologist]

After updating my system tonight (not long at all since the last update) and rebooting, my system is entirely unresponsive to input. No mouse or keyboard input, and seemingly even pressing the power button doesn’t trigger a shutdown. The system itself seems to be running fine as notifications and such popped up as it sat there.
The Manjaro boot menu as well as the BIOS respond fine, and a livecd of Manjaro also responded perfectly fine, leading me to believe it’s not a hardware issue.

I tried restoring a Timeshift backup from the livecd (which caused some issues with Grub that I resolved), but the issue persists. The backup was from the other day so the update should have been reverted.

I’m sorry information is sparse and I’d be happy to provide as much info as I can, but I can’t actually issue any commands to the system outside of a chroot unless someone has an idea.

EDIT:
Some details I can add- I’ve tried unplugging and replugging the devices of course, as well as using different USB slots. The devices themselves receive power but otherwise don’t seem to function.
The controller I had plugged in had the ‘player 1’ light active as if it was connected, rather than only having the charging lights active if that means anything

Would really appreciate any help I can get with this.

[Wollie]

@Pspritechologist

even pressing the power button doesn’t trigger a shutdown

This only can be linked to firmware or hardware issues.

[linux-aarhus]

@Pspritechologist

Would really appreciate any help I can get with this.

With the provided information, there is no clues.

@Pspritechologist

The Manjaro boot menu as well as the BIOS respond fine, and a livecd of Manjaro also responded perfectly fine, leading me to believe it’s not a hardware issue.

The following seems obvious

• The system’s firmware can be loaded
• A live ISO loads
• Manjaro boot menu loads (grub)

Since the grub menu is shown - I am guessing you dual booting other operating systems.

Have you tried to switch to another TTY? Ctrl+Alt+F4, what happens?

If you get a prompt then your issue is related to graphics, and since your topic is tagged with xfce, I am thinking you are using Nvidia GPU.

If you can sign on to the system using a TTY then please provide the link from the following command

inxi -Fc0 | curl -F'file=@-' https://0x0.st

Make a note of the link and provide it for system information reference.

If you can only access the system using a live ISO, then please follow the guide to enter a chroot environment and inside the chroot run the above command.

[Pspritechologist]

I’m not dual booting- by ‘Manjaro boot menu’ I meant the actual Manjaro menu that gives you the option to use a different kernel, for instance.

I cannot open a TTY, thus not being able to issue commands. I find it unlikely to be a graphics issue as I mentioned the system was visually active- I watched a notification appear.

I am using Nvidia, but that’s not related to XCFE

I didn’t imagine using those commands in a chroot would’ve been useful, which is why I didn’t. Will do so and report back shortly today.

[linux-aarhus]

@Pspritechologist

I cannot open a TTY, thus not being able to issue commands. I find it unlikely to be a graphics issue as I mentioned the system was visually active- I watched a notification appear.

At the grub menu - press eon the selected item - and append the number three (3) to the kernel command line, then press F10 to continue starting the system.

You should reach a tty login.

[Pspritechologist]

I’m not completely certain about this- I’m not sure I know what the power button would normally do, I don’t typically use it

[Pspritechologist]

Would using a chroot be fine? It just means I can use my pc and respond here on it instead of my phone
Fine to do it if it gives better info that way though

[Pspritechologist]

Sorry, could you specify what I’m entering here? I’m taken to the ‘Minimum Emacs-like screen’ with a lot of spooky looking text, where am I entering a 3?
I’m not recognizing anything obviously kernel-like. Closest would be linux /boot/vmlinux-6.6-x86_64 root=.... I’m not sure if this is persistent so I’m cautious to just stab at it

In the mean time, here it is from the chroot.
https://0x0.st/PbBo.txt

System:
  Kernel: 6.12.4-1-MANJARO arch: x86_64 bits: 64
  Desktop: KDE Plasma v: ERR-101 Distro: Manjaro Linux
Machine:
  Type: Desktop Mobo: Micro-Star model: Z390-A PRO (MS-7B98) v: 1.0 serial: <filter> Firmware: UEFI
    vendor: American Megatrends v: 1.A0 date: 06/10/2020
CPU:
  Info: 6-core model: Intel Core i5-9600KF bits: 64 type: MCP cache: L2: 1.5 MiB
  Speed (MHz): avg: 800 min/max: 800/4700 cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800
Graphics:
  Device-1: NVIDIA GA104 [GeForce RTX 3070] driver: nvidia v: 550.135
  Display: server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9 driver: X: loaded: nvidia
    gpu: nvidia
  API: EGL v: 1.5 drivers: kms_swrast platforms: gbm
  API: OpenGL v: 4.5 vendor: mesa v: 25.3.3-arch1.1 note: incomplete (EGL sourced)
    renderer: llvmpipe (LLVM 21.1.6 256 bits)
  API: Vulkan Message: No Vulkan data available.
  Info: Tools: api: eglinfo, glxinfo, vulkaninfo de: xfce4-display-settings
    gpu: nvidia-settings,nvidia-smi x11: xprop,xrandr
Audio:
  Device-1: Intel Cannon Lake PCH cAVS driver: snd_hda_intel
  Device-2: NVIDIA GA104 High Definition Audio driver: snd_hda_intel
  Device-3: HP HyperX QuadCast 2 S driver: hid-generic,snd-usb-audio,usbhid type: USB
  API: ALSA v: k6.12.4-1-MANJARO status: kernel-api
Network:
  Device-1: Intel Ethernet I219-V driver: e1000e
  IF: eno1 state: down mac: <filter>
  Device-2: Qualcomm Atheros AR9462 Wireless Network Adapter driver: ath9k
  IF: wlp5s0 state: down mac: <filter>
  IF-ID-1: enp0s20f0u6 state: unknown speed: -1 duplex: half mac: <filter>
Bluetooth:
  Device-1: Samsung GT-I9070 (network tethering USB debugging enabled) driver: rndis_host type: USB
  Device-2: Foxconn / Hon Hai driver: btusb type: USB
  Report: ID: hci0 state: up address: <filter> bt-v: 4.1
Drives:
  Local Storage: total: 11.03 TiB used: 518.65 GiB (4.6%)
  ID-1: /dev/nvme0n1 vendor: Crucial model: CT1000P1SSD8 size: 931.51 GiB
  ID-2: /dev/nvme1n1 vendor: Western Digital model: WD BLACK SN850X 1000GB size: 931.51 GiB
  ID-3: /dev/sda vendor: Seagate model: ST2000DM008-2FR102 size: 1.82 TiB
  ID-4: /dev/sdb vendor: Western Digital model: WD8002FZBX-00C9HA0 size: 7.28 TiB
  ID-5: /dev/sdc vendor: SanDisk model: USB 3.2Gen1 size: 114.6 GiB type: USB
Partition:
  ID-1: / size: 881.65 GiB used: 518.65 GiB (58.8%) fs: ext4 dev: /dev/nvme1n1p2
  ID-2: /boot/efi size: 299.4 MiB used: 468 KiB (0.2%) fs: vfat dev: /dev/nvme1n1p1
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 40.0 C pch: 51.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 32 GiB available: 31.28 GiB used: 4.33 GiB (13.8%)
  Processes: 239 Uptime: 10m Client: systemd inxi: 3.3.40

Mod edit: Added inxi info here, as the upload may disappear.

[Aragorn]

@Pspritechologist

Sorry, could you specify what I’m entering here? I’m taken to the ‘Minimum Emacs-like screen’ with a lot of spooky looking text, where am I entering a 3?

At the end of the line, normally.

@Pspritechologist

I’m not recognizing anything obviously kernel-like.

What you should be seeing is a kernel boot line, describing which kernel image will be loaded, with what options, et al.

@Pspritechologist

I’m not sure if this is persistent so I’m cautious to just stab at it

An edit to the command line in the way explained by @linux-aarhus is not persistent. It only applies to the boot you’re about to invoke by pressing F10.

Besides, if you’re on btrfs, then grub can’t write to that anyway.

[Pspritechologist]

Not on BTRFS, no. Is interesting that so heavily seems to be the assumed default these days though.

I seem to recall the page having multiple lines, perhaps I entered the wrong one? I pressed ‘e’ to edit boot config I believe.

Still, if it’s not more useful than simply using a chroot env, I’d rather continue with that. A livecd is how I’m currently using my computer

[Aragorn]

@Pspritechologist

Not on BTRFS, no. Is interesting that so heavily seems to be the assumed default these days though.

It’s the default if no other filesystem type is chosen, starting with Manjaro 25.0.0 Zetar.

@Pspritechologist

I seem to recall the page having multiple lines, perhaps I entered the wrong one? I pressed ‘e’ to edit boot config if I believe.

It could be that the line is so long that it wraps. But if the grub selection bar is positioned over a specific entry, then you should be seeing a single kernel boot line after pressing E.

Just move the cursor to the end of the line, add a space, and type “3”. Then, pressing F10 should boot the system in text-only mode.

@Pspritechologist

Still, if it’s not more useful than simply using a chroot env, I’d rather continue with that.

It depends on what exactly you want to do. In the above scenario, your system is in full multi-user mode with operational networking, but without the graphical user interface.

Of course, if you want or need a GUI for system repair, then the live session is the easier option.

[Pspritechologist]

It could be that the line is so long that it wraps.

It was wrapping yeah, I just thought there were also multiple.

Of course, if you want or need a GUI for system repair, then the live session is the easier option.

It’s actually more so that I’m trying to still use my computer
I’m in a livecd just installing the small number of applications I need and doing my thing. Not ideal but better than not having access to my PC.

[musdus]

Hi @Pspritechologist,

Have you tried booting with a different kernel? In Manjaro you can install multiple kernels through the Settings Manager (Kernel section). Then at boot, press Esc (just before grub) to show the grub menu and pick one of the other installed kernels from “Advanced options.”

The frozen-but-still-displaying-things behavior is actually classic nvidia - the GPU keeps showing what’s in the framebuffer while the driver is completely wedged. That can also block ACPI, which explains why the power button doesn’t work.

Switching kernels is a quick way to check if a recent update broke something.

[nikgnomic]

System data shows out of date kernel (current supported kernel: linux612 6.12.68-1)
and unexpected Desktop Environment

System:
  Kernel: 6.12.4-1-MANJARO arch: x86_64 bits: 64
  Desktop: KDE Plasma

Graphics data shows out of date nvidia driver (latest driver: linux612-nvidia 590.48.01-7 )

Graphics:
  Device-1: NVIDIA GA104 [GeForce RTX 3070] driver: nvidia v: 550.135
  Display: server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9 driver: X: loaded: nvidia
    gpu: nvidia

  Info: Tools: api: eglinfo, glxinfo, vulkaninfo de: xfce4-display-settings
    gpu: nvidia-settings,nvidia-smi x11: xprop,xrandr

System Firmware/BIOS is also out of date

Machine:
  Type: Desktop Mobo: Micro-Star model: Z390-A PRO (MS-7B98) v: 1.0 serial: <filter> Firmware: UEFI
    vendor: American Megatrends v: 1.A0 date: 06/10/2020

msi.com - Z390-A-PRO - BIOS

Title	Version	Release Date	File Size
AMI BIOS	7B98v1F	2024-08-09	8.27 MB	Download

Root partition is using ext4 filesystem:

Partition:
  ID-1: / size: 881.65 GiB used: 518.65 GiB (58.8%) fs: ext4 dev: /dev/nvme1n1p2

@Aragorn

if you want or need a GUI for system repair, then the live session is the easier option

I suggest: Download and boot latest Live ISO manjaro-xfce-26.0.1-260114-linux618 and check if the keyboard and mouse is working with up to date packages

If keyboard and mouse is working in Live ISO, use manjaro-chroot to login to installed OS and update repository packages

sudo manjaro-chroot -a