Fresh install T14 ThinkPad: ACPI - Can't tag data node

Support
,
1

Attempting to install Manjaro on a T14 gen 6 Thinkpad, Intel.

Currently, when removing quiet from the boot parameters and booting with F10 I get the following lines

[0.xxxxxxx] ACPI: \: Can't tag data node
[0.xxxxxxx] ACPI: \: Can't tag data node
[0.xxxxxxx] ACPI: \: Can't tag data node
[0.xxxxxxx] ACPI: \: Can't tag data node
[0.xxxxxxx] ACPI: \: Can't tag data node
:: running early hook [udev]
:: running hook [udev]
:: Triggering uevents...

And then it just hangs indefinitely.

What’s happened so far:

  1. Put image on USB, booted into and installed alongside windows bootloader
  2. After installation I updated mirrors and pacman -Syyu had no glaring errors, a few firmware warnings
  3. Upon restart the above ACPI errors occurred
  4. Attempted to reinstall and this time wiped out the windows bootloader (oops), same problems persisted

I have not been able to manjaro-chroot -a from the live USB and attempted acpi=off, acpi=strict in the boot parameters with no success. In terms of BIOS settings, secure boot is disabled and there is no setting for ‘fast boot’ that I can see or anything related to power management. Any combination of Ctrl+Alt+Fx has not helped when stalled on the black screen. I do have access to grub command line.

What I can do next is re-install a third time but choose a different kernel or try to configure some things when I’m inside… Looking for advice on how to troubleshoot further.

2

Hi there, I dealed with thinkpads in the past (T480/T480s and T14 Gen1 AMD), regarding firmware, to update the firmware on a Lenovo ThinkPad T14 Gen 6 you can use fwupd and fwupdmgr. Ensure that the necessary BIOS settings (like “Enable Windows Update UEFI Update”) are enabled. The fwupd utility can update system firmware (UEFI), and there may be newer versions available through the LVFS (Linux Vendor Firmware Service) than in the BIOS update ISO.

Btw is a T14 or a T14s? Intel or AMD?
Please provide more data, output of the command inxi -zv8 would be great!

1 Like
3

I would start by manual chroot and install a couple more firmware packets.

1 Like
4

Thanks… turns out I should know how to do this already since I had to do it not long ago on an X1.

For future reference though… how do I get access to a terminal when its like this? As I mentioned there is no success with TTY and chrooting with manjaro-chroot -a gives grub-prob: error: cannot find a GRUB drive for /dev/sda1. Check your device.map. => No linux partitions detected.

I’m going to reinstall a third time and fiddle with the firmware manager - it was a real pain last time!

update: reinstalled and updated firmware, prompted to restart and now back to the original issue.

Manual chrooting with this guide: [HowTo] Chroot from or into any Linux distribution is not straightforward. After mounting mount /dev/sda /chroot contains boot/, boot.catalog, efi/, efi.img, manjaro/ and there are no system directories to bind to.

5

some thoughts:

/dev/sda

is a whole device, not a partition on a device (like: /dev/sda1 …)
The guide you referenced used # to denote this partition number - for example:

When you have found the right partition, we shall now mount it by executing mount /dev/sdX# /chroot

Something is amiss here - or you misinterpreted the result of:
lsblk

I usually use:
lsblk -f
which usually gives enough identifying information on which partition holds which file system and how to assemble the file system before entering chroot

manjaro-chroot usually does work

If not in automatic mode (manjaro-chroot -a),
then after mounting the partitions manually in the correct order and then using:
manjaro-chroot /mountpoint

If you need help, share lsblk -f

6

Thanks. Yes it should be sda1. When doing mount /dev/sda1 /chroot I get:
mount: /chroot: fsconfig() failed: /dev/sda1: Can't open blockdev.

The output of lsblk -f is

NAME | FSTYPE | FSVER | LABEL | UUID
loop0 ...
loop1 ...
loop2 ...
sda | iso9660 | Joliet Extension | Manjaro_I3_2503 | date
sda1 | iso9660 | Joliet Extension | Manjaro_I3_2503 | date
sda2 | vfat | FAT12 | MISO_EFI |
nvme0n1 ...

Did I not make the bootable correctly…

Just to be clear, the idea here of chroot is to access the currently installed manjaro (on the main SSD) via the live USB so that I can make a few changes with the hope that I can successfully reboot?

