Unable to boot after latest stable update

[caho]

The update works on three computers without problems. Also the change to the plasma login manager.

But after the update my main pc from the console via “pamac update” and reboot the system run after the grub menu into a black screen.

I cannot switch to a console and I cannot login remote via ssh.

So I downloaded the latest KDE ISO and I can boot them.

Not my question:
How I switch from the USB ISO to my manjaro-installation and then restore it with timeshift.

Here is my system:

The software was bevor this update up to date. The inxi output is from2021, but you can see the hardware etc.

System:    Host: TUXEDO Kernel: 5.10.2-2-MANJARO x86_64 bits: 64 Desktop: KDE Plasma 5.20.4 Distro: Manjaro Linux 
Machine:   Type: Laptop System: TUXEDO product: TUXEDO Pulse 15 Gen1 v: Standard serial: <superuser required> 
           Mobo: TUXEDO model: PULSE1501 v: Standard serial: <superuser required> UEFI: American Megatrends v: N.1.07.A02 
           date: 12/08/2020 
Battery:   ID-1: BAT0 charge: 91.6 Wh condition: 91.6/91.6 Wh (100%) 
CPU:       Info: 8-Core model: AMD Ryzen 7 4800H with Radeon Graphics bits: 64 type: MT MCP L2 cache: 4 MiB 
           Speed: 1397 MHz min/max: 1400/2900 MHz Core speeds (MHz): 1: 1397 2: 1397 3: 1618 4: 1628 5: 1616 6: 1629 7: 1622 
           8: 1623 9: 1395 10: 1396 11: 1396 12: 1393 13: 1397 14: 1395 15: 2806 16: 2782 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Renoir driver: amdgpu v: kernel 
           Device-2: Chicony HD Webcam type: USB driver: uvcvideo 
           Display: x11 server: X.Org 1.20.10 driver: amdgpu,ati unloaded: modesetting resolution: 1920x1080~60Hz 
           OpenGL: renderer: AMD RENOIR (DRM 3.40.0 5.10.2-2-MANJARO LLVM 11.0.0) v: 4.6 Mesa 20.3.1 
Audio:     Device-1: Advanced Micro Devices [AMD/ATI] driver: snd_hda_intel 
           Device-2: Advanced Micro Devices [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor driver: N/A 
           Device-3: Advanced Micro Devices [AMD] Family 17h HD Audio driver: snd_hda_intel 
           Sound Server: ALSA v: k5.10.2-2-MANJARO 
Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi 
           IF: wlp1s0 state: down mac: fa:e7:d7:c0:ca:c4 
           Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 
           IF: eno1 state: down mac: b0:25:aa:3d:fa:c5 
Drives:    Local Storage: total: 232.89 GiB used: 16.76 GiB (7.2%) 
           ID-1: /dev/nvme0n1 vendor: Kingston model: SA2000M8250G size: 232.89 GiB 
Partition: ID-1: / size: 219.86 GiB used: 16.76 GiB (7.6%) fs: ext4 dev: /dev/nvme0n1p2 
           ID-2: /boot/efi size: 511 MiB used: 312 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p1 
Swap:      ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) dev: /dev/nvme0n1p3 
Sensors:   System Temperatures: cpu: 39.6 C mobo: N/A gpu: amdgpu temp: 31.0 C 
           Fan Speeds (RPM): N/A 
Info:      Processes: 319 Uptime: 1m Memory: 7.26 GiB used: 878 MiB (11.8%) Shell: Bash inxi: 3.2.01 

can you help me, please

regards
caho

---

Mod edit: *I’ve moved your topic to a dedicated thread.

[linux-aarhus]

You can find instructions below - basic steps to enter chroot.

[root tip] [recovery] Basic Manjaro Linux Rescue and Recovery

Purpose It is not intended as a one-stop-solution guide. The intention is To Provide A Basic Understanding of the steps required to succesfully recover when an incident has prevented the operating system from loading. Requirements Basic understanding of using a console or virtual terminal to execute commands. Ability to edit configuration files using terminal a console editor like nano, micro or vi(m). You are willing to learn The knowledge gained and skills acquired will be applicable - n…

@discobot

Prepare the update beforehand

Preparation steps

From [INFO] Stable branch - BIG update BEST practice

If it has been a long time since your last update, you may want to refresh your pacman-keyring before running the actual update.

1. Create a list of custom packages for later reference

pamac list --foreign > ~/alien-pkgs.txt

2. Remove all foreign packages

pamac remove $(pamac list --foreign --quiet)

3. Remove all orphans and other unneeded packages

pamac remove --orphans --unneeded

4. Optional: ensure the keyrings are up-to-date

sudo pacman -Syy manjaro-keyring archlinux-keyring

5. Optional: Run a simulated update

pamac update --dry-run

6. Looking good? Repeat the above without --dry-run

reboot

7. Consult the list of packages created in the first step and rebuild only those you really need

Important Note: Users of Plasma and GNOME may lose their X11 session support. Checkout our guides below before restarting your systems!

Important Note: Users of Pascal, Maxwell, or older cards will fail to load the NVIDIA driver when they were using 580xx series earlier, because the 590xx doesn’t support the older hardware anymore. Only Turing series and newer are still supported.

[caho]

thanks for your answer @linux-aarhus,

but in your link you could restore the grub. This works fine for me.
in your second description is written how to do with an very old system.

my system was completley up to date. There are no orphaned packeges. The latest update was today in the morning with a thunderbird update. I have installed the kernel 6.18.4 and I think after the update it is 6.18.8.

So is it possible with a running ISO to do a “timeshift restore” in my broken system?

[Aragorn]

@caho

So is it possible with a running ISO to do a “timeshift restore” in my broken system?

Yes, by chroot’ing into your installed system from the USB. However, you will then need to update your system again, and then you will probably run into the same problem, given that you don’t know what caused it in the first place.

Anyway, the instructions on how to chroot are in the HowTo below.

• [HowTo] Recovering from an interrupted update/upgrade

[linux-aarhus]

@caho

but in your link you could restore the grub. This works fine for me.

The guide describes how to reach a chroot environment - which you will need no matter the kind of rescue or recovery you are facing.

[caho]

I could not rescue my system. So I did a new installation.

Thank you for your support @linux-aarhus and @Aragorn

regards
caho