Any idea why solutions like the ones here https://askubuntu.com/questions/240293/my-laptop-only-boots-with-the-acpi-off-parameter-how-can-i-fix-this aren’t working?

7

… incomplete

It doesn’t show anything on the nvme disk
where the system you want to chroot into presumably is.

I didn’t pay any attention to the last sentence “Any idea why …”

Before chroot you need to mount at least two partitions:
one EFI
and
your system root

8

Sorry -

NAME | FSTYPE | FSVER | LABEL | UUID
loop0 ...
loop1 ...
loop2 ...
sda | iso9660 | Joliet Extension | Manjaro_I3_2503 | date
sda1 | iso9660 | Joliet Extension | Manjaro_I3_2503 | date
sda2 | vfat | FAT12 | MISO_EFI |
nvme0n1 
nvme0n1p1 | vfat  | FAT32 |     | some numbers
nvme0n1p2 | btrfs |       |     | some numbers
9

Your system root is on BTRFS

There is a guide on how to chroot into that.

I’d have to look for it - it’s here on the forum.

Someone will know - or you can search yourself.
(I hate the search feature on this forum …)

… found something:
The info you need is somewhat contained in here:

GRUB/Restore the GRUB Bootloader - Manjaro

(section: manual chroot)

10

Right… I think this is getting a bit beyond me. I might just re-install with ext4 and hope that a different choice of kernel fixes the issue. Why are laptops always such a pain

update:
mount: /chroot: fsconfig() failed: iso9660: Unknown parameter 'subvol'.
when doing
mount -o subvol=@ /dev/sda1 /chroot , still with btrfs for now.

Probably a wise choice to use a file system you are familiar with.

yes i don’t need btrfs, it was just the default selected on the installer and i didn’t notice. the snapshot thing does look cool however

11

Probably a wise choice to use a file system you are familiar with.

I don’t know what hardware issues there might be on a

There is the command:
inxi -zv8
to see and possibly share it here.

Thinkpads seem to be well supported:

Laptop/Lenovo - ArchWiki

1 Like
13

I have now re-installed with ext4 filesystem. I played kernel roulette and with linux61 I have the same error but am able to tty with Fn+Alt+F2.

The (linux61) errors now reads:

[0.xxxxxxx] ACPI: \: Can't tag data node (x5)
[0.xxxxxxx] acpi ACPI10007:00: invalid PBLK length [xxxxxx] (x8)
tpm tpm0: [Firmware bug]: TPM interrupt not working, polling instead
:: running early hook [udev]
:: running hook [udev]
:: Triggering uevents...
:: running hook [keymap]
:: Loading keymap...loadkmap: shortread
done.
:: Performing fsck on 'xxx'
:: Mounting 'xxx' on real root
:: running cleanup hook [udev]
Welcome to Manjaro!

And then the Manjaro startup runs up until the line of “[ OK ] Started Accounts Service.” As for the firmware bug line, I followed the Lenovo instructions.

As for what seem to be general firmware issues (ACPI errors), I ran fwupdmgr get-devices and under the branch “System Firmware” there are 5 “Update Error”'s under the following sections:

  1. PK CA
  2. UEFI Key Exchange Key
    2.1 Windows UEFI CA
  3. UEFI Signature Database
  4. UEFI dbx

which read “getting efivars free space is not supported”. No update is offered when running fwupdmgr update, though I did get prompted to update, and did so, on a previous install (see original post). And then df -l /sys/firmware/efi/efivars/ is empty/has no size?

Output of inxi -zv8:

System:
  Kernel: 6.1.146-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.1.1 clocksource: tsc
    avail: acpi_pm parameters: BOOT_IMAGE=/boot/vmlinuz-6.1-x86_64
    root=UUID=cd20d0c7-f4ce-4847-bb93-652f990edcf2 rw apparmor=1 security=apparmor
    udev.log_priority=3
  Console: tty 2 DM: LightDM v: 1.32.0 Distro: Manjaro base: Arch Linux
Machine:
  Type: Laptop System: LENOVO product: 21QGCTO1WW v: ThinkPad T14 Gen 6
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: LENOVO model: 21QGCTO1WW v: SDK0T76574 WIN serial: <superuser required>
    part-nu: LENOVO_MT_21QG_BU_Think_FM_ThinkPad T14 Gen 6 uuid: <superuser required> UEFI: LENOVO
    v: N4HET17W (1.05 ) date: 04/14/2025
Battery:
  ID-1: BAT0 charge: 56.2 Wh (98.6%) condition: 57.0/57.0 Wh (100.0%) power: 4.0 W volts: 17.7
    min: 15.6 model: Sunwoda 5B11M90127 type: Li-poly serial: <filter> status: discharging cycles: 1
Memory:
  System RAM: total: 32 GiB available: 30.88 GiB used: 706.8 MiB (2.2%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 32 GiB slots: 8 modules: 8 EC: None max-module-size: 4 GiB note: est.
  Device-1: Controller0-ChannelA type: LPDDR5 detail: synchronous size: 4 GiB speed: 8533 MT/s
    volts: curr: 0.5 width (bits): data: 16 total: 16 manufacturer: Micron Technology part-no: N/A
    serial: <filter>
  Device-2: Controller0-ChannelB type: LPDDR5 detail: synchronous size: 4 GiB speed: 8533 MT/s
    volts: curr: 0.5 width (bits): data: 16 total: 16 manufacturer: Micron Technology part-no: N/A
    serial: <filter>
  Device-3: Controller0-ChannelC type: LPDDR5 detail: synchronous size: 4 GiB speed: 8533 MT/s
    volts: curr: 0.5 width (bits): data: 16 total: 16 manufacturer: Micron Technology part-no: N/A
    serial: <filter>
  Device-4: Controller0-ChannelD type: LPDDR5 detail: synchronous size: 4 GiB speed: 8533 MT/s
    volts: curr: 0.5 width (bits): data: 16 total: 16 manufacturer: Micron Technology part-no: N/A
    serial: <filter>
  Device-5: Controller1-ChannelA type: LPDDR5 detail: synchronous size: 4 GiB speed: 8533 MT/s
    volts: curr: 0.5 width (bits): data: 16 total: 16 manufacturer: Micron Technology part-no: N/A
    serial: <filter>
  Device-6: Controller1-ChannelB type: LPDDR5 detail: synchronous size: 4 GiB speed: 8533 MT/s
    volts: curr: 0.5 width (bits): data: 16 total: 16 manufacturer: Micron Technology part-no: N/A
    serial: <filter>
  Device-7: Controller1-ChannelC type: LPDDR5 detail: synchronous size: 4 GiB speed: 8533 MT/s
    volts: curr: 0.5 width (bits): data: 16 total: 16 manufacturer: Micron Technology part-no: N/A
    serial: <filter>
  Device-8: Controller1-ChannelD type: LPDDR5 detail: synchronous size: 4 GiB speed: 8533 MT/s
    volts: curr: 0.5 width (bits): data: 16 total: 16 manufacturer: Micron Technology part-no: N/A
    serial: <filter>
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: Intel Core Ultra 7 258V bits: 64 type: MCP arch: Lunar Lake level: v3 note: check
    built: 2024+ process: TSMC n3b (3nm) family: 6 model-id: 0xBD (189) stepping: 1 microcode: 0x11F
  Topology: cpus: 1x dies: 1 clusters: 5 cores: 8 smt: <unsupported> cache: 12 MiB note: check
  Speed (MHz): avg: 400 min/max: 400/4300:4400:3700 scaling: driver: intel_pstate
    governor: powersave cores: 1: 400 2: 400 3: 400 4: 400 5: 400 6: 400 7: 400 8: 400
    bogomips: 52667
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat arch_capabilities arch_lbr
    arch_perfmon art avx avx2 avx_vnni bmi1 bmi2 bts bus_lock_detect clflush clflushopt clwb 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 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 invpcid_single
    lahf_lm lm mca mce md_clear mmx monitor movbe movdir64b movdiri msr mtrr nonstop_tsc nopl nx
    ospke pae pat pbe pcid pclmulqdq pconfig pdcm pdpe1gb pebs pge pku pln pni popcnt pse pse36
    pts rdpid rdrand rdseed rdt_a rdtscp rep_good sdbg sep serialize sha_ni smap smep smx 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 vaes vme vmx vnmi vpclmulqdq vpid waitpkg wbnoinvd
    x2apic xgetbv1 xsave xsavec xsaveopt xsaves xtopology xtpr
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: indirect_target_selection 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 status: Not affected
  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; PBRSB-eIBRS: Not
    affected; BHI: BHI_DIS_S
  Type: srbds status: Not affected
  Type: tsa status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel Lunar Lake [Intel Arc Graphics 130V / 140V] vendor: Lenovo driver: N/A arch: Xe2
    process: TSMC n3 (3nm) built: 2024+ bus-ID: 00:02.0 chip-ID: 8086:64a0 class-ID: 0300
  Device-2: Bison Integrated Camera driver: uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1
    mode: 2.0 bus-ID: 3-4:2 chip-ID: 5986:11af class-ID: fe01 serial: <filter>
  Display: unspecified server: X.org v: 1.21.1.18 driver: X: loaded: modesetting
    alternate: fbdev,vesa dri: iris gpu: N/A tty: 240x75
  API: EGL v: 1.5 platforms: device: 0 drv: swrast surfaceless: drv: swrast
    inactive: gbm,wayland,x11
  API: OpenGL v: 4.5 vendor: mesa v: 25.1.6-arch1.1 note: console (EGL sourced)
    renderer: llvmpipe (LLVM 20.1.8 256 bits)
  Info: Tools: api: eglinfo,glxinfo x11: xprop,xrandr
Audio:
  Device-1: Intel Lunar Lake-M HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel
    bus-ID: 00:1f.3 chip-ID: 8086:a828 class-ID: 0403
  API: ALSA v: k6.1.146-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
Network:
  Device-1: Intel BE201 320MHz driver: N/A modules: iwlwifi port: N/A bus-ID: 00:14.3
    chip-ID: 8086:a840 class-ID: 0280
  Device-2: Intel vendor: Lenovo driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6
    chip-ID: 8086:550f class-ID: 0200
  IF: enp0s31f6 state: down mac: <filter>
  Info: services: mld, NetworkManager, systemd-timesyncd
  WAN IP: No WAN IP found. Connected to web? SSL issues? Try enabling dig
Bluetooth:
  Device-1: Intel driver: N/A bus-ID: 00:14.7 chip-ID: 8086:a876 class-ID: 0d11
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 480.69 GiB used: 9.66 GiB (2.0%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Lenovo model: UMIS RPETJ512MMW1MDQ size: 476.94 GiB
    block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 1.0Q06B0 temp: 27.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Generic model: Flash Disk size: 3.75 GiB block-size:
    physical: 512 B logical: 512 B type: USB rev: 2.0 spd: 480 Mb/s lanes: 1 mode: 2.0 tech: SSD
    serial: <filter> fw-rev: 8.07 scheme: MBR
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 476.64 GiB size: 468.09 GiB (98.21%) used: 9.62 GiB (2.1%) fs: ext4
    dev: /dev/nvme0n1p2 maj-min: 259:2 label: N/A uuid: cd20d0c7-f4ce-4847-bb93-652f990edcf2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) used: 320 KiB (0.1%) fs: vfat
    dev: /dev/nvme0n1p1 maj-min: 259:1 label: N/A uuid: 1D39-D50F
  ID-3: /mnt raw-size: 3.75 GiB size: 3.74 GiB (99.80%) used: 39.3 MiB (1.0%) fs: vfat
    dev: /dev/sda1 maj-min: 8:1 label: N/A uuid: E09F-4684
Swap:
  Alert: No swap data was found.
Unmounted:
  Message: No unmounted partitions found.
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 1 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s)
    lanes: 1 mode: 2.0 chip-ID: 1d6b:0002 class-ID: 0900
  Hub-2: 2-0:1 info: super-speed hub ports: 3 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
  Hub-3: 3-0:1 info: hi-speed hub with single TT ports: 8 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: 3-4:2 info: Bison Integrated Camera type: video driver: uvcvideo interfaces: 5
    rev: 2.0 speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 500mA chip-ID: 5986:11af
    class-ID: fe01 serial: <filter>
  Hub-4: 3-5:3 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:0610 class-ID: 0900
  Device-1: 3-6:4 info: Alcor Micro Flash Drive type: mass storage driver: usb-storage
    interfaces: 1 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 200mA
    chip-ID: 058f:6387 class-ID: 0806 serial: <filter>
  Hub-5: 4-0:1 info: super-speed hub ports: 2 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
Sensors:
  System Temperatures: cpu: 33.0 C mobo: N/A
  Fan Speeds (rpm): fan-1: 0
Repos:
  Packages: pm: pacman pkgs: 1144 libs: 341 tools: pamac
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://gsl-syd.mm.fcix.net/manjaro/stable/$repo/$arch
    2: https://mirror.aarnet.edu.au/pub/manjaro/stable/$repo/$arch
Processes:
  CPU top: 5 of 162
  1: cpu: 0.0% command: init pid: 1 mem: 13.6 MiB (0.0%)
  2: cpu: 0.0% command: [kthreadd] pid: 2 mem: 0.00 MiB (0.0%)
  3: cpu: 0.0% command: [rcu_gp] pid: 3 mem: 0.00 MiB (0.0%)
  4: cpu: 0.0% command: [rcu_par_gp] pid: 4 mem: 0.00 MiB (0.0%)
  5: cpu: 0.0% command: [slub_flushwq] pid: 5 mem: 0.00 MiB (0.0%)
  Memory top: 5 of 162
  1: mem: 24.9 MiB (0.0%) command: NetworkManager pid: 721 cpu: 0.0%
  2: mem: 24.0 MiB (0.0%) command: systemd-journald pid: 347 cpu: 0.0%
  3: mem: 13.6 MiB (0.0%) command: init pid: 1 cpu: 0.0%
  4: mem: 11.8 MiB (0.0%) command: ModemManager pid: 763 cpu: 0.0%
  5: mem: 11.1 MiB (0.0%) command: systemd pid: 3376 cpu: 0.0%
Info:
  Processes: 162 Power: uptime: 38m states: freeze,mem,disk suspend: s2idle wakeups: 0
    hibernate: platform avail: shutdown, reboot, suspend, test_resume image: 12.34 GiB Init: systemd
    v: 257 default: graphical tool: systemctl
  Compilers: gcc: 15.1.1 Shell: Bash (login) v: 5.3.0 running-in: tty 2 inxi: 3.3.38

Mod edit:- Corrected malformed URL plus minor edits for continuity. No charge.

15

It seems not; and you still haven’t.

I don’t know how you created the Installer USB, whether using Rufus or some other method, but clearly you made the wrong configuration or command choices.

Important:

Both the installation target (the SSD) and the OS installer medium (the USB) must have a GPT partitioning scheme to successfully install a UEFI based OS.

  • Legacy mode in your BIOS should be disabled

:+1: Your SSD has a GPT partitioning scheme.
:-1: Your Installer USB has an MBR partitioning scheme.

You will need to either recreate the Manjaro Installer USB properly on a (preferably new) GPT partitioned USB.

…or…

Create a Ventoy USB instead (recommended);
follow this tutorial (carefully):

It’s time to re-install from scratch a fourth time.

Regards.

16

Thanks for this. I re-installed with Ventoy following your instructions and can confirm that both the SSD and USB have GPT partitioning scheme. Now, when running fwupdmgr get-devices there is no error regarding efivars.

There are no updates either and upon restarting I’m stuck with the same ACPI errors as above.

17

Are these acpi errors only
(I have some of those consistently)
or are they effectively preventing you to boot to a DE?

18

They are the only errors I can see when I restart after logging on to the fresh install for the first time. So, install, reboot, update with pacman -Syu and then on the second reboot I’m left at a black screen or, when removing quiet from the kernel params I see those acpi errors. If I’m on linux612 (ships with the iso) I am unable to do anything from that blackscreen and have to restart, which led me to the chrooting business earlier. On linux61 there seems to progress in that manjaro actually initiates but eventually just hangs indefinitely.

Because I am able to boot into the DE after install, I’m guessing the update is breaking something and preventing me from getting back in.

19

That is strange and unexpected.

I cannot help, though - my system hardware is much more than a decade older than yours.
(and it all works just fine)

20

Is your machine capable of Secure Boot, and if so, is it disabled in your BIOS? Manjaro does not support Secure Boot OOTB as some other distributions might.

At this time, it’s difficult to guess what the trouble may be. If you are able to boot into the Installer, chroot, and generate some logs, that might be useful to someone.

I’ll chime in again if anything else comes to mind.

Regards.

1 Like
21

Yes secure boot is disabled. I’ve been browsing this thread Error when trying to install Manjaro which looks somewhat familiar. All the checksums are ok.

Update: Small success (or not), I was able to boot into the DE with linux66. However, it feels completely bugged. Mousepad not working, wifi disabled, terminal is just blank with no cursor/username and there is no visual indication of changing workspaces

22

[root tip] [recovery] Basic Manjaro Linux Recovery